If you are already a PDE UI developer, check out the Development Resources.

The Plug-In Development Environment (PDE) is a collection of integrated tools targeted at you, the plug-in developer. Some of PDE's contributions to the Eclipse workbench include:

• New Plug-in, fragment, feature and update site projects creation wizards.
• Multi-page editors to edit manifest files for plug-ins, fragments, features and update sites.
• Import wizards to import external plug-ins, fragments and features.
• Export wizards to build, package and deploy plug-ins, fragments and features.
• a launcher to test and debug your plug-in.
• a search engine to search for plug-ins, fragments, extensions, and extension points with a scope that goes beyond the workspace.
• a log view with sorting, filtering capabilities to view the contents of the log file.

Over the next 6 months the major focus points are:

• RCP tooling.
• Runtime/OSGi tooling.
• Improving feature development tooling.
• Enhancing existing features.
• Reducing the defect backlog

For more detailed information, check out the Development Resources.

3.2 Development Effort - Milestone 2 (September 23, 2005)

• Rich Client Platform
  • Enhance the New Plug-in Project Creation wizard to allow the creation of a headless rich client application.
  • Provide a Hello World headless RCP template.
  • Add Intro support to the RCP Product editor.
• Runtime/OSGi
  • Enhance the New Plug-in Project Creation wizard to allow the creation of a pure OSGi bundle that is not dependent on the runtime layer.
• An Integrated IDE
  • Plug-in working sets should participate in builds, view filtering, searches.
  • Participate in refactoring (manifest.mf, plugin.xml and fragment.xml files).
• Eclipse Application launcher
  • Make the launch configurations portable.
  • Make the launcher tabs and the runner configuration API.
• Reduce the defect backlog.

3.2 Development Effort - Milestone 3 (November 5, 2005)

• Runtime tooling
  • Implement an Equinox OSGi Framework launcher
  • Add a "3.2" target version in the New Plug-in Project creation wizard and start generating manifest files for the 3.2 runtime.
  • Automated management of exported packages in a plug-in.  Come up with a tooling equivalent of the old <export name="*"/>
  • More refactoring: renaming a package in an Export-Package header should result in the renaming of that package in all client bundles that have imported it.
• Bundle Execution Environment - Prelude to J2SE5.0 adoption
  • Add support for the Bundle-RequiredExecutionEnvironment manifest header into the PDE plug-in editor.
  • The New Plug-in/Fragment project creation wizard to start asking the user the level of JRE the plug-in is targeted for.
  • Use the Bundle-RequiredExecutionEnvironment header when importing plug-ins to set the correct compiler compliance levels.
• NLS tooling
  • Implement an NLS wizard to externalize plug-in manifest files
• Quick fixes (Investigation)
  • Investigate a quick fix support on manifest files.
  • The pioneer quick fix would be the one to fix the soon-to-be-deprecated Eclipse-AutoStart header.
• New Source Lookup (investigation)
  • start the investigation
  • co-ordinate with the Debug and Core teams on what pieces need to be in place.
• Reduce the defect backlog.

If you are interested in participating in the development of the PDE UI component, check out the developer's mailing list: pde-ui-dev@eclipse.org. Chat with people there about your problems and interests, and find out what you can do to help.

In particular, if you have written (or have ideas for) any utilities, "spy" functions, code generators, transformers, importers, exporters, or any other code that you find useful (or would find useful) for development of plug-ins, and would like to get involved in getting the function integrated as part of PDE, we would like to hear from you.

For more detailed information, check out the Development Resources.