|
|
|||||
| Support
for Eclipse 3.1 M6 |
The Visual Editor
is now
compatible with Eclipse
3.1 M6, GEF 3.1 and EMF 2.1. |
||||
|
|
|||||
|
Ability
to create and edit RCP
Views |
The
Visual Editor can now be used to create an RCP View in a RCP enabled
plugin project![]() The template created has a default Composite that can be used as the ViewPart's client area
![]() To compose the ViewPart select SWT controls from the palette as described in Help > Contents and Using the visual editor for Java |
||||
|
|
|||||
| The Visual Editor now uses
caches which (once created) reduces loading time by 30% on an average.
The cached model
can be cleared by performing a clean
operation on the project concerned (Project > Clean...). Details of
the performance improvement effort can be
found here.
(61944) |
|||||
|
|
|||||
| The SWT font and color property
editors have improved JFace support built into them. JFace resources do
not require one to explicitly dispose them. Color property editor : ![]() Font property editor: ![]() |
|||||
|
|
|||||
| The Visual Editor is now capable
of better editing TableColumns in both SWT and Swing. It is possible to add table columns directly to the table instead of only to the Java Beans view. Table columns can also be reordered directly in graphical editor. ![]() Also it is possible to set column header text directly from the graphical editor ![]() |
|||||
|
|
|||||
| The Visual Editor is now capable
of working in a plugin based environment where necessary resources are
obtained from a (potentially different) target platform. This allows
for one to use the
Visual Editor in the development of RCP
applications which use the
plugin based environment. |
|||||
|
|
|||||
The Visual Editor's Java Bean launcher is now capable
of launching and showing the contents of RCP Views, with out the need
to run a full RCP application.![]() The RCP View once launched: ![]() |
|||||
|
|
|||||
| The Visual Editor edits and
launches RCP Views based on the current platform's preferences for a
View's tabs. If a user prefers tabs at the bottom and not be traditional style as indicated below: ![]() Then Visual Editor edits based on the preferences: ![]() Also it launches the file being edited based on the preferences: ![]() |
|||||
|
|
|||||
| The Visual Editor now
understands complex source patterns for an argument to a method. It can
understand most combinations of source as long as the entities making
up the argument are modeled. Example: The complex argument statement ![]() creates the below simple application containing a JButton. ![]() Earlier versions of the Visual Editor were incapable of handling such an expression and would result in ![]() |
|||||
The
Visual Editor now supports the new SWT controls in 3.1
|
|||||
|
|
|||||
The
New Java Visual Class
wizard added an Application style to help users develop more
powerful applications. ![]() which generates an application containing commonly used menus and event handlers already built into it ![]() Similarly the Shell style in the SWT category has also been updated. The New Java Visual Class wizard also has improved error checking built into it |
|||||
|
|
|||||
The Visual Editor now allows a
user to re-parent an SWT Shell. This is helpful for users wanting to
create dialogs and other shells from an SWT application.
|
|||||
The Visual Editor has an
improved code generation pattern which puts new expressions in the
source in a more understandable manner. It groups together expressions
of a bean based on priority and dependency checks. (91731)
|
|||||
|
|
|||||
| The Visual Editor now has a
tutorial which details the various means by which it can be extended.
The tutorial can be found here. |
|||||