Application object structure

AyMINE application internal structure related with the user-interface management

Principal view objects

The following UML structure Class model describes internal implementation of the user interface generators and managers:

fBase

Basic class for all window managers. Manages loading and general single-page view

funivDashboard – Dashboard implementation

General implementation of the dashboards. Manages the content of the dashboard including

• Top menu
• Dashboard
  • Dashboard buttons
  • Dashboard content

fUnivDetail – Detail implementation

Implementation of all single-object detail view. Internally uses managers for principal visual objects:

• Tabs
• Boxes
• Content of the boxes in the set of fields (internal object fieldset)
  Let's note that single “fieldset” is used for all attributes in all boxes

funivList – List of object

Implementation of list of objects based on the table / tree structure. Apart of the table, it also manages operations with selected boxes and filters applied on the list. Filters are encapsulated to the filter manager class

fClip – single object short representation

Short view of a single detail is presented by clip. fClip manages everything necessary to display a clip.
Clip supports subordinated clips and so it is a principal object of both single clip and tree of clip views.

fClipList – List of clips

Any list of clips is managed by this class. It manages list as well as operations (mostly inserting new) and filters. Filters uses the same filter manager as list based on the table view.

Principal supporting classes

The principal classes are based on

• Manager of interface elements
• Key interfaces between
  • View managers and browser interface
  • “JSONC” class-definitions:

Internal object structure managers

fBaseManger

Register of all fbase classes – both those that have its own window as well as those, that are included in another detail and does not have own view