Platform UI consists of several components, which provide the basic building blocks for user interfaces built with Eclipse. Some of these can be reused in arbitrary applications, while others are specific to the Eclipse IDE.
Two of the Platform UI components form the Rich Client Platform UI. These are JFace and the Workbench. JFace and the Workbench can be used to build arbitrary applications, not just the Eclipse IDE. The Eclipse IDE is just one instance of an RCP application, but it demonstrates the power and extensibility achievable by RCP applications.
Platform UI also provides the IDE application plug-in, which instantiates and configures the Generic Workbench to form the IDE Workbench, on top of which lies the rest of the Eclipse IDE Platform and the Eclipse SDK (including the Java Development Tools and Plug-in Development Environment). Unlike the Generic Workbench, the IDE application plug-in is intended only for use in the IDE Platform, and is not designed as a reusable component for use in other RCP applications.
Platform UI does, however, provide some other components that can be reused in other RCP applications. These are:
- the Outline and Properties views
- the Console view (owned by Debug)
- the Welcome Page / Intro support, with guided assistance (owned by User Assistance)
- Cheat Sheets, which guide the user through a long-running, multi-step task (owned by User Assistance)
- Common Navigator Framework and default instance ("Project Explorer")
- Platform Text generic support for text editors and annotations
Links of general interest:
- Platform UI 4.2 Plan shows our milestone-level plan for the 4.2 release.
- Platform UI 3.5 Plan shows our milestone-level plan for the 3.5 release.
- Platform UI/New Extension Point contains some hints and tips for those developing new extension points for the workbench.
- Platform UI/ResourceNavigator ResourceNavigator end of life plan.
Links for committers:
- Platform UI/Testing contains the test responsibilities for the next milestone.
- Platform UI Cycle contains the breakdown of triage and build responsibilities for the 3.6 release cycle.
- Platform UI/Bug Triage has instructions on how new Platform UI bugs should be handled.
- Platform UI/Build Submission contains steps on how to do a build submission.
- Platform UI/Development Process explains our development process, i.e. how we work with Bugzilla and CVS, how to get changes into an integration build, what to do in a milestone week, etc.
- Platform UI/Housekeeping lists all the things the team does, organized by when and how often (daily/weekly/each milestone...)
- Platform UI/Performance_Tests gives instructions on how to run the automated performance tests.
Random other links:
- Platform UI Design Discussion has some brainstorming about work we could do.
- Platform UI Incubator has information on experimental workbench content, extensions, revisions, and tools.
- Field Decorators and Validation use cases and solutions for field decoration (content assist, required fields, etc)