RAP 1.0 M4 - New and Noteworthy
This document will become the New and Noteworthy page for the next milestone release and meanwhile serves to document the development progress.
All features documented here can be obtained from CVS HEAD.
The RWT-API classes now provide Java-Doc comments. These comments are adapted from the SWT library since RWT implements a subset of SWT. The revision of the comments is not completed yet and there may be also some anticipations of implementation details that ment to be available in the 1.0 release. If you find inconsistencies in the docs, please report them to us so that we can resolve them.
RWT now supports untyped events. Note that this implementation exists for reuse of JFace and Workbench code only. If you write application code we recommend to use the typed events furthermore. Note also that there is still some work to do and that not all of the untyped event fields already provide meaningful values. In particular the doit flag does not work.
|Move to JFace 3.3||
You're reading it right - JFace 3.3 is here! This time, we used the complete JFace 3.3 codebase and stripped down the things not working (at the moment). As we can't support everything out of the box, here is a short list of things you can now use in your RAP application besides the already known stuff.
There are many more things in the JFace 3.3 codebase - just get it and play around with it. We're open for all bug reports regarding the (new) components.
Note that some of the components (like DoubleclickEvent, ViewerFilter or the Wizard framework) are now part of the demo application.
RAP JFace implementation related to the following packages is excluded:
Most of them will follow but there is a need for some new infrastructure first. At the moment, you'll find the java files of the excluded components but they are commented out to avoid confusion using "Organize Imports" or "Open Type".
|Support for opening/closing workbench parts||
You have now several possibilities to open a new view without initially defining it in your perspective.
On the one side, you can use
Another way is - like you know it from the Eclipse Workbench - to use the "Show View" menu. To implement
it in your RAP application, use
For all the views without a shortcut, there is a "Other..." item appended to the end of the list to
display the so loved "Show View" dialog where you can browse all available views. HINT: Now you can also
categorize your views - just define the
|Move extension points to org.eclipse.ui namespace||
To provide as much as possible reuse of RCP knowledge (and code) RAP provides now its workbench extension-points under the same namespace as the RCP workbench does. This is the second step of moving RAP to a subset of RCP regarding RCP-like functionality. Note that you must adjust your existing plugin.xml files like the example below:
|Move package org.eclipse.ui.entrypoint to org.eclipse.ui.application||
Due to the efforts of making RAP-APIs a subset to RCP-APIs the package org.eclipse.ui.entrypoint has been moved to org.eclipse.ui.application despite the fact that there is no need for implementing IPlatformRunnable as application definition. Please use the organize import functionality of the Eclipse IDE to adjust your existing source code.
|Reexport of UI plug-ins||
The plug-in org.eclipse.rap.ui.workbench now reexports the basic UI plug-ins that are needed for RAP UI development. This is similar to RCP. The plug-in dependencies are org.eclipse.rap.w4t, org.eclipse.rap.rwt and org.eclipse.rap.jface.
The above features are just the ones that are new since the previous milestone build. Summaries for earlier milestone builds: