Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » [ANN] RAP 1.4 planning
[ANN] RAP 1.4 planning [message #549379] Mon, 26 July 2010 14:08
Benjamin Muskalla is currently offline Benjamin MuskallaFriend
Messages: 338
Registered: July 2009
Senior Member
Hi all,

thanks for your input to our planning for the next release. Meanwhile,
we discussed our plans for 1.4 and would like to let you know about our
progress. Please note that this is only a preliminary plan, we didn't
make the final decision yet.

Here are the overall themes we'd like to address in RAP 1.4:

* Widget improvements and additions

As in every RAP release, we will improve our widget set. A new Tree
implementation is already in CVS. Non-native scrollbars would be another
improvement. There is a great demand for the upload widget, and we'd
like to integrate it into the release.
To support custom widgets better, we'd also like to come up with a small
documented client API for custom widgets.

* Theming & Design

We want to further improve the look and feel of RAP applications by
adding more theming features like shadows and more animations.
Our aging default theme also needs a fresh look.
Those widgets that are not very customizeable by theming, should be
improved. We will also ease the theming of custom widgets.

* Single Sourcing

To support single sourcing, we will update the Eclipse UI APIs to 3.7
and add more Eclipse API to RAP - first and foremost key bindings, as
there is a great demand.

* Support for other client technologies / Mobile

We see that mobile devices are getting more and more important and thus
want to improve RAP on those devices. For a start, we will fix blocking
bugs on iPhone/iPad and on Adroid.
Moreover, we will work towards a well-defined protocol between client
and server that will once allow for exchangeable client implementations.

* Reliability, Scalability and Availability

We want to further improve the performance of RAP by reducing the client
footprint.
We are involved in a research project that evaluates solutions for
transparent failover.

* Integration with other Eclipse projects

In the last release, we worked with EMF and Riena to make RAP usable
with these projects. We want to follow up this effort and will also have
a look at Virgo.

* Tooling

Two Google Summer of Code projects will be integrated into the RAP
tooling: The WAR Export and the Theme Editor.

That's it. You'll miss Draw2D on this list. We recognized that there is
a great interest in this feature and we did look into it try to come up
with an estimation. Draw2D alone would be a huge effort and we currently
cannot afford it to do that with the resources we have for OpenSource
development. GEF would require even more work. We're currently thinking
about a commercial offering for Draw2D/GEF if there's enough interest.

Cheers,

The RAP Team

--
Benjamin Muskalla | EclipseSource Karlsruhe
Need professional support for RAP and RCP?
Go to: http://eclipsesource.com/support
Twitter : @bmuskalla
Blog : http://eclipsesource.com/blogs/tag/rap/
Previous Topic:Migrating a jetty based editor
Next Topic:Where is common used Color symbolic name defined?
Goto Forum:
  


Current Time: Thu Feb 29 06:34:39 GMT 2024

Powered by FUDForum. Page generated in 0.02434 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top