To create a GUI design, you have some preliminary decisions to make concerning the interface. CA Gen tools can often assist you as you make these decisions, but, overall, many of the preliminary decisions can be made independently of the tools.
For example, as you decide on the overall form and function of the interface, you would typically address tasks such as shown next:
After you have a preliminary design, you perform several major tasks with the Window Design functionality. Each of these major tasks has subtasks associated with it. The major tasks tend to group into the following broad categories:
The major tasks tend to be iterative. For example, since one procedure may have many windows associated with it, you would iterate the tasks of specifying the characteristics for each window, the characteristics for each control, and so forth.
You can follow the major tasks in sequence to create a GUI interface. This is not the only sequence in which you could build a GUI. The major tasks show one sequence that can guide you as you create your application. As you become more familiar with the Window Design functionality, you may prefer a different sequence.
The following table lists the tasks to create windows and menu items.
|
Task |
Primary Subtasks |
|---|---|
|
Add a window |
Choose a procedure or procedure step with which you want to associate a window or dialog. |
|
Specify window characteristics |
Name the window. |
|
Add menu items to a window |
Name the menu options that appear in the menu bar and menu bar pull downs. |
|
Specify menu item characteristics |
Specify the text for the menu item. |
The following table lists the tasks to create controls and specify control characteristics.
|
Task |
Primary Subtasks |
|---|---|
|
Add controls that implement views of attributes |
Select attribute views. Specify the type of control. Specify prompts and edit patterns. |
|
Add controls that do not implement views of attributes |
Specify the result that occurs when the user selects the control. Specify the text for the control. Place the control on a window. |
|
Specify control characteristics |
Map import and export views. Specify prompts and edit patterns. Specify behavioral results of the user interacting with the control. Behavioral results also includes event processing, which is listed as a separate major task because of the amount of information associated with events. |
|
Add events |
Add an event type. Create a name for the event action. Specify the action diagram logic for the event action. This subtask is performed with the Action Diagram tool. |
The following table lists tasks to fine tune the interface.
|
Task |
Primary Subtasks |
|---|---|
|
Test the flow of user tasks from window to window |
Decide which windows open or close which other windows. Test the flow from window to window. |
|
Refine the overall appearance of the interface |
Verify the implementation of any application-wide standards. Verify the use of tool bars and status bars. Rearrange the controls in a manner that satisfies the object/action flow in which a user performs tasks. Group related controls together. Disable controls where appropriate. Create or update any bitmap images to use as objects. Verify the choices for the font and the foreground and background colors for windows, dialogs, and controls. |
|
Copyright © 2013 CA.
All rights reserved.
|
|