-
Notifications
You must be signed in to change notification settings - Fork 72
/
platform_whatsnew.html
207 lines (193 loc) · 9.87 KB
/
platform_whatsnew.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="copyright" content=
"Copyright (c) Eclipse contributors and others 2020. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page." />
<meta http-equiv="Content-Language" content="en-us" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
<style type="text/css">
/*<![CDATA[*/
body {max-width: 900px;}
table.news col.title {width: 30%;}
/*img {max-width: 520px;}*/
table.news {table-layout: fixed; border-collapse: collapse; width: 100%;}
table.news td {border-top: solid thin black; padding: 10px; overflow: visible;}
table.news tr {vertical-align: top;}
table.news tr td.section {font-size: 20px; font-weight: bold;}
table.news tr td.title {vertical-align: top; font-weight: bold;}
table.news tr td.content {vertical-align: top;}
ul {padding-left: 13px;}
/*]]>*/
</style>
<title>Eclipse Platform What's New in 4.24</title>
</head>
<body>
<h2>What's New in Eclipse 4.24 (Platform)</h2>
<p>Here are descriptions of some of the more interesting or significant changes made to the Eclipse Platform for the
4.24 release of Eclipse. They are grouped into:</p>
<ul>
<!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
<li><a href="#ViewsAndDialogs">Views, Dialogs and Toolbar</a></li>
<li><a href="#TextEditors">Text Editors</a></li>
<li><a href="#Preferences">Preferences</a></li>
<li><a href="#Debug">Debug</a></li>
<!--li><a href="#StylingThemes">Themes and Styling</a></li-->
<!--li><a href="#GeneralUpdates">General Updates</a></li-->
</ul>
<p>Plug-in developers will also be interested in the corresponding <a href=
"../../org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html">What's new</a> document in the plug-in
developer's guide.</p>
<p>We also recommend to read the <a href="../tips/platform_tips.html">Tips and Tricks</a>.</p><br />
<!-- ****************** START OF N&N TABLE ****************** -->
<table class="news">
<colgroup>
<col class="title" />
<col />
</colgroup>
<tbody>
<!-- ******************* Views, Dialogs and Toolbar ************************************* -->
<tr>
<td id="ViewsAndDialogs" class="section" colspan="2">
<h2>Views, Dialogs and Toolbar </h2>
</td>
</tr>
<tr id="welcomescreen"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=579463 -->
<td class="title"><a href="#welcomescreen">Welcome screen doesn't change toolbar visibility anymore</a></td>
<td class="content">
The Welcome screen will not hide the toolbars anymore in its maximized state to behave similar like a regular view.
</td>
</tr>
<tr id="quickaccess-filesystem"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=576341 -->
<td class="title"><a href="#codeassist-module">Find Actions can open files from file system</a></td>
<td class="content">
The <b>Find Actions</b> command, usually accessible with <b>Ctrl+3</b>, now allows to open
a file if the query is the path of an existing file on the filesystem.
</td>
</tr>
<!-- ******************* End of Views, Dialogs and Toolbar ************************************* -->
<!-- ******************* Text Editors ************************************* -->
<tr>
<td id="TextEditors" class="section" colspan="2">
<h2>Text Editors </h2>
</td>
</tr>
<tr id="multi-select-commands"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=576377 -->
<td class="title"><a href="#multi-select-commands">Action commands for multiple carets/selections</a></td>
<td class="content">
<b>Text editors</b> now provide various commands to support multiple carets/selections that can be bound to
user-defined keyboard shortcuts for easy selection of text regions in text editors. No default
keys have been assigned yet (suggestions below), but can be assigned via <b>Window > Preferences > Keys</b>:
<dl>
<dt><b>Multi selection down relative to anchor selection</b></dt>
<dd>Search next matching region and add it to the current selection, or remove first element from current multi-selection (e.g. <b>Ctrl-Alt-J</b>).</dd>
<dt><b>Multi selection up relative to anchor selection</b></dt>
<dd>Search next matching region above and add it to the current selection, or remove last element from current multi-selection (e.g. <b>Alt-J</b>).</dd>
<dt><b>End multi-selection</b></dt>
<dd>Unselects all multi-selections returning to a single cursor (e.g. <b>Esc</b>)</dd>
<dt><b>Add all matches to multi-selection</b></dt>
<dd>Looks for all regions matching the current selection or identifier and adds them to a multi-selection (e.g. <b>Ctrl-Shift-Alt-J</b>).</dd>
<dt><b>Multi caret up</b></dt>
<dd>Add a new caret/multi selection above the current line, or remove the last caret/multi selection (e.g. <b>Ctrl-Alt-Shift-Up</b>).</dd>
<dt><b>Multi caret down</b></dt>
<dd>Add a new caret/multi selection below the current line, or remove the first caret/multi selection (e.g. <b>Ctrl-Alt-Shift-Down</b>).</dd>
</dl>
In addition to the above, the display of multiple carets on the Windows platform has been improved to provide a
more stable user experience.<br/><br/>
<img width="700" src="images/multi-selection-demo.gif" alt="multi selection demo"/>
</td>
</tr>
<!-- ******************* End of Text Editors ************************************* -->
<!-- ****************** Preferences ************************************* -->
<tr>
<td id="Preferences" class="section" colspan="2">
<h2>Preferences </h2>
</td>
</tr>
<tr id="explicit-encoding-workspaces"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=516583 -->
<td class="title"><a href="#explicit-encoding-workspaces">Explicit encoding set for new workspaces</a></td>
<td class="content">
If Eclipse is started without explicit default encoding set, <b>UTF-8</b> will be set as the default encoding
for new workspaces.
<p>
In case some encoding was specified at Eclipse startup either as a JVM
system property <code>-Dfile.encoding=XYZ</code>
or by product customization preference <code>org.eclipse.core.resources/encoding=XYZ</code>
, this custom encoding will be persisted as default encoding for new workspaces.
</p>
<p>
After that all new projects created in new workspaces will also have
explicit default encoding set (they will derive that from the workspace encoding
and not from some random encoding taken from current OS settings).
</p>
<p>
Existing workspaces or projects with encoding already set will be not
affected and will keep their original encoding.
</p>
</td>
</tr>
<tr id="explicit-encoding-projects"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=479450 -->
<td class="title"><a href="#explicit-encoding-projects">Explicit encoding set for new projects</a></td>
<td class="content">
<p>All new projects created with 4.24 release will have explicit
default project encoding set after creation,
based on the workspace default encoding.
</p>
<p>
As a result, a new project will always have
<code>.settings/org.eclipse.core.resources.prefs</code>
file generated, containing information about project default encoding.
</p>
</td>
</tr>
<tr id="no-explicit-encoding-project-warning"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=479451 -->
<td class="title"><a href="#no-explicit-encoding-project-warning">Warning for projects with no explicit default encoding</a></td>
<td class="content">
<p>A warning marker is now created for projects with no explicit default encoding. The marker has a quick-fix,
that sets the project default encoding to the workspace encoding.</p>
<p>Having explicit project encoding eases sharing projects between workspaces with different encodings.</p>
<p><img src="images/no-explicit-encoding-project-warning.png" alt="warning marker and quick-fix"/></p>
</td>
</tr>
<!-- ****************** End of Preferences ************************************* -->
<!-- ******************* Themes and Styling ************************************* -->
<!--
<tr>
<td id="StylingThemes" class="section" colspan="2">
<h2>Themes and Styling </h2>
</td>
</tr>
-->
<!-- ******************* End of Themes and Styling ************************************* -->
<!-- *********************** Debug ******************************** -->
<tr>
<td id="Debug" class="section" colspan="2">
<h2>Debug</h2>
</td>
</tr>
<tr id="debug-monitor-thread-names"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=579064 -->
<td class="title"><a href="#debug-monitor-thread-names">Debug thread names</a></td>
<td class="content">
The daemon threads for monitoring the streams of a debugged programm now have names
containing PID and launch config name of the debugged process.<br />
Like: <tt>"Output Stream Monitor for PID $PID$ $ILaunchConfiguration.name$"</tt>.<br />
There are 4 threads per process: Output Stream Monitor, Input Stream Monitor, Error Stream Monitor, Process monitor.
</td>
</tr>
<!--************************ End of Debug ******************************** -->
<!-- ******************* General Updates ************************************* -->
<!--
<tr>
<td id="GeneralUpdates" class="section" colspan="2">
<h2>General Updates </h2>
</td>
</tr>
-->
<!-- ******************* End of General Updates ************************************* -->
<tr><td colspan="2"/></tr>
</tbody>
</table>
<!-- ****************** END OF N&N TABLE ****************** -->
</body>
</html>