Project Plan For WTP Source Editing, version 3.4 (Juno)

Introduction

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.

Release Deliverables

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

Table of Contents

Target Environments

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

Internationalization

Internationalization and Localization will be supported.

Table of Contents

Compatibility with Previous Releases

Table of Contents

Themes and Priorities

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.
  • 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.

  • Committed

    • hyperlink navigation for @import in css [92854] (target milestone: 3.4 M3)
    • Color preview popup on CSS color hovering [360874] (target milestone: 3.4 M4)
    • [content assist] Control+Space Bar doesn't auto-fill text when there's only one option [134073] (target milestone: 3.4 M5)
    • [content assist] Use Linked Positions for cursor positioning in applied content assist proposals [264246] (target milestone: 3.4 M7)

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.

  • Committed

    • [api] Element.getAttributeNode will create an Attribute for implied values [362006] (target milestone: 3.4 M3)

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.

Everything

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

  • Committed

    • hyperlink navigation for @import in css [92854] (target milestone: 3.4 M3)
    • [api] Element.getAttributeNode will create an Attribute for implied values [362006] (target milestone: 3.4 M3)
    • Separate the HTML validator into the org.eclipse.wst.html.core bundle so it can be used in headless tools [338111] (target milestone: 3.4 M4)
    • Color preview popup on CSS color hovering [360874] (target milestone: 3.4 M4)
    • [content assist] Control+Space Bar doesn't auto-fill text when there's only one option [134073] (target milestone: 3.4 M5)
    • [content assist] Use Linked Positions for cursor positioning in applied content assist proposals [264246] (target milestone: 3.4 M7)
  • Deferred

    • [undo] SSE Undo stack different from standard operation history [191754] (target milestone: Future)
    • [api][doc] SSE SourceParser Interfaces should be made API and documented [270708] (target milestone: Future)
    • Make already-specified attributes easier to find in the property sheet [358313] (target milestone: Future)

Table of Contents

Appendix References

  • The general WTP plan can be found here .

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"