Previous Topic: PrerequisitesNext Topic: Windows and Dialogs


Tasks Performed with Window Design Functionality

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 as listed here:

After you have a preliminary design, you perform several major tasks with Window Design functionality. Each of these major tasks has subtasks associated with it. For more information about the tasks and subtasks, see the following table.

The major tasks tend to be iterative. For example, since one procedure may have many windows associated with it, you would iterate the tasks by specifying the characteristics for each window, the characteristics for each control, and so on.

You can follow the major tasks in sequence to create a GUI application. This is not the only sequence in which you could build a GUI application, nor is it a list of all the tasks that you perform with Window Design functionality. The major tasks show one sequence that can guide you as you create your application. As you become more familiar with Window Design functionality, you may prefer a different sequence.

The following table lists major tasks performed with window design functionality.

Major Task

Primary Subtasks

Add a window

Choose a procedure or procedure step with which you want to associate a window or dialog.

Determine if you want to create an initial layout of the window or dialog based on the views for the procedure, based on a screen layout from the Screen Design tool, or based on your own design.

Specify window characteristics

Name the window.

Specify if the window is the primary one with which the user interacts.

Specify where on the desktop the window appears when first invoked.

Specify if the window can remain open while the user performs other tasks.

Specify if the window uses a bitmap for a background.

Add menu items to a window

Name the menu options that appear in the menu bar and menu bar pull downs.

Determine the arrangement (hierarchy) of the menu options.

Specify the font and colors for the menu items.

Specify menu item characteristics

Specify the text for the menu item.

Specify the result that occurs when the user selects the menu item.

Specify the command, if any, associated with the menu item.

Add controls that implement views of attributes

Select attribute views.

Specify the type of control.

Specify prompts and edit patterns.

Place the control on a window.

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 the text for the control.

Specify prompts and edit patterns.

Specify behavioral results of the user interacting with the control. Behavioral results also include 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.

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 fonts and the foreground and background colors for windows, dialogs, and controls.