|Date||Wed May 24 12:57:32 CDT 2017|
|Founders||Curtis Rueden, Mark Hiner|
|Contributors||Mark Hiner, Johannes Schindelin, Chris Allan, Barry DeZonia, Christian Dietz, Richard Domander, Gabriel Einsdorf, Aivar Grislis, Jonathan Hale, Grant Harris, Lee Kamentsky, Rick Lentz, Melissa Linkert, Kevin Mader, Hadrien Mary, Alison Walter, Jay Warrick|
First and foremost, SciJava Common is a plugin framework—a base for developing highly modular and extensible Java applications.
All plugins available on Java's classpath are automatically discovered and made available. This is accomplished by scanning classpath resources for the file path
META-INF/json/org.scijava.plugin.Plugin. Such files are generated at compile time by a Java annotation processor that writes them in response to
@Plugin annotations on Java classes, an idea inspired by the SezPoz project.
All program state, such as available plugins, is accessible from a root object known as the application context.
ImageJ encapsulates its various parts as separate "services" that provide related state functionality and track related program state. An instance of the ImageJ class is nothing more than a collection of these services; this instance is referred to as the "application gateway." Services are defined as interfaces, with concrete implementations as plugins. This design provides seams in the right places so that behavior at every level can be customized and overridden.
Here are a few of SciJava Common's major core services:
- AppService - Tracks software applications (SCIFIO, ImageJ, etc.) present in the context.
- DisplayService - Tracks available displays, as well as the active display, and provides the means to create new displays to visualize data.
- EventService - Publishes events to the event bus, and allows interested parties to subscribe to them. The service provides the central means of communication between various parts of the codebase.
- IOService - General tools for opening and saving data within the context.
- MenuService - Builds the application menu structure.
- ModuleService - Tracks available modules, and provides the infrastructure for executing them.
- ObjectService - Tracks available objects of various types, including Datasets and Displays.
- OptionsService - Tools for managing program settings.
- PlatformService - Provides hooks for extending the application's behavior depending on the deployment platform (operating system, version of Java, etc.).
- PluginService - Tracks available plugins, and provides the infrastructure for executing them (using the ModuleService).
- StatusService - Publishes status updates for ongoing operations.
- ThreadService - Manages multithreading.
- ToolService - Tracks available tools—logic binding user input to behavior—as well as the active tool (selected on the toolbar).
- UIService - Discovers and launches a user interface for interacting with ImageJ.
Some of the services which ImageJ adds:
- DatasetService - Tools for creating and managing image data.
- ImageDisplayService - Similar to DisplayService, but specifically for ImageDisplays.
- OverlayService - Tools for creating and managing image overlays and regions of interest (ROIs).
SCIFIO provides several additional services—in particular:
- FormatService - Service for managing available image formats.
The SciJava menuing system is divided into several layers, to make it easier to override its behavior or customize its appearance in a user interface.
Each module known to the system (via the ModuleService can have a
menuPath that says where it should live (by default) in the menu. It is also has a
menuRoot that says in which menu it should live, with the default being the
APPLICATION_MENU_ROOT, indicating the main application menu structure.
The MenuService takes care of constructing ShadowMenu tree structures for all available modules in the system, using their
menuRoot values. These tree structures are UI-agnostic. There is one
menuRoot, which can be requested at will from the
The UIService then takes care of constructing an actual UI-specific menu bar (or whatever UI components and/or widgets it wants) from the available
ShadowMenus. There is a type hierarchy beneath the MenuCreator interface intended for this purpose; for example, the SwingJMenuBarCreator implements
MenuCreator to create and maintain a Swing JMenuBar that reflects the state of a particular
How changes propagate
When modules are added, removed or changed (via ModulesAddedEvent, ModulesRemovedEvent, ModulesUpdatedEvent), the
MenuService listens and updates the associated
ShadowMenu(s) accordingly. It notifies interested parties that it has done so by firing a corresponding event: MenusAddedEvent, MenusRemovedEvent, or MenusUpdatedEvent.