|
|
| (7 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__
| + | This page was obsolete and has been deleted. Please see the history if you need to access the content. |
| − | | [[RAP|RAP wiki home]] | [http://eclipse.org/rap RAP project home] |
| + | |
| − | ===RAP 1.0 M3 - 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 [http://www.eclipse.org/rap/cvs.php CVS] HEAD.
| + | |
| − | | + | |
| − | <!--
| + | |
| − | Here are some of the more noteworthy things available in milestone build M3 (???) which is now available for [http://www.eclipse.org/rap/downloads.php download].
| + | |
| − | -->
| + | |
| − | | + | |
| − | ==RAP Common==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''RCP Namespaces'''
| + | |
| − | |width="80%"|After many RAP users have requested it and after discussing this topic with the SWT and Platform team we have moved org.eclipse.rwt.rap to org.eclipse.swt, org.eclipse.rap.jface to org.eclipse.jface and org.eclipse.rap.ui to org.eclipse.ui package names. This should ease the task of adopting RCP code to RAP. To adjust your existing projects to the new packages you may use the organize imports functionality of eclipse.
| + | |
| − | | + | |
| − | '''Note''': RAP will provide a strict subset of the established API in those namespaces. There are currently a few exceptions to this rule but this is work in process and the strict subset will be achieved in M4. Additional API is provided in additional packages.
| + | |
| − | | + | |
| − | |}
| + | |
| − | | + | |
| − | ==RWT==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Progress Cursor for Long Running Requests'''
| + | |
| − | |width="80%"|[[Image:RapHourGlassCursor.png]]
| + | |
| − | | + | |
| − | When a request takes longer than 500 ms to return, the cursor will change to indicate that an operation is in progress. Once the response arrives the cursor is switched back to default.
| + | |
| − | | + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |'''ToolItem and MenuItem Enhancements'''
| + | |
| − | |[[Image:RAPToolBarEnabled.png]]
| + | |
| − | [[Image:RAPToolBarDisabled.png]]
| + | |
| − | | + | |
| − | As this is a basic prerequisite for disabling workbench actions, [[8_Tool_Bars_and_Menus|ToolItem]] and [[8_Tool_Bars_and_Menus#Classes_Menu_and_MenuItem|MenuItem]] now implement the <code>setEnabled,</code> <code>getEnabled</code> and <code>isEnabled</code> methods.
| + | |
| − | | + | |
| − | In addition, the ToolItem can now show tool tips.
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |'''MenuListener'''
| + | |
| − | |[[Image:RAPFileMenu-pre.png]][[Image:RAPFileMenu.png]]<br\>
| + | |
| − | [[8_Tool_Bars_and_Menus|MenuListener]]s can now be added to [[8_Tool_Bars_and_Menus|Menus]] to process actions before a menu shows up and after it is hidden. While the <code>menuShown</code> event is processed, a preliminary menu is displayed to signal that the menu is loading. This allows for enabled/disabling menu items just before the menu comes up.
| + | |
| − | |
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |'''Link'''
| + | |
| − | |[[Image:RAPLink.png]]
| + | |
| − | The SWT control Link, a text label with embedded hyperlinks, is now also available in RWT.
| + | |
| − | A <code>SelectionListener</code> can be added to invoke arbitrary actions on a click.
| + | |
| − | |
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |'''Tab Order'''
| + | |
| − | |[[Image:RAPTabOrder.png]]
| + | |
| − | The tab order, i.e. the order that controls within a composite are traversed when the TAB key is pressed, is now configurable using the method <code>setTabList( Control[] tablist )</code> on [[11 Controls, Composites, Groups, and_Shells#Class_Composite|Composite]]. As in SWT, the default tab order now corresponds to the order that controls are added to their parent composite.
| + | |
| − | |
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |'''Image Bounds'''
| + | |
| − | |[[Image:RAPImageBounds.png]]
| + | |
| − | The size of images is now determined on image loading and can be read using <code>Image.getBounds()</code>.
| + | |
| − | As a consequence, Labels that contain images can now compute their size correctly.
| + | |
| − | |
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |'''SWT Flags'''
| + | |
| − | |
| + | |
| − | * The flag <code>SWT.TOGGLE</code> can now be used for [[7_Basic_Controls#Class_Button|Buttons]] that snap in and stay pressed.
| + | |
| − | * The flag <code>SWT.ON_TOP</code> is now supported for [[11_Controls%2C_Composites%2C_Groups%2C_and_Shells#Class_Shell|Shells]] that are always on top of all other shells.
| + | |
| − | And yes, it's now ok to use <code>SWT</code> instead of <code>RWT</code>.
| + | |
| − | |}
| + | |
| − | | + | |
| − | ==RAP JFace==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''ComboViewer'''
| + | |
| − | |width="80%"|The <code>ComboViewer</code> is now implemented (or rather copied from JFace:). It is a concrete viewer based on an RWT <code>[[7_Basic_Controls#Class_Combo|Combo]]</code> control.
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''IMenuListener'''
| + | |
| − | |width="80%"|<code>IMenuListener</code> implementations can now be added to a <code>MenuManager</code>.
| + | |
| − | |}
| + | |
| − | | + | |
| − | ==RAP Workbench==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Startup Page'''
| + | |
| − | |width="80%"|The screenshot below now is history.
| + | |
| − | [[Image:RapStartupPage.png]]
| + | |
| − | | + | |
| − | The startup procedure was cut down from two to one single request.
| + | |
| − | The current implementation provides a template startup page that contains all the necessary things for RAP to work but also allows for customization. The latter is not yet available from 'outside' - but stay tuned.
| + | |
| − | |}
| + | |
| − | | + | |
| − | ==RAP WAR Deployment==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Feature Project in CVS'''
| + | |
| − | |width="80%"|The RAP CVS contains a new project (org.eclipse.rap.demo.feature) that demonstrates how to create a deployment archive (WAR). The deployment uses the org.eclipse.equinox.servletbridge as servlet container hook. The documentation is currently integrated in the project - see the deployment_tutorial.html in the root directory.
| + | |
| − | |}
| + | |
| − | | + | |
| − | | + | |
| − | The above features are just the ones that are new since the previous milestone build.
| + | |
This page was obsolete and has been deleted. Please see the history if you need to access the content.
