Although the OASearch application was designed to illustrate variety more
than efficiency, consider the following design decisions:
- All views use multicell canvases to hold the primitive visual
parts. They are as follows:
- The Opportunities Abound Databases window
- The query windows
- The Opportunities Abound Contractor Information window, which contains
instances of the OAContractorPageX parts
- The Opportunities Abound Contract Information window
- The Opportunities Abound Skill Information window
- The Opportunities Abound Databases window (OAMain part) is the integration
point for the application. From OAMain, the query windows are
instantiated dynamically when the user selects a graphic push button or menu
item. In turn, the information windows are instantiated dynamically
from the query windows as needed.
- The connections between visual parts are minimized with the use of
promoted variables to pass data. At least one instance of each
nonvisual data part is always available (from OAMain). Inside each
visual part, attribute-to-attribute connections load data from the variables
into the windows.
- All visual parts use multicell canvases as the basis for their client
areas. (The OAContractorView part uses multicell canvas-based parts for
its notebook pages.)
- The OAContractorPage3 part contains a simple custom visual part, called
OAMorphableSpinButton, to demonstrate the implementation process.
Constructing the OASearch GUI
Design for the OAMain Part
Design for the Query Window Parts
Design for the OAContractorView Part
Design for the OAMorphableSpinButton Part
Design for the OAContractView Part
Design for the OASkillView Part
