Getting started with UI Toolkit

Before you begin

If you are a new user of UI Toolkit, it may be helpful to do the following:

• Read the introductory topics in Window Scripts to get a better understanding of what scripts are and why you use them. Also look at the individual script commands, paying special attention to the following commands, which are the ones most commonly used:

.COLUMN

.END

.ENTRY

.FIELD

.INPUT

.SELECT

.WINDOW

• Make some sample scripts and process them using the Script utility. (See Compiling window scripts with the Script utility.) You can then use Proto to look at the columns and windows you have just created.
• Become familiar with the following basic subroutines. You can’t create a Toolkit application without them:

U_START

U_FINISH

M_LDCOL

M_PROCESS

I_LDINP

I_INPUT

U_OPEN

U_CLOSE

• Examine the example programs and scripts in this manual.

Developing an application

The initial steps you should take to develop applications using UI Toolkit for traditional Synergy are as follows.

1.

Define your windows and menu columns in a window script file. See Window Scripts for more information about writing script files. We suggest you use Composer to create this script interactively.

2.

Compile the script files with Proto or Script to build the windows and columns and to store them in a window library. (You can also compile the script files from within Composer.)

3.

Test and view the windows and columns with Proto.

4.

Write a Synergy program that calls the UI Toolkit routines. You will need to include the file WND:tools.def in your program (with the Synergy DBL .INCLUDE statement). Read Requirements and considerations for UI Toolkit programs before writing your program.

5.

Compile the source code. (See Creating and running traditional Synergy applications.)

6.

Link your program with WND:tklib.elb (TKLIB_SH.EXE on OpenVMS). See Linking object modules for information on commands for linking.

On Windows, you can link against tklib_qcheck.elb, a version of the UI Toolkit library that’s built with more thorough bounds checking (the -qcheck compiler option). All code linked against this version of the Toolkit library must be compiled with -qcheck. See Bounds checking and Compiler options.

On OpenVMS, you must link your program with TKLIB_SH.EXE (instead of tklib.elb). If you are using a custom option file to link your program, you can add “TKLIB_SH/SHARE” to the option file to link with TKLIB_SH.EXE. If you are using the option file SYS$SHARE:SYNRTL.OPT, you can instead use SYS$SHARE:SYNTKLIB.OPT to automatically link against TKLIB_SH.EXE — for example:

link myprogram.obj,SYS$SHARE:SYNTKLIB.OPT/OPT

7.

Run your application. It will use the windows and menu columns stored in the window library.

1. Creating a Toolkit application with traditional Synergy.