blob: 27fb41c8d1d2be36b84732be96f0cb3b684d78c4 [file] [log] [blame]
<!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 2018, 2022. 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="news.css" type="text/css"/>
<style type="text/css">
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 Project 4.24 - New and Noteworthy</title>
</head>
<body>
<h2>Platform and Equinox</h2>
<ul>
<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="#StylingThemes">Themes and Styling</a></li> -->
<li><a href="#Debug">Debug</a></li>
<!-- <li><a href="#GeneralUpdates">General Updates</a></li> -->
</ul>
<!-- ****************** 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 &gt; Preferences &gt; 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>&quot;Output Stream Monitor for PID $PID$ $ILaunchConfiguration.name$&quot;</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 ****************** -->
<script type="text/javascript" src="scripts.js"></script>
<p style="text-align:center">
<span style="color:#808080">Previous</span> <a style="margin:1em" href=".">Up</a> <a href="jdt.php">Next</a>
</p>
</body>
</html>