|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||
See:
Description
| Interface Summary | |
| AutoConfigurable | A class that implements AutoConfigurable can use the AutoConfigurer
class to automatically build a property editor. |
| Buildable | A Buildable instance can be initialized from a configuration file. |
| Configurable | An object that implements the Configurable interface can, in addition to being built from a configuration XML file, be manipulated by the user directly in the VASSAL module editor via the Configuration window. |
| Class Summary | |
| AbstractBuildable | Abstract implementation of the Buildable interface To make a Buildable component, extend this class. |
| AbstractConfigurable | An abstract implementation of the Configurable interface. |
| AutoConfigurable.Util | |
| Builder | This class holds static convenience methods for building Buildable
objects |
| GameModule | The GameModule class is the base class for a VASSAL module. |
| Widget | A general-purpose configurable GUI container
Widgets are Configurable objects that represent
AWT components. |
| Widget.MyCellRenderer | |
| Exception Summary | |
| IllegalBuildException | An Exception indicating that an illegal operation was performed when building a Buildable component |
Provides classes for building Java instances automatically from XML
files. This is a home-grown XML-Java binding used to build a GameModule from the module file. Every XML element in
the buildFile corresponds to the name of a class in the
build package hierarchy. If a class can contain other
Buildable instances as sub-components, those
sub-component classes will be contained in a corresponding package. For
example, the VASSAL.build.module.map package contains
classes that are valid sub-components of the Map class.
Buildable
|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||