| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="../new_and_noteworthy.xsl"?> |
| <release |
| name="3.2 M6" |
| root="../../.." |
| > |
| <component name="XML"> |
| <item title="Full XML Catalog Preferences"> |
| <description> |
| <img src="sourceeditor/xml-catalog-editing.png" alt="Improved XML Catalog Preference Page"/><br/> |
| The XML Catalog page now supports creating all kinds of XML catalog elements, notably: |
| <ul> |
| <li>Rewrite entries (where a starting prefix is exchanged for another)</li> |
| <li>Suffix matching</li> |
| <li>Delegate catalogs (i.e. catalogs included if the URI being sought after matches a given prefix)</li> |
| </ul> |
| Relevant editors (XML, XML Schema, XLS) now support these catalog entry types for hyperlinking and navigation.<br/> |
| Thanks to Holger Voormann for the icons! |
| </description> |
| </item> |
| <item title="Quick Outline"> |
| <description> |
| <p> |
| The XML editor provides a Quick Outline that has a filterable set of elements. Selecting an element from the quick outline |
| will highlight the corresponding element in the source editor.</p> |
| <img src="sourceeditor/xml_quick_outline.png"></img> |
| </description> |
| </item> |
| <item title="Paged Content Assist Cycling"> |
| <description> |
| <p>Content assist in the XML editor now has multiple pages. This new functionality |
| creates an identical user experience to that of Java editors. The default, or |
| first page, of content assist still displays the same results, by default, as |
| the old content assist did but subsequent invocations of content assist will |
| display different pages of content assist suggestions.</p> |
| <img src="sourceeditor/xml_ca_pages.png"></img> |
| <p>The order in which results are displayed on the default content assist page and the |
| order in which subsequent pages are displayed are user configurable through a new |
| preference page.</p> |
| <img src="sourceeditor/xml_ca_pref.png"></img> |
| </description> |
| </item> |
| </component> |
| |
| <component name="HTML"> |
| <item title="Quick Outline"> |
| <description> |
| <p> |
| The HTML editor provides a Quick Outline that has a filterable set of elements. Selecting an element from the quick outline |
| will highlight the corresponding element in the source editor.</p> |
| <img src="sourceeditor/html_quick_outline.png"></img> |
| </description> |
| </item> |
| <item title="Paged Content Assist Cycling"> |
| <description> |
| <p>Content assist in the HTML editor now has multiple pages. This new functionality |
| creates an identical user experience to that of Java editors. The default, or |
| first page, of content assist still displays the same results, by default, as |
| the old content assist did but subsequent invocations of content assist will |
| display different pages of content assist suggestions.</p> |
| <img src="sourceeditor/html_ca_pages.png"></img> |
| <p>The order in which results are displayed on the default content assist page and the |
| order in which subsequent pages are displayed are user configurable through a new |
| preference page.</p> |
| <img src="sourceeditor/html_ca_pref.png"></img> |
| </description> |
| </item> |
| </component> |
| |
| <component name="JSP"> |
| <item title="Quick Outline"> |
| <description> |
| <p> |
| The JSP editor provides a Quick Outline that has a filterable set of elements. Selecting an element from the quick outline |
| will highlight the corresponding element in the source editor.</p> |
| <img src="sourceeditor/jsp_quick_outline.png"></img> |
| </description> |
| </item> |
| <item title="Paged Content Assist Cycling"> |
| <description> |
| <p>Content assist in the JSP editor now has multiple pages. This new functionality |
| creates an identical user experience to that of Java editors. The default, or |
| first page, of content assist still displays the same results, by default, as |
| the old content assist did but subsequent invocations of content assist will |
| display different pages of content assist suggestions.</p> |
| <img src="sourceeditor/jsp_ca_pages.png"></img> |
| <p>The order in which results are displayed on the default content assist page and the |
| order in which subsequent pages are displayed are user configurable through a new |
| preference page.</p> |
| <img src="sourceeditor/jsp_ca_pref.png"></img> |
| </description> |
| </item> |
| </component> |
| |
| <component name="CSS"> |
| <item title="Quick Outline"> |
| <description> |
| <p> |
| The CSS editor provides a Quick Outline that has a filterable set of elements. Selecting an element from the quick outline |
| will highlight the corresponding element in the source editor.</p> |
| <img src="sourceeditor/css_quick_outline.png"></img> |
| </description> |
| </item> |
| </component> |
| |
| <!-- |
| <component name="JSDT"> |
| <item title=""> |
| <description> |
| </description> |
| </item> |
| </component> |
| --> |
| <component name="JSDT Debug"> |
| <item title="JSDI API"> |
| <description> |
| <p>The JavaScript Debug Interface (JSDI) is an API that consumers can implement to hook into |
| the use of the debug core and UI bundles. Implementing SDI for a particular scenario allows |
| consumers to take advantage of the debug model and UI for <em>free</em></p> |
| <p> |
| JSDI is provided as new API in the <code>/org.eclipse.wst.jsdt.debug.core</code> bundle in the packages: |
| <ul> |
| <li><code>org.eclipse.wst.jsdt.debug.core.jsdi</code> - which contains the core JSDI descriptions |
| for debug elements and JavaScript values |
| </li> |
| <li><code>org.eclipse.wst.jsdt.debug.core.jsdi.connect</code> - which contains descriptions of debug client |
| connectors that are used to plug into the core launching framework |
| </li> |
| <li><code>org.eclipse.wst.jsdt.debug.core.jsdi.event</code> - which contains descriptions of all of the events |
| JSDI handles while debugging |
| </li> |
| <li><code>org.eclipse.wst.jsdt.debug.core.jsdi.request</code> - which contains descriptions of all of the kinds |
| of requests that can be sent using JSDI |
| </li> |
| </ul> |
| </p> |
| </description> |
| </item> |
| <item title="Breakpoint Participants"> |
| <description> |
| <p> |
| Breakpoint participants can be contributed by consumers to take part in the suspension of any of the supported |
| breakpoint types (function, line or script load). They can be provided via the <code>org.eclipse.wst.jsdt.debug.core.breakpointParticipants</code> |
| extension point. |
| |
| </p> |
| <p> |
| Rhino provides an implementation that participates in the suspension of all breakpoint types:<br/><br/> |
| <pre> |
| <code> |
| <extension point="org.eclipse.wst.jsdt.debug.core.breakpointParticipants"> |
| <participant |
| class="org.eclipse.wst.jsdt.debug.internal.rhino.breakpoints.RhinoBreakpointParticipant" |
| kind="*"> |
| </participant> |
| </extension> |
| </code> |
| </pre> |
| </p> |
| </description> |
| </item> |
| <item title="Line Breakpoints"> |
| <description> |
| <p> |
| Like any other, the JavaScript debugger provides line breakpoints. These can be set using the standard methods |
| such as toggling in the editor, from the outline view or using Ctrl+Shift+B in source. |
| </p> |
| <img src="jsdtdebug/line-bp.png" alt="JavaScript Line Breakpoint"></img> |
| </description> |
| </item> |
| <item title="Function Breakpoints"> |
| <description> |
| <p> |
| Function breakpoints are supported similarly to JDT, where you can suspend on entry or exit from a function. |
| These can be set using the standard methods such as toggling in the editor, from the outline view or using Ctrl+Shift+B in source. |
| </p> |
| <img src="jsdtdebug/function-bp.png" alt="JavaScript Function Breakpoint"></img> |
| </description> |
| </item> |
| <item title="Script Load Breakpoints"> |
| <description> |
| <p>Script load breakpoints can be set per JavaScript to suspend execution when that particular script is loaded. |
| This feature provided by a toolbar action in the Breakpoints View. |
| </p> |
| <img src="jsdtdebug/script-load-bp-chooser.png" alt="JavaScript Script Selection Dialog"></img> |
| <p> |
| Example of a script load breakpoint |
| </p> |
| <img src="jsdtdebug/script-load-bp.png" alt="JavaScript Load Breakpoint"></img> |
| </description> |
| </item> |
| <item title="Breakpoint Detail Panes"> |
| <description> |
| <p> |
| For each of the breakpoint types we support there are accompanying details panes for the new Breakpoints View. |
| Each detail pane allows you to quickly make changes to that kind of breakpoint. |
| </p> |
| <img src="jsdtdebug/function-details.png" alt="Function Breakpoint Detail Pane"></img> |
| </description> |
| </item> |
| <item title="Breakpoint Properties"> |
| <description> |
| <p> |
| Each breakpoint type has its own properties page that is opened via the Breakpoint View using the |
| standard Alt+Enter key binding or the context menu. |
| </p> |
| <img src="jsdtdebug/function-properties.png" alt="Function Breakpoint Properties"></img> |
| </description> |
| </item> |
| <item title="Suspend when any script loads"> |
| <description> |
| <p> |
| Even with support to suspend when a particular script loads, it is extremely useful to be able to know when |
| any given script loads. This is particularly useful for know when: |
| <ul> |
| <li>An evaluated script loads and you want to be able to step through it during the evaluation</li> |
| <li>You are trying to find our what scripts are loaded in what order</li> |
| <li>You are trying to find a particular script and don't know its name or have it in your workspace</li> |
| </ul> |
| This feature is provided by a view action in the Breakpoints View. |
| </p><br/><br/> |
| <img src="jsdtdebug/any-script-load.png" alt="Suspend when any script is loaded"></img> |
| </description> |
| </item> |
| <item title="Universal Launching Support"> |
| <description> |
| <p> |
| To support remote debugging we support a reusable UI that consumers get for <em>free</em> when they provide a JSDI launching connector. |
| <br/><br/> |
| The following example is the UI for Rhino launching connector. |
| </p> |
| <img src="jsdtdebug/rhino-connector.png" alt="Rhino Launching Connector UI"></img> |
| </description> |
| </item> |
| <item title="Watch Expressions"> |
| <description> |
| <p>Watch expressions can be added to a debug session in the same manner as JDT. They are re-evaluated after stepping |
| operations and are persisted across workbench invocations. |
| </p> |
| <img src="jsdtdebug/watchexpression.png" alt="JavaScript watch expression"></img> |
| </description> |
| </item> |
| <item title="Rhino Debug Support"> |
| <description> |
| <p> |
| JSDT Debug provides a base implementation of JSDI in the form of Rhino debug support. This support includes: |
| <ul> |
| <li>A Rhino launching connector</li> |
| <li>A Rhino debug client to enable remote debugging</li> |
| <li>Source lookup</li> |
| <li>Breakpoint participants</li> |
| <li>The Rhino console</li> |
| </ul> |
| </p> |
| </description> |
| </item> |
| </component> |
| <!-- |
| <component name="XML Schema"> |
| </component> |
| --> |
| </release> |
