MAIN WINDOW Clause Samples
The "Main Window" clause defines a specific period during which certain actions, rights, or obligations under the contract can be exercised or must be fulfilled. Typically, this window sets clear start and end dates for activities such as submitting bids, making claims, or performing key deliverables. By establishing a defined timeframe, the clause ensures all parties are aware of critical deadlines, thereby reducing ambiguity and helping to coordinate actions efficiently.
MAIN WINDOW. The entry point of the wizard is the class CONTRACT_WIZARD which inherits from EV_APPLICATION. The root class first checks if the environment variable $CONTRACT, pointing to the contract wizard delivery directory, is set. Afterwards it initializes the wizard and launches the application. CW_MAIN_WINDOW inherits from EV_TITLED_WINDOW and represents window of the wizard. The main window maintains a list of all dialogs appearing in the wizard and replaces the actual dialog displayed in the window when the user presses on the “Next >>” button. Each dialog inherits from CW_DIALOG. This class has an attribute box of type EV_BOX that a specialized class redefines either to EV_VERTICAL_BOX or EV_HORIZONTAL_BOX depending on the main layout of the actual task. Moreover the class has the deferred features: • initialize_box (initialize box and class attributes) • is_complete (are all components of the class filled out as needed?) • build_interface (build interface for task and extend widgets to box). I will discuss the specializations of CW_TASK beneath. Figure 6 shows the architecture of the main GUI. Figure 6: Main GUI classes of Contract Wizard CW_MAIN_WINDOW also handles navigation between dialogs. For that it has a button_bar with “Help”, “<< Back”, “Next >>”, and “Cancel” buttons at the bottom of the window. The main window handles the button actions because a dialog itself knows nothing about its preceding and following dialog. I have chosen this design so that it is easier to have several possible subsequent dialogs to one dialog. Table 1 shows the most important features of class CW_MAIN_WINDOW in their contract form. dialog_list: LINKED_LIST [CW_DIALOG] -- List with all needed dialog implementations. -- Is first dialog shown? first_dialog_definition: Result = (main_vbox.item = dialog_▇▇▇▇.▇▇▇▇▇.▇▇▇) -- Is last dialog shown? last_dialog_definition: Result = (main_vbox.item = dialog_▇▇▇▇.▇▇▇▇.▇▇▇) go_i_th_dialog (i: INTEGER) -- Show `i’ th dialog. i_within_bounds: i > 0 and then i <= dialog_list.count i_th_dialog_active: dialog_list.item = dialog_list.i_th (i) i_th_frame_shown: dialog_▇▇▇▇.▇▇▇▇.▇▇▇ = main_vbox.item -- Set button state according to shown dialog. back_button_sensitive: is_first_dialog implies not
MAIN WINDOW the project control panel
MAIN WINDOW. After Sign In, the Main Window appears as Shown below. On this page the user finds the following information. Menu Bar Menu Bar is on top left side of the window. It contains following options: □ File □ Monitor □ Trade □ Services □ Services □ Graph □ Help Shortcuts Bar Shortcuts Bar lies besides the Menu Bar on the top of the window. It contains following options: □ Market Watch □ Buy order □ Sell order □ Cancel Orders □ Executed Trades □ Outstanding orders □ Portfolio □ Net Equity □ Order History □ Graph Intraday □ Graph History □ Graph Advance Market Watch o Menu Bar □ Settings : Change font Style / Color / Size and Multiple styling of market window □ Shares Filter: Fill market window with shares as described by the Filter □ User Profile: these are basically multiple pages of market o Market Watch Under market all the information regarding shares and securities (with respect to current market) are displayed. Highlighted tuple shows that the change is taking place only in highlighted column. In main window, each row represents the information about the particular security. □ Market: REG / FUT /SIF etc. □ Symbol: Company symbol appears here. □
MAIN WINDOW. After a mode has been selected in the Select Mode window, a Main window is displayed for the selected mode. The configuration of the Main window is the same for all three modes, and comprises a Preview Area, a Common Area, and a Setup Area. Fit
1:1 Displays the image with 1 dot on the screen representing 1 pixel Preview *Displays the scanned-in image Save *Saves the image Enlarge Area *Enlarges the display of the specified area
3.2.2.1 Common Area Note: There may be minor differences depending on the mode selected. (Copy, Print, Scan)/Cancel Note: For further details on the Execute button, see the function explanations for each mode.
MAIN WINDOW. The main window of the demonstrator is made up of the following part:
1) A menu bar with the following items:
a. Exit
b. System Boot (to enter the system boot parameters)
c. Cost Function (to enter the cost function parameters)
d. System Outcomes (to show the system outcomes) If it is necessary, a WP related menu item can be added to show forms specific to one or more work packages.
2) A system log text area. It can be accessed using the showData event (for- mID=mainForm, widgetID=logWidget, type=T, data=<custom data>. See 3.3.1.16)
3) A system control area. It is made up of:
a. Start system button. It starts all the tasks in the system using the cur- rent boot configuration. If the system is already started, the button is disable.
b. Stop system button. It kills all the task in the system using the current boot configuration. If the system is already stopped, the button is disa- bled (ShutdownSystem event).
c. Boot configuration. It shows the current boot configuration.
4) A simulator control panel. It shall allow to:
a. Start simulator (StartSystemClock event)
b. Stop simulator (StopSystemClock event)
c. Pause simulator (PauseSystemClock event)
d. Speed up simulator (SpeedUpSystemClock event)
e. Speed down simulator (SpeedDownSystemClock event)
5) Scenario selection. Choosing a new scenario will stop and restart the system.
6) Simulator speed control (for fine tuning and speed indication)
MAIN WINDOW. The main window of Connecsy is built up with a console with function keys, user profile and a user table. From the main screen you can execute the most important tasks. Specific functions can be started from sub windows. All functions can also be executed by touching a screen in combination with a touch screen. Console profile User table
MAIN WINDOW