According to the MVC paradigm, the model represents the application
data. In
JViews TGO,
the model module, referred to as the
representation
model, is a container for representation objects to which it
provides access. See
Representation objects.
Whenever possible, JViews
TGO representation models are derived from existing Swing models
and like them use listeners to notify attached views of any changes
in the data. Like Swing models, JViews TGO representation
models use the JavaBeans™ Event model to implement the notification
process. In JViews TGO,
notifications are stateful, which means that they not only inform
that a modification has occurred, but also indicate what is the
nature of that modification.
Also, like Java™ Swing models, representation models impose a
specific structure on the objects they hold. Therefore, JViews TGO provides a
different representation model for each type of data structure to
be addressed and hence for each type of graphic component
displaying this data.
JViews TGO provides the
following representation model interfaces:
For more information about these predefined
representation models, see the information on each graphic
component.