Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Rap10M5 News"

(RWT)
Line 5: Line 5:
  
 
All features documented here can be obtained from [http://www.eclipse.org/rap/cvs.php CVS] HEAD.
 
All features documented here can be obtained from [http://www.eclipse.org/rap/cvs.php CVS] HEAD.
 +
 +
== 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==
 
==RWT==

Revision as of 10:37, 13 July 2007

| RAP wiki home | RAP project home |

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 CVS HEAD.

RAP Common

Client-side Widget Recycling

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

New Table features

The Table widget now notifies about double-click events by sending a SelectionListener#widgetDefaultSelected.

The column order can be queried and changed programmatically using getColumnOrder() and setColumnOrder(). Marking a column with setMoveable permits the user to change its order by drag and drop.

If a table is created with the SWT.VIRTUAL flag, TableItems are only realized client-side when they become visible. Even though, in most situations, using the TableViewer will be more convenient, the code below shows how the SetData event can be used to "manually" populate a VIRTUAL table.

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 );
New widget: CLabel

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 SWT.SHADOW_IN or SWT.SHADOW_OUT. Here is an example how it could look like:

RAPCLabel.png


Cool stuff

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.

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.

RAPCoolBarChevron.png

RAP JFace

TableViewer

As the underlying RWT Table now understands the VIRTUAL flag, the relevant TableViewer code was activated as well. Below you can see how it looks in action.

Rap VirtualTable Loading.jpeg >>> Rap VirtualTable Done.jpeg

Databinding

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 org.eclipse.rap.demo.databinding which has to be started together with the regular workbench demo application.

Here is a screenshot:

Databinding snippet view.jpg


RAP Workbench

DrillDownAdapter

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:

// Create the Drill Down Adapter
drillDownAdapter = new DrillDownAdapter(viewer);

// Add the options to the view's toolbar (IToolBarManager)
drillDownAdapter.addNavigationActions(manager);

After adding them to the IToolbarManager of your view, they are looking like this:

RAPDrillDownAdapter.png


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 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)

Back to the top