Orion client API can roughly be divided into services and library objects. Services are obtained via a service registry, rather than instantiated by the client code. All interaction with services are asynchronous. If there is a return value to be obtained from the service, it is provided via a callback object passed in by the client.
Library objects are either stateless objects providing utility functions, or statefull objects that are instantiated directly by each client that needs one. Library objects never contain shared state that is available to multiple plugins or services.
- 1 Services
- 1.1 Command Service
- 1.2 Dialog Service
- 1.3 Explorer Service
- 1.4 File Service
- 1.5 Editing Services
- 1.6 Log Service
- 1.7 Preferences
- 1.8 Selection Service
- 1.9 User Service
- 2 Library Objects
- The command service manages the available commands.
- A command is an object that describes an action a user can perform, as well as when and what it should look like when presented in various contexts.
- A KeyBinding represents of a key code and a modifier state that can be triggered by the user using the keyboard.
- Common dialog services
- A table-based explorer component
- Tree model used by eclipse.Explorer.
- Tree model used by eclipse.ExplorerTree.
- Provides operations on files, folders, and projects.
Getting directory contents
Creating work space
Loading work space
Deleting a file or folder
- Services for editor inputs
- Service for saving things
- Services for logging
- Service for reporting status
- A preference object provides functions for accessing and setting preferences
- Service for providing selections
- Service for keeping track of the user
The following objects are related to the Orion rich text editor found in editor.js.
- A Editor is a user interface for editing text.
- This is the event sent when the editor is destroyed.
- This is the event sent when the editor needs the style information for a line.
- This is the event sent when the text in the model has changed.
- This is the event sent when the text in the model is about to change.
- This is the event sent when the text is modified by the editor.
- This interface represents a ruler for the editor.
- This is the event sent when the editor scrolls.
- A Selection represents a range of selected text in the editor.
- This is the event sent when the selection changes in the editor.
- This object is used to define style information for the editor.
- This object is used to style range.
- The TextModel is an interface that provides text for the editor.
- This is the event sent when the text is about to be modified by the editor.
- An Outliner provides an itemized overview of a resource and acts as a selection provider on that resource.
- Provides API for searching the workspace.
The service registry is somewhat unusual as a library object. Although a client can directly instantiate a private service registry and populate it with their own services, a registry is more typically passed into services and plug-ins upon construction. This avoids objects having to "reach out" and know who or what defines a given service.
The following objects are all related to the service registry:
- A plugin is an object that is isolated in its own frame, and obtains and provides services via the asynchronous postMessage mechanism.
- The registry manages the set of available plugins.
- Represents a concrete service instance.
- A Service Provider is an object that implements a Service Type
- A ServiceReference enables services to be called and released.
Registering a local service
Calling a registered service
- Generates an HTML table where one of the columns is indented according to depth of children.
Constructing A Table Tree
- eclipse.util holds stateless utility methods.