Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "E4/3X API Survey"

< E4
(Model (Decorators, Workbench model, dynamism))
(Working Sets)
Line 45: Line 45:
 
== Working Sets ==
 
== Working Sets ==
 
Working sets, in general, are a somewhat awkward construction.  They are often used as a filter on your workspace but are implemented as a bag.  It might be useful in e4 to deprecated working sets in favour of a proper model "view" API.
 
Working sets, in general, are a somewhat awkward construction.  They are often used as a filter on your workspace but are implemented as a bag.  It might be useful in e4 to deprecated working sets in favour of a proper model "view" API.
* IWorkingSetManager
+
* [http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/IWorkingSetManager.html IWorkingSetManager]
* IWorkingSet
+
* [http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/IWorkingSet.html IWorkingSet]
 
* IWorkingSetUpdater
 
* IWorkingSetUpdater
 
* IWorkingSetNewWizard
 
* IWorkingSetNewWizard

Revision as of 14:06, 28 May 2008

Overview

The purpose of this page is to provide a gross overview of APIs found within 3.X platform and their applicability to 4.0. For each API there is a brief note summarizing their condition in e4, be that deprecated, superseded, or still useful as well as a list of the applicable classes/interfaces. For organizational purposes it would be helpful to segregate the list by source plug-in, and within each plug in by logical grouping (if applicable).

This list is in no way exhaustive or authoritative.

org.eclipse.ui (org.eclipse.ui.workbench)

Workbench

This area covers the top-level conceptual beast that is "the workbench."

Layouts

Parts

Preferences

Wizards

Are our classifications of wizards necessary?

Model (Decorators, Workbench model, dynamism)

Working Sets

Working sets, in general, are a somewhat awkward construction. They are often used as a filter on your workspace but are implemented as a bag. It might be useful in e4 to deprecated working sets in favour of a proper model "view" API.

Commands (Operations)

  • IWorkbenchOperationSupport

Contributions (Menus, Toolbars, Keybindings, Action Sets, Object Contributions)

Themes

With the addition of proper CSS handling Themes would likely be made redundant.

  • ITheme
  • IThemeManager
  • IThemePreview

Activities (Capabilities)

If everything in the workbench is backed by a model, are activities still needed? Could suppression of contributions be seen as a filter on that model?

  • IWorkbenchActivitySupport
  • ITriggerPointAdvisor

User Experience (Intro, Help, Browser)

Intro, at the workbench level, is effectively built as a hack on top of views. With a more flexible view model it may be possible to do away with intro entirely.

  • IIntroManager
  • IWorkbenchHelpSystem
  • IWorkbenchBrowserSupport

Back to the top