Pathmaker Programming Guide

Designing a Pathmaker Application
Preparing for Pathmaker Application Development
2–12 067868 Tandem Computers Incorporated
creating the prototype screens is much faster when DDL definitions are already
defined. If you use DDL, you can type values into the data fields; data is not retained,
but using DDL gives a better simulation of actual screens than a simulation without
DDL.
If no DDL definitions exist, simulating the interface can help you identify fields that
must be present in the database; however, simulation probably will not help you
identify relationships between the data elements.
Note Pathmaker is not intended as a database design tool; if prior database analysis or design has not been
completed, it is possible to create a prototype user interface that cannot be implemented effectively.
If you do decide to simulate without DDL, you can convert the prototype requesters to
functioning requesters by defining the DDL for all the required records and fields and
by giving Pathmaker information about the DDL definitions that you have created.
Before you decide whether to simulate with or without DDL, you should experiment
with the Pathmaker Screen Painter feature that allows you to convert decorations that
represent data fields on the prototype screen to functioning data fields. Conversion
can be a time-intensive process for a complex application with many screens. If you
have many screens with data fields on each screen, you might want to have the
Pathmaker product re-create the default screens.
Establishing Naming
Conventions
Pathmaker does not enforce naming conventions because of the wide range of
requirements at different work sites. Developers of small projects might prefer not to
have a strict standard. Large projects might require strict standards to allow the
sharing of work between project members. For most projects, it is a good idea to
establish naming conventions early in the development cycle.
Unless you develop a very simple application, you might have a large number of files
for your application. These files can include source code files, object code files, custom
service files, macro files, data files, and small utility files such as TACL macros and
obey files. There are many ways of organizing files, and you should structure your
naming conventions accordingly.
Rules for Naming Objects
in Pathmaker
Whatever naming conventions you decide to use, you must create names for:
Project catalogs
Project subvolumes
Work subvolumes
Pathmaker projects
Pathmaker objects (requesters, services, servers, server classes, and macros)
Reference objects (DDL definitions, DDL records, and NonStop SQL table object
names)
Files (disk file names and logical file names)
NonStop SQL DEFINE names