Component Areas for Platform UI

Platform UI is divided into the following functional areas. The tags in square brackets are used in bug report subject headings to indicate the affected area. The current owner of each functional area is indicated in parentheses. The queries here may not represent all bugs in a given component area if there are any that havn't been properly tagged.

Last updated: August 21, 2007

Component

Description
[About] About dialog and System Summary Editor
[ActionSets] Action sets
[ActivityMgmt] Support for activity grouping of functionality (AKA: Capabilities)
[BiDi] Bidirectional support. Triage '-dir rtl' defects to the appropriate component area first (i.e. if it's a Drag 'n Drop issue that only shows up in 'rtl' mode then triage to [DnD]...)
[CellEditors] Cell editors in Tasks view, Properties view or other views
[Commands] Command support (added in 3.0)
  • handlers. Anything dealing with handlers and handler submissions.
  • instrumentation. Instrumenting the command architecture for gathering user information.
  • macros. Sequential list of commands. Grouping commands.
  • parameters. The ability to pass parameters to commands. This is generally requested so that dyanamic commands can be defined (e.g., launch configurations).
  • performance. The performance of the key binding architecture, or its registry.
  • request. A request for a new command or a new key binding (or both).
[CommonNavigator] The generic navigator API (org.eclipse.ui.navigator).
[Contexts] Support for context grouping of functionality
[Contributions] ContributionManager, ContributionItem hierarchy, org.eclipse.jface.action, action contributions from plugin.xml
  • adapters. Anything to do with the adapter mechanism and its friends.
  • configurability. The end user's ability to manipulate contributions.
  • duplication. Places where code needs to be duplicated needlessly.
  • dynamic. Anything dealing with dynamic menus
  • dynamic plug-ins. The ability to respond to plug-ins appearing or disappearing.
  • errors. Error handling in the contributions framework.
  • interactions. How contributions from different plug-ins interact with each other. How different contributions interact with each other in the same plug-in. Also, things which the workbench can do, but plug-ins can't.
  • ordering. Controlling the order of items in the menu -- in Java or XML.
  • updating. Behaviour of the menu and toolbar management code, in response to changes in its components. This primarily deals with visibility and whether items are enabled. It also covers selection and optimization of selection changes.
  • visible/enabled. The control of visibility and the enabled state through XML.
  • widgets. Controlling the type of widget used to display a contribution. This only includes controlling widget behaviour and state (other than visible and enabled).
[Coolbar] Coolbar support (including layout within coolbar)
[DataBinding] JFace Data Binding
[Decorators] Decorators mechanism and Label Decorations preference page
[DetachedView] Views and editors in separate windows
[Dialogs] JFace and UI dialogs other than IDE, Filtered Items/Open Resource
[DND] Drag and Drop. Does not include dragging views and editors.
[DynamicUI] The ability to add/remove plug-ins from a running Eclipse
[EditorMgmt] General editor management, not text editor specific
  • associations. The file associations mechanism: behaviour, preferences and functionality.
  • drop-down. The editor drop-down: look, feel, bugs, etc.
  • history. The navigation history mechanism.
  • tabs. The tabbed editor user experience, and bugs related to editor tabs.
[EFS] Extended File System Support
[ErrorHandling] OutOfMemory, NPE etc. Exceptions that are not exepected but need to be handled to make it robust
[Examples] the 3 workbench examples (multipageeditor, propertysheet, readmetool) but not javaeditor (owned by platform-text component)
[FastView] issues related to fast views
[Features] UI related to features, other than [About], e.g. product branding, default perspective, etc.
[FieldAssist] Defects concerning ControlDecoration, Required Fields, Content Proposal, Decorated Fields or Field Assistance
[GlobalActions] actions created in workbench action builder that are not directly related to other components
[Graphics] Any graphics that UI has control over.
[GTK/Linux] GTK/Linux specific issues.
[Help] F1 help; missing or problems with content
[IDE] Issues related to the IDE as an app (as opposed to RCP)
[Intro] Intro part management and legacy welcome page support
[Import/Export] Import/Export wizards
[JFace] parts of JFace not covered by [Dialogs], [Preferences], [Viewers] and [Wizards]
[KeyBindings] Key bindings engine and preferences; requests to change key bindings, or keys not working
  • assist. The key binding assist dialog.
  • doc. Documentation, articles or notes about best practices. Also, changing code to conform to best practices.
  • errors. Error handling.
  • interactions. Interactions between the key binding architecture and native facilities (e.g., mnemonics). Also, the order in which events arrive.
  • misc Anything does not fit in other categories.
  • out-of-order. Anything dealing with the two special keys: ESC and DEL.
  • performance. The performance of the key binding architecture, or its registry.
  • preference page. The keys preference page.
  • registry. The registry, its syntax, and backward compatibility.
  • request. A request for a new command or a new key binding (or both).
[LinkedResources] Handling of linked resources in Navigator and New File/Folder wizards
[Mac] Mac specific issues
[Markers] Issues related to markers, including tasks, problems, bookmarks, etc. e.g. bugs related to MarkerImageProvider, MarkerHelp, MarkerResolutions
[Metadata] Anything related to the metadata associated with plug-ins (e.g., MANIFEST.MF, build.properties, .classpath, version numbers, compiler settings, formatter settings, etc.)
[Model] anything related to org.eclipse.ui.model classes IWorkbenchAdapter, WorkbenchLabelProvider, WorkbenchContentProvider
[MPE] bugs related to Multipage editor that are not [Editor Mgmt] and not editor specific
[Navigator] Navigator view
[OLE] OLE support on Windows
[OpenModes] Single click, double click support
[OpenResource] Open Resource and FilteredItemsSelection dialogs
[Outline] Outline view
[PerspectiveBar] The bar used to indicate which perspectives are currently open and allow easy switching between them.
[Perspectives] Perspective management
[Preferences] preferences dialog, field editors and workbench preference pages
[PresentationAPI] Bugs pertaining to the presentation API.
[Presentations] Code related to maintaining the Eclipse 2.1 and 3.0 look and feel.
[Progress] Responsive UI work relating to Progress View and Progress dialogs
[PropertiesDialog] Properties dialog
[PropertiesView] Properties view
[QuickAccess] Ctrl-3 quick access dialog issues
[RCP] Rich Client Platform issues
[StatusHandling] Issues related to the status handling facliity (added in 3.3)
[TabbedProperties] Tabbed Properties issues (plugin org.eclipse.ui.views.properties.tabbed)
[Themes] Dealing with dialog/window fonts/colours and the theme API
[Trim] Defects in Trim contributions or trim management (DnD, persistance, layout...)
[Undo] Dealing with the new undo/redo support introduced in Eclipse 3.1
[ViewMgmt] View management
[Viewers] JFace viewers
[Win32] Win32 specific issues
[Wizards] JFace wizards and workbench new item wizards (excluding import/export)
[Workbench] ui.plugin, Workbench, WorkbenchWindow
[WorkbenchParts] Bugs pertaining to part lifecycle.
[WorkbenchLauncher] Primarily, that portion of startup where the UI team decides where the workspace will be.
[WorkingSets] Working sets