RAP 1.2 M6 released
The RAP-Team released a new milestone build (RAP 1.2 M6) of their Rich Ajax Platform and added some missing SWT API in RAP and the org.eclipse.ui.intro extension point to create your own intro support.
If you want to see all the changes of the new milestone release, you should possibly visit the “New and Noteworthy” page [1].
RWT
New API added
TypedEvent#display
Display: Set user data
setData(Object)
setData(String, Object), etc.
Display#timerExec()
Monitor:
getPrimaryMonitor() on Display
getMonitor() on Control
Device#getClientArea()
RowLayout#center
Widget#notifyListeners()
CTabFolder#getItem(Point)
DateTime#setDate(int, int, int)
SashForm: sashWidth and setMaximizedControl()
Shell#forceActive()
Spinner: Selection listener
TabItem#setToolTipText(String)
Text#setLineHeight()
ToolItem: setDisabledImage() and setHotImage()
CCombo widget
The org.eclipse.swt.custom.CCombo widget was added and it works much the same as in SWT.
Forms
FormText
You can now use the org.eclipse.ui.forms.widgets.FormText as a read-only text control that is capable of rendering wrapped text. Text can be rendered as-is or by parsing the formatting XML tags (<p>, <li>, <a>, <img>, <control> and <span>).
Workbench
Intro support
It is now possible to create your own intro support for your application, because the org.eclipse.ui.intro extension point provides a generic mechanism for this. For more information please visit [2].
Databinding
The databinding core plug-ins were restructured. Like in RCP, the RAP workbench has a dependency to core databinding. That’s why org.eclipse.databinding.observable and org.eclipse.databinding.property are now required to run the workbench. You should update your build scripts and launch configurations after that.
