Package diva.gui

The Diva GUI framework.

See: Description

Interface Summary

Interface	Description
AppContext	A context for either an application or an applet that wants to use the diva.gui infrastructure.
Application	Application is an interface that captures the notion of a graphical application.
ContextView	A Context view is a view that knows about an app context that it exists.
Document	Document is an interface that captures the notion of a document in a graphical application.
DocumentFactory	DocumentFactory is an factory interface that creates Document objects.
MDIContext	An app context that provides methods for multiple documents and views.
Page	A multi-page document contains an ordered set of pages.
StoragePolicy	StoragePolicy captures the notion of how an application deals with persistent storage.
View	View is an interface that captures the notion of a view on a document in a graphical application.
ViewListener	A listener interface for receiving events on views.

Class Summary

Class	Description
AbstractApplication	An abstract implementation of the Application interface.
AbstractDocument	An abstract implementation of the Document interface.
AbstractStoragePolicy	It is nice if storage policies suggest good pathnames.
AbstractView	An abstract implementation of the View interface that consists of mostly empty methods to be filled in by concrete subclasses.
AppContextDelegate	This class provides basic support for an instance of AppContext which delegates its operation to one of the basic AppContexts (usually an AppContext or an ApplicationContext.) This is similar to an interface adapter, except the default implementation of each method is to call the identical method on the delegate context.
ApplicationContext	A context for an application in the diva.gui infrastructure.
ApplicationExceptionHandler	This class makes it easy for an application to trap exceptions in AWT event handlers.
ApplicationResources	Deprecated Use diva.resource.DefaultBundle instead.
BasicFrame	BasicFrame is a very simple application context that is used to display tutorial examples.
BasicPage	A simple concrete implementation of the Page interface.
BasicStoragePolicy	A StoragePolicy that doesn't really check for correct operation.
DefaultActions	A collection of static methods that create useful default actions.
DefaultStoragePolicy	A Default storage policy that is useful for most applications.
DesktopContext	DesktopContext is an application context that displays multiple content panes in an instance of a JDesktopPane.
ExtensionFileFilter	A convenience implementation of FileFilter that filters out all files except for those type extensions that it knows about.
GUIUtilities	A collection of utilities for the GUI.
MDIApplication	An abstract superclass for applications that use an MDI (multiple document interface) style of presentation.
MultipageDocument	A document that contains a linear sequence of Pages.
MultipageModel	A document that contains a linear sequence of Pages.
MultipageParser	Parse all pages of a multi-page document from a file.
MultipageWriter	MultipageWriter writes out all pages of a multi-page document to a file.
MultiWindowApplication	An application that manages a group of toplevel frames for each document.
ViewAdapter	An adapter for view listener, containing empty method implementations.
ViewEvent	A view event is generated when a view of a Document is iconified, selected, closed, and so on.

Package diva.gui Description

The Diva GUI framework. This is a simple and extensible application framework that most applications should be able to build on without too much trouble. There are two kinds of class in here:

• GUI components. The GUI portion makes extensive use of Swing widgets. The set of classes of this kind ranges from simple widgets that we needed up to full-featured application frames.
• Document framework classes. These classes provide a set of classes to ease the task of constructing multi-document applications. The document framework uses the model-view-controller architecture to manage the state of the application.

In both cases, we have been careful not to make policy decisions that will impact your ability to customize and extend these classes to suit your own needs. An example: there is no default menu layout, so you are not restricted to using conventional (File, Edit etc) menu layouts if you don't want to. There is, however, a good deal of support for standard menu entries if you choose to use it!