Base classes for building a plugin-based, UI-driven application. Plugins may implement
Pluginfor a programmatic
ApplicationComponentfor life cycle methods and references to the rest of the application. In order to implement UI-actions, consider sub-classing
ApplicationAction, as it allows you to easily position the action in the UI.
- See Also:
- beaTunes plugins
Interface Summary Interface Description ActionContainerAction container. ApplicationComponent<T extends ApplicationComponent>An application component with support for a simple lifecycle and a main application object. PluginThe Plugin interface may be implemented by beaTlets that wish to provide a
PluginDescriptorto better control requirements and provide information about themselves, like copyright, license, etc.
PluginManager.PluginReference<P> UIRegionRegion in the UI that
ApplicationActions can be installed into.
Class Summary Class Description AbsoluteActionLocationAbsolute action location. ActionLocationSpecifies where in the UI an action should be installed. ApplicationActionApplication action. ApplicationAction.ApplicationActionFacadeFacade that suppresses certain action properties so that the action that may have rich icons etc can also be used in other contexts. Digest PluginDescriptorDescribes a plugin(-bundle/jar) and its requirements. PluginManager<T extends ApplicationComponent>Loads, starts and makes plugins available. PluginRepositoryPlugin Repository. RelativeActionLocationRelative action location. RuntimePluginDescriptorDescribes a plugin(-bundle/jar) and its requirements at runtime. ScriptEngineAdapterThis adapter for ScriptEngine allows the instantiation of classes defined in a script file. ScriptPluginLoader<A extends ApplicationComponent>Script loader (mainly for beaTlets). VersionRepresenting a version.
Enum Summary Enum Description RelativeActionLocation.RelativePositionRelative positions.
Exception Summary Exception Description ShutdownVetoExceptionSignals that a component does not want to be shut down.