blob: 23e7af1bc5a7aa6ca50ba7e5e7782042ec563c4f [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, 2019. 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.23 - 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="#Debug">Debug</a></li>
<li><a href="#Preferences">Preferences</a></li>
<li><a href="#StylingThemes">Themes and Styling</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="manage-trusted-pgp-keys"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577193 -->
<td class="title"><a href="#manage-trusted-pgp-keys">Manage trusted PGP keys</a></td>
<td class="content">
The <b>Install/Update &gt; Trust</b> preference page supports adding or removing <b>PGP public keys</b> that are
trusted by default during the installation process. Artifacts signed with a secret key corresponding to one of
the trusted public PGP keys will install without prompting the <b>Trust</b> dialog.
</td>
</tr>
<tr id="ProgressStableSort"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=578643 -->
<td class="title"><a href="#ProgressStableSort">Stable Sort Order in Progress View</a></td>
<td class="content">
The <b>Progress</b> View will not move jobs down anymore. New jobs are always added at the bottom. That makes it easier to hit the right cancel button.
<p>Old behaviour: long running job jumps around.</p>
<img width="739" src="images/progress_old.gif" alt="wild moving"/>
<p>New behaviour: long running job stays on top.</p>
<img width="628" src="images/progress_new.gif" alt="stays on top"/>
</td>
</tr>
<!-- ******************* End of Views, Dialogs and Toolbar ************************************* -->
<!-- ******************* Debug ************************************* -->
<tr>
<td id="Debug" class="section" colspan="2">
<h2>Debug </h2>
</td>
</tr>
<tr id="inline-debug-values"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=507546 -->
<td class="title"><a href="#inline-debug-values">Debuggers can show values inline</a></td>
<td class="content">
The <b>Run/Debug</b> preference page now has a new option to allow to <b>show debug
values inline on text editors</b>. When enabled, this will print debug values as a code minings annotation on the end
of line. The values shown would then react to change in the debug context as you navigate
through the execution.
<p>
This is an experimental feature and since this requires extra effort for the debuggers to enable it, not all
debuggers may support it yet e.g. Java debugger does not support it yet.
</p>
<p>
<img width="800" src="images/debug-value-inline.png" alt=""/>
</p>
<p>
<img src="images/debug-preference-inline.png" alt="Debug Preference"/>
</p>
</td>
</tr>
<!-- ******************* End of Debug ************************************* -->
<!-- ****************** Preferences ************************************* -->
<tr>
<td id="Preferences" class="section" colspan="2">
<h2>Preferences </h2>
</td>
</tr>
<tr id="large-file-associations"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577289 -->
<td class="title"><a href="#large-file-associations">Large File Associations preferences</a></td>
<td class="content">
A new set of preferences is added, that can specify which editor is used to open large files of a specific type. This allows users
to specify editors that scale better for large project files: e.g. a text editor for large generated sources,
or an external editor for very large files that are not handled well by Eclipse editors.
<p>The preferences can be set via the respective preference page: <b>General &gt; Editors &gt; Large File Associations</b></p>
<p><img src="images/large_file_associations_preference_page.png" alt="Large File Associations preference page"/></p>
<p>The preferences can also be via product customization (<code>-productCustomization &lt;path to file&gt;</code>), e.g. contents:</p>
<pre>
# all types with a preference, needed by the preference page UI
org.eclipse.ui.workbench/largeFileLimits_types=java,xml,txt
org.eclipse.ui.workbench/largeFileLimits_disabled=cpp
# default, show prompt for all to types that don't have a preference
org.eclipse.ui.workbench/largeFileLimits_default_enabled=true
org.eclipse.ui.workbench/largeFileLimits_default_value=100000
# specific editor associations per type and file size
org.eclipse.ui.workbench/largeFileLimits.java=4096,org.eclipse.ui.DefaultTextEditor,8192,largeFileLimits_prompt
org.eclipse.ui.workbench/largeFileLimits.xml=1048576,org.eclipse.ui.DefaultTextEditor,77777,Emacs
org.eclipse.ui.workbench/largeFileLimits.txt=2048,largeFileLimits_prompt
</pre>
</td>
</tr>
<!-- ****************** End of Preferences ************************************* -->
<!-- ******************* Themes and Styling ************************************* -->
<tr>
<td id="StylingThemes" class="section" colspan="2">
<h2>Themes and Styling </h2>
</td>
</tr>
<tr id="win32-dark-buttons-css"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577042 -->
<td class="title"><a href="#win32-dark-buttons-css">Windows dark theme uses natively styled buttons</a></td>
<td class="content">
The buttons on Windows OS now use the native support in dark theme.
<p>New native look and feel:</p>
<img src="images/new-dark-buttons.png" alt=""/>
<p>Old look and feel:</p>
<img src="images/old-dark-buttons.png" alt=""/>
</td>
</tr>
<!-- ******************* End of Themes and Styling ************************************* -->
<!-- ******************* General Updates ************************************* -->
<tr>
<td id="GeneralUpdates" class="section" colspan="2">
<h2>General Updates </h2>
</td>
</tr>
<tr id="process-pid"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=574403 -->
<td class="title"><a href="#process-pid">Process ID in Debugger</a></td>
<td class="content">
Eclipse Debug framework can now show process ID (pid) of the started processes.
The pid is shown (if supported by the concrete debugger implementation) in the <b>Console</b>
view description and <b>Properties</b> page for the process.
<p><img src="images/process_properties.png" alt="Process properties page shows process ID"/></p>
<p>
This should work out of the box for all
processes using or extending <code>org.eclipse.debug.core.model.RuntimeProcess</code>, and can be
easily added to other processes by specifying <code>IProcess.ATTR_PROCESS_ID</code> process attribute.
</p>
<p>Additionally, the <b>Java debugger</b> now shows process id for the process element in the <b>Debug</b> view.</p>
<p><img src="images/show_pid.png" alt="Debugger shows process ID"/></p>
</td>
</tr>
<!-- ******************* End of General Updates ************************************* -->
</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>