Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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/Eclipse Application Services"

< E4
Line 11: Line 11:
 
* Reacting to changes to the context (such as plug-ins that come and go).
 
* Reacting to changes to the context (such as plug-ins that come and go).
 
* Scheduling background work.
 
* Scheduling background work.
* Contributing to the [[E4/Workbench_Model|workbench model]] (e.g. tool items, menus).
+
* Participating in editor lifecycle (units of saveability, dirtiness, saving, prompting to save).
 +
* Dynamically contributing to the [[E4/Workbench_Model|workbench model]] (e.g. tool items, menus, sub-parts).
 +
* Updating enablement, labels, icons of menu and tool items.
 
* Registering command handlers.
 
* Registering command handlers.
 
* Reacting to changes to the [[E4/Workbench_Model|workbench model]].
 
* Reacting to changes to the [[E4/Workbench_Model|workbench model]].
Line 17: Line 19:
 
* Reporting status (think status line).
 
* Reporting status (think status line).
 
* Logging.
 
* Logging.
 +
 +
Domain-specific services:
 +
* IWorkspace.
 +
* Database connection.
 +
* My EMF model.
 +
 +
Not sure about:
 +
* String comparison/collation.
 +
* String localization.

Revision as of 17:20, 16 October 2008

  • Receiving input.
  • Producing selection.
  • Persisting data (receiving persisted state, and producing persistable state).
  • Accessing preferences (mostly read access, but sometimes write access).
  • Managing shared resources (e.g. JFace LocalResourceManager).
  • Status handling (errors and warnings).
  • Connecting to the help system.
  • Participating in Undo/Redo.
  • Adapting objects.
  • Participating in label and icon decoration.
  • Reacting to changes to the context (such as plug-ins that come and go).
  • Scheduling background work.
  • Participating in editor lifecycle (units of saveability, dirtiness, saving, prompting to save).
  • Dynamically contributing to the workbench model (e.g. tool items, menus, sub-parts).
  • Updating enablement, labels, icons of menu and tool items.
  • Registering command handlers.
  • Reacting to changes to the workbench model.
  • Reporting progress and responding to cancellation requests.
  • Reporting status (think status line).
  • Logging.

Domain-specific services:

  • IWorkspace.
  • Database connection.
  • My EMF model.

Not sure about:

  • String comparison/collation.
  • String localization.

Back to the top