The Source Editing project is a project under the
Eclipse WTP top-level Project. Its main goal is to provide source
editing support for
typical web languages and the intermixing 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 project for the
WTP 3.4 (Juno) release.

Internationalization

Themes and their priorities communicate the main objectives of
the project and their importance. 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 aspects 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.

Ease of Use

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.

Scaling Up

Source Editing must be able to deal with development and
deployment on
an
increasingly large and more complex scale. Source Editing
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 together.

Design for Extensibility

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
APIs 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 together.

Quality

Source Editing is one of the most heavily used projects within WTP and
carries a correspondingly weighty bug report list because of it. Items
under this theme are meant to address the backlog of bug reports not
concerning performance and is not to include enhancements. It is
expected that these require a significant enough amount of time to
merit inclusion within the plan. Items under this theme are only to be
chosen by Committers.

Quality
plan items are designated with the "plan" keyword and "qplan"
within the status whiteboard.