Update the project list.
One of the project names wasn't listed correctly. Links to sources of
new and noteworthy information have been added for a few projects.
Change-Id: I52e6dcb642b4ded0f1bd8252b9c7131ace45956f
diff --git a/noteworthy/noteworthy.html b/noteworthy/noteworthy.html
index c929bfc..5055333 100644
--- a/noteworthy/noteworthy.html
+++ b/noteworthy/noteworthy.html
@@ -154,16 +154,6 @@
<div id="toc" class="toc2">
<div id="toctitle">Table of Contents</div>
<ul class="sectlevel1">
-<li><a href="#platform">Platform</a>
-<ul class="sectlevel2">
-<li><a href="#windows">Windows</a></li>
-<li><a href="#macos">MacOS</a></li>
-<li><a href="#gtk3">GTK3</a></li>
-<li><a href="#editors">Editors</a></li>
-<li><a href="#dark-theme">Dark Theme</a></li>
-<li><a href="#other">Other</a></li>
-</ul>
-</li>
<li><a href="#jdt">Java™ development tools</a>
<ul class="sectlevel2">
<li><a href="#java-10-support">Java™ 10 Support</a></li>
@@ -186,544 +176,23 @@
<li><a href="#debugger">Debugger</a></li>
</ul>
</li>
+<li><a href="#platform">Platform</a>
+<ul class="sectlevel2">
+<li><a href="#windows">Windows</a></li>
+<li><a href="#macos">MacOS</a></li>
+<li><a href="#gtk3">GTK3</a></li>
+<li><a href="#editors">Editors</a></li>
+<li><a href="#dark-theme">Dark Theme</a></li>
+<li><a href="#other">Other</a></li>
+</ul>
+</li>
<li><a href="#open-source-projects">Open Source Projects</a></li>
-<li><a href="#sources">Sources</a></li>
<li><a href="#notices">Notices</a></li>
</ul>
</div>
</div>
<div id="content">
<div class="sect1">
-<h2 id="platform"><a class="anchor" href="#platform"></a>Platform</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="windows"><a class="anchor" href="#windows"></a>Windows</h3>
-<div class="sect3">
-<h4 id="improved-tree-and-table-widget-scaling-at-high-dpi-on-windows"><a class="anchor" href="#improved-tree-and-table-widget-scaling-at-high-dpi-on-windows"></a>Improved Tree and Table widget scaling at high DPI on Windows</h4>
-<div class="paragraph">
-<p>Trees and Tables scale Checkboxes and expand/collapse buttons properly.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/tree-table-scaling.png" alt="Tree widget image before and after">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="dropped-support-for-windows-xp"><a class="anchor" href="#dropped-support-for-windows-xp"></a>Dropped support for Windows XP</h4>
-<div class="paragraph">
-<p>Eclipse/SWT has dropped support for the Windows XP Operating System and other Windows versions older than Windows Vista. Microsoft support for Windows XP, including security updates, ended in April 2014 and Windows XP has not been listed as a target environment for the Eclipse Platform for several years.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="macos"><a class="anchor" href="#macos"></a>MacOS</h3>
-<div class="sect3">
-<h4 id="improved-readability-of-default-text-font-on-macos"><a class="anchor" href="#improved-readability-of-default-text-font-on-macos"></a>Improved readability of default text font on macOS</h4>
-<div class="paragraph">
-<p>Reading the source code is the task developers perform the most during coding. So text editors must assist the user as good as possible with that.</p>
-</div>
-<div class="paragraph">
-<p>On macOS Eclipse Photon now uses the "Menlo" font as the default text font, which does also contain bold font faces. This increases readability in source code editors using bold font faces:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/Menlo.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="dark-buttons-on-mac"><a class="anchor" href="#dark-buttons-on-mac"></a>Dark buttons on Mac</h4>
-<div class="paragraph">
-<p>The background color of a button can now be styled on the Mac. This is used to style the buttons in the dark theme.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/dark-mac-buttons.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="animated-waiting-cursor-on-macos"><a class="anchor" href="#animated-waiting-cursor-on-macos"></a>Animated waiting cursor on macOS</h4>
-<div class="paragraph">
-<p>During long taking UI actions the cursor switches to a waiting cursor. On macOS this used to be a static black/white circle. From Eclipse Photon the macOS system’s busy cursor is changed to a spinning blue ball (also called beach ball).</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/macos-wait-cursor.png" alt="image">
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="gtk3"><a class="anchor" href="#gtk3"></a>GTK3</h3>
-<div class="sect3">
-<h4 id="improved-caret-performance-on-gtk3"><a class="anchor" href="#improved-caret-performance-on-gtk3"></a>Improved caret performance on GTK3</h4>
-<div class="paragraph">
-<p>Caret performance on the SWT GTK3 port has been enhanced to allow for smoother drawing. Previously the caret stuttered when moved or when other controls in the same shell were manipulated. Now the caret moves smoothly and blinks at a consistent rate.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="accessibility-support-on-gtk3"><a class="anchor" href="#accessibility-support-on-gtk3"></a>Accessibility support on GTK3</h4>
-<div class="paragraph">
-<p>Significant improvements have been made in the <strong>Accessibility</strong> support on the SWT Linux/GTK3 port. Users are able to use assistive technologies seamlessly with SWT GTK3, just as they were able to with GTK2, and without any hangs or crashes.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gtk_theme-override-support-for-swt-gtk3"><a class="anchor" href="#gtk_theme-override-support-for-swt-gtk3"></a>GTK_THEME override support for SWT-GTK3</h4>
-<div class="paragraph">
-<p>Eclipse SWT on GTK3.14+ now supports the use of GTK_THEME as an environment variable. SWT applications are correctly styled when using the GTK_THEME environment variable to override the system theme, and/or specify a dark variant. Below are the before and after screenshots of ControlExample running with GTK_THEME=Adwaita:dark set.</p>
-</div>
-<div class="paragraph">
-<p>Before:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/gtk3-theme-override-support-before.png" alt="before">
-</div>
-</div>
-<div class="paragraph">
-<p>After:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/gtk3-theme-override-support-after.png" alt="after">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-memory-usage-on-swt-gtk3"><a class="anchor" href="#improved-memory-usage-on-swt-gtk3"></a>Improved memory usage on SWT-GTK3</h4>
-<div class="paragraph">
-<p>Eclipse SWT on GTK3 has reduced memory usage after resolving a memory leak in setBackground/setForeground Color machinery. The leak was approximately 50MB/hour and affected clients running SWT on GTK3.14+.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="editors"><a class="anchor" href="#editors"></a>Editors</h3>
-<div class="sect3">
-<h4 id="manage-associations-of-content-types-with-editors"><a class="anchor" href="#manage-associations-of-content-types-with-editors"></a>Manage associations of content types with editors</h4>
-<div class="paragraph">
-<p>The <em>Content Types</em> preference page was extended to allow to view, create and remove associations with editors.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/content-type-editor-association.png" alt="image">
-</div>
-</div>
-<div class="paragraph">
-<p>Using the content type to define editor association is to be preferred over using the <em>File Associations</em> preferences.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="associate-content-type-with-a-file-name-pattern"><a class="anchor" href="#associate-content-type-with-a-file-name-pattern"></a>Associate content type with a file name pattern</h4>
-<div class="paragraph">
-<p>From the <strong>Preferences > General > Content Types</strong> preference page, you can now associate a content type with a file name pattern and use <code>?</code> or <code>*</code> wildcards at any place in that pattern (respectively to match any character or any string).</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/wildcard-content-type-association.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="browser-editor-can-toggle-auto-refresh"><a class="anchor" href="#browser-editor-can-toggle-auto-refresh"></a>Browser Editor can toggle auto-refresh</h4>
-<div class="paragraph">
-<p>The Browser Editor now contains a drop down option for enabling auto-refresh for local pages. When enabled, the Browser Editor will automatically refresh if the opened file is edited and saved.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/browser-autorefresh.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="codemining-support-with-sourceviewer"><a class="anchor" href="#codemining-support-with-sourceviewer"></a>CodeMining support with SourceViewer</h4>
-<div class="paragraph">
-<p>A <strong>code mining</strong> represents a <strong>content</strong> (ex: label, icons) that should be <strong>shown along with source text</strong>, like the number of references, a way to run tests (with run/debug icons), etc. The main goal of code mining is to help developer to understand more the written/writing code</p>
-</div>
-<div class="paragraph">
-<p>A code mining is represented by <code>org.eclipse.jface.text.codemining.ICodeMining</code> which are provided by <code>org.eclipse.jface.text.codemining.ICodeMiningProvider</code> The <code>org.eclipse.jface.text.source.ISourceViewerExtension5</code> provides the capability to register <code>org.eclipse.jface.text.codemining.ICodeMiningProvider</code> and update code minings.</p>
-</div>
-<div class="paragraph">
-<p>The example <a href="http://git.eclipse.org/c/platform/eclipse.platform.text.git/tree/org.eclipse.jface.text.examples/src/org/eclipse/jface/text/examples/codemining/CodeMiningDemo.java">CodeMiningDemo</a> draws <strong>classes references / implementations</strong> code minings:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/codemining-sourceviewer-support.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="detach-view-or-editor-via-its-context-menu"><a class="anchor" href="#detach-view-or-editor-via-its-context-menu"></a>Detach view or editor via its context menu</h4>
-<div class="paragraph">
-<p>You can now detach a view or an editor via its context menu.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/detach-editor.png" alt="image">
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="dark-theme"><a class="anchor" href="#dark-theme"></a>Dark Theme</h3>
-<div class="sect3">
-<h4 id="improved-text-operation-icons-for-the-dark-theme"><a class="anchor" href="#improved-text-operation-icons-for-the-dark-theme"></a>Improved text operation icons for the dark theme</h4>
-<div class="paragraph">
-<p>The block selection, word warp and show whitespace icons have been adjusted to look good in the dark theme.</p>
-</div>
-<div class="paragraph">
-<p>Before:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/old-text-toolbar-entries.png" alt="before">
-</div>
-</div>
-<div class="paragraph">
-<p>After:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/new-text-toolbar-entries.png" alt="after">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-popup-dialogs-for-the-dark-theme"><a class="anchor" href="#improved-popup-dialogs-for-the-dark-theme"></a>Improved popup dialogs for the dark theme</h4>
-<div class="paragraph">
-<p>Popup dialogs as for example the platform’s update notification popup now uses a dark background and a light foreground color in the dark theme.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/update_dialog_dark.png" alt="Update dialog in dark theme">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-text-color-in-text-editor-for-the-dark-theme"><a class="anchor" href="#improved-text-color-in-text-editor-for-the-dark-theme"></a>Improved text color in text editor for the dark theme</h4>
-<div class="paragraph">
-<p>The text editor now uses an improved font color in the dark theme so that you can read better.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/text-editor-dark-font-new.png" alt="after">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-coloring-of-links-in-code-element-information-in-the-dark-theme"><a class="anchor" href="#improved-coloring-of-links-in-code-element-information-in-the-dark-theme"></a>Improved coloring of links in code element information in the dark theme</h4>
-<div class="paragraph">
-<p>The colors of links in code element information controls now take the color settings of the "Hyperlink text color" and the "Active hyperlink text color" from the "Colors & Fonts" preference page into account. The readability in the dark theme has been improved a lot by this.</p>
-</div>
-<div class="paragraph">
-<p>Before:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/element_info_before.png" alt="before">
-</div>
-</div>
-<div class="paragraph">
-<p>After:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/element_info_after.png" alt="after">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-the-text-editor-s-expand-and-collapse-nodes-for-the-dark-theme"><a class="anchor" href="#improved-the-text-editor-s-expand-and-collapse-nodes-for-the-dark-theme"></a>Improved the text editor’s expand and collapse nodes for the dark theme</h4>
-<div class="paragraph">
-<p>The collapse and expand nodes in the text editor’s left hand side ruler were improved for the dark theme.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/expand_old_new.png" alt="old and new version of the icons">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-the-generic-editor-s-mark-occurrences-annotation-color-for-the-dark-theme"><a class="anchor" href="#improved-the-generic-editor-s-mark-occurrences-annotation-color-for-the-dark-theme"></a>Improved the generic editor’s mark occurrences annotation color for the dark theme</h4>
-<div class="paragraph">
-<p>The occurrences annotation marker color in the generic editor’s left hand side ruler were improved for the dark theme. Image is zoomed for better visibility.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/annotations.png" alt="old and new version of occurrence annotation">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="canvas-elements-are-styled-in-the-default-dark-theme"><a class="anchor" href="#canvas-elements-are-styled-in-the-default-dark-theme"></a>Canvas elements are styled in the default dark theme</h4>
-<div class="paragraph">
-<p>The default dark theme now contains CSS for styling Canvas elements by default.</p>
-</div>
-<div class="paragraph">
-<p>Old:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/color-fonts-canvas-old.png" alt="image">
-</div>
-</div>
-<div class="paragraph">
-<p>New:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/color-fonts-canvas-new.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="consistently-use-blue-color-for-links-in-the-dark-theme"><a class="anchor" href="#consistently-use-blue-color-for-links-in-the-dark-theme"></a>Consistently use blue color for links in the dark theme</h4>
-<div class="paragraph">
-<p>Links now consistently use a light blue color in the dark theme. One example where this was very visible is PDE’s manifest editor:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/links_in_dark_theme.png" alt="PDE's mantifest editor showing before and after">
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="other"><a class="anchor" href="#other"></a>Other</h3>
-<div class="sect3">
-<h4 id="open-resource-dialog-highlights-matching-characters"><a class="anchor" href="#open-resource-dialog-highlights-matching-characters"></a>Open resource dialog highlights matching characters</h4>
-<div class="paragraph">
-<p>The matching characters from the filter are now highlighted in the Open Resource dialog.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/open-resource-highlight-matching.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="import-export-preferences-from-preference-dialog"><a class="anchor" href="#import-export-preferences-from-preference-dialog"></a>Import/export preferences from preference dialog</h4>
-<div class="paragraph">
-<p>Easily accessible buttons for opening the <strong>Import/Export</strong> preferences wizards have been added to the lower left corner of the <strong>Preferences</strong> dialog. The wizards are still accessible through the <strong>File > Import…​</strong> and <strong>File > Export…​</strong> wizards.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/preference-import-export.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="expanded-highlighting-in-open-resource-dialog"><a class="anchor" href="#expanded-highlighting-in-open-resource-dialog"></a>Expanded Highlighting in Open Resource Dialog</h4>
-<div class="paragraph">
-<p>The Open Resource dialog now shows you how the search term matches the found resources by highlighting the names based on camel-case and pattern ( * and ? ) searches.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/open-resource-highlight.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="undo-redo-toolbar-buttons"><a class="anchor" href="#undo-redo-toolbar-buttons"></a>Undo/Redo Toolbar Buttons</h4>
-<div class="paragraph">
-<p>The main toolbar can now show Undo and Redo buttons.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/undo-redo-toolbar.png" alt="image">
-</div>
-</div>
-<div class="paragraph">
-<p>The buttons are not available by default. They can be added via <strong>Window > Perspective > Customize Perspective…​</strong>:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/undo-redo-customize.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="quickaccess-matches-preference-pages-by-keyword"><a class="anchor" href="#quickaccess-matches-preference-pages-by-keyword"></a>QuickAccess matches Preference pages by keyword</h4>
-<div class="paragraph">
-<p>QuickAccess (<code>Ctrl+3</code>) now also returns Preference pages that have a keyword matching user input.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/quickAccessMatchesPrefKeywords.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="perfect-matches-appear-first-in-selection-dialogs"><a class="anchor" href="#perfect-matches-appear-first-in-selection-dialogs"></a>Perfect matches appear first in selection dialogs</h4>
-<div class="paragraph">
-<p>Within selection dialogs, including <strong>Open Type</strong> and <strong>Open Resource</strong>, perfect matches appear as the first result, ensuring that users no longer have to scroll through historical matches and the alphabetically sorted list to find their desired result.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/perfect-match-first-search.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="delete-nested-projects"><a class="anchor" href="#delete-nested-projects"></a>Delete nested projects</h4>
-<div class="paragraph">
-<p>The <strong>Delete Resources</strong> dialog now shows a <strong>Delete nested projects</strong> option to delete all projects whose location on file system is a descendant of one of the selected projects.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/delete-nested-projects.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="debug-perspective-layout-changed"><a class="anchor" href="#debug-perspective-layout-changed"></a>Debug perspective layout changed</h4>
-<div class="paragraph">
-<p>Default Debug perspective layout changed, see screenshot below. The aim is to give the editor area more space and to show more relevant information without scrolling. Display view, Expressions view and Project Explorer are now shown by default, Problems view replaces Tasks.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/debug_perspective_changes.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="workers-use-job-names-as-thread-names"><a class="anchor" href="#workers-use-job-names-as-thread-names"></a>Workers use job names as thread names</h4>
-<div class="paragraph">
-<p>The jobs framework now uses <code>Job</code> names for <code>Worker</code> thread names. Previously all running <code>Worker’s got enumerated thread names, without any hint what the current `Worker</code> is actually doing:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/worker_obfuscated.png" alt="Worker names before M5">
-</div>
-</div>
-<div class="paragraph">
-<p>Now the <code>Job</code> name is added next to the <code>Worker</code> name:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/worker_deobfuscated.png" alt="Worker names after M5">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="right-click-option-to-export-launch-configurations"><a class="anchor" href="#right-click-option-to-export-launch-configurations"></a>Right click option to export Launch Configurations</h4>
-<div class="paragraph">
-<p>The Export Launch Configurations Wizard is now accessible through the right click menu on Launch Configurations. This wizard is still available with <strong>File > Export > Run/Debug > Launch Configurations</strong></p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/right-click-export-launch-config.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="flat-layout-in-tabbed-properties-view"><a class="anchor" href="#flat-layout-in-tabbed-properties-view"></a>Flat layout in tabbed properties view</h4>
-<div class="paragraph">
-<p>In the light theme the tabbed properties view now completely uses the same flat styling as the form-based editors do.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/prop_light.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="open-close-projects-by-working-set-in-project-explorer"><a class="anchor" href="#open-close-projects-by-working-set-in-project-explorer"></a>Open/Close Projects by Working Set in Project Explorer</h4>
-<div class="paragraph">
-<p>The ability to Open, Close, Close Unrelated, and Build all appropriate projects in a Working Set has been added to the right click menu of Working Sets in the Project Explorer.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/open_close_workingsets.png" alt="image">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="modify-project-natures"><a class="anchor" href="#modify-project-natures"></a>Modify project natures</h4>
-<div class="paragraph">
-<p>The Project Properties dialog now features a page to add or remove natures on a project.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/editNatures.png" alt="image">
-</div>
-</div>
-<div class="paragraph">
-<p>As mentioned on the page, some natures may not properly handle manual addition/removal, so using this can lead to some inconsistencies in those cases.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="possibility-to-configure-the-color-of-text-editor-s-range-indicator"><a class="anchor" href="#possibility-to-configure-the-color-of-text-editor-s-range-indicator"></a>Possibility to configure the color of text editor’s range indicator</h4>
-<div class="paragraph">
-<p>The text editor’s range indicators’s color can now be configured via the <strong>Colors and Fonts</strong> preference page.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/range_ind_pref.png" alt="Range indicator in the Colors and Fonts preference page">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="styling-for-text-editor-s-range-indicator"><a class="anchor" href="#styling-for-text-editor-s-range-indicator"></a>Styling for text editor’s range indicator</h4>
-<div class="paragraph">
-<p>The Eclipse default dark theme now includes styling for the text editor’s range indicator.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/range_ind_dark.png" alt="Range indicator in the dark theme">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="allow-workspace-to-build-projects-in-parallel"><a class="anchor" href="#allow-workspace-to-build-projects-in-parallel"></a>Allow workspace to build projects in parallel</h4>
-<div class="paragraph">
-<p>The <strong>Workspace</strong> preference page now has a new option to allow the workspace to build projects in parallel:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/preferences-simultaneous-builds.png" alt="preference page screenshot">
-</div>
-</div>
-<div class="paragraph">
-<p>Under some safe circumstances, the workspace can now choose to build independent projects in parallel. In such case, the maximum amount of jobs/threads that will be running builds in parallel will be controlled by this preference. A value of <code>1</code> will indicate that build won’t be parallelized keeping the legacy behavior.</p>
-</div>
-<div class="paragraph">
-<p>The optimal value will depend on the machine and workspace projects specificities. Recommendation is to try relatively low values (such as <code>4</code>) first which will allow to save time, when allowed by projects, while not risking the CPU overload.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="refresh-on-access-on-by-default"><a class="anchor" href="#refresh-on-access-on-by-default"></a>Refresh on access on by default</h4>
-<div class="paragraph">
-<p>For years the Eclipse IDE is shipping with a customization that files are automatically refreshed if the user accesses them. Other Eclipse based tools like the Spring Tools Suite were missing this customization, so now they do not have to manually instruct their IDE to see the update.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="open-resource-dialog-always-shows-the-paths"><a class="anchor" href="#open-resource-dialog-always-shows-the-paths"></a>Open resource dialog always shows the paths</h4>
-<div class="paragraph">
-<p>You can now use the Open Resource dialog to see the file paths. Previously it only showed the paths if there were duplicate entries.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images//open-resource-dialog.png" alt="after">
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="improved-the-generic-editor-s-mark-occurrences-annotation-label"><a class="anchor" href="#improved-the-generic-editor-s-mark-occurrences-annotation-label"></a>Improved the generic editor’s mark occurrences annotation label</h4>
-<div class="paragraph">
-<p>The occurrences annotation marker label has been improved to show the word occurring rather than the line. In the image below, see the difference between old label at the top and the new one at the bottom.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="./images/annotationlabel.png" alt="old and new version of occurrence annotation">
-</div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
<h2 id="jdt"><a class="anchor" href="#jdt"></a>Java™ development tools</h2>
<div class="sectionbody">
<div class="sect2">
@@ -2139,6 +1608,536 @@
</div>
</div>
<div class="sect1">
+<h2 id="platform"><a class="anchor" href="#platform"></a>Platform</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="windows"><a class="anchor" href="#windows"></a>Windows</h3>
+<div class="sect3">
+<h4 id="improved-tree-and-table-widget-scaling-at-high-dpi-on-windows"><a class="anchor" href="#improved-tree-and-table-widget-scaling-at-high-dpi-on-windows"></a>Improved Tree and Table widget scaling at high DPI on Windows</h4>
+<div class="paragraph">
+<p>Trees and Tables scale Checkboxes and expand/collapse buttons properly.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/tree-table-scaling.png" alt="Tree widget image before and after">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="dropped-support-for-windows-xp"><a class="anchor" href="#dropped-support-for-windows-xp"></a>Dropped support for Windows XP</h4>
+<div class="paragraph">
+<p>Eclipse/SWT has dropped support for the Windows XP Operating System and other Windows versions older than Windows Vista. Microsoft support for Windows XP, including security updates, ended in April 2014 and Windows XP has not been listed as a target environment for the Eclipse Platform for several years.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="macos"><a class="anchor" href="#macos"></a>MacOS</h3>
+<div class="sect3">
+<h4 id="improved-readability-of-default-text-font-on-macos"><a class="anchor" href="#improved-readability-of-default-text-font-on-macos"></a>Improved readability of default text font on macOS</h4>
+<div class="paragraph">
+<p>Reading the source code is the task developers perform the most during coding. So text editors must assist the user as good as possible with that.</p>
+</div>
+<div class="paragraph">
+<p>On macOS Eclipse Photon now uses the "Menlo" font as the default text font, which does also contain bold font faces. This increases readability in source code editors using bold font faces:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/Menlo.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="dark-buttons-on-mac"><a class="anchor" href="#dark-buttons-on-mac"></a>Dark buttons on Mac</h4>
+<div class="paragraph">
+<p>The background color of a button can now be styled on the Mac. This is used to style the buttons in the dark theme.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/dark-mac-buttons.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="animated-waiting-cursor-on-macos"><a class="anchor" href="#animated-waiting-cursor-on-macos"></a>Animated waiting cursor on macOS</h4>
+<div class="paragraph">
+<p>During long taking UI actions the cursor switches to a waiting cursor. On macOS this used to be a static black/white circle. From Eclipse Photon the macOS system’s busy cursor is changed to a spinning blue ball (also called beach ball).</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/macos-wait-cursor.png" alt="image">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gtk3"><a class="anchor" href="#gtk3"></a>GTK3</h3>
+<div class="sect3">
+<h4 id="improved-caret-performance-on-gtk3"><a class="anchor" href="#improved-caret-performance-on-gtk3"></a>Improved caret performance on GTK3</h4>
+<div class="paragraph">
+<p>Caret performance on the SWT GTK3 port has been enhanced to allow for smoother drawing. Previously the caret stuttered when moved or when other controls in the same shell were manipulated. Now the caret moves smoothly and blinks at a consistent rate.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="accessibility-support-on-gtk3"><a class="anchor" href="#accessibility-support-on-gtk3"></a>Accessibility support on GTK3</h4>
+<div class="paragraph">
+<p>Significant improvements have been made in the <strong>Accessibility</strong> support on the SWT Linux/GTK3 port. Users are able to use assistive technologies seamlessly with SWT GTK3, just as they were able to with GTK2, and without any hangs or crashes.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="gtk_theme-override-support-for-swt-gtk3"><a class="anchor" href="#gtk_theme-override-support-for-swt-gtk3"></a>GTK_THEME override support for SWT-GTK3</h4>
+<div class="paragraph">
+<p>Eclipse SWT on GTK3.14+ now supports the use of GTK_THEME as an environment variable. SWT applications are correctly styled when using the GTK_THEME environment variable to override the system theme, and/or specify a dark variant. Below are the before and after screenshots of ControlExample running with GTK_THEME=Adwaita:dark set.</p>
+</div>
+<div class="paragraph">
+<p>Before:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/gtk3-theme-override-support-before.png" alt="before">
+</div>
+</div>
+<div class="paragraph">
+<p>After:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/gtk3-theme-override-support-after.png" alt="after">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-memory-usage-on-swt-gtk3"><a class="anchor" href="#improved-memory-usage-on-swt-gtk3"></a>Improved memory usage on SWT-GTK3</h4>
+<div class="paragraph">
+<p>Eclipse SWT on GTK3 has reduced memory usage after resolving a memory leak in setBackground/setForeground Color machinery. The leak was approximately 50MB/hour and affected clients running SWT on GTK3.14+.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="editors"><a class="anchor" href="#editors"></a>Editors</h3>
+<div class="sect3">
+<h4 id="manage-associations-of-content-types-with-editors"><a class="anchor" href="#manage-associations-of-content-types-with-editors"></a>Manage associations of content types with editors</h4>
+<div class="paragraph">
+<p>The <em>Content Types</em> preference page was extended to allow to view, create and remove associations with editors.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/content-type-editor-association.png" alt="image">
+</div>
+</div>
+<div class="paragraph">
+<p>Using the content type to define editor association is to be preferred over using the <em>File Associations</em> preferences.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="associate-content-type-with-a-file-name-pattern"><a class="anchor" href="#associate-content-type-with-a-file-name-pattern"></a>Associate content type with a file name pattern</h4>
+<div class="paragraph">
+<p>From the <strong>Preferences > General > Content Types</strong> preference page, you can now associate a content type with a file name pattern and use <code>?</code> or <code>*</code> wildcards at any place in that pattern (respectively to match any character or any string).</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/wildcard-content-type-association.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="browser-editor-can-toggle-auto-refresh"><a class="anchor" href="#browser-editor-can-toggle-auto-refresh"></a>Browser Editor can toggle auto-refresh</h4>
+<div class="paragraph">
+<p>The Browser Editor now contains a drop down option for enabling auto-refresh for local pages. When enabled, the Browser Editor will automatically refresh if the opened file is edited and saved.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/browser-autorefresh.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="codemining-support-with-sourceviewer"><a class="anchor" href="#codemining-support-with-sourceviewer"></a>CodeMining support with SourceViewer</h4>
+<div class="paragraph">
+<p>A <strong>code mining</strong> represents a <strong>content</strong> (ex: label, icons) that should be <strong>shown along with source text</strong>, like the number of references, a way to run tests (with run/debug icons), etc. The main goal of code mining is to help developer to understand more the written/writing code</p>
+</div>
+<div class="paragraph">
+<p>A code mining is represented by <code>org.eclipse.jface.text.codemining.ICodeMining</code> which are provided by <code>org.eclipse.jface.text.codemining.ICodeMiningProvider</code> The <code>org.eclipse.jface.text.source.ISourceViewerExtension5</code> provides the capability to register <code>org.eclipse.jface.text.codemining.ICodeMiningProvider</code> and update code minings.</p>
+</div>
+<div class="paragraph">
+<p>The example <a href="http://git.eclipse.org/c/platform/eclipse.platform.text.git/tree/org.eclipse.jface.text.examples/src/org/eclipse/jface/text/examples/codemining/CodeMiningDemo.java">CodeMiningDemo</a> draws <strong>classes references / implementations</strong> code minings:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/codemining-sourceviewer-support.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="detach-view-or-editor-via-its-context-menu"><a class="anchor" href="#detach-view-or-editor-via-its-context-menu"></a>Detach view or editor via its context menu</h4>
+<div class="paragraph">
+<p>You can now detach a view or an editor via its context menu.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/detach-editor.png" alt="image">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="dark-theme"><a class="anchor" href="#dark-theme"></a>Dark Theme</h3>
+<div class="sect3">
+<h4 id="improved-text-operation-icons-for-the-dark-theme"><a class="anchor" href="#improved-text-operation-icons-for-the-dark-theme"></a>Improved text operation icons for the dark theme</h4>
+<div class="paragraph">
+<p>The block selection, word warp and show whitespace icons have been adjusted to look good in the dark theme.</p>
+</div>
+<div class="paragraph">
+<p>Before:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/old-text-toolbar-entries.png" alt="before">
+</div>
+</div>
+<div class="paragraph">
+<p>After:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/new-text-toolbar-entries.png" alt="after">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-popup-dialogs-for-the-dark-theme"><a class="anchor" href="#improved-popup-dialogs-for-the-dark-theme"></a>Improved popup dialogs for the dark theme</h4>
+<div class="paragraph">
+<p>Popup dialogs as for example the platform’s update notification popup now uses a dark background and a light foreground color in the dark theme.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/update_dialog_dark.png" alt="Update dialog in dark theme">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-text-color-in-text-editor-for-the-dark-theme"><a class="anchor" href="#improved-text-color-in-text-editor-for-the-dark-theme"></a>Improved text color in text editor for the dark theme</h4>
+<div class="paragraph">
+<p>The text editor now uses an improved font color in the dark theme so that you can read better.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/text-editor-dark-font-new.png" alt="after">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-coloring-of-links-in-code-element-information-in-the-dark-theme-2"><a class="anchor" href="#improved-coloring-of-links-in-code-element-information-in-the-dark-theme-2"></a>Improved coloring of links in code element information in the dark theme</h4>
+<div class="paragraph">
+<p>The colors of links in code element information controls now take the color settings of the "Hyperlink text color" and the "Active hyperlink text color" from the "Colors & Fonts" preference page into account. The readability in the dark theme has been improved a lot by this.</p>
+</div>
+<div class="paragraph">
+<p>Before:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/element_info_before.png" alt="before">
+</div>
+</div>
+<div class="paragraph">
+<p>After:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/element_info_after.png" alt="after">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-the-text-editor-s-expand-and-collapse-nodes-for-the-dark-theme"><a class="anchor" href="#improved-the-text-editor-s-expand-and-collapse-nodes-for-the-dark-theme"></a>Improved the text editor’s expand and collapse nodes for the dark theme</h4>
+<div class="paragraph">
+<p>The collapse and expand nodes in the text editor’s left hand side ruler were improved for the dark theme.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/expand_old_new.png" alt="old and new version of the icons">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-the-generic-editor-s-mark-occurrences-annotation-color-for-the-dark-theme"><a class="anchor" href="#improved-the-generic-editor-s-mark-occurrences-annotation-color-for-the-dark-theme"></a>Improved the generic editor’s mark occurrences annotation color for the dark theme</h4>
+<div class="paragraph">
+<p>The occurrences annotation marker color in the generic editor’s left hand side ruler were improved for the dark theme. Image is zoomed for better visibility.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/annotations.png" alt="old and new version of occurrence annotation">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="canvas-elements-are-styled-in-the-default-dark-theme"><a class="anchor" href="#canvas-elements-are-styled-in-the-default-dark-theme"></a>Canvas elements are styled in the default dark theme</h4>
+<div class="paragraph">
+<p>The default dark theme now contains CSS for styling Canvas elements by default.</p>
+</div>
+<div class="paragraph">
+<p>Old:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/color-fonts-canvas-old.png" alt="image">
+</div>
+</div>
+<div class="paragraph">
+<p>New:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/color-fonts-canvas-new.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="consistently-use-blue-color-for-links-in-the-dark-theme"><a class="anchor" href="#consistently-use-blue-color-for-links-in-the-dark-theme"></a>Consistently use blue color for links in the dark theme</h4>
+<div class="paragraph">
+<p>Links now consistently use a light blue color in the dark theme. One example where this was very visible is PDE’s manifest editor:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/links_in_dark_theme.png" alt="PDE's mantifest editor showing before and after">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="other"><a class="anchor" href="#other"></a>Other</h3>
+<div class="sect3">
+<h4 id="open-resource-dialog-highlights-matching-characters"><a class="anchor" href="#open-resource-dialog-highlights-matching-characters"></a>Open resource dialog highlights matching characters</h4>
+<div class="paragraph">
+<p>The matching characters from the filter are now highlighted in the Open Resource dialog.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/open-resource-highlight-matching.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="import-export-preferences-from-preference-dialog"><a class="anchor" href="#import-export-preferences-from-preference-dialog"></a>Import/export preferences from preference dialog</h4>
+<div class="paragraph">
+<p>Easily accessible buttons for opening the <strong>Import/Export</strong> preferences wizards have been added to the lower left corner of the <strong>Preferences</strong> dialog. The wizards are still accessible through the <strong>File > Import…​</strong> and <strong>File > Export…​</strong> wizards.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/preference-import-export.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="expanded-highlighting-in-open-resource-dialog"><a class="anchor" href="#expanded-highlighting-in-open-resource-dialog"></a>Expanded Highlighting in Open Resource Dialog</h4>
+<div class="paragraph">
+<p>The Open Resource dialog now shows you how the search term matches the found resources by highlighting the names based on camel-case and pattern ( * and ? ) searches.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/open-resource-highlight.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="undo-redo-toolbar-buttons"><a class="anchor" href="#undo-redo-toolbar-buttons"></a>Undo/Redo Toolbar Buttons</h4>
+<div class="paragraph">
+<p>The main toolbar can now show Undo and Redo buttons.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/undo-redo-toolbar.png" alt="image">
+</div>
+</div>
+<div class="paragraph">
+<p>The buttons are not available by default. They can be added via <strong>Window > Perspective > Customize Perspective…​</strong>:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/undo-redo-customize.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="quickaccess-matches-preference-pages-by-keyword"><a class="anchor" href="#quickaccess-matches-preference-pages-by-keyword"></a>QuickAccess matches Preference pages by keyword</h4>
+<div class="paragraph">
+<p>QuickAccess (<code>Ctrl+3</code>) now also returns Preference pages that have a keyword matching user input.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/quickAccessMatchesPrefKeywords.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="perfect-matches-appear-first-in-selection-dialogs"><a class="anchor" href="#perfect-matches-appear-first-in-selection-dialogs"></a>Perfect matches appear first in selection dialogs</h4>
+<div class="paragraph">
+<p>Within selection dialogs, including <strong>Open Type</strong> and <strong>Open Resource</strong>, perfect matches appear as the first result, ensuring that users no longer have to scroll through historical matches and the alphabetically sorted list to find their desired result.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/perfect-match-first-search.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="delete-nested-projects"><a class="anchor" href="#delete-nested-projects"></a>Delete nested projects</h4>
+<div class="paragraph">
+<p>The <strong>Delete Resources</strong> dialog now shows a <strong>Delete nested projects</strong> option to delete all projects whose location on file system is a descendant of one of the selected projects.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/delete-nested-projects.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="debug-perspective-layout-changed"><a class="anchor" href="#debug-perspective-layout-changed"></a>Debug perspective layout changed</h4>
+<div class="paragraph">
+<p>Default Debug perspective layout changed, see screenshot below. The aim is to give the editor area more space and to show more relevant information without scrolling. Display view, Expressions view and Project Explorer are now shown by default, Problems view replaces Tasks.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/debug_perspective_changes.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="workers-use-job-names-as-thread-names"><a class="anchor" href="#workers-use-job-names-as-thread-names"></a>Workers use job names as thread names</h4>
+<div class="paragraph">
+<p>The jobs framework now uses <code>Job</code> names for <code>Worker</code> thread names. Previously all running <code>Worker’s got enumerated thread names, without any hint what the current `Worker</code> is actually doing:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/worker_obfuscated.png" alt="Worker names before M5">
+</div>
+</div>
+<div class="paragraph">
+<p>Now the <code>Job</code> name is added next to the <code>Worker</code> name:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/worker_deobfuscated.png" alt="Worker names after M5">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="right-click-option-to-export-launch-configurations"><a class="anchor" href="#right-click-option-to-export-launch-configurations"></a>Right click option to export Launch Configurations</h4>
+<div class="paragraph">
+<p>The Export Launch Configurations Wizard is now accessible through the right click menu on Launch Configurations. This wizard is still available with <strong>File > Export > Run/Debug > Launch Configurations</strong></p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/right-click-export-launch-config.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flat-layout-in-tabbed-properties-view"><a class="anchor" href="#flat-layout-in-tabbed-properties-view"></a>Flat layout in tabbed properties view</h4>
+<div class="paragraph">
+<p>In the light theme the tabbed properties view now completely uses the same flat styling as the form-based editors do.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/prop_light.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="open-close-projects-by-working-set-in-project-explorer"><a class="anchor" href="#open-close-projects-by-working-set-in-project-explorer"></a>Open/Close Projects by Working Set in Project Explorer</h4>
+<div class="paragraph">
+<p>The ability to Open, Close, Close Unrelated, and Build all appropriate projects in a Working Set has been added to the right click menu of Working Sets in the Project Explorer.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/open_close_workingsets.png" alt="image">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="modify-project-natures"><a class="anchor" href="#modify-project-natures"></a>Modify project natures</h4>
+<div class="paragraph">
+<p>The Project Properties dialog now features a page to add or remove natures on a project.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/editNatures.png" alt="image">
+</div>
+</div>
+<div class="paragraph">
+<p>As mentioned on the page, some natures may not properly handle manual addition/removal, so using this can lead to some inconsistencies in those cases.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="possibility-to-configure-the-color-of-text-editor-s-range-indicator"><a class="anchor" href="#possibility-to-configure-the-color-of-text-editor-s-range-indicator"></a>Possibility to configure the color of text editor’s range indicator</h4>
+<div class="paragraph">
+<p>The text editor’s range indicators’s color can now be configured via the <strong>Colors and Fonts</strong> preference page.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/range_ind_pref.png" alt="Range indicator in the Colors and Fonts preference page">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="styling-for-text-editor-s-range-indicator"><a class="anchor" href="#styling-for-text-editor-s-range-indicator"></a>Styling for text editor’s range indicator</h4>
+<div class="paragraph">
+<p>The Eclipse default dark theme now includes styling for the text editor’s range indicator.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/range_ind_dark.png" alt="Range indicator in the dark theme">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="allow-workspace-to-build-projects-in-parallel"><a class="anchor" href="#allow-workspace-to-build-projects-in-parallel"></a>Allow workspace to build projects in parallel</h4>
+<div class="paragraph">
+<p>The <strong>Workspace</strong> preference page now has a new option to allow the workspace to build projects in parallel:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/preferences-simultaneous-builds.png" alt="preference page screenshot">
+</div>
+</div>
+<div class="paragraph">
+<p>Under some safe circumstances, the workspace can now choose to build independent projects in parallel. In such case, the maximum amount of jobs/threads that will be running builds in parallel will be controlled by this preference. A value of <code>1</code> will indicate that build won’t be parallelized keeping the legacy behavior.</p>
+</div>
+<div class="paragraph">
+<p>The optimal value will depend on the machine and workspace projects specificities. Recommendation is to try relatively low values (such as <code>4</code>) first which will allow to save time, when allowed by projects, while not risking the CPU overload.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="refresh-on-access-on-by-default"><a class="anchor" href="#refresh-on-access-on-by-default"></a>Refresh on access on by default</h4>
+<div class="paragraph">
+<p>For years the Eclipse IDE is shipping with a customization that files are automatically refreshed if the user accesses them. Other Eclipse based tools like the Spring Tools Suite were missing this customization, so now they do not have to manually instruct their IDE to see the update.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="open-resource-dialog-always-shows-the-paths"><a class="anchor" href="#open-resource-dialog-always-shows-the-paths"></a>Open resource dialog always shows the paths</h4>
+<div class="paragraph">
+<p>You can now use the Open Resource dialog to see the file paths. Previously it only showed the paths if there were duplicate entries.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images//open-resource-dialog.png" alt="after">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="improved-the-generic-editor-s-mark-occurrences-annotation-label"><a class="anchor" href="#improved-the-generic-editor-s-mark-occurrences-annotation-label"></a>Improved the generic editor’s mark occurrences annotation label</h4>
+<div class="paragraph">
+<p>The occurrences annotation marker label has been improved to show the word occurring rather than the line. In the image below, see the difference between old label at the top and the new one at the bottom.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/annotationlabel.png" alt="old and new version of occurrence annotation">
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="open-source-projects"><a class="anchor" href="#open-source-projects"></a>Open Source Projects</h2>
<div class="sectionbody">
<div class="paragraph">
@@ -2177,7 +2176,7 @@
<p><a href="https://projects.eclipse.org/projects/birt">Eclipse Business Intelligence and Reporting Tools</a></p>
</li>
<li>
-<p><a href="https://projects.eclipse.org/projects/tools.cdt">Eclipse C/C++ Development Tools</a></p>
+<p><a href="https://projects.eclipse.org/projects/tools.cdt">Eclipse C/C++ Development Tools</a>: <a href="https://wiki.eclipse.org/CDT/User/NewIn95">New in CDT 9.5</a></p>
</li>
<li>
<p><a href="https://projects.eclipse.org/projects/modeling.emf.cdo">Eclipse CDO</a></p>
@@ -2207,7 +2206,7 @@
<p><a href="https://projects.eclipse.org/projects/technology.eclemma">Eclipse EclEmma</a></p>
</li>
<li>
-<p><a href="https://projects.eclipse.org/projects/technology.efxclipse">Eclipse eclipse</a></p>
+<p><a href="https://projects.eclipse.org/projects/technology.efxclipse">Eclipse e(fx)clipse</a></p>
</li>
<li>
<p><a href="https://projects.eclipse.org/projects/modeling.ecoretools">Eclipse Ecore Tools</a></p>
@@ -2258,7 +2257,7 @@
<p><a href="https://projects.eclipse.org/projects/modeling.graphiti">Eclipse Graphiti</a></p>
</li>
<li>
-<p><a href="https://projects.eclipse.org/projects/eclipse.jdt">Eclipse Java development tools</a></p>
+<p><a href="https://projects.eclipse.org/projects/eclipse.jdt">Eclipse Java development tools</a>: <a href="https://eclipse.org/eclipse/news/4.8/jdt.php">New features for Java developers</a></p>
</li>
<li>
<p><a href="https://projects.eclipse.org/projects/webtools.jeetools">Eclipse Java EE Tools</a></p>
@@ -2354,10 +2353,10 @@
<p><a href="https://projects.eclipse.org/projects/tools.pdt">Eclipse PHP Development Tools</a>: <a href="https://wiki.eclipse.org/PDT/NewIn60">New in 6.0</a></p>
</li>
<li>
-<p><a href="https://projects.eclipse.org/projects/eclipse.platform">Eclipse Platform</a></p>
+<p><a href="https://projects.eclipse.org/projects/eclipse.platform">Eclipse Platform</a>: <a href="https://www.eclipse.org/eclipse/news/4.8/platform.php">New features in the Platform</a>, <a href="https://www.eclipse.org/eclipse/news/4.8/platform_isv.php">New APIs in the Platform and Equinox</a></p>
</li>
<li>
-<p><a href="https://projects.eclipse.org/projects/eclipse.pde">Eclipse Plug-in Development Environment</a></p>
+<p><a href="https://projects.eclipse.org/projects/eclipse.pde">Eclipse Plug-in Development Environment</a>: <a href="https://www.eclipse.org/eclipse/news/4.8/pde.php">New features for plug-in developers</a></p>
</li>
<li>
<p><a href="https://projects.eclipse.org/projects/modeling.pmf">Eclipse Presentation Modeling Framework</a></p>
@@ -2460,21 +2459,6 @@
</div>
</div>
<div class="sect1">
-<h2 id="sources"><a class="anchor" href="#sources"></a>Sources</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Content for this document were harvested from multiple sources, including:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="https://www.eclipse.org/eclipse/news/4.8/M7/">Eclipse Platform 4.8 New and Noteworthy</a></p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect1">
<h2 id="notices"><a class="anchor" href="#notices"></a>Notices</h2>
<div class="sectionbody">
<div class="paragraph">
diff --git a/noteworthy/source/projects.adoc b/noteworthy/source/projects.adoc
index 9bad4fd..9b6b3a7 100644
--- a/noteworthy/source/projects.adoc
+++ b/noteworthy/source/projects.adoc
@@ -22,7 +22,7 @@
* https://projects.eclipse.org/projects/modeling.mdt.bpmn2[Eclipse BPMN2]
* https://projects.eclipse.org/projects/tools.buildship[Eclipse Buildship]
* https://projects.eclipse.org/projects/birt[Eclipse Business Intelligence and Reporting Tools]
-* https://projects.eclipse.org/projects/tools.cdt[Eclipse C/C++ Development Tools]
+* https://projects.eclipse.org/projects/tools.cdt[Eclipse C/C++ Development Tools]: https://wiki.eclipse.org/CDT/User/NewIn95[New in CDT 9.5]
* https://projects.eclipse.org/projects/modeling.emf.cdo[Eclipse CDO]
* https://projects.eclipse.org/projects/technology.recommenders[Eclipse Code Recommenders]
* https://projects.eclipse.org/projects/technology.collections[Eclipse Collections]
@@ -32,7 +32,7 @@
* https://projects.eclipse.org/projects/datatools[Eclipse Data Tools Platform]
* https://projects.eclipse.org/projects/technology.dltk[Eclipse Dynamic Languages Toolkit]
* https://projects.eclipse.org/projects/technology.eclemma[Eclipse EclEmma]
-* https://projects.eclipse.org/projects/technology.efxclipse[Eclipse eclipse]
+* https://projects.eclipse.org/projects/technology.efxclipse[Eclipse e(fx)clipse]
* https://projects.eclipse.org/projects/modeling.ecoretools[Eclipse Ecore Tools]
* https://projects.eclipse.org/projects/modeling.emf.emf[Eclipse EMF]
* https://projects.eclipse.org/projects/modeling.ecp[Eclipse EMF Client]
@@ -49,7 +49,7 @@
* https://projects.eclipse.org/projects/modeling.gmf-runtime[Eclipse GMF Runtime]
* https://projects.eclipse.org/projects/tools.gef[Eclipse Graphical Editing Framework]
* https://projects.eclipse.org/projects/modeling.graphiti[Eclipse Graphiti]
-* https://projects.eclipse.org/projects/eclipse.jdt[Eclipse Java development tools]
+* https://projects.eclipse.org/projects/eclipse.jdt[Eclipse Java development tools]: https://eclipse.org/eclipse/news/4.8/jdt.php[New features for Java developers]
* https://projects.eclipse.org/projects/webtools.jeetools[Eclipse Java EE Tools]
* https://projects.eclipse.org/projects/soa.jwt[Eclipse Java Workflow Tooling]
* https://projects.eclipse.org/projects/webtools.jsdt[Eclipse JavaScript Development Tools]
@@ -81,8 +81,8 @@
* https://projects.eclipse.org/projects/modeling.mdt.papyrus[Eclipse Papyrus]
* https://projects.eclipse.org/projects/tools.ptp[Eclipse Parallel Tools Platform]
* https://projects.eclipse.org/projects/tools.pdt[Eclipse PHP Development Tools]: https://wiki.eclipse.org/PDT/NewIn60[New in 6.0]
-* https://projects.eclipse.org/projects/eclipse.platform[Eclipse Platform]
-* https://projects.eclipse.org/projects/eclipse.pde[Eclipse Plug-in Development Environment]
+* https://projects.eclipse.org/projects/eclipse.platform[Eclipse Platform]: https://www.eclipse.org/eclipse/news/4.8/platform.php[New features in the Platform], https://www.eclipse.org/eclipse/news/4.8/platform_isv.php[New APIs in the Platform and Equinox]
+* https://projects.eclipse.org/projects/eclipse.pde[Eclipse Plug-in Development Environment]: https://www.eclipse.org/eclipse/news/4.8/pde.php[New features for plug-in developers]
* https://projects.eclipse.org/projects/modeling.pmf[Eclipse Presentation Modeling Framework]
* https://projects.eclipse.org/projects/eclipse[Eclipse Project]
* https://projects.eclipse.org/projects/modeling.mmt.qvt-oml[Eclipse QVT-OML]
