Construct a new application.
The options for creating the application.
The application command registry.
The application context menu.
The application shell widget.
The shell widget is the root "container" widget for the entire application. It will typically expose an API which allows the application plugins to insert content in a variety of places.
A promise which resolves after the application has started.
This promise will resolve after the start() method is called,
when all the bootstrapping and shell mounting work is complete.
Activate the plugin with the given id.
The ID of the plugin of interest.
A promise which resolves when the plugin is activated or rejects with an error if it cannot be activated.
Add the application event listeners.
The default implementation of this method adds listeners for
'keydown' and 'resize' events.
A subclass may reimplement this method as needed.
Attach the application shell to the DOM.
The id of the host node for the shell, or ''.
If the id is not provided, the document body will be the host.
A subclass may reimplement this method as needed.
A method invoked on a document 'contextmenu' event.
The default implementation of this method opens the application
contextMenu at the current mouse position.
If the application context menu has no matching content or if the shift key is pressed, the default browser context menu will be opened instead.
A subclass may reimplement this method as needed.
A method invoked on a document 'keydown' event.
The default implementation of this method invokes the key down processing method of the application command registry.
A subclass may reimplement this method as needed.
A method invoked on a window 'resize' event.
The default implementation of this method updates the shell.
A subclass may reimplement this method as needed.
Handle the DOM events for the application.
The DOM event sent to the application.
This method implements the DOM EventListener interface and is
called in response to events registered for the application. It
should not be called directly by user code.
Test whether a plugin is registered with the application.
The id of the plugin of interest.
true if the plugin is registered, false otherwise.
List the IDs of the plugins registered with the application.
A new array of the registered plugin IDs.
Register a plugin with the application.
The plugin to register.
An error will be thrown if a plugin with the same id is already registered, or if the plugin has a circular dependency.
If the plugin provides a service which has already been provided by another plugin, the new service will override the old service.
Register multiple plugins with the application.
The plugins to register.
This calls registerPlugin() for each of the given plugins.
Resolve an optional service of a given type.
The token for the service type of interest.
A promise which resolves to an instance of the requested
service, or null if it cannot be resolved.
Services are singletons. The same instance will be returned each time a given service token is resolved.
If the plugin which provides the service has not been activated, resolving the service will automatically activate the plugin.
User code will not typically call this method directly. Instead, the optional services for the user's plugins will be resolved automatically when the plugin is activated.
Resolve a required service of a given type.
The token for the service type of interest.
A promise which resolves to an instance of the requested service, or rejects with an error if it cannot be resolved.
Services are singletons. The same instance will be returned each time a given service token is resolved.
If the plugin which provides the service has not been activated, resolving the service will automatically activate the plugin.
User code will not typically call this method directly. Instead, the required services for the user's plugins will be resolved automatically when the plugin is activated.
Start the application.
The options for starting the application.
A promise which resolves when all bootstrapping work is complete and the shell is mounted to the DOM.
This should be called once by the application creator after all initial plugins have been registered.
If a plugin fails to the load, the error will be logged and the other valid plugins will continue to be loaded.
Bootstrapping the application consists of the following steps:
Generated using TypeDoc
A class for creating pluggable applications. The namespace for the
Applicationclass statics.Notes
The
Applicationclass is useful when creating large, complex UI applications with the ability to be safely extended by third party code via plugins.