Difference between revisions of "Platform UI"

From Eclipsepedia

Jump to: navigation, search
 
(31 intermediate revisions by 12 users not shown)
Line 1: Line 1:
 +
{{Platform UI}}
 
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.
 
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.
 
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.
 
JFace is a UI toolkit with classes for handling many common UI programming tasks. JFace is window-system-independent in both its API and implementation, and is designed to work with [[SWT]] without hiding it. JFace includes the usual UI toolkit components of image and font registries, text, dialog, preference and wizard frameworks, and progress reporting for long running operations. Two of its more interesting features are actions and viewers. The action mechanism allows user commands to be defined independently from their exact whereabouts in the UI. Viewers are model based adapters for certain SWT widgets, simplifying the presentation of application data structured as lists, tables or trees.
 
 
The Workbench provides the user interface structure for Eclipse. The purpose of the Workbench is to facilitate the seamless integration of tools. These tools contribute to extension points defined by the Workbench. The Workbench is responsible for the presentation and coordination of the user interface. The tools metaphor is not specific to development tools, but can apply equally well to arbitrary applications. Note that the Workbench is sometimes called the Generic Workbench, to distinguish it from its instantiation in the Eclipse IDE, where it is called the IDE Workbench.
 
  
 
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 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.
Line 12: Line 9:
  
 
* the Outline and Properties views
 
* the Outline and Properties views
* the Console view
+
* the Console view (owned by [[Debug]])
* the Welcome Page / Intro support, with guided assistance
+
* 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
+
* 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
 +
 
 +
For more details on the Rich Client Platform and other components available for use in RCP applications, see the [[Rich Client Platform|RCP Home Page]] and the [[RCP FAQ]].
 +
 
 +
Links of general interest:
 +
* [[Platform_UI/Plan/4.2|Platform UI 4.2 Plan]] shows our milestone-level plan for the 4.2 release.
 +
* [[Platform_UI/Plan/3.5|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)
 +
 
 +
Accessibility
 +
* [[Platform UI/Accessibility Features]]
 +
* [[Platform Accessibility Testing]]
 +
* [[Platform Accessibility Status]]
 +
 
 +
<googlecalendar width="100%" height="300" mode="AGENDA" title="Platform UI Calendar">k2p11l83aoci65qpf9jgpf3j5c%40group.calendar.google.com</googlecalendar>
 +
This calendar is available in the following formats:<br>
 +
[[Image:Ical.gif]][http://www.google.com/calendar/ical/k2p11l83aoci65qpf9jgpf3j5c%40group.calendar.google.com/public/basic.ics iCal],[[Image:Xml.gif]][http://www.google.com/calendar/feeds/k2p11l83aoci65qpf9jgpf3j5c%40group.calendar.google.com/public/basic ATOM News Feed],[[Image:Html.gif]][http://www.google.com/calendar/embed?src=k2p11l83aoci65qpf9jgpf3j5c%40group.calendar.google.com&ctz=Canada/Toronto HTML]
 +
 
  
For more details on the Rich Client Platform and other components available for use in RCP applications, see the [[Rich Client Platform][RCP Home Page]] and the [[RCP FAQ]].
+
[[Category:Platform UI]][[Category:Eclipse Project]]

Revision as of 09:18, 30 June 2011

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

For more details on the Rich Client Platform and other components available for use in RCP applications, see the RCP Home Page and the RCP FAQ.

Links of general interest:

Links for committers:

Random other links:

Accessibility

This calendar is available in the following formats:
Ical.gifiCal,Xml.gifATOM News Feed,Html.gifHTML