blob: b1ead7ebb22bc39b6194814a74676373dec1961c [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Use this to test local rendering in firefox -->
<!--
Format is detailed at
http://wiki.eclipse.org/Development_Resources/Project_Plan
-->
<!--<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>-->
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/eclipse/development/project-plan-render.xsl"?>
<p:plan plan-format="1.0" xmlns:p="http://www.eclipse.org/project/plan"
xmlns="http://www.w3.org/1999/xhtml" name="JavaScript Development Tools">
<p:release projectid="webtools.jsdt" version="3.3 (Indigo)" />
<p:introduction>
<div>The JavaScript Development Tools (JSDT) project is a
part of the Eclipse WTP top-level Project. It provides a JavaScript
IDE for Eclipse.
This document describes the features and the API set in the JSDT project
for the WTP 3.3 release.</div>
</p:introduction>
<p:release_deliverables>
<div>
<ul>
<li>Source
code for deliverables tagged in CVS as version tagged
&quot;R3_3_0&quot;, viewable in the WebTools_Project
<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.jsdt/?root=WebTools_Project">CVS repository</a>
.
</li>
<li>The Eclipse IDE for JavaScript Web Developers package</li>
</ul>
</div>
</p:release_deliverables>
<p:release_milestones>
<p:preamble>
<p>
JSDT adheres to the overall <a
href="http://www.eclipse.org/projects/project-plan.php?projectid=webtools#release_milestones">WTP Milestone Schedule</a>.
</p>
</p:preamble>
<p:postamble />
</p:release_milestones>
<p:target_environments>
<div>
JSDT will support the platforms certified by the Eclipse Platform
project. For a list of platforms supported , see
<a
href="http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#target_environments">Eclipse Target Operating Environments</a>
.
</div>
<p:internationalization>
<div>Internationalization and Localization will be supported.</div>
</p:internationalization>
</p:target_environments>
<p:compatibility_with_previous_releases />
<p:themes_and_priorities>
<p:preamble>
<div>
<p>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.
</p>
<p>
The sections to follow defines the plan items in the JSDT
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.</p>
</div>
</p:preamble>
<p:theme name="Ease of Use">
<p:description>
<div>
<p>
Features provided by WTP should be simple to use for users with
widely-varying backgrounds and skill sets.
</p>
<ul>
<li>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.</li>
<li>Usability and Accessibility reviews should be done for the
most common task flows. Cheat Sheets should be provided to assist
users in performing tasks.</li>
<li>WTP should provide enhanced user documentation, tutorials,
white
papers, demonstrations.</li>
</ul>
<p>
<i>Ease of Use</i>
plan items are designated with "EaseOfUse" in the Status
Whiteboard and the "plan" keyword.
</p>
</div>
</p:description>
<!--
keyword "plan" and status white-board includes the string
"EaseOfUse"
-->
<p:committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;status_whiteboard_type=substring&amp;status_whiteboard=EaseOfUse&amp;product=JSDT&amp;target_milestone=3.3&amp;target_milestone=3.3+M1&amp;target_milestone=3.3+M2&amp;target_milestone=3.3+M3&amp;target_milestone=3.3+M4&amp;target_milestone=3.3+M5&amp;target_milestone=3.3+M6&amp;target_milestone=3.3+M7&amp;target_milestone=3.3+RC1&amp;target_milestone=3.3+RC2&amp;target_milestone=3.3+RC3&amp;target_milestone=3.3+RC4&amp;keywords=plan&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:committed>
<p:proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;status_whiteboard_type=substring&amp;status_whiteboard=EaseOfUse&amp;product=JSDT&amp;target_milestone=---&amp;keywords=plan&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:proposed>
<p:deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;status_whiteboard_type=substring&amp;status_whiteboard=EaseOfUse&amp;product=JSDT&amp;target_milestone=Future&amp;target_milestone=4.0&amp;target_milestone=3.4&amp;keywords=plan&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:deferred>
</p:theme>
<p:theme name="Scaling Up">
<p:description>
<div>
<p>
JSDT must be able to deal with development on an
increasingly large and more complex scale. JSDT
should spend focused
effort on performance testing and improvement
when dealing with
extremely large projects and workspaces,
particularly where
extensibility is offered.
</p>
<p>
<i>Scaling Up</i>
plan items are designated with the "plan" and "performance"
keywords together.
</p>
</div>
</p:description>
<!-- keywords "plan" and "performance" -->
<p:committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=JSDT&amp;target_milestone=3.3&amp;target_milestone=3.3+M1&amp;target_milestone=3.3+M2&amp;target_milestone=3.3+M3&amp;target_milestone=3.3+M4&amp;target_milestone=3.3+M5&amp;target_milestone=3.3+M6&amp;target_milestone=3.3+M7&amp;target_milestone=3.3+RC1&amp;target_milestone=3.3+RC2&amp;target_milestone=3.3+RC3&amp;target_milestone=3.3+RC4&amp;keywords_type=allwords&amp;keywords=plan+performance&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit" />
<p:proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=JSDT&amp;target_milestone=---&amp;keywords_type=allwords&amp;keywords=plan+performance&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:proposed>
<p:deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=JSDT&amp;target_milestone=Future&amp;target_milestone=4.0&amp;target_milestone=3.4&amp;keywords_type=allwords&amp;keywords=plan+performance&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:deferred>
</p:theme>
<p:theme name="Design for Extensibility">
<p:description>
<div>
<p>
The 'P' in WTP stands for Platform, meaning JSDT 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.
</p>
<p>
<i>Design for Extensibility</i>
plan items are designated with the "plan" and "api" keywords together.
</p>
</div>
</p:description>
<!-- keywords "plan" and "api" -->
<p:committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=JSDT&amp;target_milestone=3.3&amp;target_milestone=3.3+M1&amp;target_milestone=3.3+M2&amp;target_milestone=3.3+M3&amp;target_milestone=3.3+M4&amp;target_milestone=3.3+M5&amp;target_milestone=3.3+M6&amp;target_milestone=3.3+M7&amp;target_milestone=3.3+RC1&amp;target_milestone=3.3+RC2&amp;target_milestone=3.3+RC3&amp;target_milestone=3.3+RC4&amp;keywords_type=allwords&amp;keywords=plan+api&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:committed>
<p:proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=JSDT&amp;target_milestone=---&amp;keywords_type=allwords&amp;keywords=plan+api&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:proposed>
<p:deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;product=JSDT&amp;target_milestone=Future&amp;target_milestone=4.0&amp;target_milestone=3.4&amp;keywords_type=allwords&amp;keywords=plan+api&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:deferred>
</p:theme>
<p:theme name="Everything">
<p:description>
<div>Following are plan items including those not yet categorized
into a theme.</div>
</p:description>
<!-- keyword "plan" -->
<p:committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=JSDT&amp;target_milestone=3.3&amp;target_milestone=3.3+M1&amp;target_milestone=3.3+M2&amp;target_milestone=3.3+M3&amp;target_milestone=3.3+M4&amp;target_milestone=3.3+M5&amp;target_milestone=3.3+M6&amp;target_milestone=3.3+M7&amp;target_milestone=3.3+RC1&amp;target_milestone=3.3+RC2&amp;target_milestone=3.3+RC3&amp;target_milestone=3.3+RC4&amp;keywords=plan&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit" />
<p:proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=JSDT&amp;target_milestone=---&amp;keywords=plan&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:proposed>
<p:deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=JSDT&amp;target_milestone=Future&amp;target_milestone=4.0&amp;target_milestone=3.4&amp;keywords=plan&amp;order=target_milestone%2Cpriority%2Cbug_id&amp;cmdtype=doit"></p:deferred>
</p:theme>
</p:themes_and_priorities>
<p:appendix name="References">
<ul>
<li>
The general WTP plan can be found
<a
href="http://www.eclipse.org/projects/project-plan.php?projectid=webtools">here</a>
.
</li>
</ul>
</p:appendix>
</p:plan>