Bug 541725: N&N for eclipse 4.10
Updated images and content after review
Change-Id: Ieecf09ada67ab2047f06f97602e5317d18fc7452
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/declare_local_variable_type_as_var_option_in_extract_local_variable.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/declare_local_variable_type_as_var_option_in_extract_local_variable.png
new file mode 100644
index 0000000..ea8e149
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/declare_local_variable_type_as_var_option_in_extract_local_variable.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/declare_local_variable_type_as_var_result.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/declare_local_variable_type_as_var_result.png
new file mode 100644
index 0000000..233039b
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/declare_local_variable_type_as_var_result.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/extract_local_variable_drop_down.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/extract_local_variable_drop_down.png
new file mode 100644
index 0000000..3ddd741
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/extract_local_variable_drop_down.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/extract_local_variable_var_support.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/extract_local_variable_var_support.png
deleted file mode 100644
index a0d3508..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/extract_local_variable_var_support.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j11_compliance.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j11_compliance.png
new file mode 100644
index 0000000..959ff32
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j11_compliance.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-implementors-type.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-implementors-type.png
new file mode 100644
index 0000000..681d707
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-implementors-type.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-implementations.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-implementations.png
index 11c7c6c..785fe73 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-implementations.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-implementations.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-search.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-search.png
index 08b1556..42f06d2 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-search.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-codemining-references-search.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-disable-completion-insertion-triggers.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-disable-completion-insertion-triggers.png
index 2537cd6..09e80f8 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-disable-completion-insertion-triggers.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jdt-disable-completion-insertion-triggers.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_add_var_lambda_parameter_types.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_add_var_lambda_parameter_types.png
index 627722d..a3f65b5 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_add_var_lambda_parameter_types.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_add_var_lambda_parameter_types.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_remove_lambda_parameter_types.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_remove_lambda_parameter_types.png
index d089a4b..46641d9 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_remove_lambda_parameter_types.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_remove_lambda_parameter_types.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_lambda_parameter_types_with_var.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_lambda_parameter_types_with_var.png
index ea12bfc..1123cd9 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_lambda_parameter_types_with_var.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_lambda_parameter_types_with_var.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_var_in_lambda_parameter_types_with_inferred_types.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_var_in_lambda_parameter_types_with_inferred_types.png
index 91f9ae2..f9c77b9 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_var_in_lambda_parameter_types_with_inferred_types.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickassist_replace_var_in_lambda_parameter_types_with_inferred_types.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
index 0b74bdf..987e55a 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
@@ -73,6 +73,9 @@
<img src="images/j11.png" alt=""/>
</p>
An option to set compiler compliance to 11 on a Java project is also provided.
+ <p>
+ <img src="images/j11_compliance.png" alt=""/>
+ </p>
</td>
</tr>
@@ -89,7 +92,7 @@
<tr id="add-var-lambda-parameter-types"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=535690 -->
<td class="title">Quick assist to add 'var' type to lambda parameters</td>
<td class="content">
- A new quick assist has been implemented that allows the user to add 'var' type to lambda parameters.
+ A new quick assist is provided that allows you to add <code>var</code> type to lambda parameters.
This quick assist is only available if the project compliance is Java 11 or above.
<p>
<img src="images/quickassist_add_var_lambda_parameter_types.png" alt="" />
@@ -100,7 +103,7 @@
<tr id="replace-lambda-parameter-types-with-var"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=535690 -->
<td class="title">Quick assist to replace lambda parameter types with 'var'</td>
<td class="content">
- A new quick assist has been implemented that allows the user to replace lambda parameter types with 'var'.
+ A new quick assist is provided that allows you to replace lambda parameter types with <code>var</code>.
This quick assist is only available if the project compliance is Java 11 or above.
<p>
<img src="images/quickassist_replace_lambda_parameter_types_with_var.png" alt="" />
@@ -111,7 +114,7 @@
<tr id="replace-var-lambda-parameter-types"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=535690 -->
<td class="title">Quick assist to replace 'var' in lambda parameter types with inferred types</td>
<td class="content">
- A new quick assist has been implemented that allows the user to replace 'var' in lambda parameter types with inferred types.
+ A new quick assist is provided that allows you to replace <code>var</code> with inferred lambda parameter types.
This quick assist is only available if the project compliance is Java 11 or above.
<p>
<img src="images/quickassist_replace_var_in_lambda_parameter_types_with_inferred_types.png" alt="" />
@@ -133,34 +136,46 @@
<p>
<img src="images/jdt-codemining-references-implementations.png" alt="" />
</p>
- <p>
- This feature can be enabled in <b>Preferences > Java > Editor > Code Minings</b>:
- </p>
- <p>
- <img src="images/jdt-codemining-preferences.png" alt="" />
- </p>
- <p>
- The reference count includes the implementation count.
- </p>
- <p>
- Clicking on <b>references</b> launches the search for references:
- </p>
- <p>
+ <ul>
+ <li>
+ <p>
+ This feature can be enabled in <b>Preferences > Java > Editor > Code Minings</b>:
+ </p>
+ <p>
+ <img src="images/jdt-codemining-preferences.png" alt="" />
+ </p>
+ </li>
+ <li>
+ <p>
+ The reference count includes the implementation count.
+ </p>
+ </li>
+ <li>
+ <p>
+ Clicking on <b>references</b> launches the search for references:
+ </p>
+ <p>
<img src="images/jdt-codemining-references-search.png" alt="" />
- </p>
- <p>
- Clicking on <b>implementations</b> opens the Type Hierarchy view:
- </p>
- <p>
+ </p>
+ </li>
+ <li>
+ <p>
+ Clicking on <b>implementations</b> opens the Type Hierarchy view:
+ </p>
+ <p>
<img src="images/jdt-codemining-implementors-type.png" alt="" />
- </p>
- <p>This is implemented using the <a href="https://www.eclipse.org/eclipse/news/4.8/M5/#codemining-extension-point">Code Mining extension-point</a>.</p>
+ </p>
+ </li>
+ <li>
+ <p>This is implemented using the <a href="https://www.eclipse.org/eclipse/news/4.8/M5/#codemining-extension-point">Code Mining extension-point</a>.</p>
+ </li>
+ </ul>
</td>
</tr>
<tr id="remove-lambda-parameter-types"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=535690 -->
<td class="title">Quick assist to remove lambda parameter types</td>
<td class="content">
- A new quick assist has been implemented that allows the user to remove lambda parameter types.
+ A new quick assist is provided that allows you to remove lambda parameter types.
<p>
<img src="images/quickassist_remove_lambda_parameter_types.png" alt="" />
</p>
@@ -169,13 +184,22 @@
<tr id="localVariable-var-support"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=535671 -->
<td class="title">Extract local variable to var type</td>
<td class="content">
- When extracting to a local variable, an option to declare the local variable type as 'var' has been provided.
+ When extracting to a local variable, an option to declare the local variable type as <code>var</code> has been provided.
This option is only available if the project compliance is Java 10 or above.
<p>
- When you select this option, the local variable type will be 'var' as shown below:
+ <img src="images/extract_local_variable_drop_down.png" alt="" />
</p>
<p>
- <img src="images/extract_local_variable_var_support.png" alt="" />
+ When you select the highlighted option, the local variable type will be of type <code>var</code>.
+ </p>
+ <p>
+ <img src="images/declare_local_variable_type_as_var_option_in_extract_local_variable.png" alt="" />
+ </p>
+ <p>
+ Result:
+ </p>
+ <p>
+ <img src="images/declare_local_variable_type_as_var_result.png" alt="" />
</p>
</td>
</tr>
@@ -231,20 +255,20 @@
</tr>
<tr id="Create-module-info-on-projects-below-9"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=526643 -->
- <td class="title">Convert project using Java 8 or below to modular project</td>
+ <td class="title">Convert Java 8 (or below) project to modular project</td>
<td class="content">
- You can now convert a project with compliance set to Java 8 or below to a modular project by selecting the <b>Create module-info.java</b> context menu on the project.
+ You can now convert a project with compliance set to Java 8 or below to a modular project by selecting the <b>Create module-info.java</b> action from the context menu on the project.
<p>
<img src="images/create_module_info_support_java_8_below_projects_option.png" alt="" />
</p>
- <p>When you select the above option on a project using JRE less than Java 9, the below dialog will appear if an appropriate JRE with version greater than or equal to Java 9 is present in the workspace.
- The highest available JRE is selected and the compliance setting for the project is also updated accordingly.
+ <p>When you select this action on a Java 8 (or below) project and if a JRE with version 9 or above is present in the workspace, then the following dialog appears.
</p>
<p>
<img src="images/create_module_info_support_java_8_below_projects_compliance_change.png" alt="" />
</p>
- <p>Selecting 'Yes' adds the suggested JRE to build path, removes the old JRE from build path, updates the compiler compliance accordingly and opens the <b>Create module-info.java</b> dialog.</p>
- <p>Selecting 'No' leaves the project unchanged.</p>
+ <p>
+ The highest available JRE is selected and the compliance setting for the project is also updated accordingly. After this the <b>Create module-info.java</b> dialog opens.
+ </p>
</td>
</tr>
<!-- ******************* End of Java Views and Dialogs ************************************* -->
@@ -313,7 +337,7 @@
<tr id="null-scheduling-rule"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=531554 -->
<td class="title">Make JDT builder use null as scheduling rule</td>
<td class="content">
- By configuring the <b>org.eclipse.jdt.core/useNullSchedulingRule</b> preference to true, the JDT builder will use <code>null</code>
+ By configuring the <b>org.eclipse.jdt.core/useNullSchedulingRule</b> preference to <code>true</code>, the JDT builder will use <code>null</code>
as the scheduling rule instead of the workspace root. The preference can be changed using the Preferences APIs, or by editing
the <code>plugin_customization.ini</code> file of your application.
<p> This prevents the Java builder from locking the whole workspace. The user can continue to work in parallel and other builders
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html b/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html
index 19b6ac7..1a62642 100644
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html
+++ b/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html
@@ -80,7 +80,7 @@
<tr id="target-definition-code-mining"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=534758 -->
<td class="title">Code mining in Target Definition editor</td>
<td class="content">
- You can now activate or reload a target platform by clicking-on the corresponding code-mining in the <b>Target definition editor</b>.
+ You can now activate or reload a target platform by clicking-on the corresponding code mining in the <b>Target definition editor</b>.
<p>
<img src="images/target-definition-code-mining.png" alt="" />
</p>
@@ -97,7 +97,7 @@
<td class="title">Breaking interface implementation to class reported</td>
<td class="content">
When a class implements an interface or extends an abstract class that can cause
- a breaking change in the client, it is reported as a problem by API tools.
+ a breaking change in the client, it is now reported as a problem by API tools.
<p>
<img src="images/breaking-change-by-interface-abs-class-add-to-class.png" alt="" />
</p>
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html b/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html
index 646fcfa..33a0ba9 100644
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html
@@ -48,23 +48,23 @@
<tr id="contentassistant-enable-completion-proposal-trigger-chars"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=539165 -->
<td class="title">Enable/Disable completion proposal trigger characters in ContentAssistant</td>
<td class="content">
- The <code>ContentAssistant</code> class received methods to allow consumer to configure whether the
- completion proposal trigger characters (which can be used additionally to <i>Enter</i> key to insert
+ New methods have been added to the <code>ContentAssistant</code> class to allow consumers to configure whether the
+ completion proposal trigger characters (which can be used in addition to <b>Enter</b> key to insert
the current completion proposal) are honored or ignored.
<p>
- If <code>ContentAssistant.enableCompletionProposalTriggerChars(false)</code> was used,
- then completion proposal trigger characters are ignored and user needs to press the <i>Enter</i> key to
+ If <code>ContentAssistant.enableCompletionProposalTriggerChars(false)</code> is used,
+ then completion proposal trigger characters are ignored and user needs to press the <b>Enter</b> key to
trigger insertion.<br/>
- If <code>ContentAssistant.enableCompletionProposalTriggerChars(true)</code>, then completion proposal
- trigger characters can be used as well as <i>Enter</i> to insert the proposal.<br/>
- Default behavior if the <code>enableCompletionProposalTriggerChars(boolean)</code> method was not called is equivalent
- to <code>enableCompletionProposalTriggerChars(true)</code> so extra trigger characters are honored.
+ If <code>ContentAssistant.enableCompletionProposalTriggerChars(true)</code> is used, then completion proposal
+ trigger characters can be used in addition to the <b>Enter</b> key to insert the proposal.<br/>
+ If the <code>enableCompletionProposalTriggerChars(boolean)</code> method is not called, then the default behavior is equivalent
+ to calling <code>enableCompletionProposalTriggerChars(true)</code> so that extra trigger characters are honored.
</p>
<p>
- This feature is useful if your content-assist is configured to automatically trigger quite often (such
+ This feature is useful if your content-assist is configured to automatically trigger often (such
as on every character insertion). Coupling heavy usage of auto-activation of content-assist and extra
- insertion trigger characters often results in undesired insertions, making it preferable to only keep
- Enter as insertion character (<code>ContentAssistant.enableCompletionProposalTriggerChars(false)</code>).
+ insertion trigger characters often results in undesired insertions, making it preferable to keep only
+ Enter as the insertion character (<code>ContentAssistant.enableCompletionProposalTriggerChars(false)</code>).
</p>
</td>
</tr>
@@ -76,7 +76,7 @@
</tr>
<tr id="experimental-gtk4-support"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=541173 -->
- <td class="title"><a href="#experimental-gtk4-support">Added experimental support for GTK4</a></td>
+ <td class="title">Added experimental support for GTK4</td>
<td class="content">
SWT has introduced basic, experimental support for <b>GTK4</b>. The GTK bindings can be built using the build script
(<a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/bundles/org.eclipse.swt/Eclipse%20SWT%20PI/gtk/library/build.sh">build.sh</a>) with the arguments <code>-gtk4 install</code>.
@@ -86,7 +86,7 @@
</tr>
<tr id="read-only-combo"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=508634 -->
- <td class="title"><a href="#read-only-combo">Styling of Read-only Combo on Windows</a></td>
+ <td class="title">Styling of read-only Combo on Windows</td>
<td class="content">
Setting the background and foreground color of a <code>SWT.READ_ONLY Combo</code> on Windows is now supported.
<p><img src="images/readonly_combo_windows.png" alt="Read only ComboBox on Windows"/></p>
@@ -94,9 +94,9 @@
</tr>
<tr id="styledtext-line-vertical-indent"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=539618 -->
- <td class="title"><a href="#styledtext-line-vertical-indent">API added to customize line vertical indent in StyledText</a></td>
+ <td class="title">API added to customize line vertical indent in StyledText</td>
<td class="content">
- A new API <code>StyledText.setLineVerticalIndent(int lineIndex, int verticalLineIndent)</code> has been added to customize the vertical indent of a specified line.
+ A new API <code>StyledText.setLineVerticalIndent(int lineIndex, int verticalLineIndent)</code> has been added to customize the vertical indent of the line with the specified line index.
The corresponding getter <code>StyledText.getLineVerticalIndent(int index)</code> has also been added.
<p>
For an example, see <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet374.java">Snippet374</a>
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html b/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
index a47a6ce..9a68843 100644
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
@@ -54,17 +54,17 @@
<tr id="ctrl-e-show-path"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=539446 -->
<td class="title">Quick Switch Editor dialog shows path</td>
<td class="content">
- The <b>Quick Switch Editor (Ctrl+E)</b> dialog for editor selection now shows the path of the resource along with it's filename.
+ The <b>Quick Switch Editor (Ctrl+E)</b> dialog for editor selection now shows the path of the resource along with its filename.
<p>
<img src="images/ctrl-e-show-path.png" alt="" />
</p>
</td>
</tr>
- <tr id="workspace-dialog-directory-proposals"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=539235 -->
+ <tr id="workspace-dialog-directory-proposals"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=538480 -->
<td class="title">Workspace selection dialog offers completion proposals</td>
<td class="content">
- The <b>Workspace selection</b> dialog now shows completion proposals, making it easier to pick a workspace with the keyboard.
+ The <b>Workspace selection</b> dialog now shows completion proposals making it easier to pick a workspace with the keyboard.
<p>
<img src="images/choose_workspace_dialog_proposals.png" alt="" />
</p>
@@ -105,7 +105,7 @@
</td>
</tr>
<tr id="chevron-drawing"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=535068 -->
- <td class="title"><a href="#chevron-drawing">Improved drawing of the chevron button of tab folders</a></td>
+ <td class="title">Improved drawing of the chevron button of tab folders</td>
<td class="content">
When a CTabfolder contains more tabs than that can be displayed, the chevron button appears showing the number of tabs that are hidden.<br/>
This chevron button doesn't have transparency artifacts anymore, making it more readable especially in the dark theme.
@@ -119,7 +119,7 @@
<tr id="dark-theme-combo-win"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=508634 -->
<td class="title"><a href="#dark-theme-combo-win">Combo box styled in Windows Dark theme</a></td>
<td class="content">
- Leveraging the SWT support to style the Read-only Combo, Combo boxes are now styled in the Dark theme on Windows.
+ Leveraging the SWT support to style the read-only Combo, the combo boxes are now styled in the Dark theme on Windows.
<p>Old style:</p>
<p><img src="images/old-dark-combo-win.png" alt=""/></p>
<p>New style:</p>
@@ -135,9 +135,9 @@
</td>
</tr>
<tr id="link-handlers"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=530833 -->
- <td class="title"><a href="#link-handlers">Added support for custom URL schemes</a></td>
+ <td class="title">Added support for custom URL schemes</td>
<td class="content">
- Eclipse platform can now handle custom URL schemes. When you click on a link with such a specific URL scheme, Eclipse first starts (if it's not running yet) and then handles the clicked link.
+ Eclipse platform can now handle custom URL schemes. When you click on a link with a specific custom URL scheme, Eclipse first starts (if it's not running yet) and then handles the clicked link.
<p>
An URL scheme defines the context and thus defines the type of URL, which determines the interpretation of the following URL part.
Examples of a few popular schemes include <code>https</code>, <code>ssh</code> and <code>git</code>.
@@ -152,7 +152,7 @@
</td>
</tr>
<tr id="gtk2-removal"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=530841 -->
- <td class="title"><a href="#gtk2-removal">Dropped support for GTK2</a></td>
+ <td class="title">Dropped support for GTK2</td>
<td class="content">
GTK2 is no longer a supported target environment for Eclipse/SWT on Linux in 4.10, and Eclipse/SWT applications will no longer run on GTK2. Furthermore the <code>SWT_GTK3</code>
environment variable is ignored, as only GTK3 is supported now.
