Plug-in Development Environment
Dialogs, Wizards and Views
|Eclipse views with browser technology||
It is possible to create views and editors with browser technology instead of SWT.
To showcase this, a new Plug-in Template is available when creating
a new project or a new view.
The views can be created using Eclipse with PDE only, but the inclusion of web technology like the Wild Web Developer plug-in is recommended.
You can create a plug-in with a browser-technology-view via: File > New > Other... > Plug-in Project.
On the last page of the wizard, you can select the template.
Press Next to select the type of content you want to experiment with.
The wizards are also accessible when you create a new view via the Extensions tab of the Manifest editor.
This Game view shows how you run a standalone web application inside a view.
|Context Spy added to PDE||
The Context Spy allows to view the key/values available for dependency injection.
This view has been migrated to PDE.
|Bundle Spy added to PDE||The Bundle Spy allows to view the state of the OSGi bundles and is now available via PDE.|
|Expand all, Collapse all button in target editor||
It is now possible to expand all locations in the Target Editor.
If the locations are expanded, it is possible to collapse all as shown below.
|Reference an existing target inside another one||
It is now possible to reference an existing target file inside another target:
This could be used for different purposes:
|Reexport removal is reported||
|API analysis parallel to the build job||
To improve workflow and save time for plug-in developers, API analysis is executed now parallel to the build job.
This feature might sometimes not work as expected - therefore a new preference is available in the
General > Plug-in Development > Run API analysis parallel to the build job
|Improved launching of Eclipse/Equinox applications||
Launching Eclipse and Equinox applications based on features has been reworked:
When you Add Required Plug-ins to a plug-in based Eclipse/Equinox application launch, 'test'-fragments are not added anymore only because their host participates in the launch. The same applies for launches based on features where requirements are added automatically. Furthermore the handling of multiple versions of bundles with the same symbolic-name has been refined for plug-in and feature based launches.