Project Plan For PHP Development Tools, version 2.2

Introduction

The PDT project provides a PHP Development Tools framework for the Eclipse platform. This project encompasses all development components necessary to develop PHP and facilitate extensibility. It leverages the existing Web Tools Platform (PDT) and Dynamic Languages Toolkit (DLTK) in providing developers with PHP capabilities.

Release Deliverables

  • PDT runtime package
  • PDT SDK Package
  • PDT Automated Test Package
  • The Eclipse IDE for PHP Developers package

Table of Contents

Release Milestones

PDT Milestones follow the Eclipse release milestones by an offset of 3 as set by theGalileo release schedule.

M311/12/2010

M3 milestone

M412/18/2010

M4 milestone

M502/05/2010

M5 milestone

M603/19/2010

M6 milestone.Feature complete, API and UI Freeze

M75/07/2010

M7 milestone. PMC review starts

RC105/21/2010

RC1 milestone.PMC approval required, 1 vote required

RC25/28/2010

RC2 milestone.PMC approval required, 2 votes required

RC36/17/2010

RC3 milestone.Document Freeze. PMC approval required, 3 votes required

GA6/23/2010

GA

Table of Contents

Target Environments

PDT will support the platforms certified by the Eclipse Platform project. For a list of platforms supported in PDT 2.2, seeEclipse Target Operating Environments

.

Internationalization

Internationalization and Localization will be supported.

  • Internationalization (I18N)

    Each project should be able to work in an international environment, including support for operating in different locales and processing/displaying international data (dates, strings, etc.).

  • Localization

    Each project should provide an environment that supports the localization of the technology (i.e. translation). This includes, but is not limited to, ensuring that strings are externalized for easy translation.

  • Where possible, projects should use an open and transparent process to create, maintain and deliver language packs translated into multiple languages in a timely manner. The primary languages to consider are: English, Simplified Chinese, Traditional Chinese, Japanese, French, German, Spanish.

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. The following themes are derived from those defined by the Eclipse Requirement council for the Eclipse Galileo release and from the PDT 2.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 PDT 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.

Ease of Use

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

  • PDT User Interface should be consistent and should follow the Eclipse User Experience Guidelines.
  • Usability and Accessibility reviews should be done for the most common task flows. Cheat Sheets should be provided to assist users in performing tasks
  • PDT should provide enhanced user documentation, tutorials, white papers, demonstrations.

  • Committed
    • No items.
  • Proposed
    • No items.
  • Deferred
    • No items.

PHP 5.3 and Phar Support

PDT should be up-to-date with supporting the latest Phar and PHP 5.3 specification level.

  • Committed
    • No items.
  • Proposed
    • No items.
  • Deferred
    • No items.

Other

Following are plan items that are not yet categorized into a theme.

  • Committed
    • No items.
  • Proposed
    • No items.
  • Deferred
    • No items.

Table of Contents

Appendix References

  1. The general tools plan can be foundhere.

Table of Contents

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