Implementation Model |
Overview
|
Architecture
|
Differentiation
|
Life Cycle Management
| Success Stories | Demo | Product Specifications | FAQ | ||
| |||
|
|
| ||
|
Omni*Builder generates multi-tier GUI applications in a variety of technologies. These applications take full advantage of the rich presentation functionality inherent in client-based applications. The windows may have been automatically generated by Omni*Builder or may have been painted individually. A wide set of window panel types is available such as dialog, modal dialog, spreadsheets, etc., and window controls such as calendar control, list box, tree, radio button, tabs, etc. | |||
Sensitive Menus |
Omni*Builder automatically creates context-sensitive pop-up-menus listing the services available on an object. In the following example, the ZoomLocation service brings up a spreadsheet to show a complete list of locations. | ||
|
Hierarchies are fully supported with complete child/sibling management, including the ability to move branches within the tree. | |||
![]() | |||
|
Zoom functionality is available as a service attached to a pop-up-menu. | |||
|
The generated application has many sophisticated browsing operations. The relationships between objects defined in the Business Model provide the basis of navigation. The generated application manages the details of data access and display associated with each window panel or query. | |||
| Buttons, Controls and Services
Buttons on windows may invoke services or display other windows with related information. A full selection of window controls is available providing presentation, data entry formatting, and selection functionality. The generated application uses a 3-tier architecture to manage database access, transaction processing and presentation. | |||
|
| |||
| Business Services are invoked with a context-sensitive menu. | |||
| Windows and
Multiple Objects
Complex business models require windows that feature views of the data patterned after the business process. Windows allow multiple views of objects to be displayed. For example, a Human Resources application may choose to display a list of employees on a window with tab dialogs providing query by example, details of the selected employee, and views of other child entities such as assignments and skills. | |||
| Queries
Query-By-Example windows are defined without writing SQL statements. Queries can be expanded to include other entities based on the relationships defined in the Business Model. In a Human Resources system, a query to locate a list of employees may include a search based on their skills or current assignments. | |||
|
|
|||
|
The list panel displays the results of the Query-by-example. The related entities Location, Assignment and Skill also appear in the QBE. |
|||
|
| |||
|
| |||
|
Overview
| Architecture
| Differentiation
| Life Cycle Management
| Success Stories | Demo | Product Specifications | FAQ Home | Top | Contact us | Site Map |