Table of Contents

• Introduction
• Release Deliverables
• Release Milestones
• Target Environments
• Compatibility with Previous Releases
• Themes and Priorities
• Appendix

The Source Editing project is a sub-project in the Eclipse WTP top level Project. Its main goal is to provide source editing support for typical "web" languages and the mixing of them, with a focus on making the editors extensible and easily reusable. This document describes the features and the API set in the Source Editing subproject for the Galileo release.

• Source code for deliverables tagged in CVS as version tagged "R3_1_0", viewable in the WebTools_Project CVS repository.

WTP Milestones follow the Eclipse release milestones by an offset of +2 as set by the Galileo release schedule.

WTP will support the platforms certified by the Eclipse Platform project. For a list of platforms supported in WTP 3.1, see Eclipse Target Operating Environments.

Internationalization and Localization will be supported.

Themes and their priorities communicate the main objectives of the project and their importance. The following themes are derived from those defined by the Eclipse Requirement council for the Eclipse Galileo release and from the WTP 3.0 release themes. These will be prioritized based on the community feedback. New themes could be synthesized from the requirements submitted by the community.

The sections to follow defines the plan items in the Source Editing project. The plan items are grouped under the respective themes where applicable. Each plan item corresponds to a new feature, API or some apsects of the project that needs to be improved. A plan item has an entry in the Eclipse Bugzilla system that has a detailed description of the plan item. Not all plan items represent the same amount of work; some may be quite large, others, quite small. Although some plan items are for work that is more pressing than others, the plan items appear in no particular order. See the corresponding bugzilla items for up-to-date status information on ongoing work and planned delivery milestones.

Features provided by WTP should be simple to use for users with widely-varying backgrounds and skill sets.

• WTP User Interface should be consistent and should follow the Eclipse User Experience Guidelines. Experienced Eclipse users should find few, if any, unpleasant surprises or omissions in the UI.
• Usability and Accessibility reviews should be done for the most common task flows. Cheat Sheets should be provided to assist users in performing tasks.
• WTP should provide enhanced user documentation, tutorials, white papers, demonstrations.

Ease of Use plan items are designated with "EaseOfUse" in the Status Whiteboard and the "plan" keyword.

Source Editing must be able to deal with development and deployment on an increasingly larger and more complex scale. WTP should spend focused effort on performance testing and improvement when dealing with extremely large projects and workspaces, particularly where extensibility is offered.

Scaling Up plan items are designated with the "plan" and "performance" keywords.

The 'P' in WTP stands for Platform, meaning Source Editing can be used by adopters to extend its functionality. This theme is about continuing to ensure the success of its adopters by promoting new API's and Extension points. These should be backed with robust Junit tests and good documentation.

Design for Extensibility plan items are designated with the "plan" and "api" keywords.

Following are plan items including those not yet categorized into a theme.