Review and cleanup of N&N content. (#57)
Cleanup and fix validation errors
diff --git a/4.25/images/all-references-popup.png b/4.25/images/all-references-popup.png
index c5ec577..f1f062c 100644
--- a/4.25/images/all-references-popup.png
+++ b/4.25/images/all-references-popup.png
Binary files differ
diff --git a/4.25/images/ansi_sample.jpg b/4.25/images/ansi_sample.jpg
deleted file mode 100644
index f715830..0000000
--- a/4.25/images/ansi_sample.jpg
+++ /dev/null
Binary files differ
diff --git a/4.25/images/system_encoding.png b/4.25/images/system_encoding.png
index f12039f..5f282c5 100644
--- a/4.25/images/system_encoding.png
+++ b/4.25/images/system_encoding.png
Binary files differ
diff --git a/4.25/index.html b/4.25/index.html
index afb4da9..3331695 100644
--- a/4.25/index.html
+++ b/4.25/index.html
@@ -19,11 +19,9 @@
The Eclipse installer and other packages can be downloaded from the <a href="https://www.eclipse.org/downloads/packages/installer">Eclipse Installer</a> page.
</p>
- <!--
<p>
The 4.25 release notes for the Eclipse SDK project can be found <a href="https://www.eclipse.org/eclipse/development/readme_eclipse_4.25.php">here</a>.
</p>
- -->
<p>Here are some of the more noteworthy items available in this release.</p>
diff --git a/4.25/jdt.html b/4.25/jdt.html
index a4e3d0a..15c2d8e 100644
--- a/4.25/jdt.html
+++ b/4.25/jdt.html
@@ -26,10 +26,10 @@
<!--<li><a href="#JavaXX">Java™ XX Support</a></li>-->
<li><a href="#JUnit">JUnit</a></li>
<li><a href="#JavaEditor">Java Editor</a></li>
- <li><a href="#JavaViewsAndDialogs">Java Views and Dialogs</a></li>
- <li><a href="#JavaFormatter">Java Formatter</a></li>
+ <!--<li><a href="#JavaViewsAndDialogs">Java Views and Dialogs</a></li>-->
+ <!--<li><a href="#JavaFormatter">Java Formatter</a></li>-->
<li><a href="#Debug">Debug</a></li>
- <li><a href="#JDTDev">JDT Developers</a></li>
+ <!--<li><a href="#JDTDev">JDT Developers</a></li>-->
</ul>
<!-- ****************** START OF N&N TABLE ****************** -->
@@ -58,11 +58,12 @@
</tr>
<tr id="junit5-test-suite-wizard-support"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/168 -->
- <td class="title"><a href="#junit5-test-suite-wizard-support">test suite wizard JUnit 5 support</a></td>
+ <td class="title"><a href="#junit5-test-suite-wizard-support">Test Suite wizard supports JUnit 5</a></td>
<td class="content">
- The <b>New JUnit Test Suite Wizard</b> has been enhanced to now allow the creation of a JUnit 5 test suite using the <b>@Suite</b> annotation. To open the <b>New JUnit Test Suite Wizard</b> for the current package, go to <b>New > Other > Java > JUnit > JUnit Test Suite</b>.
+ The <b>New JUnit Test Suite Wizard</b> has been enhanced to now allow the creation of a JUnit 5 test suite using the <b>@Suite</b> annotation.
+ To open the <b>New JUnit Test Suite Wizard</b> for the current package, go to <b>New > Other > Java > JUnit > JUnit Test Suite</b>.
- <p
+ <p>
The following shows what the wizard now looks like:
</p>
<p><img src="images/test-suite-wizard-junit5.png" alt="Test Suite Wizard"/></p>
@@ -85,7 +86,8 @@
<tr id="while-to-enhanced-for"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/55 -->
<td class="title"><a href="#while-to-enhanced-for">Convert while loops to enhanced for loops</a></td>
<td class="content">
- The clean-up to convert to use enhanced for loops where possible has been enhanced to convert eligible while statements that use an iterator into enhanced for loops. The current clean-up already support converting for loops using an iterator into an enhanced for loop.
+ The clean-up to convert to enhanced 'for' loops where possible has been enhanced to convert eligible while statements that use an iterator into enhanced for loops.
+ The current clean-up already supports converting 'for' loops using an iterator into an enhanced 'for' loop.
<p>
To apply the cleanup, select the Java 5 <b>Convert to enhanced 'for' loops</b> checkbox on the <b>Java Feature</b> tab in your cleanup profile.
</p>
@@ -105,7 +107,8 @@
<tr id="convert-to-switch-expression"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/106 -->
<td class="title"><a href="#convert-to-switch-expression">Convert to switch expression</a></td>
<td class="content">
- The clean-up to convert to use a switch expression where possible has been enhanced to recognize switch statements that have every case either end in a return statement or a throw of an exception. In such a case the switch statement is converted into a return of a switch expression.
+ The clean-up to convert to a switch expression where possible has been enhanced to recognize switch statements that have every case either end in a return statement or a throw of an exception.
+ In such a case the switch statement is converted into a return of a switch expression.
<p>
To apply the cleanup, select the Java 14 <b>Convert to switch expression where possible</b> checkbox on the <b>Java Feature</b> tab in your cleanup profile.
</p>
@@ -114,7 +117,7 @@
</p>
<p><img src="images/convert-to-switch-expression-before.png" alt="Before"/></p>
<p>
- Is changed to:
+ is changed to:
</p>
<p><img src="images/convert-to-switch-expression-after.png" alt="After"/></p>
</td>
@@ -122,30 +125,6 @@
<!-- ******************* End of Java Editor ************************************* -->
- <!-- ******************* Java Views and Dialogs ************************************* -->
- <tr>
- <td id="JavaViewsAndDialogs" class="section" colspan="2">
- <h2>Java Views and Dialogs</h2>
- </td>
- </tr>
- <!-- ******************* End of Java Views and Dialogs ************************************* -->
-
- <!-- ******************* Java Compiler ************************************* -->
- <tr>
- <td id="JavaCompiler" class="section" colspan="2">
- <h2>Java Compiler</h2>
- </td>
- </tr>
- <!-- ******************* End of Java Compiler ************************************* -->
-
- <!-- ******************* Java Formatter ************************************* -->
- <tr>
- <td id="JavaFormatter" class="section" colspan="2">
- <h2>Java Formatter </h2>
- </td>
- </tr>
- <!-- ******************* End of Java Formatter ************************************* -->
-
<!-- *********************** Debug ******************************** -->
<tr>
<td id="Debug" class="section" colspan="2">
@@ -154,24 +133,16 @@
</tr>
<tr id="doubleclick-in-debug-popups"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/85 -->
- <td class="title"><a href="#doubleclick-in-debug-popups">Double clicking in the "AllReferences and "AllInstances" popup navigates to the type</a></td>
+ <td class="title"><a href="#doubleclick-in-debug-popups">Double click in "All References and "All Instances" pop-up to navigate to Type</a></td>
<td class="content">
- <p>
- Previously, the "All References" and "All Instances" popup wasn't acted on clicking on any of the shown items, this is improved, so if the selected variable or field type's source code is available, the editor tries to open it, and navigate to the declaration.
- </p>
+ Previously, clicking on any of the shown items in the "All References" and "All Instances" popup wasn't acted upon.
+ This is now improved - if the selected variable or field type's source code is available, the editor tries to open it, and navigate to the declaration.
<p><img src="images/all-references-popup.png" alt="Popup"/></p>
</td>
</tr>
<!--************************ End of Debug ******************************** -->
- <!-- *********************** JDT Developers ******************************** -->
- <tr>
- <td id="JDTDev" class="section" colspan="2">
- <h2>JDT Developers</h2>
- </td>
- </tr>
- <!-- *********************** End of JDT Developers ******************************** -->
<tr><td colspan="2"/></tr>
</tbody>
</table>
diff --git a/4.25/pde.html b/4.25/pde.html
index 02633c6..dcf8117 100644
--- a/4.25/pde.html
+++ b/4.25/pde.html
@@ -23,10 +23,10 @@
<body>
<h2>Plug-in Development Environment</h2>
<ul>
- <li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
+ <!--<li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
<li><a href="#editors">Editors</a></li>
<li><a href="#APITools">API Tools</a></li>
- <li><a href="#pde-compiler">PDE Compiler</a></li>
+ <li><a href="#pde-compiler">PDE Compiler</a></li> -->
<li><a href="#GeneralUpdates">General Updates</a></li>
</ul>
@@ -37,29 +37,6 @@
<col />
</colgroup>
<tbody>
- <!-- ******************** Dialogs, Wizard and Views ********************** -->
- <tr>
- <td id="dialogs-wizards-views" class="section" colspan="2"><h2>Dialogs, Wizards and Views</h2></td>
- </tr>
- <!-- ******************** End ofDialogs, Wizard and Views ********************** -->
-
- <!-- ******************** Editors ********************** -->
- <tr>
- <td id="editors" class="section" colspan="2"><h2>Editors</h2></td>
- </tr>
- <!-- ******************** End of Editors ********************** -->
-
- <!-- ******************** APITools ********************** -->
- <tr>
- <td id="APITools" class="section" colspan="2"><h2>API Tools</h2></td>
- </tr>
- <!-- ******************** End of APITools ********************** -->
-
- <!-- ******************** PDE Compiler ********************** -->
- <tr>
- <td id="pde-compiler" class="section" colspan="2"><h2>PDE Compiler</h2></td>
- </tr>
- <!-- ******************** End of PDE Compiler ********************** -->
<!-- ******************* General Updates ************************************* -->
<tr>
<td id="GeneralUpdates" class="section" colspan="2"><h2>General Updates </h2> </td>
@@ -78,11 +55,11 @@
<tr id="default-osgi-annotations">
<td class="title"><a href="#default-osgi-annotations">Support for the OSGi Bundle and Versioning Annotations</a></td>
<td class="content">
- <p>PDE now supports the <a href="https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.bundle">OSGi Bundle</a> and
+ PDE now supports the <a href="https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.bundle">OSGi Bundle</a> and
<a href="https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.versioning">OSGi Versioning</a> annotations to be used in a Plugin Project.
- </p>
<p>
- To <b>enable</b> the annotations one only needs to add them to the target platform e.g. with the following locations:
+ To enable the annotations you only need to add them to the target platform e.g. with the following locations:
+ </p>
<pre>
<target name="annotations">
<locations>
@@ -110,9 +87,9 @@
</target>
</pre>
but of course any other source is accepted (e.g. directory locations or update-sites).
- </p>
<p>
- You can now <b>use</b> them for example the following way on a package-info.java:
+ For example, you can now <b>use</b> them in the following way on a package-info.java:
+ </p>
<pre>
@org.osgi.annotation.bundle.Export
@org.osgi.annotation.versioning.Version("1.0")
@@ -128,18 +105,21 @@
}
</pre>
and then they can be processed by other tools (e.g. bnd or tycho).
- </p>
+ PDE now also supports the <code>@Export</code> and <code>@Version</code> annotations, if you put them on a <code>package-info.java</code> file like this:
<p>
- <b>PDE</b> has now also support for the <code>@Export</code> and <code>@Version</code> annotations, if you put them on a <code>package-info.java</code> file like this:
- <img src="images/bunde-export-version-header.png" />
+ <img src="images/bunde-export-version-header.png" alt=""/>
+ </p>
the <code>MANIFEST.MF</code> is updated accordingly
- <img src="images/manifest-example.png" />
+ <p>
+ <img src="images/manifest-example.png" alt=""/>
</p>
<p>
The same works for <code>@Header</code> annotation, adding this like this:
- <img src="images/header-example.png" />
- this results in an extra header added to the <code>MANIFEST.MF</code>
- <img src="images/manifest-example2.png" />
+ <img src="images/header-example.png" alt=""/>
+ </p>
+ this results in an extra header being added to the <code>MANIFEST.MF</code>
+ <p>
+ <img src="images/manifest-example2.png" alt=""/>
</p>
</td>
</tr>
diff --git a/4.25/platform.html b/4.25/platform.html
index d00192d..baaf230 100644
--- a/4.25/platform.html
+++ b/4.25/platform.html
@@ -28,7 +28,6 @@
<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 ****************** -->
@@ -66,7 +65,7 @@
<tr id="enable-word-wrap-on-open"> <!-- https://github.com/eclipse-platform/eclipse.platform.text/issues/67 -->
<td class="title"><a href="#enable-word-wrap-on-open">Preference to enable word wrap by default</a></td>
<td class="content">
- In the preferences under <b>General → Editors → Text Editors</b> one can now specify that 'word wrap'
+ A new preference has been added in the <b>General > Editors > Text Editors</b> page to specify that 'word wrap'
should be enabled by default when opening text editors. This preference is disabled by default.
<p/>
<img src="images/enable_word_wrap_on_open.png" alt="" />
@@ -83,8 +82,8 @@
<tr id="specify-project-encoding-severity"> <!-- https://github.com/eclipse-platform/eclipse.platform.resources/issues/166-->
<td class="title"><a href="#specify-project-encoding-severity">Specify severity of missing project encoding check</a></td>
<td class="content">
- In the preferences under <b>General → Workspace</b> you can now specify the severity you want to use to
- report missing project encoding. Default is "Warning". The other available values are "Ignore", "Info" and "Error".
+ In the <b>Preferences</b> under <b>General > Workspace</b> you can now specify the severity you want to use to
+ report missing project encoding. The default value is "Warning". The other available values are "Ignore", "Info" and "Error".
<p/>
<img src="images/project-encoding.png" alt="" />
</td>
@@ -98,6 +97,31 @@
<h2>Themes and Styling </h2>
</td>
</tr>
+
+ <tr id="form-no-gradients"> <!-- https://github.com/eclipse-platform/eclipse.platform.ui/pull/121 -->
+ <td class="title"><a href="#form-no-gradients">Forms have updated default background color</a></td>
+ <td class="content">
+ The background color of UI toolkit <b>forms</b> has been updated, as blue gradients are not very common now in user interfaces.
+ This will affect all form based user interfaces which do not use styling.
+ You can see the new behavior in the Eclipse IDE when theming is turned off via the preferences.
+ <p>Old look:</p>
+ <img src="images/form-old-gradient.png" alt="" />
+ <p>New look:</p>
+ <img src="images/form-new-no-gradient.png" alt=""/>
+ </td>
+ </tr>
+
+ <tr id="CTabFolder-highlightBar"> <!-- https://github.com/eclipse-platform/eclipse.platform.swt/issues/55 -->
+ <td class="title"><a href="#CTabFolder-highlightBar">Selected tab in CTabFolder is now highlighted</a></td>
+ <td class="content">
+ The selected tab in a CTabFolder now has a highlight bar to more easily identify the the current selection.
+ <p>Example showing the workbench with theming disabled:</p>
+ <p>Old look:</p>
+ <img src="images/ctabfolder-before.png" alt="" />
+ <p>New look:</p>
+ <img src="images/ctabfolder-after.png" alt=""/>
+ </td>
+ </tr>
<!-- ******************* End of Themes and Styling ************************************* -->
<!-- *********************** Debug ******************************** -->
@@ -110,14 +134,17 @@
<tr id="debug-system-encoding"> <!-- https://github.com/eclipse-platform/eclipse.platform.debug/issues/42 -->
<td class="title"><a href="#debug-system-encoding">System encoding for Console</a></td>
<td class="content">
- <p>
- New launch configuration attribute is added to allow processes start with system encoding.
- As a result, Java processes can start without specifying explicit "-Dfile.encoding=" option, so JVM will use
- system defaults defined by user environment.
- </p>
- <img src="images/system_encoding.png" alt=""/>
+ A new launch configuration attribute is added to allow processes start with the system encoding.
+ As a result, Java processes can start without specifying explicit "-Dfile.encoding=" option and JVM will use
+ the system defaults defined by the user environment.
<p>
- API notes: if <code>DebugPlugin.ATTR_FORCE_SYSTEM_CONSOLE_ENCODING</code> attribute is set,
+ See Common tab in <b>Debug Configuration</b> dialog as shown below:
+ </p>
+ <p>
+ <img src="images/system_encoding.png" alt=""/>
+ </p>
+ <p>
+ API Notes: If <code>DebugPlugin.ATTR_FORCE_SYSTEM_CONSOLE_ENCODING</code> attribute is set,
<code>ILaunchManager.getEncoding(ILaunchConfiguration)</code>
will return the value of <code>Platform.getSystemCharset()</code> and
<code>ILaunchConfiguration.getAttribute(DebugPlugin.ATTR_CONSOLE_ENCODING, null)</code>
@@ -129,11 +156,11 @@
<tr id="debug-ansi-support"> <!-- https://github.com/eclipse-platform/eclipse.platform.debug/issues/47 -->
<td class="title"><a href="#debug-ansi-support">Support for ANSI escape codes in Console</a></td>
<td class="content">
- <p>Console interprets ANSI escape codes to produce styled output.</p>
+ The <b>Console</b> interprets ANSI escape codes to produce styled output.
- <p>Supports 16 colors / 256 colors / true-colors for foreground and background, color palettes,
+ <p>It supports 16 colors / 256 colors / true-colors for foreground and background, color palettes,
and attributes like bold, italic, underline, invert, conceal, strike, crossed-out, framed:</p>
- <p><img src="images/ansi_sample.png" width="100%" alt="Screenshot of a console with colored text"/></p>
+ <p><img src="images/ansi_sample.png" width="800" alt="Screenshot of a console with colored text"/></p>
<p>Only <code>"CSI n m"</code>
(<a href="https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_Graphic_Rendition)_parameters">SGR,
@@ -143,46 +170,14 @@
Non-SGR sequences are not interpreted, but are recognized and hidden, so you will not see them.</p>
<p>This functionality is available for all the text output to the standard output or standard error.
- It works for Java, C/C++, Perl, Python, shell, Groovy, Maven, any Eclipse supported language.</p>
+ It works for Java, C/C++, Perl, Python, shell, Groovy, Maven or any Eclipse supported language.</p>
- <p>Preferences:</p>
- <p><img src="images/ansi_prefs.png" width="100%" alt="Screenshot of the ANSI support preferences dialog"/></p>
+ <p>Preferences are available under <b>Preferences > Run/Debug > Console > ANSI Support</b>.</p>
+ <p><img src="images/ansi_prefs.png" alt="Screenshot of the ANSI support preferences dialog"/></p>
</td>
</tr>
<!--************************ End of Debug ******************************** -->
-
- <!-- ******************* General Updates ************************************* -->
- <tr>
- <td id="GeneralUpdates" class="section" colspan="2">
- <h2>General Updates </h2>
- </td>
- </tr>
-
- <tr id="form-no-gradients"> <!-- https://github.com/eclipse-platform/eclipse.platform.ui/pull/121 -->
- <td class="title"><a href="#form-no-gradients">Forms default background color updated</a></td>
- <td class="content">
- The UI toolkit <b>forms</b> got an updated background, as blue gradients are not very common any more in user interfaces. This will affect all form based user interfaces which do not use styling.
- In the Eclipse IDE you will be affected if you turned theming off via the preferences.
- <p>Old:</p>
- <img src="images/form-old-gradient.png" alt="" />
- <p>New:</p>
- <img src="images/form-new-no-gradient.png" alt=""/>
- </td>
- </tr>
-
- <tr id="CTabFolder-highlightBar"> <!-- https://github.com/eclipse-platform/eclipse.platform.swt/issues/55 -->
- <td class="title"><a href="#CTabFolder-highlightBar">CTabFolder now show a highlight bar for selected tab</a></td>
- <td class="content">
- The CTabFolder now show a highlight bar to more easily identify the the currently selected tab folder:
- <p>Example showing the workbench, theming disabled:</p>
- <p>Old:</p>
- <img src="images/ctabfolder-before.png" alt="" />
- <p>New:</p>
- <img src="images/ctabfolder-after.png" alt=""/>
- </td>
- </tr>
- <!-- ******************* End of General Updates ************************************* -->
<tr><td colspan="2"/></tr>
</tbody>
</table>
diff --git a/4.25/platform_isv.html b/4.25/platform_isv.html
index d594129..2c5d069 100644
--- a/4.25/platform_isv.html
+++ b/4.25/platform_isv.html
@@ -43,7 +43,7 @@
<tr id="less-icons-in-message-dialogs"> <!-- https://github.com/eclipse-platform/eclipse.platform.ui/pull/181-->
<td class="title"><a href="#less-icons-in-message-dialogs">MessageDialog not using icons for user facing dialogs.</a></td>
<td class="content">
- The MessageDialog has been update to not use icons for user facing dialogs of type QUESTION, QUESTION_WITH_CANCEL and CONFIRM
+ The <code>org.eclipse.jface.dialogs.MessageDialog</code> has been updated to not use icons for user facing dialogs of type <code>QUESTION, QUESTION_WITH_CANCEL and CONFIRM</code>
to align with the UI guidelines regarding such dialogs for the various operating systems.
</td>
</tr>
@@ -57,22 +57,23 @@
<tr id="CTabFolder-setSelectionBarThickness"> <!-- https://github.com/eclipse-platform/eclipse.platform.swt/pull/55 -->
<td class="title"><a href="#CTabFolder-setSelectionBarThickness">Configure highlight bar thickness on CTabFolder</a></td>
<td class="content">
- The <code>CTabFolder</code> now has a new API <code>setSelectionBarThickness</code> that allows to configure how the highlight bar is rendered.
+ The <code>CTabFolder</code> now has a new API <code>setSelectionBarThickness(int thickness)</code> that allows to set the thickness of the highlight bar in the selected tab.
+
+ <p>By default a highlight bar is now drawn in the selected tab. You can switch to the old look without highlight bar by using <code>CTabFolder#setSelectionBarThickness(0)</code>.</p>
<p>Old look and feel:</p>
<img src="images/ctabfolder-before.png" alt="" />
- <p>Note:- above can be achieved using <code>CTabFolder#setSelectionBarThickness(0)</code>:</p>
<p>New look and feel:</p>
<img src="images/ctabfolder-after.png" alt=""/>
</td>
</tr>
<tr id="MessageBox-setButtonLabels"> <!-- https://github.com/eclipse-platform/eclipse.platform.swt/issues/233 -->
- <td class="title"><a href="#MessageBox-setButtonLabels">Set custom text for <code>MessageDialog</code>'s buttons</a></td>
+ <td class="title"><a href="#MessageBox-setButtonLabels">Set custom text for MessageBox's buttons</a></td>
<td class="content">
- The <code>MessageBox</code> now has a new API <code>setButtonLabels(Map<Integer, String> labels)</code> that allows to configure the text of buttons.
+ The <code>MessageBox</code> now has a new API <code>setButtonLabels(Map<Integer, String> labels)</code> that allows to configure the text on the buttons.
<p>Old behavior:</p>
<img src="images/messageBox-before.png" alt="" />
- <p>New behavior: We can now set custom button text using <code>MessageBox#setButtonLabels(Map.of(SWT.YES, "Close"))</code>:</p>
+ <p>New behavior: You can now set custom text for the buttons using <code>MessageBox#setButtonLabels(Map.of(SWT.YES, "Close"))</code>:</p>
<img src="images/messageBox-after.png" alt=""/>
</td>
</tr>
