Eclipse WTP Source Editing 3.1.0

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

Internationalization and Localization will be supported.

Target Environments

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.

Themes

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.

  • Improve the XML Schema editor usability and consistency [251557] (target milestone: 3.1 M5)
  • TODO markers in JSP Scriptlets are not shown [71558] (target milestone: 3.1 M1)
No items.
No items.

Scaling Up

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.

  • need to support second coloring capabilities [232752] (target milestone: 3.1 M5)
  • Improve performance when editing large XML Schema documents [156564] (target milestone: 3.1 M7)
No items.
No items.

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

  • getDynamicAttributes should be available on TLDElementDeclaration [245280] (target milestone: 3.1 M6)
No items.
No items.

Everything

Following are plan items including those not yet categorized into a theme.
  • getDynamicAttributes should be available on TLDElementDeclaration [245280] (target milestone: 3.1 M6)
  • need to support second coloring capabilities [232752] (target milestone: 3.1 M5)
  • Improve the XML Schema editor usability and consistency [251557] (target milestone: 3.1 M5)
  • Improve performance when editing large XML Schema documents [156564] (target milestone: 3.1 M7)
  • TODO markers in JSP Scriptlets are not shown [71558] (target milestone: 3.1 M1)
No items.
  • JSP parser : <%= true .. comment %> is validated as a correct expression [238385] (target milestone: 3.2)