Listener that listens to changes in an addon container.
Listener that can be informed when data sources are being handled.
This is the central backend of Lucy where all add-ons are registered, to which add-ons can add functionality and from which already added functionality can be retrieved.
Listener for changes in a
A help manager is responsible for offering the possibility to context sensitive help.
Event thrown when the addon container has changed.
Manager that takes care of everything related to adding new data formats.
Class that represents the logic to choose a
Class that represents the logic to choose one or multiple
Event fired when a set of data sources is handled.
Event describing significant state changes in the Lucy backend.
Factory class to create a
Lucy's default frontend.
Manager of preferences.
A factory to create
Class that handles the addon loading.
The following image illustrates the relations between the front-end, back-end and addons
The back-end is the core of Lucy: it is the basic point where add-ons of Lucy can extend the Lucy functionality (for instance by adding extra model decoders) and retrieve all kinds of information (for instance what maps are currently available).
Addons are the modular elements that add functionality to the Lucy application. They are plugged in into the back-end, and they in their turn plug their functionality into the back-end.
The front-end glues all parts together: it is responsible for creating the main user interface,
instantiating and configuring the back-end and creating and plugging all the addons. The default
front-end creates a separate user interface, but it is possible to write a custom Lucy frontend
that integrates the Lucy application with another existing application. For example, the
lucy.frontend.mapcentric sample demonstrates how to customize the front-end in order to
show a map-centric application with panels that float over the map.