Difference between revisions of "Rap10M6 News"

From Eclipsepedia

Jump to: navigation, search
(ext point move)
m (RAP Common)
Line 11: Line 11:
 
|width="20%"|'''Extension Point move'''
 
|width="20%"|'''Extension Point move'''
 
|width="80%"|
 
|width="80%"|
To be with RAP as near as possible at the original implementation of RCP we decided to repackage some bits to a new bundle called "org.eclipse.rap.ui" - an equivalent to the existing "org.eclipse.ui" plug-in. As consequence some of the existing extension points has been moved to another namespace. Here is a list with all changes:
+
To be with RAP as near as possible at the original implementation of RCP we decided to repackage some bits to a new bundle called <em>org.eclipse.rap.ui</em> - an equivalent to the existing <em>org.eclipse.ui</em> plug-in. As a consequence some of the existing extension points have been moved to another namespace. Here is a list with all changes:
  
The RAP-specific extension points were moved from the "org.eclipse.rap.ui.workbench" namespace to "org.eclipse.rap.ui". This affects:
+
The RAP-specific extension points were moved from the <em>org.eclipse.rap.ui.workbench</em> namespace to <em>org.eclipse.rap.ui</em>. This affects:
 
* adapterfactory
 
* adapterfactory
 
* entrypoint
 
* entrypoint
Line 19: Line 19:
 
* resources
 
* resources
  
Extension points for themeing were moved from "org.eclipse.rap.swt" to the namespace mentioned above. This affects:
+
Extension points for themeing were moved from <em>org.eclipse.rap.swt</em> to the namespace mentioned above. This affects:
 
* themeableWidgets
 
* themeableWidgets
 
* themes
 
* themes
  
  
All other extensions points (like "org.eclipse.ui.*") are not affected at all.
+
All other extensions points (like <em>org.eclipse.ui.*</em>) are not affected at all.
  
 
To adapt your existing plug-ins
 
To adapt your existing plug-ins
 
* open your manifest editor of your plug-in
 
* open your manifest editor of your plug-in
 
* switch to the "Dependencies" tab
 
* switch to the "Dependencies" tab
* replace "org.eclipse.rap.ui.workbench" with "org.eclipse.rap.ui"
+
* replace <em>org.eclipse.rap.ui.workbench</em> with <em>org.eclipse.rap.ui</em>
 
* switch to the "plugin.xml" tab in order to adapt the namespace changes according to the list above. PDE will help here.
 
* switch to the "plugin.xml" tab in order to adapt the namespace changes according to the list above. PDE will help here.
 
|}
 
|}

Revision as of 13:31, 13 August 2007

| RAP wiki home | RAP project home |

Contents

RAP 1.0 M6 - 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.

RAP Common

Extension Point move

To be with RAP as near as possible at the original implementation of RCP we decided to repackage some bits to a new bundle called org.eclipse.rap.ui - an equivalent to the existing org.eclipse.ui plug-in. As a consequence some of the existing extension points have been moved to another namespace. Here is a list with all changes:

The RAP-specific extension points were moved from the org.eclipse.rap.ui.workbench namespace to org.eclipse.rap.ui. This affects:

  • adapterfactory
  • entrypoint
  • phaselistener
  • resources

Extension points for themeing were moved from org.eclipse.rap.swt to the namespace mentioned above. This affects:

  • themeableWidgets
  • themes


All other extensions points (like org.eclipse.ui.*) are not affected at all.

To adapt your existing plug-ins

  • open your manifest editor of your plug-in
  • switch to the "Dependencies" tab
  • replace org.eclipse.rap.ui.workbench with org.eclipse.rap.ui
  • switch to the "plugin.xml" tab in order to adapt the namespace changes according to the list above. PDE will help here.

RWT

Latest qooxdoo

We just migrated to the latest revision of qooxdoo, the client-side JavaScript library of RAP. Beside many bug fixes, with this update, two flavors of qooxdoo builds are provided. The one with which RAP runs by default is optimized in size and speed. Targeted to custom widget developers is the debug variant. When launching RAP with the -Dorg.eclipse.swt.clientLibraryVariant=debug VM argument, the debug version of qooxdoo is used that offers better readable JavaScript code.

RAP Forms

Forms Suppport

There is initial support for the Forms Toolkit, Forms Editors and the like. The focus was put on API compatibility and functionality rather than mimicking the exact look of RCP Forms. The following is a list of the things that are already available:

  • ColumnLayout and TableWrapLayout
  • ExpandableComposite and Section
  • Hyperlink, ImageHyperlink (yet without actually showing the image) and HyperlinkGroup
  • TreeNode, Twistie and their common ancestor ToggleHyperlink
  • ScrolledPageBook
  • Form and ScrolledForm, FormToolkit
  • Form editors (FormEditor, FormPage, SharedHeaderFormEditor)

RAPFormsDemo.jpeg

Thanks to the donation of a Fortune 500 corporation we were able to acquire additional resources to have this implemented.

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

New for RAP 1.0 milestone build M5 (July 13, 2007)
New for RAP 1.0 milestone build M4 (June 08, 2007)
New for RAP 1.0 milestone build M3 (April 27, 2007)
New for RAP 1.0 milestone build M2 (March 2, 2007)