RapPlan

| RAP wiki home | RAP project home |

RAP development plan

This document is a draft and is subject to change, we welcome all feedback.

To ensure the planning process is transparent and open to the entire Eclipse community, we (the RAP project team) post plans in an embryonic form and revise them throughout the release cycle.

Draft plan for RAP 1.0

• 2006-06 - 2006-09 initial code contribution: Java component library for UI development (done)
• 2006-10: Moving widget toolkit to org.eclipse packages, re(de)fine widget toolkit api (done / without milestone release)
• 2007-02 M1: Basic WebWorkbench implementation running on OSGi (functionality implemented - release targeted for first week of february) (done)
• 2007-03 M2: extending workbench functionality, initial work on Perspective switcher, extending jface functionality (dialog framework) (done)
• 2007-04-27 M3: move to org.eclipse.swt, org.eclipse.jface, org.eclipse.ui namespaces, .war deployment, ViewActions (basic implementation), Taborder (done)
• 2007-06-08 M4: move to qooxdoo 0.7, finalize move to a RCP API subset, implement untyped listeners, adapt codebase to RCP 3.3, theme management, expand JFace, Workbench implementation (open/close workbench parts, ...) (done)
• 2007-07-13 M5: background process management (ProgressMonitor, Display.syncExec ...), finalize new table component, branding functionality, performance optimization (client side widget cache), expand Workbench implementation (perspective extensions, perspective switcher, ...), client side font size calculation, data binding (done)

• 2007-08-17 M6 IN PROGRESS
  • Provide all API for Release 1.0
    • check for UnsupportedOperationException
    • move required classes from w4t to rwt bundle, refactor package names, w4t_startup
    • introduce org.eclipse.ui plugin (done)
    • resolve api differences for Dialogs, Color, Font, Image
    • mark Adaptable non-api
    • Provide facade for TextSizeDetermination
    • Define API for custom widget developers
  • performance optimization
  • robustness
  • finalize TableViewer, TreeViewer
  • branding functionality
    • servlet name
    • favicon
    • title
    • theming
    • make index page body configurable
• 2007-09-14 RC1: Code freeze for 1.0
  • final performance optimization
  • error handling
  • fixing of major bugs

• 2007-09-28 v1.0: Release 1.0
  • fixing of critical bugs

The work will be conducted in the following components

Component: org.eclipse.rap.ui

Workbench

• WorkbenchAdvisor, WorkbenchWindowAdvisor, ActionBarAdvisor
• extension of menubars / toolbars by extension points
• WorkbenchWindow SelectionService
• WorkbenchPage PartListener

• IWorkbenchPart, IViewPart
• IWorkbenchPart: maximize, minimize, restore (done)
• IWorkbenchPart: Workbench Actions for opening workbench parts
• IWorkbenchPart: Close-Button (configuarble)
• Toolbar, Menu for ViewParts

• ActionSets: IWorkbenchWindowActionDelegate

Perspectives

• definition of perspectives by IPerspectiveFactory (partly done - finalizing implementation e.g. StandaloneView)
• Perspective extensions
• Perspective Switcher
• Perspective Actions(open, close etc)
• Perspective Name in WindowTitle

Component: org.eclipse.rap.jface

• Actions
• MenuManager
• CoolBarManager
• Structured Viewers: TreeViewer, TableViewer
• WindowManager, Window, ApplicationWindow
• ImageDescriptor, ImageRegistry
• Dialog Framework (done for the most frequently used classes)

Component: org.eclipse.rap.rwt

• Font: base implementation (done)
• Font: font size calculation

• Image: ImageLoader with size calculation
• Table: Extending the current implementation to match SWT (e.g. inline-editing, bounds, font, and color for TableItem, images, etc.)
• Tree: Extending the functionality to match SWT Tree (e.g. selection should not cause expand event, Images etc.)
• Browser-Widget (mostly done)
• Z-Index (done)
• Modify-Event (done for existing widgets as there are Text and Spinner)
• Menu: Extending the functionality to match SWT (e.g. enable and visible properties, ArmEvent for MenuItem, MenuEvent for Menu, etc.)

Community involvement desirable

the implementation of the following functionality will largely depend on community involvement

• StatusBar (implemented by RAP team)
• TraverseEvents? (deferred)
• Short-Cuts (Accelerator) (deferred)
• Preferences (deferred)
• Drag&Drop of Workbenchparts (deferred)
• Columns for the tree widget (used e.g. by the PropertySheet) (implemented by RAP team)

Out of scope for version 1.0

• IEditorPart, IEditorInput (done)
• Workspace, Resources
• Help System, context sensitive help, HelpEvents
• KeyEvents
• Low-Level-MouseEvents
• Paint-Events
• Undocked ViewParts
• Navigation
• Accessibility
• SWT-AWT - Bridge
• StyledText
• Cursor