Understanding how the typical screen-based application works is a prerequisite for any developer wanting to implement a Enhanced UI User Interface solution.
Since the organization of modeling and mapping of a Flynet application is based on Screens, Fieldmaps and Fields, this guide is organized around these entities.
In the Studio Project Explorer, you categorize and define these objects in the following hierarchy:
Screen Definitions are associated with visible screens belonging to the Project
One or more FieldMap definitions can be defined as belonging to each Screen Definition
One or more Field definitions can be defined as belonging to each FieldMap
As part of the application definition, modeling and generation logic, the Flynet Viewer developers have identified common aspects or roles for each of these definitions or entities. These roles (and behaviors) are identified for each entity through a variety of properties which you control through the property grid associated with each individual entity's definition in the project workspace.
While clicking with the mouse to select and change a property is a simple action, knowing which property to set requires an understanding first of the behaviors of typical screen applications, then what design features are available in the Enhanced UI which re-publish those features in a more usable and attractive presentation.
The following sections describe the common behaviors currently modeled in the Flynet Viewer Studio and generated by the Enhanced UI Generator:
Please read these sections and refer back to them on an ongoing basis, to help you in your use of the Flynet Viewer Studio and its associated tools.
Click to view the next section, Screen Roles and Behaviors
