Project Plan For Rich Ajax Platform, version 1.2
Introduction
Preliminary
The RAP 1.2 project plan is still in preliminary state and not yet agreed upon by all parties.
The RAP project enables developers to build rich, Ajax-enabled Web applications by using the Eclipse development model, plug-ins with the well known Eclipse workbench extenstion points, JFace, and a widget toolkit with SWT API.
Release Deliverables
- Tooling (includes tool for debugging and testing, runtime, documentation) available as Update Site
- Runtime (target platform, includes source) available as downloadable archive
Release Milestones
Release milestones will be occurring at roughly 6 week intervals,
and will be aligned with the
Galileo Simultaneous Release train.
Milestone names start with M2 in order to clarify this
relationship.
M2 | 10/8/2008 | 1.2 M2 |
M3 | 11/19/2008 | 1.2 M3 |
M4 | 1/12/2009 | 1.2 M4 |
M5 | 2/16/2009 | 1.2 M5 |
M6 | 3/23/2009 | 1.2 M6 (API Freeze) |
M7 | 5/11/2009 | 1.2 M7 (Feature Freeze) |
RC1 | 5/25/2009 | 1.2 RC1 |
RC2 | 6/1/2009 | 1.2 RC2 |
RC3 | 6/8/2009 | 1.2 RC3 |
RC4 | 6/15/2009 | 1.2 RC4 |
The target date for availability of RAP 1.2 is
June 26, 2009 (with Galileo)
Target Environments
The server-side part of the Rich Ajax Platform 1.2 will be written and compiled against
- Equinox Version 3.5
- Version 1.4.2 of the Java Platform APIs (i.e., Java 2 Platform, Release 1.4.2 SE)
- Java Servlet API Version 2.3 - 2.5
The client-side reference implementation depends upon qooxdoo. For this release the following web browsers/rendering engines will be supported
- Internet Explorer >= 7.0
- Gecko (i.e. Firefox, Netscape)
- Webkit (i.e. Safari, Google Chrome)
Internationalization
The Rich Ajax Platform is designed as the basis for internationalized
products. The user interface elements provided by the RAP
components, including dialogs and error messages, are externalized. The
English strings are provided as the default resource bundles.
Compatibility with Previous Releases
RAP 1.2 will be backward compatible with RAP 1.1.
Themes and Priorities
Reduce the gap between RWT and SWT
As RWT implements a subset of the SWT API, we aim to implement functionality yet missing from RWT.
This includes to make use of the newly implemented API in higher layers (e.g. Workbench, JFace).
- Committed
- Slider widget missing [256740] (target milestone: 1.2 M4)
- Cursor support missing [244004]
(target milestone: 1.2 M2) - [DateTime] DateTime widget missing [183177]
(target milestone: 1.2 M2) - [MessageBox] MessageBox missing [198389]
(target milestone: 1.2 M2) - KeyEvents are missing [225764]
(target milestone: 1.2 M4) - Enable cursor usage in Workbench code [246772]
(target milestone: 1.2 M2) - JFace Cell Editors missing [247122]
(target milestone: 1.2 M3) - TraverseEvents for cell editors are missing [250611]
(target milestone: 1.2 M3) - ExpandBar missing [231086]
(target milestone: 1.2 M2) - Scale widget is missing [239006]
(target milestone: 1.2 M2)
- Proposed
- Drag & Drop
- Deferred
Design for Extensibility
This theme is about the extensibility of the RAP platform to achieve
independance from a certain client technology.
- Committed
- Specify and implement an exchangable client/server synchronization mechanism.
- Proposed
- Deferred
New Web Centric Features
- Committed
- Web Look & Feel for the Workbench (Exemplary implmentation and API to plug in other implementations)
- Extend themeability of existing widgets
- Proposed
- More flexible widget decorations (e.g. rounded corners)
- Enable RAP applications to run on multiple browser-tabs, in portlet environments
- Deferred