Getting Started

Chapter 1: Overview

This chapter introduces Dialog System and describes how programs are developed with Dialog System.

1.1 Dialog System

The Micro Focus Dialog System provides for independence between screen and keyboard input/output (I/O), and a COBOL application program. In much the same way that a database management system (DBMS) provides for independence of the data from the application, Dialog System separates out the human interface. This means that the application program needs only to be concerned with basic data processing tasks, and thus becomes smaller, simpler and much easier to code and maintain. Dialog System consists of a definition component and a run-time component.

You can use the definition component to define panels, which are rectangular working areas on the screen where you can specify data fields and keystrokes. The interaction between the screen and the user, based on this definition of keystrokes associated with a panel, is known as a dialog. Panels, which can be up to 80 characters wide and 25 lines long, can be used individually to create layouts for simple data entry, or they can be used collectively to make screensets.

A screenset is a set of panels with their associated data fields and dialog for one application. You can design complex screensets, incorporating pulldown menus, popup windows, selection bars, scrolling groups, help screens, function key support, and data validations.

You can use the run-time component to run the screenset and dialog interactions without an application program; this enables you to test a screenset and its dialog without the application program that uses the screenset. The run-time component also supports the screenset when it is being used by a program. This is done by using a simple call interface between the program and the screenset through a control block and a Data Block.

Therefore, once a program is produced, you can make extensive changes to the screenset without actually changing the program.

1.2 Environments

This guide describes the Character Mode version of Dialog System. You can use this version to create character-based user interfaces for applications running in character environments. The alternative version, for Graphical Mode, enables you to create graphical user interfaces for applications to run in graphical environments such as Microsoft Windows.

Obviously, the differences between UNIX and Windows operating systems result in differences in the use of certain facilities, such as line drawing and character graphics. To avoid problems, use only standard ASCII characters (codes 032 through 127) in any text that you enter. See the chapter Panel Painting for more information. Other limitations are clearly identified in this guide.

1.3 Program Development with Dialog System

The approach to program development using Dialog System is different to previous methods of program development. How much you change your own approach depends on a number of factors, including your own individual preferences.

The fundamental advantage of using Dialog System over your previous method is that all keyboard and screen handling is removed from your program. Additionally, most of the data validation, menu control, scrolling lists and help screens are no longer handled by your program.

Instead, all of these functions are handled by the Dialog System, using a very simple call interface to the COBOL program through a control block and a Data Block.

The major steps in developing your application with Dialog System are:

Defining the Data Block. The Data Block is passed between the calling program and the Dialog System at run time, and contains the data fields and any data validations. See the chapter Data Definition.
Defining the panels. This step includes creating screen panels and establishing any desired colors and screen prompts. See the chapter Panels.
Positioning data fields on the panels. See chapters Panel Fields and Panel Groups.
Defining the dialog. The dialog is the control of the function of keystrokes, for example showing a "help" panel if F1 is pressed. See the chapter Dialog.
Testing the screenset. You can run the screenset to test the behavior of the screenset and its associated dialog. See the chapter Running the Screenset.
Modifying the screenset, as required.
Generating a copyfile. You generate a COBOL copyfile from the screenset for use in the COBOL application program. See the chapter Generating the Copyfile.
Writing a calling program. You write a COBOL application program with the necessary calls to the Dialog System. See the chapter Programming.
Testing the calling program.
Modifying the screenset, as required.
Linking Dialog System modules to your application. This is an optional step you can use if you want to create a single executable object by linking Dialog System modules to your application. See the chapter Linking.

Getting Started