Package org.esa.beam.framework.ui.command

This package provides an implementation of the GoF 'Command Pattern' for the MERIS/(A)ATSR Toolbox.

See:
Description

Interface Summary

CommandComponentFactory	This interface is currently not used.
CommandListener	The CommandListener is a ...
CommandManager	A command manager is used to create, register and deregister a list of commands.
CommandStateListener	The listener for receiving command events from ExecCommands, ToolCommands and CommandGroups.
CommandUIFactory	The CommandUIFactory is used to create menu items and tool bar buttons for different types of a Command instance.

Class Summary

BarBuilder
Command	The Command is a ...
CommandAdapter	The CommandAdapter is a ...
CommandEvent	The CommandEvent is a ...
CommandGroup	The CommandGroup is a group of commands represented by a menu item group.
CommandMenuUtils	The CommandMenuUtils is a helper class to build up menus.
DefaultCommandManager	The DefaultCommandManager provides a default implementation for the CommandManager interface.
DefaultCommandUIFactory	The DefaultCommandUIFactory is used to create menu items and tool bar buttons for a given Command.
ExecCommand	The ExecCommand is an ...
SelectableCommand	A command which also has a 'selected' state.
ToolCommand	A command which activates a tool.

Package org.esa.beam.framework.ui.command Description

This package provides an implementation of the GoF 'Command Pattern' for the MERIS/(A)ATSR Toolbox.

This implementation of the command pattern

separates application logic from GUI code,

builds upon the Swing Action Architecture, but command code is executed in separate command listeners,

provides commands, checked commands and command groups

provides automatic menu registration:

ordinary commands create ordinary menu items,

checked commands create check-box menu items,

command groups create sub-menus

provides all properties that a Swing Action can have plus the 'checked' property

provides context dependend popup-menu registration (not implemented yet)

uses command constraints to decide where (parent/location) and when (context dependent) a command appears in the GUI

enables tracking of which commands have been performed,

eases the implementation of undo/redo capabilities (in the future)