Uses of Package
ARoad0.Pattern

Packages that use ARoad0.Pattern
ARoad0.AcsAddon.Accbee.MySQL.gBase Provides the gBase classes for modelling a MySQL 5 server as an extension, in the AcsAddon MySQL, of the generic ARoad0.gBase package. 
ARoad0.AcsAddon.Accbee.MySQL.gBaseBeanInfo Provides the gBaseBeanInfo classes for modelizing a MySQL 5 database management system, as an extension of the generic ARoad0.gBaseBeanInfo package, in the AcsAddon MySQL. 
ARoad0.AcsAddon.Accbee.MySQL.gWork Provides the gWork classes for creating and analyzing a MySQL 5 database management system, as an extension of the generic ARoad0.gWork package, in the AcsAddon MySQL. 
ARoad0.AcsAddon.Accbee.Ubuntu.gBase Provides the gBase classes for modelizing a Linux Ubuntu operating system, as an extension, in the AcsAddon Ubuntu, of the generic ARoad0.gBase package. 
ARoad0.AcsAddon.Accbee.Ubuntu.gBaseBeanInfo Contains the gBaseBeanInfo classes for modelizing a Linux Ubuntu operating system, as an extension of the generic ARoad0.gBaseBeanInfo package, in the AcsAddon Ubuntu. 
ARoad0.AcsAddon.Accbee.Ubuntu.gWork Contains gWork classes for creating and analyzing a Linux Ubuntu operating system, as an extension of the generic ARoad0.gWork package, in the AcsAddon Ubuntu. 
ARoad0.Gui1 Provides the internal frames and standard panels for handling the CRUD operations on the database objects, for the Access Road desktop. 
ARoad0.Gui2 Provides the classes for displaying the tree frames and the GraphicViews which display the diagrams in the desktop, following the gDMak package requests. 
ARoad0.Pattern Contains the classes and interfaces for defining a design pattern. 
ARoad0.gBase CORE OF THE PROGRAM This package contains the fresh object-oriented database management system for Access Road; this package documentation page is recommended as a first reading for all the Access Road developers. 
ARoad0.gBaseBeanInfo Contains the classes applying an extended JavaBean framework, so-called the BeanInfoPattern, to define how to handle the generic gBase objects in the GUI. 
ARoad0.gDMak Provides the decision makers, responsible for managing all the events in the Access Road menu, and by this way, contains the managers of the basic operations. 
ARoad0.gWork Contains the classes of the second core of the program that processes the search of rights in the open views. 
ARoad0.gWorkInterface Contains interfaces to process the search of rights in the views, as a support to the gWork package. 
 

Classes in ARoad0.Pattern used by ARoad0.AcsAddon.Accbee.MySQL.gBase
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.AcsAddon.Accbee.MySQL.gBaseBeanInfo
BeanInfoPattern
          This interface is responsible for describing a BaseObject class and for helping to implement the BeanInfo interface.
 

Classes in ARoad0.Pattern used by ARoad0.AcsAddon.Accbee.MySQL.gWork
AcsFactoryForAcsAddon
          This interface is responsible for describing an AcsFactory in the gWork package of an AcsAddon.
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.AcsAddon.Accbee.Ubuntu.gBase
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.AcsAddon.Accbee.Ubuntu.gBaseBeanInfo
BeanInfoPattern
          This interface is responsible for describing a BaseObject class and for helping to implement the BeanInfo interface.
 

Classes in ARoad0.Pattern used by ARoad0.AcsAddon.Accbee.Ubuntu.gWork
AcsFactoryForAcsAddon
          This interface is responsible for describing an AcsFactory in the gWork package of an AcsAddon.
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.Gui1
BeanInfoPattern
          This interface is responsible for describing a BaseObject class and for helping to implement the BeanInfo interface.
MVC_Controller
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
MVC_Model
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
MVC_View
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
StaticClass
          The StaticClass pattern ensures that all the methods of a class are static, and the constructor is private
 

Classes in ARoad0.Pattern used by ARoad0.Gui2
MVC_Controller
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
MVC_Model
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
MVC_View
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
StaticClass
          The StaticClass pattern ensures that all the methods of a class are static, and the constructor is private
 

Classes in ARoad0.Pattern used by ARoad0.Pattern
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.gBase
BeanInfoPattern
          This interface is responsible for describing a BaseObject class and for helping to implement the BeanInfo interface.
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.gBaseBeanInfo
BeanInfoPattern
          This interface is responsible for describing a BaseObject class and for helping to implement the BeanInfo interface.
 

Classes in ARoad0.Pattern used by ARoad0.gDMak
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
 

Classes in ARoad0.Pattern used by ARoad0.gWork
MVC_Controller
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events
Singleton
          from Grand patterns, the singleton pattern ensures that only one instance of a class is created.
StaticClass
          The StaticClass pattern ensures that all the methods of a class are static, and the constructor is private
 

Classes in ARoad0.Pattern used by ARoad0.gWorkInterface
MVC_Controller
          The MVC pattern ensures that the GUI has a clear structure, with: (1) a model: a database-oriented class, (2) 1a view: a class which displays the objects on the desktop, (3) a controller: a class which offers service utilities to the two other classes, and manages the more complex events