|
|
| (14 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | | [[RAP|RAP wiki home]] | [http://eclipse.org/rap RAP project home] |
| + | This page was obsolete and has been deleted. Please see the history if you need to access the content. |
| − | ===RAP 1.0 M5 - 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.
| + | |
| − | | + | |
| − | During the development cycle towards M5 major enhancements of the RWT infrastructure happend.
| + | |
| − | The two most notables are font size calcualtaion and client-side widget pooling.
| + | |
| − | Please note that despite extensive testing, due to the complexity of the enhancements, there
| + | |
| − | might occur problems under rare circumstances. If you experience any inexplicable behavior, please let us know.
| + | |
| − | | + | |
| − | As the next development cycles will focus on robustness and stability, we will provide integration builds on a regular basis to make progress in these fields accessible earlier.
| + | |
| − | | + | |
| − | == RAP Common ==
| + | |
| − | | + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Client-side widget recycling'''
| + | |
| − | |width="80%"|
| + | |
| − | | + | |
| − | RWT introduces a mechanism that helps to soften the massive memory consumption on the client.
| + | |
| − | Many of the client-side widget are not thrown away anymore, but kept in an object pool for later reuse.
| + | |
| − | Especially with long-running applications in the Internet Explorer browser, this can make a huge difference.
| + | |
| − | The pooling does not include all RWT widgets now, so there is still potential for further optimization.
| + | |
| − | | + | |
| − | Please note that this topic is work in progress and, despite extensive testing, might lead to errors under rare circumstances.
| + | |
| − | If you experience any inexplicable behavior, please let us know.
| + | |
| − | |}
| + | |
| − | | + | |
| − | ==RWT==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''New Table features'''
| + | |
| − | |width="80%"|
| + | |
| − | | + | |
| − | The <code>Table</code> widget now notifies about double-click events by sending a <code>SelectionListener#widgetDefaultSelected</code>.
| + | |
| − | | + | |
| − | The column order can be queried and changed programmatically using <code>getColumnOrder()</code> and <code>setColumnOrder()</code>. Marking a column with <code>setMoveable</code> permits the user to change its order by drag and drop.
| + | |
| − | | + | |
| − | If a table is created with the <code>SWT.VIRTUAL</code> flag, <code>TableItem</code>s are only realized client-side when they become visible. Even though, in most situations, using the <code>[[#RAP _JFace|TableViewer]]</code> will be more convenient, the code below shows how the <code>SetData</code> event can be used to "manually" populate a <code>VIRTUAL</code> table.
| + | |
| − | <pre>
| + | |
| − | Table table = new Table( shell, SWT.VIRTUAL );
| + | |
| − | table.addListener( SWT.SetData, new Listener() {
| + | |
| − | public void handleEvent( final Event event ) {
| + | |
| − | TableItem item = ( TableItem )event.item;
| + | |
| − | int index = table.indexOf( item );
| + | |
| − | item.setText( "Item " + index );
| + | |
| − | }
| + | |
| − | } );
| + | |
| − | table.setItemCount( 300 );
| + | |
| − | </pre>
| + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''New widget: CLabel'''
| + | |
| − | |width="80%"|
| + | |
| − | | + | |
| − | With the new CLabel widget you can now have images and text on your label without any workaround. Additionally you can set different border styles like <code>SWT.SHADOW_IN</code> or <code>SWT.SHADOW_OUT</code>. Here is an example how it could look like:
| + | |
| − | | + | |
| − | [[Image:RAPCLabel.png]]
| + | |
| − | | + | |
| − | | + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Cool stuff'''
| + | |
| − | |width="80%"|
| + | |
| − | | + | |
| − | By reimplementing the CoolItem and CoolBar widget we got many improvements in this area. First is that support of multiple rows in the CoolBar which is used if there is not enough space to show all the items in one row.
| + | |
| − | | + | |
| − | [[Image:RAPCoolBarRows.png]]
| + | |
| − | | + | |
| − | Additionally if there is not enough space to wrap the CoolItems a chevron will be visible to have access to the invisible items.
| + | |
| − | | + | |
| − | [[Image:RAPCoolBarChevron.png]]
| + | |
| − | |}
| + | |
| − | | + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Theming enhancements'''
| + | |
| − | |width="80%"|
| + | |
| − | | + | |
| − | The RAP theming infrastructure allows for further customizations of the UI.
| + | |
| − | It is now possible to specify borders, paddings, fonts, and images in a custom theme file.
| + | |
| − | Even custom widgets can now hook their theming into RAP via extension point.
| + | |
| − | |}
| + | |
| − | | + | |
| − | ==RAP JFace==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''TableViewer'''
| + | |
| − | |width="80%"|
| + | |
| − | As the underlying RWT <code>Table</code> now understands the <code>VIRTUAL</code> flag, the relevant <code>TableViewer</code> code was activated as well. Below you can see how it looks in action.
| + | |
| − | | + | |
| − | [[Image:Rap_VirtualTable_Loading.jpeg]] <b>>>></b> [[Image:Rap_VirtualTable_Done.jpeg]]
| + | |
| − | |}
| + | |
| − | | + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''Databinding'''
| + | |
| − | |width="80%"|
| + | |
| − | Main functionalty of org.eclipse.jface.databinding has been ported to RAP.
| + | |
| − | You can see databinding in action in the newly added perspective 'Databinding' in the RAP Demo application. Note that the databinding demo comes as a seperate plugin called <code>org.eclipse.rap.demo.databinding</code> which has to be started together with the regular workbench demo application.
| + | |
| − | | + | |
| − | Here is a screenshot:
| + | |
| − | | + | |
| − | [[Image:databinding_snippet_view.jpg]]
| + | |
| − | | + | |
| − | | + | |
| − | |}
| + | |
| − | | + | |
| − | ==RAP Workbench==
| + | |
| − | {|
| + | |
| − | |-valign="top" align="left"
| + | |
| − | |width="20%"|'''DrillDownAdapter'''
| + | |
| − | |width="80%"|
| + | |
| − | | + | |
| − | Drilldown Adapters are a feature available for TreeViewers to help navigate through the data, instead of having to deal with ever expanding trees. In this way you can essentially zoom in to view just one part of the tree, i.e., drill down. Only two lines of code were added throughout the initialization of the viewer to invoke this feature in the context menu. Only one line was needed to add them to the view's toolbar. They are shown below:
| + | |
| − | | + | |
| − | <pre>
| + | |
| − | // Create the Drill Down Adapter
| + | |
| − | drillDownAdapter = new DrillDownAdapter(viewer);
| + | |
| − | | + | |
| − | // Add the options to the view's toolbar (IToolBarManager)
| + | |
| − | drillDownAdapter.addNavigationActions(manager);
| + | |
| − | </pre>
| + | |
| − | | + | |
| − | After adding them to the IToolbarManager of your view, they are looking like this:
| + | |
| − | | + | |
| − | [[Image:RAPDrillDownAdapter.png]]
| + | |
| − | |}
| + | |
| − | | + | |
| − | | + | |
| − | The above features are just the ones that are new since the previous milestone build. Summaries for earlier milestone builds:
| + | |
| − | | + | |
| − | [[Rap10M4_News|New for RAP 1.0 milestone build M4 (June 08, 2007)]]<br />
| + | |
| − | [[Rap10M3_News|New for RAP 1.0 milestone build M3 (April 27, 2007)]]<br />
| + | |
| − | [[Rap10M2_News|New for RAP 1.0 milestone build M2 (March 2, 2007)]]
| + | |
| − | | + | |
| − | [[Category:RAP]]
| + | |
This page was obsolete and has been deleted. Please see the history if you need to access the content.
