Bug 550498 - N&N for 4.13
Copy news content and images from news repo to doc bundles.
Change-Id: Ic89873d559f8acb85f86ba17c25c7bcf862ff254
diff --git a/bundles/org.eclipse.jdt.doc.user/topics_WhatsNew.xml b/bundles/org.eclipse.jdt.doc.user/topics_WhatsNew.xml
index 5b2d911..e4137a6 100644
--- a/bundles/org.eclipse.jdt.doc.user/topics_WhatsNew.xml
+++ b/bundles/org.eclipse.jdt.doc.user/topics_WhatsNew.xml
@@ -4,9 +4,9 @@
<!-- Define topics for the What's New -->
<!-- ================================ -->
<toc label="What's New">
- <topic href="whatsNew/jdt_whatsnew.html#Java12" label="Java12" />
- <topic href="whatsNew/jdt_whatsnew.html#JavaEditor" label="Java Editor" />
<topic href="whatsNew/jdt_whatsnew.html#JavaViewsAndDialogs" label="Java Views and Dialogs" />
+ <topic href="whatsNew/jdt_whatsnew.html#JavaEditor" label="Java Editor" />
+ <topic href="whatsNew/jdt_whatsnew.html#JavaFormatter" label="Java Formatter" />
+ <topic href="whatsNew/jdt_whatsnew.html#JUnit" label="JUnit" />
<topic href="whatsNew/jdt_whatsnew.html#Debug" label="Debug" />
- <topic href="whatsNew/jdt_whatsnew.html#JDTDev" label="JDT Developers" />
</toc>
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-after.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-after.png
new file mode 100644
index 0000000..6d08b03
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-after.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-before.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-before.png
new file mode 100644
index 0000000..9f11bfa
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-before.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-feature.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-feature.png
new file mode 100644
index 0000000..20c3d92
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/abstract-removal-feature.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing-unboxing-feature.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing-unboxing-feature.png
new file mode 100644
index 0000000..4055842
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing-unboxing-feature.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/content-assist-debug-shell.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/content-assist-debug-shell.png
deleted file mode 100644
index bf08a00..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/content-assist-debug-shell.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrlclickimpl.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrlclickimpl.png
deleted file mode 100644
index 0a34ebf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrlclickimpl.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enable-preview.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enable-preview.png
deleted file mode 100644
index 1618991..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enable-preview.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enable_preview_features_quickfix.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enable_preview_features_quickfix.png
deleted file mode 100644
index 474c877..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enable_preview_features_quickfix.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-patch-module.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-patch-module.png
new file mode 100644
index 0000000..51b6977
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-patch-module.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/finalquickfix1.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/finalquickfix1.png
new file mode 100644
index 0000000..e5cc0d4
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/finalquickfix1.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/finalquickfix2.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/finalquickfix2.png
new file mode 100644
index 0000000..cf7f64f
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/finalquickfix2.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionafter.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionafter.png
new file mode 100644
index 0000000..c457f87
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionafter.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionbefore.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionbefore.png
new file mode 100644
index 0000000..b1bf376
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionbefore.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionquickfix.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionquickfix.png
new file mode 100644
index 0000000..6a54a02
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/foreachcollectionquickfix.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-new-blank-lines-settings.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-new-blank-lines-settings.png
new file mode 100644
index 0000000..ad33aec
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-new-blank-lines-settings.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-remove-excess-blank-lines.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-remove-excess-blank-lines.png
new file mode 100644
index 0000000..86e4e8c
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-remove-excess-blank-lines.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-switch.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-switch.png
deleted file mode 100644
index a78cbd5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-switch.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/getter-setter-dialog-new.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/getter-setter-dialog-new.png
deleted file mode 100644
index 7952065..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/getter-setter-dialog-new.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jstc-initial-clear.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jstc-initial-clear.png
deleted file mode 100644
index 3f58271..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jstc-initial-clear.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/lambda-variables-view.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/lambda-variables-view.png
deleted file mode 100644
index 2ac1244..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/lambda-variables-view.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/launch-dependencies.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/launch-dependencies.png
new file mode 100644
index 0000000..b6f2b75
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/launch-dependencies.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/merge-process-output.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/merge-process-output.png
new file mode 100644
index 0000000..f4261a3
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/merge-process-output.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/method-implementation-codeminings-click.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/method-implementation-codeminings-click.png
deleted file mode 100644
index 55addbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/method-implementation-codeminings-click.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/method-implementation-codeminings.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/method-implementation-codeminings.png
deleted file mode 100644
index 931142a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/method-implementation-codeminings.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/module-dependencies-cropped.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/module-dependencies-cropped.png
deleted file mode 100644
index 84a4094..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/module-dependencies-cropped.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/module-info-comment-generation-check-box.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/module-info-comment-generation-check-box.png
deleted file mode 100644
index 3e0e865..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/module-info-comment-generation-check-box.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/modulejavadoc.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/modulejavadoc.png
new file mode 100644
index 0000000..fbecb2d
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/modulejavadoc.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/modulejavadocprefs.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/modulejavadocprefs.png
new file mode 100644
index 0000000..c6bdfee
--- /dev/null
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/modulejavadocprefs.png
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-info-comment-generation-checkbox.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-info-comment-generation-checkbox.png
deleted file mode 100644
index 200ab64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-info-comment-generation-checkbox.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/parameter-name-codeminings.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/parameter-name-codeminings.png
deleted file mode 100644
index 2e0ec8b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/parameter-name-codeminings.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-change-compliance-12.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-change-compliance-12.png
deleted file mode 100644
index 0ccde31..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-change-compliance-12.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-configure-severity-12.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-configure-severity-12.png
deleted file mode 100644
index 45b52ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-configure-severity-12.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-default-switch-expression.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-default-switch-expression.png
deleted file mode 100644
index f44ec90..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-default-switch-expression.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-default-switch-statement.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-default-switch-statement.png
deleted file mode 100644
index 37ed947..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-default-switch-statement.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-missing-case-switch-expression.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-missing-case-switch-expression.png
deleted file mode 100644
index 4b57003..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-missing-case-switch-expression.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-missing-case-switch-statement.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-missing-case-switch-statement.png
deleted file mode 100644
index 69b3edf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-missing-case-switch-statement.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-open-missing-projects-problem-view.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-open-missing-projects-problem-view.png
deleted file mode 100644
index dc3866d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-open-missing-projects-problem-view.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-open-missing-projects.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-open-missing-projects.png
deleted file mode 100644
index 3f1a2ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quickfix-open-missing-projects.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/run-to-line.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/run-to-line.png
deleted file mode 100644
index 7a22e2c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/run-to-line.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/service-provider-change-constructor-visibility.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/service-provider-change-constructor-visibility.png
deleted file mode 100644
index 2cc6308..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/service-provider-change-constructor-visibility.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/service-provider-create-constructor.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/service-provider-create-constructor.png
deleted file mode 100644
index ea9e9b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/service-provider-create-constructor.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/split-switch-case-labels.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/split-switch-case-labels.png
deleted file mode 100644
index a7c66b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/split-switch-case-labels.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_case_expression.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_case_expression.png
deleted file mode 100644
index c33ab53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_case_expression.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_expression_templates.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_expression_templates.png
deleted file mode 100644
index ff63cee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_expression_templates.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_labeled_expression.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_labeled_expression.png
deleted file mode 100644
index 33fd152..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_labeled_expression.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_labeled_statement.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_labeled_statement.png
deleted file mode 100644
index 82580f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch_labeled_statement.png
+++ /dev/null
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 fa0c671..8576f00 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
@@ -17,20 +17,20 @@
table.news tr td.content {vertical-align: top;}
ul {padding-left: 13px;}
</style>
-<title>What's New in Eclipse 4.12 (JDT)</title>
+<title>What's New in Eclipse 4.13 (JDT)</title>
</head>
<body>
-<h2>What's New in Eclipse 4.12 (JDT)</h2>
+<h2>What's New in Eclipse 4.13 (JDT)</h2>
<p>Here are descriptions of some of the more interesting or significant changes made to the Java development tools (JDT)
for the 4.12 release of Eclipse.
They are grouped into:</p>
<ul>
- <li><a href="#Java12">Java™ 12 Support</a></li>
- <li><a href="#JavaEditor">Java Editor</a></li>
<li><a href="#JavaViewsAndDialogs">Java Views and Dialogs</a></li>
+ <li><a href="#JavaEditor">Java Editor</a></li>
+ <li><a href="#JavaFormatter">Java Formatter</a></li>
+ <li><a href="#JUnit">JUnit</a></li>
<li><a href="#Debug">Debug</a></li>
- <li><a href="#JDTDev">JDT Developers</a></li>
</ul>
<p>See also the <b><a href="../../org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html">Eclipse Platform What's New</a></b>
@@ -39,225 +39,13 @@
<br/>
<!-- ****************** START OF N&N TABLE****************** -->
-<table class="news" >
+<table class="news">
<colgroup>
<col class="title" />
<col />
</colgroup>
<tbody>
- <!-- ******************* Java 12 Support ************************************* -->
- <tr >
- <td id="Java12" class="section" colspan="2">
- <h2>Java™ 12 Support </h2>
- </td>
- </tr>
-
- <tr id="quickfix-change-compliance-12"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=543781 -->
- <td class="title">Change project compliance and JRE to 12</td>
- <td class="content">
- A quick fix <b>Change project compliance and JRE to 12</b> is provided to change the current project to be compatible with Java 12.
- <p>
- <img src="images/quickfix-change-compliance-12.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="enable-preview"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=542579 -->
- <td class="title">Enable preview features</td>
- <td class="content">
- Preview features in Java 12 can be enabled using <b>Preferences > Java > Compiler > Enable preview features</b> option.
- The problem severity of these preview features can be configured using the <b>Preview features with severity level</b> option.
- <p>
- <img src="images/enable-preview.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="quickfix-enable-preview-12"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544257 -->
- <td class="title">Set Enable preview features</td>
- <td class="content">
- A quick fix to <b>Enable preview features</b> option in preferences is provided.
- <p>
- <img src="images/enable_preview_features_quickfix.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="quickfix-configure-severity-12"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=543669 -->
- <td class="title">Configure problem severity of preview features</td>
- <td class="content">
- A quick fix <b>Configure problem severity</b> is provided to update the problem severity of preview features in Java 12.
- <p>
- <img src="images/quickfix-configure-severity-12.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="quickfix-default-switch-statement"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=543665 -->
- <td class="title">Add default case to switch statement</td>
- <td class="content">
- A quick fix <b>Add 'default' case</b> is provided to add default case to a enhanced switch statement in Java 12.
- <p>
- <img src="images/quickfix-default-switch-statement.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="quickfix-missing-case-switch-statement"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545259 -->
- <td class="title">Add missing case statements to switch statement</td>
- <td class="content">
- A quick fix <b>Add missing case statements</b> is provided for a enhanced switch statement in Java 12.
- <p>
- <img src="images/quickfix-missing-case-switch-statement.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="quickfix-default-switch-expression"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545256 -->
- <td class="title">Add default case to switch expression</td>
- <td class="content">
- A quick fix <b>Add 'default' case</b> is provided to add default case to a switch expression.
- <p>
- <img src="images/quickfix-default-switch-expression.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="quickfix-missing-case-switch-expression"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545340 -->
- <td class="title">Add missing case statements to switch expression</td>
- <td class="content">
- A quick fix <b>Add missing case statements</b> is provided for switch expressions.
- <p>
- <img src="images/quickfix-missing-case-switch-expression.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="switch-spaces"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545423 -->
- <td class="title">Format whitespaces in 'switch'</td>
- <td class="content">
- As Java 12 introduced some new features into the <code>switch</code> construct, the formatter profile has some new settings for it.
- The settings allow you to control spaces around the arrow operator (separately for <code>case</code> and <code>default</code>) and around commas in a multi-value case.
- <p>
- The settings can be found in the <b>Profile Editor</b> (<b>Preferences > Java > Code Style > Formatter > Edit...</b>) under the <b>White space > Control statements > 'switch'</b> subsection.
- </p>
- <p>
- <img src="images/formatter-switch.png" alt="" />
- </p>
- </td>
- </tr>
-
- <tr id="split-switch-case-labels"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545261 -->
- <td class="title">Split Switch Case Labels</td>
- <td class="content">
- As Java 12 introduced the ability to group multiple <code>switch</code> case labels into a single case expression, a quick assist is provided that allows these grouped labels to be split into separate case statements.
- <p>
- <img src="images/split-switch-case-labels.png" alt="" />
- </p>
- </td>
- </tr>
-
- <!-- ******************* End of Java 12 Support ************************************* -->
-
- <!-- ******************* JUnit ************************************* -->
- <!--
- <tr>
- <td id="JUnit" class="section" colspan="2">
- <h2>JUnit</h2>
- </td>
- </tr>
- -->
- <!-- ******************* End of JUnit ************************************* -->
-
- <!-- ******************* Java Editor ************************************* -->
- <tr>
- <td id="JavaEditor" class="section" colspan="2">
- <h2>Java Editor </h2>
- </td>
- </tr>
-
- <tr id="parameter-name-codemining"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=529011 -->
- <td class="title">Show method parameter names on code as code minings</td>
- <td class="content">
- In the <b>Java > Editor > Code Mining</b> preferences, you can now enable the <b>Show parameter names</b>
- option. This will show the parameter names as code minings in method or constructor calls, for cases where the resolution may
- not be obvious for a human reader.
- <p>
- For example, the code mining will be shown if the argument name in the method call is not an exact match of the parameter name or
- if the argument name doesn't contain the parameter name as a substring.
- </p>
- <p>
- <img src="images/parameter-name-codeminings.png" alt=""/>
- </p>
- </td>
- </tr>
- <tr id="method-implementation-codemining"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=529011 -->
- <td class="title">Show number of implementations of methods as code minings</td>
- <td class="content">
- In the <b>Java > Editor > Code Mining</b> preferences, selecting <b>Show implementations</b>
- with the <b>Show References (including implementations) for</b> -> <b>Methods</b> option now shows
- implementations of methods.
- <p>
- <img src="images/method-implementation-codeminings.png" alt=""/>
- </p>
- <p>
- Clicking on method implementations brings up the <b>Search</b> view that shows all implementations
- of the method in sub-types.
- </p>
- <p>
- <img src="images/method-implementation-codeminings-click.png" alt=""/>
- </p>
- </td>
- </tr>
- <tr id="ctrl-click-codemining"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=529011 -->
- <td class="title">Open single implementation/reference in editor from code mining</td>
- <td class="content">
- When the <b>Java > Editor > Code Mining</b> preferences are enabled and a single implementation or reference is shown, moving the cursor over the annotation and using <b>Ctrl+Click</b> will open the editor and display the single implementation or reference.
- <p>
- <img src="images/ctrlclickimpl.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="service-provider-constructor-quick-fix"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=541261 -->
- <td class="title">Additional quick fixes for service provider constructors</td>
- <td class="content">
- Appropriate quick fixes are offered when a service defined in a <code>module-info.java</code> file has a service provider implementation whose no-arg constructor is not visible, or is non-existent.
- <p>
- <img src="images/service-provider-create-constructor.png" alt=""/>
- </p>
- <p>
- <img src="images/service-provider-change-constructor-visibility.png" alt=""/>
- </p>
- </td>
- </tr>
-
- <tr id="new-switch_labeled_statment_expression_template"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545417 -->
- <td class="title">Template to create Switch Labeled Statement and Switch Expressions</td>
- <td class="content">
- The <b>Java Editor</b> now offers new templates for the creation of switch labeled statements and switch expressions.
- On a switch statement, three new templates: <b>switch labeled statement</b>, <b>switch case expression</b> and <b>switch labeled expression</b>
- are available as shown below. These new templates are available on Java projects having compliance level of Java 12 or above.
- <p>
- <img src="images/switch_labeled_statement.png" alt="" />
- </p>
- <p>
- <img src="images/switch_case_expression.png" alt="" />
- </p>
- <p>
- <img src="images/switch_labeled_expression.png" alt="" />
- </p>
-
- If <b>switch</b> is being used as an expression, then only <b>switch case expression</b> and <b>switch labeled expression</b>
- templates are available as shown below:
- <p>
- <img src="images/switch_expression_templates.png" alt="" />
- </p>
-
- </td>
- </tr>
- <!-- ******************* End of Java Editor ************************************* -->
<!-- ******************* Java Views and Dialogs ************************************* -->
<tr>
@@ -266,109 +54,145 @@
</td>
</tr>
- <tr id="comment-generation-checkbox"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545011 -->
- <td class="title">Enable comment generation in modules and packages</td>
+ <tr id="console-output-synchronization"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=32205 -->
+ <td class="title">Synchronize standard and error output in console</td>
<td class="content">
- An option is now available to enable/disable the comment generation while creating <code>module-info.java</code>
- or <code>package-info.java</code>.
- <p>
- <img src="images/module-info-comment-generation-check-box.png" alt=""/>
- </p>
- <p>
- <img src="images/package-info-comment-generation-checkbox.png" alt=""/>
- </p>
+ The Eclipse <b>Console view</b> currently can not ensure that mixed standard and error output is shown in the same order
+ as it is produced by the running process. For Java applications the launch configuration <b>Common Tab</b> now
+ provides an option to merge standard and error output. This ensures that standard and error output is shown in the
+ same order it was produced but at the same time disables the individual coloring of error output.
+ <p><img src="images/merge-process-output.png" alt="Differences between merging enabled and disabled"/></p>
</td>
</tr>
- <tr id="getter-setter-quick-assist"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=232920 -->
- <td class="title">Improved 'create getter and setter' quick assist</td>
- <td class="content">
- The quick assist for creating getter and setter methods from fields no longer forces you to create both.
- <p>
- <img src="images/getter-setter-dialog-new.png" alt=""/>
- </p>
- </td>
- </tr>
- <tr id="quickfix-open-missing-projects"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=343121 -->
- <td class="title">Quick fix to open all required closed projects</td>
- <td class="content">
- A quick fix to open all required closed projects is now available in the <b>Problems</b> view.
- <p>
- <img src="images/quickfix-open-missing-projects-problem-view.png" alt=""/>
- </p>
- <p>
- <img src="images/quickfix-open-missing-projects.png" alt=""/>
- </p>
- </td>
- </tr>
- <tr id="buildpath-module-dependencies"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=546352 -->
- <td class="title">New UI for configuring <b>Module Dependencies</b></td>
- <td class="content">
- The <b>Java Build Path</b> configuration now has a new tab <b>Module Dependencies</b>,
- which will gradually replace the options previously hidden behind the <b>Is Modular</b>
- node on other tabs of this dialog. The new tab provides an intuitive way for configuring all
- those module-related options for which Java 9 had introduced new command line options
- like <code>--limit-modules</code> etc.
- <p>
- <a href="images/module-dependencies.png"><img src="images/module-dependencies-cropped.png" alt="Module Dependencies dialog"/></a>
- </p>
- <p>
- The dialog focuses on how to build one Java Project, here "org.greetings".
- </p><p>
- Below this focus module, the left hand pane shows all modules that participate in the build,
- where decorations A and S mark automatic modules and system modules, respectively. The extent
- of system modules (from JRE) can be modified with the <b>Add System Module...</b> and
- <b>Remove</b> buttons (corresponds to <code>--add-modules</code> and <code>--limit-modules</code>).
- </p><p>
- When a module is selected in the left hand pane, the right hand pane allows to configure
- the following properties for this module:
- </p>
- <dl>
- <dt><b>Read Module:</b></dt>
- <dd>Select additional modules that should be accessible from the
- selected module (corresponds to <code>--add-reads</code>)</dd>
- <dt><b>Expose Package:</b></dt>
- <dd>Select additional packages to be exposed ("exports" or "opens")
- from the selected module (corresponds to <code>--add-exports</code> or <code>--add-opens</code>)</dd>
- <dt><b>Patch with:</b></dt>
- <dd>Add more packages and classes to the selected module
- (corresponds to <code>--patch-module</code>)</dd>
- </dl>
- </td>
- </tr>
-
<!-- ******************* End of Java Views and Dialogs ************************************* -->
-
- <!-- ******************* Java Compiler ************************************* -->
-
+
+ <!-- ******************* Java Editor ************************************* -->
<tr>
- <td id="JavaCompiler" class="section" colspan="2">
- <h2>Java Compiler</h2>
- </td>
- </tr>
- <tr id="new-java-index">
- <td class="title">Experimental Java index retired</td>
- <td class="content">
- Eclipse 4.7 introduced a new experimental Java index which was disabled by default.<br/>
- Due to lack of resources to properly support all Java 9+ language changes,
- this index is not available anymore starting with Eclipse 4.12.
- <p>
- The preference to enable it in <b>Preferences > Java</b> is removed and the old index will be always used.
- </p>
- <b>Note:</b> <b>Preferences > Java > Rebuild Index</b> button can be used to delete the existing index files and free disk space.
+ <td id="JavaEditor" class="section" colspan="2">
+ <h2>Java Editor</h2>
</td>
</tr>
- <!-- ******************* End of Java Compiler ************************************* -->
+ <tr id="foreach-loop-collections"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548002 -->
+ <td class="title">Convert to enhanced 'for' loop using Collections</td>
+ <td class="content">
+ The Java quickfix/cleanup <b>Convert to enhanced 'for' loop</b> is now offered on <code>for</code> loops that are iterating through Collections. The
+ loop must reference the <code>size</code> method as part of the condition and if accessing elements in the body, must use the <code>get</code>
+ method. All other Collection methods other than <code>isEmpty</code> invalidate the quickfix being offered.
+ <p><img src="images/foreachcollectionbefore.png" alt="for loop using Collections before"/></p>
+ <p><img src="images/foreachcollectionquickfix.png" alt="for loop using Collections quickfix"/></p>
+ <p><img src="images/foreachcollectionafter.png" alt="for loop using Collections after"/></p>
+ </td>
+ </tr>
+
+ <tr id="final-fields-quickfix"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=83544 -->
+ <td class="title">Initialize 'final' fields</td>
+ <td class="content">
+ A Java quickfix is now offered to initialize an uninitialized <code>final</code> field in the class constructor. The fix will initialize a <code>String</code> to the empty string, a numeric base type to 0, and for class fields it initializes them using their default constructor if available or <code>null</code> if no default constructor exists.
+ <p><img src="images/finalquickfix1.png" alt="unitialized final field before"/></p>
+ <p><img src="images/finalquickfix2.png" alt="final field initialized in constructor"/></p>
+ </td>
+ </tr>
+
+ <tr id="autoboxing-unboxing"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549242 -->
+ <td class="title">Autoboxing and Unboxing</td>
+ <td class="content">
+ Use Autoboxing and Unboxing when possible. These features are enabled only for Java 5 and higher.
+ <p><img src="images/autoboxing-unboxing-feature.png" alt=""/></p>
+ </td>
+ </tr>
+
+ <tr id="enhanced-redundant-modifier-removal"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549242 -->
+ <td class="title">Improved redundant modifier removal</td>
+ <td class="content">
+ <b>Remove redundant modifier</b> now also removes useless <code>abstract</code> modifier on the interfaces.
+ <p><img src="images/abstract-removal-feature.png" alt=""/></p>
+ For the given code:
+ <p><img src="images/abstract-removal-before.png" alt=""/></p>
+ You get this:
+ <p><img src="images/abstract-removal-after.png" alt=""/></p>
+ </td>
+ </tr>
+
+ <tr id="javadoc-for-module-info"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=546350 -->
+ <td class="title">Javadoc comment generation for module</td>
+ <td class="content">
+ Adding a Javadoc comment to a Java module (module-info.java) will result in automatic annotations being added per the new module comment preferences.
+ <p><img src="images/modulejavadocprefs.png" alt="Javadoc module comment preferences"/></p>
+ <p>
+ The <code>$(tags)</code> directive will add <code>@uses</code> and <code>@provides</code> tags for all <b>uses</b> and <b>provides</b> module statements.
+ </p>
+ <p><img src="images/modulejavadoc.png" alt="Javadoc module comment example"/></p>
+ </td>
+ </tr>
+ <!-- ******************* End of Java Editor ************************************* -->
<!-- ******************* Java Formatter ************************************* -->
- <!--
<tr>
<td id="JavaFormatter" class="section" colspan="2">
<h2>Java Formatter </h2>
</td>
</tr>
- -->
+ <tr id="remove-excess-blank-lines"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549255 -->
+ <td class="title">Remove excess blank lines</td>
+ <td class="content">
+ All the settings in the <b>Blank lines</b> section can now be configured to <b>remove excess blank lines</b>, effectively taking precedence over the <i>Number of empty lines to preserve</i> setting.
+ Each setting has its own button to turn the feature on, right next to its number control.
+ The button is enabled only if the selected number of lines is smaller than the <i>Number of empty lines to preserve</i>, because otherwise any excess lines are removed anyway.
+ <p>
+ <img src="images/formatter-remove-excess-blank-lines.png" alt="" />
+ </p>
+ </td>
+ </tr>
+ <tr id="blank-lines-changes"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=550083 -->
+ <td class="title">Changes in blank lines settings</td>
+ <td class="content">
+ There's quite a lot of changes in the <b>Blank lines</b> section of the formatter profile.
+ <p>
+ Some of the existing subsections and settings are now phrased differently to better express their function:
+ </p>
+ <ul>
+ <li>The <i>Blank lines within class declarations</i> subsection is now <i>Blank lines within type declaration</i></li>
+ <li><i>Before first declaration</i> is now <i>Before first member declaration</i></li>
+ <li><i>Before declarations of the same kind</i> is now <i>Between member declarations of different kind</i></li>
+ <li><i>Before member class declarations</i> is now <i>Between member type declarations</i></li>
+ <li><i>Before field declarations</i> is now <i>Between field declarations</i></li>
+ <li><i>Before method declarations</i> is now <i>Between method/constructor declarations</i></li>
+ </ul>
+ <p>
+ More importantly, a few new settings have been added to support more places where the number of empty lines can be controlled:
+ </p>
+ <ul>
+ <li><i>After last member declaration</i> in a type (to complement previously existing <i>Before first member declaration</i> setting)</li>
+ <li><i>Between abstract method declarations</i> in a type (these cases were previously handled by <i>Between method/constructor declarations</i>)</li>
+ <li><i>At end of method/constructor body</i> (to complement previously existing <i>At beginning of method/constructor body</i> setting)</li>
+ <li><i>At beginning of code block</i> and <i>At end of code block</i></li>
+ <li><i>Before statement with code block</i> and <i>After statement with code block</i></li>
+ <li><i>Between statement groups in 'switch'</i></li>
+ </ul>
+ <p>
+ Most of the new settings have been put in a new subsection <b>Blank lines within method/constructor declarations</b>.
+ </p>
+ <p>
+ <img src="images/formatter-new-blank-lines-settings.png" alt="" />
+ </p>
+ </td>
+ </tr>
<!-- ******************* End of Java Formatter ************************************* -->
+
+<!-- ******************* JUnit ************************************* -->
+ <tr>
+ <td id="JUnit" class="section" colspan="2">
+ <h2>JUnit</h2>
+ </td>
+ </tr>
+ <tr id="junit-5.5.1"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548964 -->
+ <td class="title">JUnit 5.5.1</td>
+ <td class="content">
+ <a href="https://junit.org/junit5/docs/5.5.1/release-notes/">JUnit 5.5.1</a> is here and Eclipse JDT has been updated to use this version.
+ </td>
+ </tr>
+ <!-- ******************* End of JUnit ************************************* -->
<!-- *********************** Debug ******************************** -->
<tr>
@@ -376,79 +200,37 @@
<h2>Debug</h2>
</td>
</tr>
- <tr id="run-to-line-in-annotation-ruler"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=498428 -->
- <td class="title">'Run to Line' on Ctrl+Alt+Click in annotation ruler</td>
+ <tr id="enhanced-patch-module-support"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=546738 -->
+ <td class="title">Enhanced support for --patch-module during launch</td>
<td class="content">
- A new shortcut, <b>Ctrl+Alt+Click</b>, has been added to the annotation ruler that will invoke the <b>'Run to Line'</b> command and take the program execution to the line of invocation.
- <p>
- <img src="images/run-to-line.png" alt="" />
- </p>
+ The <b>Java Launch Configuration</b> now supports patching of different modules by different sources during the launch. This can be verified in the <b>Override Dependencies...</b> dialog
+ in the <b>Dependencies</b> tab in a Java Launch Configuration.
+ <p><img src="images/launch-dependencies.png" alt=""/></p>
+ <p><img src="images/enhanced-patch-module.png" alt=""/></p>
</td>
</tr>
-
- <tr id="content-assist-debug-shell"><!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=546071 -->
- <td class="title">Content assist in Debug Shell</td>
- <td class="content">
- Content assist <b>(Ctrl+Space)</b> support is now available in the <b>Debug Shell</b>.
- <p><img src="images/content-assist-debug-shell.png" alt=""/></p>
- </td>
- </tr>
-
- <tr id="jstc-clear-initial-message"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=343023 -->
- <td class="title">Clear Java Stack Trace Console usage hint on first edit</td>
- <td class="content">
- The <b>Java Stack Trace Console</b> shows a usage hint when opened the first time. This message is now automatically removed
- when the user starts typing or pasting a stack trace.
- <p><img src="images/jstc-initial-clear.png" alt=""/></p>
- </td>
- </tr>
-
- <tr id="lambda-variables-variable-view"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=534687 -->
- <td class="title">Lambda variable names shown in Variables view</td>
- <td class="content">
- The Lambda variable names are now shown in the <b>Variables</b> view while debugging projects in the workspace.
- <p><img src="images/lambda-variables-view.png" alt=""/></p>
- </td>
- </tr>
-
<!--************************ End of Debug ******************************** -->
- <!-- *********************** JDT Developers ******************************** -->
+ <!-- ******************* Java Build ************************************* -->
<tr>
- <td id="JDTDev" class="section" colspan="2">
- <h2>JDT Developers</h2>
+ <td id="JavaBuild" class="section" colspan="2">
+ <h2>Java Build</h2>
</td>
</tr>
-
- <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544362 -->
- <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=540485 -->
-
- <tr id="javadoc-support-tags">
- <td class="title">Support for new Javadoc tags</td>
+
+ <tr id="full-build-on-jdt-core-settings-change"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549457 -->
+ <td class="title">Full build on JDT core preferences change</td>
<td class="content">
- The following Javadoc tags are now supported by the compiler and auto-complete.
- <p>
- Tags introduced in JDK 8:<br/>
- <code>@apiNote</code><br/>
- <code>@implSpec</code><br/>
- <code>@implNote</code>
- </p>
- <p>
- Tags introduced in JDK 9:<br/>
- <code>@index</code><br/>
- <code>@hidden</code><br/>
- <code>@provides</code><br/>
- <code>@uses</code>
- </p>
- <p>
- Tags introduced in JDK 10:<br/>
- <code>@summary</code>
- </p>
+ Manually changing the settings file <b>.settings/org.eclipse.jdt.core.prefs</b> of a project
+ will result in a full project build, if the workspace auto-build is on. For example, pulling
+ different settings from a git repository or generating the settings with a tool will now trigger a build.
+ Note that this includes timestamp changes, even if actual settings file contents were not changed.
+ <p>For the 4.13 release, it is possible to disable this new behavior with the VM property:
+ <b><span style="white-space: nowrap;">-Dorg.eclipse.disableAutoBuildOnSettingsChange=true</span></b>.
+ It is planned to remove this VM property in a future release.</p>
</td>
</tr>
-
-
- <!-- *********************** End of JDT Developers ******************************** -->
+ <!-- ******************* End of Java Build ************************************* -->
</tbody>
</table>
<!-- ****************** END OF N&N TABLE ****************** -->
diff --git a/bundles/org.eclipse.pde.doc.user/topics_WhatsNew.xml b/bundles/org.eclipse.pde.doc.user/topics_WhatsNew.xml
index e0b30db..5ab4b11 100644
--- a/bundles/org.eclipse.pde.doc.user/topics_WhatsNew.xml
+++ b/bundles/org.eclipse.pde.doc.user/topics_WhatsNew.xml
@@ -16,6 +16,6 @@
<!-- ================================ -->
<toc label="What's new">
<topic href="whatsNew/pde_whatsnew.html#dialogs-wizards-views" label="Dialogs, Wizards and Views"/>
- <topic href="whatsNew/pde_whatsnew.html#editors" label="Editors" />
<topic href="whatsNew/pde_whatsnew.html#APITools" label="API Tools" />
+ <topic href="whatsNew/pde_whatsnew.html#pde-compiler" label="PDE Compiler" />
</toc>
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/feature-launch-startlevels.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/feature-launch-startlevels.png
new file mode 100644
index 0000000..b684bdf
--- /dev/null
+++ b/bundles/org.eclipse.pde.doc.user/whatsNew/images/feature-launch-startlevels.png
Binary files differ
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/features-view.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/features-view.png
new file mode 100644
index 0000000..e9325ed
--- /dev/null
+++ b/bundles/org.eclipse.pde.doc.user/whatsNew/images/features-view.png
Binary files differ
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-api-addition.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-api-addition.png
new file mode 100644
index 0000000..f592c9c
--- /dev/null
+++ b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-api-addition.png
Binary files differ
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-category-editor-source.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-category-editor-source.png
deleted file mode 100644
index 78d6c98..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-category-editor-source.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-remove-restriction.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-remove-restriction.png
deleted file mode 100644
index f83dd50..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-remove-restriction.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/show-view-dialog.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/show-view-dialog.png
new file mode 100644
index 0000000..32025b3
--- /dev/null
+++ b/bundles/org.eclipse.pde.doc.user/whatsNew/images/show-view-dialog.png
Binary files differ
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 3977a76..b281fce 100644
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html
+++ b/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html
@@ -4,7 +4,7 @@
<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2018. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/>
<meta http-equiv="Content-Language" content="en-us"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<link rel="STYLESHEET" href="../book.css" type="text/css"/>
+<link rel="STYLESHEET" href="news.css" type="text/css"/>
<style type="text/css">
body {max-width: 900px;}
table.news col.title {width: 30%;}
@@ -17,25 +17,19 @@
table.news tr td.content {vertical-align: top;}
ul {padding-left: 13px;}
</style>
-<title>What's New in 4.12 (PDE)</title>
+<title>What's New in 4.13 (PDE)</title>
</head>
<body>
-<h2>What's New in 4.12 (PDE)</h2>
+<h2>What's New in 4.13 (PDE)</h2>
<p>Here are descriptions of some of the more interesting or significant changes made to the Plug-in Development Environment (PDE)
-for the 4.12 release of Eclipse. They are grouped into:</p>
+for the 4.13 release of Eclipse. They are grouped into:</p>
<ul> <!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
<li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
- <li><a href="#editors">Editors</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>
</ul>
-<p>See also the
-<b><a href="../../org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html">Eclipse Platform What's New</a></b>
-and
-<b><a href="../../org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html">JDT What's New</a></b>
-documents.</p>
-<p>We also recommend to read the <a href="../tips/pde_tips.htm">Tips and Tricks</a>.</p>
-<br/>
<!-- ****************** START OF N&N TABLE****************** -->
<table class="news">
@@ -44,177 +38,123 @@
<col />
</colgroup>
<tbody>
- <!-- ******************** Dialogs, Wizards and Views ********************** -->
+ <!-- ******************** Dialogs, Wizard and Views ********************** -->
<tr>
<td id="dialogs-wizards-views" class="section" colspan="2"><h2>Dialogs, Wizards and Views</h2></td>
</tr>
- <tr id="pde-target-platform-preferences"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=546400 -->
- <td class="title">Target Platform preferences</td>
+ <tr id="feature-launch-startlevels"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=331595 -->
+ <td class="title">Configure start levels for feature based launch</td>
<td class="content">
- The <b>Preferences > Plug-in Development > Target Platform</b> preference page now allows to change the height balance between 'Target definitions' and 'Locations' areas.
+ <b>Feature-based Launch Configuration</b> now supports custom start levels and auto-start properties for individual plugins.
+ <p>
+ To configure them, you need to add the plugins via <b>Add Plug-ins...</b> first.
+ </p>
+ <p>
+ When launching a feature-based product, defined start levels and selected features are automatically
+ filled out in the created launch configuration. You can then select <b>features selected below</b> to
+ convert it to feature-based without any further configuration.
+ </p>
+ <p>
+ <img src="images/feature-launch-startlevels.png" alt="" />
+ </p>
</td>
</tr>
- <!--
- -->
- <!-- ******************** End ofDialogs, Wizards and Views ********************** -->
+
+ <tr id="features-view"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=543217 -->
+ <td class="title">New Features view</td>
+ <td class="content">
+ You can now view the structure of features in your workspace projects using the new <b>Features</b> view.
+ <p>
+ To open the view, go to the <b>Show View</b> dialog (<b>Window > Show View > Other...</b>) and choose it from
+ the <b>Plug-in Development</b> category.
+ </p>
+ <p>
+ <img src="images/show-view-dialog.png" alt="" />
+ </p>
+ <p>
+ By default the view shows only features, with child features listed under their parents rather than at the top level.
+ The buttons on the view's toolbar allow plugins/fragments included within a feature to be shown, child features to be
+ shown at the top level, and for the hierarchy to be inverted (to show the features including each feature).
+ </p>
+ <p>
+ <img src="images/features-view.png" alt="" />
+ </p>
+ </td>
+ </tr>
+ <!-- ******************** End ofDialogs, Wizard and Views ********************** -->
<!-- ******************** Editors ********************** -->
- <!--
- -->
- <tr>
- <td id="editors" class="section" colspan="2"><h2>Editors</h2></td>
- </tr>
- <tr id="pde-category-editor-source"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=546803 https://bugs.eclipse.org/bugs/show_bug.cgi?id=547322 -->
- <td class="title">'Source' tab for Product and Category Editor</td>
- <td class="content">
- The <b>Product Editor</b> and <b>Category Editor</b> now have a 'Source' tab to enable direct access to their manifests.
- <p>
- <img src="images/pde-category-editor-source.png" alt="" />
- </p>
- </td>
- </tr>
+ <!-- <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>
- <tr id="pde-restriction-removal-reported"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=327452 -->
- <td class="title">Removing API restriction results in API error</td>
- <td class="content">
- Removing PDE API tools restriction such as <code>@noextend</code>, <code>@noimplement</code> and <code>@noinstantiate</code> now results in an incompatible bundle version API tool error, since clients of this code can
- access more APIs after the removal.
- <p>
- A quick fix for this error is available, and it increases the minor version to reflect the code changes.
- </p>
- <p>
- <img src="images/pde-remove-restriction.png" alt="" />
- </p>
- </td>
- </tr>
- <tr id="api-analysis-report-application"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=547206 -->
- <td class="title">Run API analysis as application</td>
+ <tr id="quickfix-for-first-api-addition"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=243878 -->
+ <td class="title">Quickfix to add missing since tag after version update</td>
<td class="content">
- To ease automation without Ant, the API Tools analysis can be performed using a regular Eclipse application
- named <code>org.eclipse.pde.api.tools.apiAnalysis</code>.
+ On any API addition that also results in a version change, a quickfix is now available that first
+ updates the version appropriately and then adds the <code>@since</code> tag based on the updated version.
<p>
- It can receive the following parameters:
+ <img src="images/pde-api-addition.png" alt="" />
</p>
- <ul>
- <li><code>-project </path/to/project></code> configures which project should be analyzed. It has to be a valid Plug-in project containing a .project file.</li>
- <li><code>-dependencyList </path/to/a/dependencyList.txt></code> configures the target platform for the analysis. This file will be parsed, using new lines and
- colon (:) as separator and all tokens that match a path on the filesystem will be added to the Target Platform.</li>
- <li><code>-baseline <default|/path/to/baseline.target></code> specifies the baseline to use for comparison. If omitted or <code>default</code>, it is the current
- running platform. If a path to a <code>.target</code> file is specified, it will resolve the target definition and use the included bundles as baseline.</li>
- <li><code>-failOnError</code> If present, the application will return an error (non-<code>0</code>) in case of API errors.</li>
- </ul>
- <p>
- The API analysis uses the project settings, but forces the <em>incompatible api component version report major without breaking change</em> and <em>incompatible api component version report minor without api change</em>
- rules breakage to be reported as errors.
- </p>
- <p>
- Example of invocation can look like:
- </p>
- <p>
- <code>./eclipse -project /home/mistria/sandbox/org.eclipse.e4.ui.css.core -dependencyList /home/mistria/sandbox/org.eclipse.e4.ui.css.core/dependencies.txt -failOnError</code>
- </p>
- <p>
- Additionally to the potential non-<code>0</code> result, example of output can look like:
- </p>
- <p>
- <code>
-1 API ERRORS
-* Marker [on: /org.eclipse.e4.ui.css.core/META-INF/MANIFEST.MF, id: 80, type: org.eclipse.pde.api.tools.version_numbering, attributes: [apiMarkerID: 4, charEnd: 228, charStart: 210, description: , lineNumber: 7, message: The minor version should be the same for version 0.11.400, since no new APIs have been added since version 0.12.700, messagearguments: 0.11.400#0.12.700, problemid: 926941240, severity: 2, sourceId: API Tools, version: 0.12.700.qualifier], created: 5/16/19, 5:36 PM]
-1 API warnings
-* Marker [on: /org.eclipse.e4.ui.css.core, id: 81, type: org.eclipse.pde.api.tools.api_usage, attributes: [apiMarkerID: 3, charEnd: -1, charStart: -1, lineNumber: 0, message: Execution environment references were not checked for 'org.eclipse.e4.ui.css.core' because no environment descriptions are installed. , messagearguments: org.eclipse.e4.ui.css.core, problemid: 665845798, severity: 1, sourceId: API Tools], created: 5/16/19, 5:36 PM]
- </code>
- </p>
- <p>
- Here is an example of how this could be used in Tycho to trigger API checks in a Tycho build, in <code>pom.xml</code>
- </p>
- <pre style="width:778px;">
-<project>
- [...]
- <build>
- [...]
- <plugins>
- [...]
- <plugin>
- <artifactId>maven-dependency-plugin</artifactId>
- <executions>
- <execution>
- <id>list-dependencies</id>
- <goals>
- <goal>list</goal>
- </goals>
- <phase>verify</phase>
- <configuration>
- <outputAbsoluteArtifactFilename>true</outputAbsoluteArtifactFilename>
- <outputScope>false</outputScope>
- <outputFile>${project.build.directory}/dependencies.txt</outputFile>
- </configuration>
- </execution>
- </executions>
- </plugin>
- <plugin>
- <groupId>org.eclipse.tycho.extras</groupId>
- <artifactId>tycho-eclipserun-plugin</artifactId>
- <version>1.4.0</version>
- <executions>
- <execution>
- <id>api-analysis</id>
- <goals>
- <goal>eclipse-run</goal>
- </goals>
- <phase>verify</phase>
- <configuration>
- <applicationsArgs>
- <!-- need to set workspace to a dir that's not a child of the project -->
- <arg>-data</arg>
- <args>${project.basedir}/../target/${project.artifactId}-apiAnalyzer-workspace</args>
- <args>-application</args>
- <args>org.eclipse.pde.api.tools.apiAnalysis</args>
- <args>-project</args>
- <args>${project.basedir}</args>
- <args>-baseline</args>
- <args>default</args>
- <args>-dependencyList</args>
- <args>${project.build.directory}/dependencies.txt</args>
- <args>-failOnError</args>
- </applicationsArgs>
- <repositories>
- <repository>
- <id>eclipse-4.12</id>
- <layout>p2</layout>
- <url>https://download.eclipse.org/eclipse/updates/4.12-I-builds/</url>
- </repository>
- </repositories>
- <dependencies>
- <!-- This will constitute the default baseline -->
- <dependency>
- <artifactId>org.eclipse.sdk.ide</artifactId>
- <type>p2-installable-unit</type>
- </dependency>
- </dependencies>
- </configuration>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
-</project>
- </pre>
</td>
</tr>
+
+ <tr id="optimization-pde-api-tools-build">
+ <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=344110 -->
+ <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=344163 -->
+ <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=549630 -->
+ <td class="title">Optimization in API tools builder </td>
+ <td class="content">
+ There are various optimizations that are done for API analysis builder which has
+ improved the performance in some scenarios tremendously.
+ <ul>
+ <li>Changing <b>Missing API baseline</b> option in <b>Preferences > Plug-in Development > API Baselines</b> preference page
+ updates the marker appropriately instead of doing a full build.</li>
+ <li>Removing or unchecking baseline in <b>Preferences > Plug-in Development > API Baselines</b> preference page removes all markers
+ which requires a baseline instead of a full build.</li>
+ <li>Removing or unchecking all API Use Scan locations in <b>Preferences > Plug-in Development > API Use Scans</b> preference page removes the relevant markers instead of doing a full build.</li>
+ </ul>
+ <p>
+ For example, changing <b>Missing API baseline</b> option in <code>org.eclipse.jdt.core</code> finishes instantaneously instead of 3 to 4 seconds earlier.
+ </p>
+ </td>
+ </tr>
+
+ <tr id="full-build-on-pde-api-tools-settings-change"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549838 -->
+ <td class="title">Full build on API tools preferences change</td>
+ <td class="content">
+ Manually changing the settings file <b>.settings/org.eclipse.pde.api.tools.prefs</b> of a project
+ will result in a full project build, if the workspace auto-build is on.
+ <p>For the 4.13 release, it is possible to disable this new behavior with the VM property:
+ <b><span style="white-space: nowrap;">-Dorg.eclipse.disableAutoBuildOnSettingsChange=true</span></b>.
+ It is planned to remove this VM property in a future release.</p>
+ </td>
+ </tr>
+
<!-- ******************** End of APITools ********************** -->
<!-- ******************** PDE Compiler ********************** -->
- <!--
- <tr>
- <td id="pde-compiler" class="section" colspan="2"><h2>PDE Compiler</h2></td>
+ <tr>
+ <td id="pde-compiler" class="section" colspan="2"><h2>PDE Compiler</h2></td>
+ </tr>
+
+ <tr id="full-build-on-pde-compiler-settings-change"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549839 -->
+ <td class="title">Full build on PDE compiler preferences change</td>
+ <td class="content">
+ Manually changing the settings file <b>.settings/org.eclipse.pde.prefs</b> of a project
+ will result in a full project build, if the workspace auto-build is on.
+ <p>For the 4.13 release, it is possible to disable this new behavior with the VM property:
+ <b><span style="white-space: nowrap;">-Dorg.eclipse.disableAutoBuildOnSettingsChange=true</span></b>.
+ It is planned to remove this VM property in a future release.</p>
+ </td>
</tr>
- -->
+
<!-- ******************** End of PDE Compiler ********************** -->
</tbody>
diff --git a/bundles/org.eclipse.platform.doc.isv/topics_WhatsNew.xml b/bundles/org.eclipse.platform.doc.isv/topics_WhatsNew.xml
index 1cbf8a5..2ced2d4 100644
--- a/bundles/org.eclipse.platform.doc.isv/topics_WhatsNew.xml
+++ b/bundles/org.eclipse.platform.doc.isv/topics_WhatsNew.xml
@@ -6,4 +6,5 @@
<toc label="What's new">
<topic href="whatsNew/platform_isv_whatsnew.html#Platform" label="Platform"/>
<topic href="whatsNew/platform_isv_whatsnew.html#SWT" label="SWT"/>
+ <topic href="whatsNew/platform_isv_whatsnew.html#JFace" label="JFace"/>
</toc>
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/dark-theme-swt-app.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/dark-theme-swt-app.png
deleted file mode 100644
index 0db838e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/dark-theme-swt-app.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/generic-editor-icon.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/generic-editor-icon.png
new file mode 100644
index 0000000..9b8dd82
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/generic-editor-icon.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/gtk-toolitem-padding.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/gtk-toolitem-padding.png
new file mode 100644
index 0000000..7416e32
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/gtk-toolitem-padding.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/progress-monitor.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/progress-monitor.png
new file mode 100644
index 0000000..79cfe17
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/progress-monitor.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-gtk.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-gtk.png
new file mode 100644
index 0000000..9258d58
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-gtk.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-mac.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-mac.png
new file mode 100644
index 0000000..a9342e0
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-mac.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-win.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-win.png
new file mode 100644
index 0000000..d59ecc0
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/styled-text-disabled-win.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/swt-snippet-explorer.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/swt-snippet-explorer.png
new file mode 100644
index 0000000..d2dd08c
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/swt-snippet-explorer.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/win32-text-search-cancel.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/win32-text-search-cancel.png
new file mode 100644
index 0000000..b4f13a7
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/win32-text-search-cancel.png
Binary files differ
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 e43be72..a35d48a 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
@@ -17,17 +17,18 @@
table.news tr td.content {vertical-align: top;}
ul {padding-left: 13px;}
</style>
-<title>Eclipse Platform What's New in 4.12</title>
+<title>Eclipse Platform What's New in 4.13</title>
</head>
<body>
-<h2>What's New in Eclipse 4.12</h2>
+<h2>What's New in Eclipse 4.13</h2>
<p>Here are descriptions of some of the changes of interest to plug-in developers
-made to the Eclipse Platform and SWT for the 4.12 release of Eclipse.
+made to the Eclipse Platform and SWT for the 4.13 release of Eclipse.
</p>
<ul>
<li><a href="#Platform">Platform Changes</a></li>
<li><a href="#SWT">SWT Changes</a></li>
+ <li><a href="#JFace">JFace Changes</a></li>
</ul>
<p>
@@ -48,242 +49,205 @@
<tr>
<td id="Platform" class="section" colspan="2"><h2>Platform Changes</h2></td>
</tr>
-
- <tr id="compare-merge-generic-editor"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545531 -->
- <td class="title">Compare/merge files using Generic Editor extensions</td>
+
+ <tr id="generic-editor-icon"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=513034 -->
+ <td class="title">Content-type-specific icons in generic editor</td>
<td class="content">
- To leverage the extensions for <b>Generic Editor</b> (syntax highlighting, hover...) when
- comparing files, you can now simply associate the <code>org.eclipse.ui.genericeditor.compareViewer</code>
- to the desired file content-types. This will automatically add to the compare view most extensions
- contributed to the Generic Editor.
- <pre>
-<extension point="org.eclipse.compare.contentMergeViewers">
- <contentTypeBinding
- contentMergeViewerId="org.eclipse.ui.genericeditor.compareViewer"
- contentTypeId="org.eclipse.wildwebdeveloper.parent"/>
-</extension></pre>
- </td>
- </tr>
-
- <tr id="quick-access-customization"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=162006 -->
- <td class="title">Extensible Quick Access content</td>
- <td class="content">
- The <b>Quick Access</b> search (accessible with <code>Ctrl+3</code> shortcut) now provides
- a new <code>org.eclipse.ui.quickAccess</code> extension point to contribute additional content.
- <p>Classes in package <code>org.eclipse.ui.quickaccess</code> have been made API for this use-case.</p>
+ An extension was added to the generic editor so that it now can provide icons for content-type. See extension point <b>org.eclipse.ui.genericeditor.icons</b> for more details.
<p>
- The following example shows how Run and Launch Configurations are made available in Quick Access:
- </p>
- <pre>
-<extension point="org.eclipse.ui.quickAccess">
- <computer class="org.eclipse.debug.internal.ui.quickaccess.RunQuickAccessProvider" name="%Run.name"/>
- <computer class="org.eclipse.debug.internal.ui.quickaccess.DebugQuickAccessProvider" name="%Debug.name"/>
-</extension></pre>
- <p>
- The computers implement the <code>org.eclipse.ui.quickaccess.IQuickAccessComputer</code> class, which
- is responsible for returning some <code>org.eclipse.ui.quickaccess.QuickAccessElement</code>.
- </p>
- <p>
- Computers are only contributing when their host bundle is started, bundles will not be started automatically
- when querying Quick Access.
+ <img src="images/generic-editor-icon.png" alt="" />
</p>
</td>
</tr>
+
+ <tr id="multiline-sfe"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548650 -->
+ <td class="title">Multiline Support for StringFieldEditor</td>
+ <td class="content">
+ The implementation of <code>StringFieldEditor</code> now provides the option to use a multi-line Text widget, suitable
+ for editing larger String values in a preference page.
+ </td>
+ </tr>
- <tr id="type-parameters-beans-jface-databinding"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=531748 -->
- <td class="title">Type parameters on Beans and JFace databinding classes</td>
- <td class="content">
- Type parameters have been added to relevant classes and methods in the
- <a href="https://help.eclipse.org/2019-06/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fapi%2Forg%2Feclipse%2Fcore%2Fdatabinding%2Fbeans%2Fpackage-summary.html">
- <code>org.eclipse.core.databinding.beans</code></a> and
- <a href="https://help.eclipse.org/2019-06/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fapi%2Forg%2Feclipse%2Fjface%2Fdatabinding%2Fswt%2Fpackage-summary.html">
- <code>org.eclipse.jface.databinding</code></a> bundles. This makes code using
- these classes more explicit and clear and can help catching bugs in an early stage.
- These changes complete the effort to use generics to improve the databinding framework,
- which was started several years ago. If you use these databinding bundles you should be
- able to get rid of many raw type warnings which have been unavoidable for a long time.
- <p>
- Example:
- </p>
-<pre>
-// The BeanProperties.value method returns a IBeanValueProperty<Bean, String>
-IObservableValue<String> nameModel =
- BeanProperties.value(Bean.class, "name", String.class).observe(bean);
-// The WidgetProperties.text method returns a IWidgetValueProperty<Text, String>
-IObservableValue<String> nameTarget = WidgetProperties.text().observe(textControl);
+ <tr id="request-specific-quickaccess"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548058 -->
+ <td class="title">API to compute Quick Access proposals according to user input</td>
+ <td class="content">
+ An extension interface <b><code>org.eclipse.ui.quickaccess.IQuickAccessComputerExtension</code></b> to use as extension to
+ <code>org.eclipse.ui.quickaccess.IQuickAccessComputer</code> when using extension point <code>org.eclipse.ui.quickaccess/computer</code>
+ was added. This provides the ability to compute a new extra set of proposals whenever filter change.
+ </td>
+ </tr>
-dataBindingContext.bindValue(nameTarget, nameModel);
-</pre>
- <p>
- The changes are fully binary compatible and no behaviour is changed.
- </p><p><b>Tips for using the typed databinding API</b>
+ <tr id="javax-injext">
+ <td class="title">Bundle org.eclipse.core.runtime no longer reexports javax.inject</td>
+ <td class="content">
+ The org.eclipse.core.runtime bundle had <code>javax.inject</code> as an <b>optional</b> dependency, which it
+ previously reexported, but not anymore.
+ <p>
+ Technically, it's not a breaking change as <code>javax.inject</code> was never
+ guaranteed to be there thus whether it is reexported or not was not certain. Eclipse Platform can not guarantee the API stability of this package so it makes no
+ sense to make such a promise.
+ </p>
+ <p>
+ Clients have to <code>Import-Package: javax.inject</code> explicitly if they need it.
+ </p>
+ </td>
+ </tr>
+
+ <tr id="non-persisted-ui"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544871 -->
+ <td class="title">E4XMIResource optionally filters Transient UI Elements</td>
+ <td class="content">
+ When using the E4XMIResource directly, transient UI elements are no longer filtered by default.
+ Note that transient UI elements are filtered by default when saved from the application.
+
+ <p>To filter transient UI elements, call the save method with the new option
+ <code>options.put(E4XMIResource.OPTION_FILTER_PERSIST_STATE, Boolean.TRUE); resource.save(options);</code></p>
+ </td>
+ </tr>
+ <tr id="logging-api"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=550347 -->
+ <td class="title">Simplified Platform logging API</td>
+ <td class="content">
+ Platform provides convenient logging API, <code>Platform.getLog(Class)</code> which can be used to access the log for the bundle to which the class belongs.
+ </td>
+ </tr>
+ <tr id="monitor-logging"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=482062 -->
+ <td class="title">Tracing option for correct progress reporting usage</td>
+ <td class="content">
+ Earlier releases added support for tracing the correct usage of progress monitors. Unfortunately, this was missed while documenting in previous noteworthy documents.
+
+ <p>To enable this tracing, add <code>org.eclipse.equinox.common/progress_monitors=true</code> in your ".options" file and start Eclipse via the -debug flag, or use the tracing option in the launch configuration.
</p>
- <ul>
- <li>
- Using the <code>UpdateValueStrategy.create</code> method to create update strategies with a converter
- avoids the need to specify type arguments:
-<pre>
-dataBindingContext.bindValue(ageTarget, ageModel,
- UpdateValueStrategy.create(converter), null);
-</pre>
- </li><li>
- It is often easier to work out the types when sub-expressions are assigned to variables:
-<pre>
-UpdateValueStrategy<String, Integer> toModel = new UpdateValueStrategy><();
-toModel.setConverter(converter);
-toModel.setAfterConvertValidator(validator);
-dataBindingContext.bindValue(target, model, toModel, null);
-</pre>
- </li><li>
- New methods for creating typed versions of property objects have been added in some places:
-<pre>
-// Returns a IViewerValuePropert<Viewer, ModelObject>
-ViewerProperties.singleSelection(ModelObject.class)
-</pre>
- </li><li>Upgrading to Java 10 lets you use the <code>var</code> keyword, which avoids much
- of the verbosity of using property objects with type parameters:
-<pre>
-var text = WidgetProperties.text();
-</pre>
- </li>
- </ul>
- <p>
- <b>Note about typed property factory classes:</b> To avoid causing compile errors for clients new versions of
- property factory classes that return typed property objects have been created. This applies for the
- following classes: <code>WidgetProperties</code>, <code>ViewerProperties</code>,
- <code>BeanProperties</code> and <code>PojoProperties</code>.
- </p><p>
- To start using these classes simply replace the import of the untyped factory classes by an import of the
- typed version.
- </p><p>
- <b>Note about EMF Databinding:</b> EMF Databinding has not been updated with type parameters. That can make it
- awkward to use EMF Databinding together with the generified databinding APIs. A good strategy for working
- around that is to create factory methods for EMF properties with generic types as their return values:
- </p>
-<pre>
-@SuppressWarnings("unchecked")
-public static IValueProperty<ModelEObject, String> name(EditingDomain editingDomain) {
- return EMFEditProperties.value(editingDomain, ModelPackage.Literals.MODEL_EOBJECT__NAME);
-}
-</pre>
-
- </td>
- </tr>
-
- <tr id="cnf-tooltip-support"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=178017 -->
- <td class="title">Tooltip support for CommonViewers</td>
- <td class="content">
- It is now possible to provide tooltips to <code>CommonViewer</code> via <code>ILabelProvider</code>.
- <p>To do this, two steps are necessary:</p>
- <ol>
- <li>Enable tooltip support for the respective viewer by setting the option <code>org.eclipse.ui.navigator.enableTooltipSupport</code> to
- <code>true</code> in the extension declaration, as in
-<pre>
-<extension point="org.eclipse.ui.navigator.viewer">
- <viewer id="org.eclipse.ui.example.cnf.viewer">
- <!-- ... -->
- <options>
- <b><property
- name="org.eclipse.ui.navigator.enableTooltipSupport"
- value="true" /></b>
- </options>
- </viewer>
-</extension>
-</pre></li>
- <li>Contribute an <code>ILabelProvider</code> which also implements <code>org.eclipse.jface.viewers.IToolTipProvider</code>.
- The tooltip text can be provided by the method <code>getToolTipText(Object element)</code>
- following the same rules as <code>getText(Object element)</code>. I.e., the non-null, non-empty string
- obtained from the highest-ranked label provider is used as the tooltip.
- </li>
- </ol>
- </td>
- </tr>
-
- <tr id="wizard-dialog-nonmodal"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=147762 -->
- <td class="title">Wizards can now be non-modal</td>
- <td class="content">
- New APIs have been added to <code>WizardDialog</code> to enable a wizard to be non-modal.
- <p>
- When a dialog is modal it means that the underlying window can not be used. Eclipse Wizard Dialogs are modal by default.
- There are cases where it is desired that the dialog is not modal but that the underlying window can be reached <b>while</b> the user is finishing the wizard.
- The following API methods are added to the JFace <code>WizardDialog</code> class.
- </p>
- <ul>
- <li><code>public WizardDialog setModal(boolean modal)</code></li>
- <li><code>public boolean isModal()</code></li>
- </ul>
- <p>
- In addition, the following methods have been made public to allow full control over the shell style of the <code>WizardDialog</code>.
- </p>
- <ul>
- <li><code>public void setShellStyle(int newShellStyle)</code></li>
- <li><code>public int getShellStyle()</code></li>
- </ul>
- <p>
- You can now use the following code:
- <code><br/>
- <br/>WizardDialog d = new WizardDialog(shell, wizard);
- <br/>d.setModal(false);
- <br/>d.open();
- </code>
- </p>
- <p>
- or fluent
- <code><br/><br/>
- new WizardDialog(shell, wizard).setModal(false).open();
- </code>
- </p>
- </td>
- </tr>
-
- <tr id="swt-lines-visible"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544360 -->
- <td class="title">CSS attribute swt-lines-visible</td>
- <td class="content">
- A new css attribute <code>'swt-lines-visible'</code> is supported on <code>Table</code> and <code>Tree</code> widgets and is mapped to <code>getLinesVisible()</code>.
- <p>
- For example: The value of this property is true if <code>Tree.getLinesVisible()</code> returns true, else the value is false.
+ <p>
+ <img src="images/progress-monitor.png" alt="" />
</p>
- </td>
+ </td>
</tr>
-
<!-- ******************** End of Platform ********************** -->
<!-- *********************** SWT *********************** -->
<tr>
<td id="SWT" class="section" colspan="2"><h2>SWT Changes</h2></td>
</tr>
-
- <tr id="dark-theme-mac"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=540357 -->
- <td class="title">Dark mode support on Mac</td>
- <td class="content">
- An SWT application on macOS 10.14 can now be launched in dark theme and all the controls are rendered with the native dark appearance.
- The application will automatically launch in the light or dark theme based on the System appearance (set in System preferences).
- <p>
- You need to launch the application with <code>org.eclipse.swt.display.useSystemTheme=true</code> system property to enable this behavior.
- The default value of this property is false.
- </p>
- Screenshot of an SWT application in dark theme:
- <p>
- <img src="images/dark-theme-swt-app.png" alt="swt application in dark theme"/>
- </p>
- </td>
+
+ <tr id="gdkpixbuf-imageloader"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545032 -->
+ <td class="title">New native implementation of ImageLoader on GTK</td>
+ <td class="content">
+ The implementation of <code>ImageLoader</code> on GTK now uses the native <code>GdkPixbuf</code> API for image loading and saving.
+ <p>
+ Key highlights of the new ImageLoader on GTK:
+ </p>
+ <ul>
+ <li>Loading and saving images has native performance, with a significant speedup especially in loading JPEG files</li>
+ <li>Better GIF animation support</li>
+ <li>Support for more image formats</li>
+ </ul>
+ </td>
</tr>
- <tr id="display-dispose-gtk"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=531634 -->
- <td class="title">Display.Close and Display.Dispose events sent on GTK on logoff/shutdown</td>
- <td class="content">
- <code>Display.Close</code> and <code>Display.Dispose</code> events are now supported on GTK on logoff/shutdown. This works on GNOME and XFCE (> 4.13) sessions. This brings Linux/GTK in line with the Windows and Mac implementations:
- <ul>
- <li><code>Display.Close</code> can set the <code>Event.doit</code> to <code>false</code> to send a "not ready" hint to the session manager. However, the session manager will usually ignore this hint and continue logoff/shutdown anyway. The time limit imposed by the session manager is 1 second, so it is not suitable for showing the user any UI.</li>
- <li><code>Display.Dispose</code> lets you run any final cleanup, such as saving settings on exit. Also, any code you have after a <code>while (!xxx.isDisposed())</code> loop will run now. The time limit imposed by the session manager is 10 seconds.</li>
- </ul>
- </td>
+ <tr id="gtk-toolitem-padding"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=395296 -->
+ <td class="title">Reduced ToolItem padding on GTK</td>
+ <td class="content">
+ A fix in <code>ToolItem</code> has greatly reduced the size of some toolbars on GTK.
+ <p>
+ Previously, all <code>ToolItem</code>s were the same size as the largest of them in a given toolbar. With this fix, items are
+ now independently sized, which reduces the total size of toolbars that contain large items.
+ </p>
+ <p>
+ EGit's Rebase Interactive view is a good example of this fix. In the following screenshot, the toolbar shown on top has
+ the fix applied, compared to the larger, unpatched toolbar on the bottom.
+ </p>
+ <p><img src="images/gtk-toolitem-padding.png" alt="ToolItems with reduced padding compared to before"/></p>
+ </td>
+ </tr>
+
+ <tr id="win32-text-search-cancel"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=293230 -->
+ <td class="title">Search/Cancel icons supported in Text widget on Windows</td>
+ <td class="content">
+ The Text widget on Windows now supports displaying the search and cancel icons for <code>SWT.ICON_SEARCH</code> and <code>SWT.ICON_CANCEL</code> styles respectively.
+ With the Windows support added, these style APIs are now supported on all the three platforms and are no longer marked as a <code>HINT</code>.
+ <p><img src="images/win32-text-search-cancel.png" alt="Text widget with search and clear buttons"/></p>
+ </td>
+ </tr>
+
+ <tr id="swt-is-dark-theme"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549451 -->
+ <td class="title">API to query if current OS theme is dark</td>
+ <td class="content">
+ A new method <code>public static boolean Display.isSystemDarkTheme()</code> is now available to query if the current OS theme has a dark appearance.
+ The method returns <code>true</code> if the current OS theme is dark, else it returns <code>false</code>.
+ </td>
+ </tr>
+
+ <tr id="swt-styled-text-disabled"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=4745 -->
+ <td class="title">StyledText now supports a disabled look</td>
+ <td class="content">
+ The StyledText widget now supports a disabled look on all platforms when <code>StyledText.setEnabled(false)</code> is called.
+ <p><img src="images/styled-text-disabled-gtk.png" alt=""/></p>
+ <p><img src="images/styled-text-disabled-win.png" alt=""/></p>
+ <p><img src="images/styled-text-disabled-mac.png" alt=""/></p>
+ </td>
+ </tr>
+
+ <tr id="swt-disabled-colors"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548190 -->
+ <td class="title">New color constants for disabled widgets</td>
+ <td class="content">
+ Two new color constants are available in SWT, to match the colors used in disabled widgets. <code>SWT.COLOR_TEXT_DISABLED_BACKGROUND</code> matches the background color of a disabled text widget, and
+ <code>SWT.COLOR_WIDGET_DISABLED_FOREGROUND</code> matches the foreground color of a disabled widget.
+ </td>
+ </tr>
+
+ <tr id="swt-snippet-explorer"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=547934 -->
+ <td class="title">SWT Snippet Explorer</td>
+ <td class="content">
+ The <a href="https://www.eclipse.org/swt/snippets/">SWT Snippets</a> project in the <a href="https://git.eclipse.org/c/platform/eclipse.platform.swt.git/">SWT repository</a> now includes a simple application called SnippetExplorer which can list, search and launch single or
+ multiple snippets at once. It also shows the snippets description, source code and a preview image where applicable.
+ <p><img src="images/swt-snippet-explorer.png" alt=""/></p>
+ </td>
+ </tr>
+
+ <tr id="swt-gtk-input-methods"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548628 -->
+ <td class="title">Input method switching on GTK</td>
+ <td class="content">
+ Early versions of GTK3 allowed the input method to be changed at the application level. This
+ functionality has been deprecated for quite some time, and has now been removed from SWT.
+ <p>To change the input method, please use the global input method settings available in the desktop environment.</p>
+ </td>
</tr>
<!-- *********************** End of SWT *********************** -->
+
+ <!-- *********************** JFace *********************** -->
+ <tr>
+ <td id="JFace" class="section" colspan="2"><h2>JFace Changes</h2></td>
+ </tr>
+
+ <tr id="columnViewEditor-cycleTabTraversal"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549194 -->
+ <td class="title">New ColumnViewerEditor tab traversal added</td>
+ <td class="content">
+ Tabbing to the start or end of a viewer (during an inline edit) is
+ now possible by passing
+ <b><code>ColumnViewerEditor.TABBING_CYCLE_IN_VIEWER</code></b> as a feature when calling
+ <code>TableViewerEditor.create(viewer,
+ editorActivationStrategy, feature)</code> or <code>TreeViewerEditor.create(viewer, editorActivationStrategy,
+ feature)</code>.
+ <p>
+ With this new feature flag enabled:
+ </p>
+ <ul>
+ <li>
+ Pressing <b>Tab</b> while editing the <b>last item</b> in a
+ viewer starts an inline edit on the <b>first item</b>.
+ </li>
+ <li>
+ Pressing <b>Shift+Tab</b> while editing the first item starts an
+ inline edit on the last item.
+ </li>
+ </ul>
+ </td>
+ </tr>
+ <!-- *********************** End of JFace *********************** -->
+
</tbody>
</table>
<!-- ****************** END OF N&N TABLE ****************** -->
</body>
-</html>
\ No newline at end of file
+</html>
diff --git a/bundles/org.eclipse.platform.doc.user/topics_WhatsNew.xml b/bundles/org.eclipse.platform.doc.user/topics_WhatsNew.xml
index 675cbac..f2779ed 100644
--- a/bundles/org.eclipse.platform.doc.user/topics_WhatsNew.xml
+++ b/bundles/org.eclipse.platform.doc.user/topics_WhatsNew.xml
@@ -4,7 +4,9 @@
<!-- Define topics for the What's New -->
<!-- ================================ -->
<toc label="What's new">
-<topic href="whatsNew/platform_whatsnew.html#ViewsAndDialogs" label="Views, Dialogs and Toolbar"/>
+<topic href="whatsNew/platform_whatsnew.html#ViewsAndDialogs" label="Views, Dialogs and Editors"/>
+<topic href="whatsNew/platform_whatsnew.html#Debug" label="Debug"/>
+<topic href="whatsNew/platform_whatsnew.html#Preferences" label="Preferences"/>
<topic href="whatsNew/platform_whatsnew.html#StylingThemes" label="Themes and Styling"/>
<topic href="whatsNew/platform_whatsnew.html#GeneralUpdates" label="Equinox"/>
</toc>
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/compare-editor-colors.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/compare-editor-colors.png
new file mode 100644
index 0000000..6b7ce6e
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/compare-editor-colors.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/correct_backgrounds.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/correct_backgrounds.png
new file mode 100644
index 0000000..4481ebb
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/correct_backgrounds.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/dark-theme-alternating-lines.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/dark-theme-alternating-lines.png
deleted file mode 100644
index 3aead8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/dark-theme-alternating-lines.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/environment-variable-context-menu.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/environment-variable-context-menu.png
new file mode 100644
index 0000000..cbfaaf0
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/environment-variable-context-menu.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/environment-variable-inline-editing.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/environment-variable-inline-editing.png
new file mode 100644
index 0000000..2932e6e
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/environment-variable-inline-editing.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/external-tool-showcommandline.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/external-tool-showcommandline.png
new file mode 100644
index 0000000..e949905
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/external-tool-showcommandline.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/freeze-event.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/freeze-event.png
new file mode 100644
index 0000000..73bbc32
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/freeze-event.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/help_system_dark.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/help_system_dark.png
new file mode 100644
index 0000000..e120254
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/help_system_dark.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/help_system_high_res.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/help_system_high_res.png
new file mode 100644
index 0000000..805040e
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/help_system_high_res.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/hidpi-mac-new-behavior.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/hidpi-mac-new-behavior.png
deleted file mode 100644
index 0964985..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/hidpi-mac-new-behavior.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/hidpi-mac-old-behavior.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/hidpi-mac-old-behavior.png
deleted file mode 100644
index 11a680a..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/hidpi-mac-old-behavior.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/long-dialog-text.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/long-dialog-text.png
new file mode 100644
index 0000000..e6349ae
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/long-dialog-text.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/pass-directory-to-launcher.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/pass-directory-to-launcher.png
deleted file mode 100644
index f1aff94..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/pass-directory-to-launcher.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/project-explorer-inline-normal.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/project-explorer-inline-normal.png
new file mode 100644
index 0000000..ed17b9d
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/project-explorer-inline-normal.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/quick-search.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/quick-search.png
new file mode 100644
index 0000000..5249630
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/quick-search.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/run-debug-quickaccess.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/run-debug-quickaccess.png
deleted file mode 100644
index 427fde7..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/run-debug-quickaccess.png
+++ /dev/null
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/save_project_explorer.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/save_project_explorer.png
new file mode 100644
index 0000000..4d02300
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/save_project_explorer.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/selection-count.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/selection-count.png
new file mode 100644
index 0000000..0fc8afd
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/selection-count.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/selection-offset.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/selection-offset.png
new file mode 100644
index 0000000..f500e26
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/selection-offset.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/short-dialog.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/short-dialog.png
new file mode 100644
index 0000000..d581a89
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/short-dialog.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/show_key_bindings.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/show_key_bindings.png
new file mode 100644
index 0000000..d520d29
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/show_key_bindings.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/showin_project_explorer.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/showin_project_explorer.png
new file mode 100644
index 0000000..c066707
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/showin_project_explorer.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/text-editors-color-intable.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/text-editors-color-intable.png
new file mode 100644
index 0000000..05e5ccc
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/text-editors-color-intable.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ui-monitor-preference.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/ui-monitor-preference.png
new file mode 100644
index 0000000..c59fd10
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/images/ui-monitor-preference.png
Binary files differ
diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/view_menu.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/view_menu.png
deleted file mode 100644
index b8708ab..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/view_menu.png
+++ /dev/null
Binary files differ
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 14d9381..feb0682 100644
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
+++ b/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
@@ -17,17 +17,19 @@
table.news tr td.content {vertical-align: top;}
ul {padding-left: 13px;}
</style>
-<title>Eclipse Platform What's New in 4.12</title>
+<title>Eclipse Platform What's New in 4.13</title>
</head>
<body>
-<h2>What's New in Eclipse 4.12 (Platform)</h2>
+<h2>What's New in Eclipse 4.13 (Platform)</h2>
<p>Here are descriptions of some of the more interesting or significant changes
-made to the Eclipse Platform for the 4.12 release of Eclipse. They are grouped into:</p>
+made to the Eclipse Platform for the 4.13 release of Eclipse. They are grouped into:</p>
<ul><!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
- <li><a href="#ViewsAndDialogs">Views, Dialogs and Toolbar</a></li>
+ <li><a href="#ViewsAndDialogs">Views, Dialogs and Editors</a></li>
+ <li><a href="#Debug">Debug</a></li>
+ <li><a href="#Preferences">Preferences</a></li>
<li><a href="#StylingThemes">Themes and Styling</a></li>
- <li><a href="#Equinox">Equinox</a></li>
+ <li><a href="#GeneralUpdates">General Updates</a></li>
</ul>
<p>
Plug-in developers will also be interested in the corresponding
@@ -43,132 +45,283 @@
<col />
</colgroup>
<tbody>
- <!-- ******************* Views, Dialogs and Wizards ************************************* -->
+
+ <!-- ******************* Views, Dialogs and Editors ************************************* -->
<tr>
<td id="ViewsAndDialogs" class="section" colspan="2">
- <h2>Views, Dialogs and Wizards </h2>
+ <h2>Views, Dialogs and Editors</h2>
+ </td>
+ </tr>
+
+ <tr id="quick-text-search"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548518 -->
+ <td class="title">Quick Search</td>
+ <td class="content">
+ The new <b>Quick Search</b> dialog provides a convenient, simple and fast way to run a textual
+ search across your workspace and jump to matches in your code. The dialog provides a quick overview
+ showing matching lines of text at a glance. It updates as quickly as you can type and allows for quick
+ navigation using only the keyboard. A typical workflow starts by pressing the keyboard shortcut <b>Ctrl+Alt+Shift+L </b>
+ (or<b> Cmd+Alt+Shift+L</b> on Mac). Typing a few letters updates the search result as you type. Use <b>Up-Down</b> arrow keys
+ to select a match, then hit <b>Enter</b> to open it in an editor.
+ <p>
+ <img src="images/quick-search.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <tr id="save-action-project-explorer"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=211520 -->
+ <td class="title">Save editor when Project Explorer has focus</td>
+ <td class="content">
+ You can now save the active editor even when the <b>Project Explorer</b> has focus. In cases where an extension contributes <b>Saveables</b> to the Project Explorer,
+ the extension is honored and the save action on the Project Explorer will save the provided saveable item instead of the active editor.
+ <p>
+ <img src="images/save_project_explorer.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <tr id="showin-action-project-explorer"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=314642 -->
+ <td class="title">"Show In" context menu available for normal resources</td>
+ <td class="content">
+ The <b>Show In</b> context menu is now available for an element inside a resource project on the <b>Project Explorer</b>.
+ <p>
+ <img src="images/showin_project_explorer.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <tr id="project-explorer-normal-resource-inline-rename"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548877 -->
+ <td class="title">Inline rename for normal resources while in Project Explorer</td>
+ <td class="content">
+ In the <b>Project Explorer</b>, renaming (with the <b>F2</b> shortcut or <b>Rename</b> context-menu) will start an inline rename for normal resources.
+ After hitting the Enter key, a dialog will let you review the rename operation before performing the rename.
+ <p>
+ <img src="images/project-explorer-inline-normal.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <tr id="colors-in-compareviewer"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=450320 -->
+ <td class="title">Show colors for additions and deletions in Compare viewer</td>
+ <td class="content">
+ In simple cases such as a 2-way comparison or a 3-way comparison with no merges and conflicts, the <b>Compare Viewer</b> now shows different colors,
+ depending on whether text has been added, removed or modified. The default colors are green, red and black respectively.
+ <p>
+ <img src="images/compare-editor-colors.png" alt=""/>
+ </p>
+ <p>
+ The colors can be customized through usual theme customization approaches, including using related entries in the <b>Colors and Fonts</b>
+ preference page.
+ </p>
</td>
</tr>
- <tr id="pass-directory-to-launcher"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=500388 -->
- <td class="title">Import project by passing it as command-line argument</td>
+ <tr id="editor-status-line"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549604 -->
+ <td class="title">Editor status line shows more selection details</td>
<td class="content">
- You can import a project into Eclipse by passing its path as a parameter to the launcher.
- The command would look like <code>eclipse /path/to/project</code> on Linux and Windows, or
- <code>open Eclipse.app -a /path/to/project</code> on macOS.
+ The status line for <b>Text Editors</b> now shows the cursor position, and when the editor has something selected,
+ shows the number of characters in the selection as well. This also works in the block selection mode.
<p>
- <img src="images/pass-directory-to-launcher.png" alt="" />
- </p>
+ These two new additions to the status line can be disabled via the <b>General > Editors > Text Editors</b> preference page.
+ </p>
+ <p>
+ <img src="images/selection-count.png" alt=""/>
+ </p>
+ <p>
+ <img src="images/selection-offset.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <tr id="shorter-dialog-texts"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549939 -->
+ <td class="title">Shorter dialog text</td>
+ <td class="content">
+ Several dialog texts have been shortened. This allows you to capture the important information faster.
+ <p>Previously:</p>
+ <p>
+ <img src="images/long-dialog-text.png" alt=""/>
+ </p>
+ <p>Now:</p>
+ <p>
+ <img src="images/short-dialog.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <tr id="close-project-via-middle-click"><!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=549894 -->
+ <td class="title">Close project via middle-click</td>
+ <td class="content">
+ In the <b> Project Explorer</b>, you can now close a project using middle-click.
</td>
</tr>
- <tr id="launch-config-quickaccess"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=545544 -->
- <td class="title">Launch Run and Debug configurations from Quick Access</td>
- <td class="content">
- From the <b>Quick Access</b> proposals (accessible with <code>Ctrl+3</code> shortcut) you can now
- directly launch any of the Run or Debug configurations available in your workspace.
+ <!-- ******************* End of Views, Dialogs and Editors ************************************* -->
+
+ <!-- ****************** Debug ************************************* -->
+ <tr>
+ <td id="Debug" class="section" colspan="2">
+ <h2>Debug </h2>
+ </td>
+ </tr>
+
+ <tr id="environment-table-improvements"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548344 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=548520 -->
+ <td class="title">Improved usability of Environment tab in Launch Configurations</td>
+ <td class="content">
+ In the <b>Environment Tab</b> of the <b>Launch Configuration</b> dialog, you can now double-click on an environment variable name or value and start editing it directly from the table.
<p>
- <img src="images/run-debug-quickaccess.png" alt="" />
+ <img src="images/environment-variable-inline-editing.png" alt=""/>
</p>
+ Right-clicking on the environment variable table now opens a context menu, allowing for quick addition, removal, copying, and pasting of environment variables.
<p>
- <b>Note:</b> For performance reasons, the extra <b>Quick Access</b> entries are only visible if the <code>org.eclipse.debug.ui</code>
- bundle was already activated by some previous action in the workbench such as editing a launch configuration, or expanding the
- <i>Run As...</i> menus.
+ <img src="images/environment-variable-context-menu.png" alt=""/>
</p>
</td>
</tr>
- <!-- ******************* End of Views, Dialogs and Toolbar ************************************* -->
+
+ <tr id="external-tool-showcommandline"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548886 -->
+ <td class="title">Show Command Line for external program launch</td>
+ <td class="content">
+ The <b>External Tools Configuration</b> dialog for launching an external program now supports the <b>Show Command Line</b> button.
+ <p>
+ <img src="images/external-tool-showcommandline.png" alt=""/>
+ </p>
+ </td>
+ </tr>
+
+ <!-- ****************** End of Debug ************************************* -->
<!-- ****************** Preferences ************************************* -->
- <!--
<tr>
<td id="Preferences" class="section" colspan="2">
<h2>Preferences </h2>
</td>
</tr>
- -->
+
+ <tr id="close-editors-automatically"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=490353 -->
+ <td class="title">Close editors automatically when reaching 99 open editors</td>
+ <td class="content">
+ The preference to close editors automatically is now enabled by default. It will be triggered when you have opened 99 files.
+ If you continue to open editors, old editors will be closed to protect you from performance problems.
+ You can modify this setting in the <b>Preferences</b> dialog via the <b>General > Editors > Close editors automatically</b> preference.
+ </td>
+ </tr>
+
+ <tr id="text-editors-color-preview">
+ <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548057 -->
+ <td class="title">In-table color previews for Text Editor appearance color options</td>
+ <td class="content">
+ You can now see all the colors currently being used in <b>Text Editors</b> from the Appearance color
+ options table, located in the <b>Preferences > General > Editors > Text Editor</b> page.
+ <p>
+ <img src="images/text-editors-color-intable.png" alt="" />
+ </p>
+ </td>
+ </tr>
+
+ <tr id="ui-freeze-monitor">
+ <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548385 -->
+ <td class="title">Automatic detection of UI freezes in the Eclipse SDK</td>
+ <td class="content">
+ The Eclipse SDK has been configured to show stack traces for UI freezes in the <b>Error Log</b> view by default for new workspaces.
+ You can use this information to identify and report slow parts of the Eclipse IDE.
+ <p>
+ <img src="images/freeze-event.png" alt="" />
+ </p>
+ You can disable the monitoring or tweak its settings via the options in the <b>General > UI Responsiveness Monitoring</b> preference page as shown below.
+ <p>
+ <img src="images/ui-monitor-preference.png" alt="" />
+ </p>
+
+ </td>
+
+ </tr>
+
<!-- ****************** End of Preferences ************************************* -->
- <!-- ******************* Themes and Styling ************************************* -->
- <tr>
- <td id="StylingThemes" class="section" colspan="2">
- <h2>Themes and Styling </h2>
- </td>
- </tr>
-
- <tr id="view-menu"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=466511 -->
- <td class="title">Improved View Menu Icon</td>
- <td class="content">
- The icon used for the view menu has been improved. It is now crisp on high
- resolution displays and also looks much better in the dark theme.
- <p>Compare the old version at the top and the new version at the bottom:</p>
- <p>
- <img src="images/view_menu.png" alt="" />
- </p>
- </td>
- </tr>
-
- <tr id="mac-hidpi"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=489451 -->
- <td class="title">High resolution images drawn on Mac</td>
- <td class="content">
- On Mac, images and text are now drawn in high resolution during GC operations.
- You can see crisp images on high resolution displays in the editor rulers, forms, etc in Eclipse.
- <p>Compare the old version at the top and the new version at the bottom:</p>
- <p>
- <img src="images/hidpi-mac-old-behavior.png" alt="" />
- </p>
- <p>
- <img src="images/hidpi-mac-new-behavior.png" alt="" />
- </p>
- </td>
- </tr>
-
- <tr id="dark-theme-background-lines"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544360 -->
- <td class="title">Table/Tree background lines shown in dark theme on Mac</td>
- <td class="content">
- In dark theme on Mac, the <code>Table</code> and <code>Trees</code> in Eclipse now show the alternating dark lines
- in the background when <code>setLinesVisible(true)</code> is set.
- Earlier they had a gray background even if line visibility was true.
- <p>
- Example of a Tree and Table in Eclipse with alternating dark lines in the background:
- </p>
- <p>
- <img src="images/dark-theme-alternating-lines.png" alt="Tree and Table in Eclipse with alternating dark lines in the background" />
- </p>
- </td>
- </tr>
- <!-- ******************* End of Themes and Styling ************************************* -->
+ <!-- ******************* Themes and Styling ************************************* -->
+ <tr>
+ <td id="StylingThemes" class="section" colspan="2">
+ <h2>Themes and Styling </h2>
+ </td>
+ </tr>
-
- <!-- ******************* Equinox ************************************* -->
- <tr>
- <td id="Equinox" class="section" colspan="2">
- <h2>Equinox</h2>
+ <tr id="start-in-dark-theme"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=547038 -->
+ <td class="title">Start automatically in dark theme based on OS theme</td>
+ <td class="content">
+ On Linux and Mac, Eclipse can now start automatically in dark theme when the OS theme is dark.
+ This works by default, that is on a new workspace or when the user has not explicitly set or changed the theme in Eclipse.
+ </td>
+ </tr>
+
+ <tr id="help-system-dark"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=532185 -->
+ <td class="title">Display of Help content respects OS theme</td>
+ <td class="content">
+ More and more operating systems provide a system wide dark theme. Eclipse now respects this system wide theme setting
+ when the Eclipse help content is displayed in an external browser. A prerequisite for this is a browser that supports
+ the <em><a href="https://caniuse.com/#search=prefers-color-scheme">prefers-color-scheme</a></em> CSS media query.
+ <p>
+ As of writing this the following browser versions support it:
+ </p>
+ <ul>
+ <li>Firefox version 67</li>
+ <li>Chrome version 76</li>
+ <li>Safari version 12.1</li>
+ </ul>
+ <img src="images/help_system_dark.png" alt="Eclipse help content in dark theme" style="width: 100%"/>
</td>
- </tr>
-
- <tr id="parallel-bundle-activation"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=540507 -->
- <td class="title">Support activating bundles in parallel</td>
- <td class="content">
- When the <b>Equinox OSGi Framework</b> is launched the installed bundles are activated
- according to their configured start-level. The bundles with lower start-levels are
- activated first. Bundles within the same start-level are activated sequentially from
- a single thread.
+ </tr>
+
+ <tr id="help-system-svg"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=548008 -->
+ <td class="title">Help content uses high resolution icons</td>
+ <td class="content">
+ The <b>Help System</b> as well as the help content of the <b>Eclipse Platform</b>, the <b>Java Development Tooling</b> and
+ the <b>Plug-in Development Environment</b> now use high resolution icons.
+ They are now crisp on high resolution displays and also looks much better in the dark theme.
<p>
- A new configuration option <code>equinox.start.level.thread.count</code> has been added
- that enables the framework to start bundles within the same start-level in parallel. The
- default value is <code>1</code> which keeps the previous behavior of activating bundles from a
- single thread. Setting the value to <code>0</code> enables parallel activation using a
- thread count equal to <code>Runtime.getRuntime().availableProcessors()</code>. Setting the
- value to a number greater than <code>1</code> will use the specified number as the thread
- count for parallel bundle activation.
- </p>
- <p>The default is <code>1</code> because of the risk of possible deadlock when
- activating bundles in parallel. Extensive testing must be done on the set of bundle
- installed in the framework before considering enabling this option in a product.</p>
+ <img src="images/help_system_high_res.png" alt="Eclipse help with high resolution icons" style="width: 100%"/></p>
</td>
- </tr>
- <!-- ******************* End of Equinox ************************************* -->
+ </tr>
+
+ <tr id="styling-forms"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549969 -->
+ <td class="title">Improved dark theme on Windows</td>
+ <td class="content">
+ Labels, Sections, Checkboxes, Radio Buttons, FormTexts and Sashes on forms now use the correct background color in the dark mode on windows.
+ <p>
+ <img src="images/correct_backgrounds.png" alt="Old and New styling of forms" style="width: 100%"/>
+ </p>
+ </td>
+ </tr>
+ <!-- ******************* End of Themes and Styling ************************************* -->
+
+ <!-- ******************* General Updates ************************************* -->
+ <tr>
+ <td id="GeneralUpdates" class="section" colspan="2">
+ <h2>General Updates </h2>
+ </td>
+ </tr>
+ <tr id="ui-performance"> <!-- multiple bugs -->
+ <td class="title">Interactive performance</td>
+ <td class="content">
+ Interactive performance has been further improved in this release and several UI freezes have been fixed.
+ </td>
+ </tr>
+
+ <tr id="show-keybinding"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=540440 -->
+ <td class="title">Show key bindings when command is invoked</td>
+ <td class="content">
+ For presentations, screen casts and learning purposes, it is very helpful to show the corresponding
+ key binding when a command is invoked. When the command is invoked (via a key
+ binding or menu interaction) the key binding, the command's name and description are shown
+ on the screen.
+ <p>
+ <img src="images/show_key_bindings.png" alt="Key binding of triggered command shown on screen" style="width: 90%"/>
+ </p>
+ <p>
+ You can activate this in the <b>Preferences</b> dialog via the <em>Show key binding when command is invoked</em> check box on the <b>General > Keys</b> preference page.
+ To toggle this setting quickly the command 'Toggle Whether to Show Key Binding' can be used (e.g. via the quick access).
+ </p>
+ </td>
+ </tr>
+ <!-- ******************* End of General Updates ************************************* -->
</tbody>
</table>
<!-- ****************** END OF N&N TABLE ****************** -->
