RAP 1.2 M6 - New and Noteworthy

Here are some of the more noteworthy things that are available in this milestone build which is now available for download.

This list shows all bugs that were fixed during this milestone.

RWT

New API added For this milestone, we concentrated on implementing SWT API that was still missing in RAP. This will make it easier for the community to reuse existing code or to utilize new features. Here is a list of API methods added in this milestone:
  • TypedEvent#display
  • User data on Display (setData( Object ), setData( String, Object ), etc.)
  • Display#timerExec()
  • Monitor and its accessors like getPrimaryMonitor() on Display and getMonitor() on Control
  • Device#getClientArea()
  • RowLayout#center
  • Widget#notifyListeners()
  • CTabFolder#getItem( Point )
  • DateTime#setDate( int, int, int )
  • sashWidth and setMaximizedControl() on SashForm
  • Shell#forceActive()
  • Selection listener on Spinner
  • TabItem#setToolTipText( String )
  • Text#setLineHeight()
  • setDisabledImage() and setHotImage() on ToolItem
CCombo widget Now there is a CCombo widget that works much the same as in SWT.

 

Forms

FormText The org.eclipse.ui.forms.widgets.FormText has been implemented in RAP. FormText is 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 like <p>, <li>, <a>, <img>, <control> and <span>. You can use the FormToolkit to create an instance: 
   
  FormText formText = toolkit.createFormText( form.getBody(), true );

For further details please also see this bug

 

Workbench

Intro support The org.eclipse.ui.intro extension point provides a generic mechanism that can be used to create your own intro support for your application. The main purpose of this extension is to define the class that implements IIntroPart and to specify the binding between a branding and an intro part. As RAP does not support products as known from RCP you can use the org.eclipse.rap.ui.branding extension point to bind your intro to a specific branding. For example, the following contribution defines a hypothetical intro part to be shown by the workbench on startup: 

<extension  
    point="org.eclipse.ui.intro">
  <intro
    class="com.example.SampleIntroPart"
    id="someId"
    icon="someIcon.png">
  </intro>
  <introBrandingBinding
    introId="someId"
    brandingId="com.example.someBrandingId">
  </introBrandingBinding>
</extension>
When starting the application for the first time the intro will appear in fullscreen covering the rest of the workbench window:

In standby mode the workbench shows the regular perspective with the intro on the right side:

For more informations about how to use the intro extension, see Contributing a HelloWorld intro Part
Databinding During the M6 milestone, the databinding core plug-ins were restructured. Like its RCP counterpart, the RAP workbench has a dependency to core databinding and thus is affected from these changes.

Effectively, two more bundles, org.eclipse.databinding.observable and org.eclipse.databinding.property are now required to run the workbench. Please update your build scripts and launch configurations accordingly.

The above features are just the ones that are new since the last milestone build. Summaries for earlier builds: