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.
Difference between revisions of "ERCP 1.1 Draft Plan"
(→Compatibility with previous Releases) |
(→Proposed items) |
||
| Line 86: | Line 86: | ||
None at this time | None at this time | ||
==== Proposed items ==== | ==== Proposed items ==== | ||
| − | + | '''Support for different OSGi environments''' Mobile platforms may provide their own OSGi implementations in order to better utilize these platforms eRCP should be able to run on top any OSGi runtime. | |
| + | |||
==== Defered items ==== | ==== Defered items ==== | ||
None at this time | None at this time | ||
Revision as of 10:20, 28 September 2006
Contents
Embedded Rich Client Platform Project 1.1 DRAFT Plan
Please send comments about this draft plan to the dsdp-ercp-dev@eclipse.org mailing list.
This document lays out the feature and API set for the next release of Embedded Rich Client Platform Project, to be released , in July 2007, and usually called "eRCP 1.1", for short.
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 post plans in an embryonic form and revise them throughout the release cycle.
The first part of the plan deals with the important matters of release deliverables, release milestones, target operating environments, and release-to-release compatibility. These are all things that need to be clear for any release, even if no features were to change.
The remainder of the plan consists of plan items for the subcomponents under the eRCP project,
The current status of each plan item is noted:
- Committed plan item - A committed plan item is one that we have decided to address for the release.
- Proposed plan item - A proposed plan item is one that we are considering addressing for the release. Although we are actively investigating it, we are not yet in a position to commit to it, or to say that we won't be able to address it. After due consideration, a proposal will either be committed or deferred.
- Deferred plan item - A reasonable proposal that will not make it in to this release for some reason is marked as deferred with a brief note as to why it was deferred. Deferred plan items may resurface as committed plan items at a later point.
Release deliverables
The release deliverables have the same form as previous releases, namely:
- Source code release, available as versions tagged "R1_1" from eRCP CVS Repository
- eRCP runtime binary for Windows platform (downloadable).
- eRCP runtime binary for Windows Mobile 2003/5 (downloadable).
- eRCP device and emulator runtime binaries for Nokia Series 80 (downloadable).
- eSWT device and emulator runtime binaries for Nokia Series 80 (downloadable).
Release milestones and release candidates
Release milestones will occur with the Eclipse Platform milestone releases and will be compatible with Eclipse 3.3 builds. The following are the approximate dates for eRCP milestones.
- Wednesday Nov. 15, 2006 - Milestone 1 (1.1 M1) - stable build
- Wednesday Jan. 10, 2007 - Milestone 2 (1.1 M2) - stable build
Target Operating Environments
- Microsoft Windows XP
- Microsoft Windows Mobile 2003/5
- Nokia Series 80
Compatibility with previous Releases
eRCP 1.1 will be compatible with eRCP 1.0
API Contract Compatibility:
Binary Compatibility:
Source Compatibility:
Major themes
Improve Quality
Focused effort will be made to reduce bug backlog, improving test coverage, performance and performance testing.
Improve Mobile Usability
The usability of eRCP components should be extended further to better accomodate mobile device needs. Here are the requirements
- As many of the targeted devices require one handed (non-touch)operation eRCP should ensure that its UI components are fully compatible with such cases.
- Better handling of the different screen sizes
Components
eSWT
Committed items
None at this time
Proposed items
ScrollableComposite Scrollable composite is a good candidate for further enhancing the eSWT component offering. With the addition of the ScrolledComposite eSWT can also provide auto-scrolling (see bug152940) which will improve the handling of different screen sizes.
Defered items
None at this time
Core Runtime
Committed items
None at this time
Proposed items
Support for different OSGi environments Mobile platforms may provide their own OSGi implementations in order to better utilize these platforms eRCP should be able to run on top any OSGi runtime.
Defered items
None at this time
eWorkbech
Committed items
None at this time
Proposed items
None at this time
Defered items
None at this time
eUpdate
Committed items
None at this time
Proposed items
None at this time
Defered items
None at this time