Digital PDFs

AA-MA86D-TE

June 1990

67 pages

Original

2.2MB

Document:	ULTRIX Worksystem Software Introduction to the ULTRIX Worksystem Software Environment
Order Number:	AA-MA86D-TE
Revision:	0
Pages:	67
Original Filename:

OCR Text

ULTRIX Worksystem Software

Introduction to the ULTRIX
Worksystem Software Environment
Order Number: AA-MA86D-TE
June 1990

Product Version:

ULTRIX Worksystem Software Version 4.0

Operating System and Version:

ULTRIX Version 4.0

digital equipment corporation
maynard, massachusetts

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as
set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause of
DFARS 252.227-7013.
© Digital Equipment Corporation 1989, 1990
All rights reserved.

The information in this document is subject to change without notice and should not be construed as a
commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no
responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or copied only in
accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by
Digital or its affiliated companies.

The following are trademarks of Digital Equipment Corporation:

lomaama
CDA
DDIF
DDIS
DEC
DECnet
DECstation

DECUS
DECwindows
DTIF
MASSBUS
MicroVAX
Q-bus
ULTRIX
ULTRIX Mail Connection

ULTRIX Worksystem Software
UNIBUS
VAX
VAXstation
VMS
VMS/ULTRIX Connection

VT
XUI

PostScript and Display PostScript are registered trademarks of Adobe Systems, Inc.
UNIX is a registered trademark of AT&T in the USA and other countries.
X Window System, X, and XII are registered trademarks of MIT.

Contents
About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Overview of the UWS Environment
xm and DECwindows Features. . . . . . . . . . . . . . . . . . . . . . . . . .
xm Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DECwindows Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
XUI Toolkit .......................................
Xlib Programming Library. . . . . . . . . . . . . . . . . . . . . . . . . . . .
'I'ransport Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extending the Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vii

1-2
1-5
1-5
1-5
1-6

1-7
1-7
1-8
1-8

2 The User Environment
Overview of the User Environment . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Controlling Your DECwindows Session. . . . . . . . . . .
Managing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing the ULTRIX Operating System .. . . . . . . . . . . . . . . . . .
Getting Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DECwindows Desktop Applications . . . . . . . . . . . . . . . . . . . . . . . .
Calculator ........................................
Calendar ..........................................
Cardfiler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CDA Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DECterm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1
2-3
2-4
2-4
2-6

2-7
2-8
2-8
2-9
2-10
2-10
2-10
2-11
iii

Notepad .........................................
Paint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PostScript Previewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Puzzle ...........................................
Other Worksystem Applications . . . . . . . . . . . . . . . . . . . . . . . . . . .
Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Visual Differences ..................................

2-11
2-12
2-12
2-13
2-13
2-13
2-13

3 The Programming Environment
Overview of the Programming Environment . . . . . . . . . . . . . . . . .
Creating and Managing Windows ......................
The Xlib Library ......................................
XUI Toolkit ..........................................
High-Level Widget Creation Routines. . . . . . . . . . . . . . . . . . .
Low-Level Widget Creation Routines. . . . . . . . . . . . . . . . . . . .
xm Intrinsics Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cut and Paste Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convenience Routines ...............................
Compound String Routines. . . . . . . . . . . . . . . . . . . . . . . . . . .
XUI User Interface Language Compiler. . . . . . . . . . . . . . . . . .
XUI Resource Manager ..............................

3-1
3-2
3-3
3-3
3-4
3-4
3-4
3-5
3-5
3-5
3-5
3-6

4 Customizing Your OECwindows Environment
Why Customize with .Xdefaults? . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the .Xdefaults File. . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Specification Examples. . . . . . . . . . . . . . . . .
More About Widgets and Resources . . . . . . . . . . . . . . . . . . . . . . . .
Locating Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Precedence for Setting Resources. . . . . . . . . . . . . . . . . . . . . . .
General Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Widget-Specific Resources ......................
Application-Specific Resources . . . . . . . . . . . . . . . . . . .
Identifying Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Widget Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Naming Widgets in Resource Specification Strings ...
Changing Key Definitions ...............................
Assigning New Text Editing Commands ...........
Sample Translations Resource Specification. . . . . . . . .

4-1
4-2
4-4
4-5
4-7
4-8
4-8
4-8
4-9
4-1 0
4-1 0
4-13
4-13
4-15
4-17
4-18
4-19

ndex
:xamples
4-1
4-2
4-3
4-4

Sample .Xdefaults File .................................. .
Default File for the DECwindows Clock Application ........... .
Default File for the DECwindows Notepad Application ......... .
Sample Text Specifications .............................. .

4-4
4-11
4-12
4-19

DECwindows Distributed Applications ..................... .
XUI Architecture ...................................... .
DECwindows User Environment .......................... .
Session Manager Window ............................... .
UE Window .......................................... .
Calendar Window ...................................... .
Cardfiler Windows ..................................... .
Main Mail Window ..................................... .
The Visual Differences Display ........................... .
XUI Programming Environment .......................... .
Window Components ................................... .
Widget Hierarchy ...................................... .

1-4
1-6
2-2
2-4
2-6
2-9
2-10
2-12
2-14
3-2
4-3
4-14

General Resources ..................................... .
Widget-Specific Resources ............................... .
XUI Toolkit Widgets .................................... .
Text Editing Keys and Preset Functions .................... .
Text Fun,ctions ....................................... .

4-9
4-10
4-15
4-17
4-20

:igures
1-1
1-2
2-1
2-2
2-3
2-4
2-5
2-6
2-7
3-1

4-1
4-2

rabies
4-1
4-2
4-3
4-4
4-5

About This Guide

This manual introduces the ULTRIX Worksystem Software
environment and describes how to customize its components
and applications.

Audience
This manual is intended for all ULTRIX Worksystem Software
users.

Organization
This manual consists of four chapters:
• Chapter 1 introduces the ULTRIX Worksystem environment.
• Chapter 2 provides an overview of the user environment and
DECwindows applications.
• Chapter 3 provides an overview of the programming
environment.
• Chapter 4 describes how to personalize DECwindows
applications by modifying entries in the .Xdefaults file.

Related Documentation
You should have the following manuals at hand:

• ULTRIX Worksystem Software Reference Pages
• DECwindows User's Guide
• DECwindows Desktop Applications Guide
• The Little Gray Book: An ULTRIX Primer

vii

You may also wish to have the following manuals at hand:

• XU] Style Guide
• Guide to Writing Applications Using XUI Toolkit Widgets
• Guide to XU] Toolkit: C Language Binding

Conventions
mouse

The term mouse refers to any pointing device, such as
a mouse, a puck, or a stylus.

bold

Boldface text is used to introduce new terms.
A key name enclosed in a box indicates that you press
a key on the keyboard.

IReturn I

A sequence such as ICfrl/xl indicates that you must
hold down the key labeled Ctrl while you press
another key or a pointing device button.
A sequence such as ~ indicates that you must first
press and release the key labeled PF1, then press and
release another key or a pointing device button.

italics

In syntax and function descriptions, italic type
indicates terms that are variable.
In examples, a horizontal ellipsis indicates one of the
following possibilities:
•

Additional optional arguments in a statement
have been omitted.

•

The preceding item or items can be repeated one
or more times.

•

Additional parameters, values, or other
information can be entered.

A vertical ellipsis indicates the omission of items from
a code example or command format; the items are
omitted because they are not important to the topic
being discussed.

viii

1
Overview of the UWS Environment

111111

The ULTRIX Worksystem Software (UWS) environment comprises
DECwindows applications, X User Interace (XUI) and X
programming libraries, and guidelines for creating applications
with XUI-compliant interfaces. This environment gives you the
following capabilities:
• The ability to distribute applications throughout the network,
letting customers take full advantage of network resources.
• A software environment that supports the advanced graphics
capabilities of workstations and personal computers.
• A software development environment that makes it easy
to create applications with a consistent look and feelregardless of the hardware and operating system on which
the applications run.
• The ability to use workstations and personal computers to
display multiple applications concurrently-accomplished
most easily in a windowed environment. Each application
has a window on the screen that displays output and accepts
input.
This chapter summarizes the features of the worksystem
environment and describes the XVI architecture.

Overview of the UWS Environment 1-1

XUI and DECwindows Features
XUI is an advanced windowing system that extends and
improves the X Window System, Version 11. DECwindows is
Digital's implementation of XUI-based software components and
applications.
The X Window System was developed at the Massachusetts
Institute of Technology (MIT) with cooperation from Digital
Equipment Corporation. The X Window System provides a
high-performing, high-level, and device-independent graphics
programming environment. Since its introduction by MIT, the X
Window System has become an industry standard.
XUI incorporates and extends the X Window System to provide a
windowing environment with the following features:
• Graphics-oriented interaction with the operating system
DECwindows handles all your interactions with the system.
These interactions include initializing a session, managing
your environment and resources, starting applications, and
managing windows. You can create windows, move windows,
resize windows, and shrink windows to icons.
•

Consistent user interfaces
DECwindows user interfaces consist of graphic objects that
look and function the same, regardless of the application
you are using. This simplifies learning about and using new
applications.

• A library of desktop applications
DECwindows provides a variety of applications, including the
following: Clock, Calculator, Calendar, Cardfiler, CDA Viewer,
DECterm terminal emulator, Paint Graphics Editor, Notepad
Text Editor, and Mail.
•

Powerful libraries of programming routines that simplify the
development of graphics-oriented applications
Some of the functions these routines perform include:
• Graphics operations-drawing points, lines, rectangles,
arcs, and text
• Display management-open, close, and obtain information
about the display
• Window manipulation-create, destroy, configure, and
change window attributes

1-2 Overview of the UWS Environment

Applications using these routines run on all supported
hardware without modifications. For example, an application
designed for the VAXstation II looks and functions the same
on a VAXstation 2000.
• Libraries for creating and accessing documents containing
text, graphics, and scanned images.
• Libraries for communicating with Digital's implementation of
the Display PostScript ® system.
• Network-transparent application interface
The XUI architecture lets you run an application on a
remote node, while displaying and inputting data on a local
workstation. The network functions that make this possible
are transparent; the application appears to run locally.
This network transparency allows workstations to access the
power and resources of other systems on the network.
• Compatibility with VMS
Because ULTRIX and VMS DECwindows use the same set
of programming libraries, you can easily port applications
to and from VMS DECwindows systems; no modifications to
applications are required.
• Extensible architecture
The XVI architecture has been designed to accommodate new
hardware as it becomes available and to add new features.
• Security
XUI supports the full range of security available to systems
running the ULTRIX operating system. In addition to
UTLRIX security features, XVI provides the ability to specify
which systems can access a server.
Figure 1-1 illustrates several features of XUI. Three applications
display a window on a VAXstation. Two of the applications run
on remote processors, and yet all the applications appear to run
locally.

® PostScript and Display PostScript are registered trademarks of Adobe Systems Incorporated.

Overview of the UWS Environment

1-3

Figure 1-1

DECwindows Distributed Applications

Window A displays output
from an applicaton running
remotely on a VAX 8800.

Window B displays output
from an application running
remotely on a VAX 8300.

.....

Window C displays output

from
anon
application
running I:
-===~~======t----locally
the workstation.

niiiii5iiiiiaiiiFiifiiin
ZS-0300-R

1-4 Overview of the UWS Environment

XUI Architecture
The XUI architecture is an extension of the X Window System
architecture. Components of the architecture include the
following:
• DECwindows applications
• XUI Toolkit
• Xlib library
• Network transport
• Server
• Device drivers
In addition to these basic components, XUI includes the
Compound Document Architecture (CDA) Toolkit. The CDA
Toolkit allows applications to create and access documents
containing text, graphics, and scanned images. Figure 1-2
illustrates the relationships among the components of the XUI
architecture.

DECwindows Applications
For more
information
about the user
environment and
DECwindows
applications, see
Chapter 2.

DECwindows applications provide a consistent, graphics-oriented
user interface that makes it easy to interact with the ULTRIX
operating system. In the work system environment, applications
look and respond similarly.
To perform windowing and graphics functions or to get input from
the mouse and keyboard, DECwindows applications call routines
from the XUI Toolkit and Xlib programming libraries.

XUI Toolkit
For more
information
about the
programming
environment see
Chapter 3.

The XUI Toolkit includes Digital's implementation of the X
Toolkit and consists of high-level library routines that allow
applications to create and manage a user interface. Using XUI
Toolkit routines, applications can create, modify, and control
interface objects such as menus, scroll bars, and buttons. In turn,
XUI Toolkit routines call Xlib routines to perform fundamental
input and output functions.

Overview of the UWS Environment

1-5

Figure 1-2

XUI Architecture

Application

Extensions

j------- -------,
:I.. _Network
Transport :
_ _ _ _ _ _[_ _ _ _ _ _ _ _,
X11 Protocol

j------- -------,

: Network Transport
1.._______
______ J :

Extensions

ZS-0301-R

Xlib Programming Library
The Xlib programming library is Digital's implementation of the
X Window System's graphics programming library. Xlib provides
low-level routines for creating windows, managing windows,
performing graphics functions, and communicating with the
Display PostScript interpreter.

1-6 Overview of the UWS Environment

Xlib routines handle application requests by generating and
sending XII protocol requests through the network to another
component of the architecture called the server. The XlI protocol
defines the common language through which an application and
workstation communicate.

Transport Layers
The network transport mechanism uses TCP/IP or DECnet to
handle communication, in the form of Xll protocol packets,
between Xlib and the server.
The implementation of the transport (TCPIIP or DECnet) and the
XII protocol allows the application and the user interface to be
physically separated across the network. For example, you can
run an application on a remote node while displaying the window
locally on a workstation. The window accepts input and displays
output for the application. The application appears to run on the
workstation.
XUI also provides an optimized, shared-memory transport
mechanism. When an application runs locally on the workstation
that displays the interface, the optimized transport reduces the
time required to transfer a protocol packet to or from the server.

Server
The X server is Digital's implementation of the X Window System
server. The server is the component of the architecture that allows
application interfaces to interact with all supported systems in the
same way. Residing on the displaying system, the server performs
the following:
•

Handles interprocess communication between client
applications and the X server

• Distributes user input to and accepts output request from
client applications
• Maintains an access control list that contains processor host
names from which client applications can execute.
In essence, the server converts the data that represents the
request to a command that can be executed by the appropriate
device drivers.

Overview of the UWS Environment

1-7

Device Drivers
A device driver library supports the hardware devices that
interact with the window system.
The use of a device library allows programmers to write deviceindependent client applications. This means programmers do not
have to rewrite, recompile, or relink an application when a new
hardware display is added. Instead, the X server and its device
drivers need only be modified or extended.
Device drivers process requests from the server to the display and
pass data from the input devices to the server. The device driver
architecture consists of the following components:
• Port input drivers
• Class input drivers
• Common driver
• Output driver

Extending the Architecture
A major feature of the XUI architecture is its extensibility.
The programming libraries, Xll protocol, and server can all be
extended to support new hardware or to implement new features.
For example, you could extend XUI to support three-dimensional
applications. This would require the following actions:
• Develop a new library of routines to create and manage three
dimensional images
• Add protocol requests that correspond to the new routines
• Extend the server so that it can interpret and execute the
requests
The XUI architecture is also designed to support optional libraries
that layer on top ofXlib, for example, the GKS programming
library. Such libraries do not require extensions to the protocol or
server.

1-8 Overview of the UWS Environment

2
The User Environment
By providing consistent, graphics-oriented user interfaces to all
software components and applications, the DECwindows user
environment makes it easy to interact with the operating system
and to use applications. This chapter provides an overview of
the user environment and describes the DECwindows desktop
applications.

Overview of the User Environment
The DECwindows user environment is designed to increase
productivity by saving time. DECwindows provides an
environment in which applications look and respond similarly. For
example, if two different applications display a menu, the menu
looks the same for both applications, and the steps required to
pick a menu option are the same.
You interact with a DECwindows system by finding an object on
the screen that represents the task you want to perform, then use
a pointing device (for example, a mouse) to select that object.
Typical interface objects include:
• Menu bars
• Scroll bars
• Pull-down menus
• Pop-up menus
• Buttons

The User Environment 2-1

The DECwindows user environment saves time by letting you
start a number of applications simultaneously. For example, you
can run a program in one window, read mail in a second window,
and execute a command in a third.
The DECwindows user environment includes the following
components:
• The Session Manager
• The Window Manager
• The User Executive
• DECwindows applications
• Online help
Figure 2-1 illustrates some components of the DECwindows user
environment. The following sections describe the components of
the user environment.

Session Manager:
Session Applications

Customize

Print Screen

Help

Messages
Starting Applh ~
___D_EC_t_el_'m_________________________________
Commands Edit Customize

2-2 The User Environment

~~
Help

Starting and Controlling Your DECwindows Session
The Session Manager, your initial interface for DECwindows,
acts as a control panel for your DECwindows session. From the
Session Manager, you can
• Log on to your workstation and start a DECwindows session
• Create new DECterm terminal emulator and User Executive
(UE) windows or start other DECwindows applications
• Customize your DECwindows environment
• Capture window snapshots in a file for printing
• Lock your workstation by pausing your DECwindows session
• End your DECwindows session
For more
information
about the
Session
Manager, see the
DECwindows
User's Guide.

DECwindows comes with preset options that you can change.
You use the Session Manager to change these options, thereby
customizing your environment to fit your working style. For
example, with Session Manager, you can change options to
customize your:
• Keyboard settings
• Windows
• Pointer
• Security settings
You can also set options to have the Session Manager
automatically start certain applications, such as the DECterm
terminal emulator, each time a new session begins. Figure 2-2
shows the Session Manager window.

The User Environment 2-3

Figure 2-2

Session Manager Window

[~_ ~essi~r~~~~~I~~~~~~~~_[~~~~~':.fl"-~~8_~~~~~._,~~ Ri9_~~~~~~~--,-~[5j]
Session

Applications

Customize

Print Screen

Help

Messages
0

Starting Process 6801 "dxterm"

Q-

Managing Windows
To learn how
to manipulate
windows
and other
DECwindows
techniques,
see the
DECwindows
User's Guide.

As you start applications and create windows, you might want
to change how windows look on your screen. The DECwindows
Window Manager lets you:

• Shrink windows to icons
•

Change the size of windows

• Move windows around on your screen
• Stack windows
If your screen becomes too crowded, you can shrink windows to
icons. When you shrink a window, DECwindows puts an icon
representing the window in an area of the screen called the Icon
Box. Windows that you shrink remain active but are hidden from
view. You can expand the icon to redisplay the entire window by
selecting the icon from the icon box.

Accessing the ULTRIX Operating System
The User Executive (UE) is a graphic interface to the ULTRIX
operating system. Using UE, you can execute system commands
and run DECwindows applications. Because the UE lets you
make selections from menus, you do not need to remember the
format of system commands.

2-4 The User Environment

To learn more
'Lbout using
'Lnd customizing
UE~ see the
DECwindows
User~s Guide.

When you run the UE, the main window displays the names of
the files in your current directory. To execute a command, you
select the file to which the command applies, then choose the
appropriate command. The UE prompts you for parameters, then
executes the command.
UE provides the following commands for working with directories
and files:
• Create Directory
• Copy
• Display
• Move
• Search
• Remove
• Print

[{you are
unfamiliar with
the ULTRIX
operating
system, see
The Little
Gray Book: An
ULTRIX Primer.

You can start many DECwindows applications from the UE
window. When you choose an item from the UE Applications
menu, DECwindows starts the application in a new window. The
UE window remains available to start additional applications or
to perform other tasks.
You can customize UE menus to suit your work environment.
For example, you can add menu options that perform additional
file operations or add new menu names and build accompanying
pull-down menus. Figure 2-3 shows the User Executive window.

The User Environment 2-5

Figure 2-3
~

UE Window

Startup -/usrlstaff2/hume

101il

Control Cus10mize Views FDes Applications
Direc10rles FDes Total: 12 Selected: 0
~staff2
Irume

Man
bin

..
hin
. profile
.cshrc
. login
.mh-profile

Hail
· fOJ:Ward
· ue-proflle
· dxcalendar . dwc
sample_figure.ddif

Full Direc10ry Path : msrlstaff2~

Fnter:

1*·1

GeHing Online Help
DECwindows provides online help for the user environment.
For most applications, you get help from a pull-down menu.
DECwindows displays a general help screen from which you
can request more specific help. Some applications also provide
context-sensitive help. For these applications, DECwindows
displays help that is relevant to the window you are using.
Basic information about using DECwindows, such as how to
manage windows and use dialog boxes and scroll bars, is available
from the Session Manager online help. In addition, many
DECwindows terms are explained in the Session Manager help.
Help is designed to let you request general information on an
application and quickly narrow the focus of your inquiry. With
DECwindows Help you can:
• Navigate quickly through help topics
• Record a history of your help session
• Search help for a keyword or topic supplied by the application
• Save the help text in a file for printing.

2-6 The User Environment

The Help menu contains the Overview and About menu items. To
see an overview of your application, choose the Overview menu
item. To get product information about your application, such as
the software version number, choose the About menu item. Some
applications have additional Help menu items, for example, the
Glossary menu item, which lets you look up terms used in your
application.
Choosing any menu item from the Help menu displays a Help
window.

DECwindows Desktop Applications
For more
information
about using
individual
applications,
see the
DECwindows
Desktop
Applications
Guide.

DECwindows includes a variety of applications that are designed
to increase productivity by automating basic tasks. For example,
Mail automates sending and receiving interoffice mail; the
Cardfiler automates creating and filing index cards.
Because DECwindows is based on the industry-standard X
Window System, you will be able to choose from an extensive
offering of applications from Digital and other vendors.
DECwindows provides the following applications:
• Calculator
• Calendar
• Cardfiler
• Clock
• CDA Viewer
• DECterm terminal emulator
• Mail
• Notepad
• Paint
• PostScript Previewer
• Puzzle

The User Environment 2-7

For information
about basic
DECwindows
terms and
techniques,
refer to the
DECwindows
User's Guide.

You use the same basic window techniques with every
DECwindows Application. This simplifies learning about and
using new applications. Some of these basic techniques include:
• Using a mouse to point to and select screen objects
• Choosing items from menus
• Using scroll bars
•

Supplying information in dialog boxes

• Copying or moving text within a window or between
applications
The following sections introduce the DECwindows applications.

Calculator
You use the Calculator to perform basic arithmetic functions:
addition, subtraction, multiplication, division, percentages, and
square roots. You can also use the Calculator to perform advanced
operations, such as trigonometric and inverse trigonometric
functions.
You enter data in the Calculator by using the moUSe t() click
buttons on the screen, or by using the keyboard. The Calculator
has two displays. One display shows the current operation; the
other display shows the contents of memory.

Calendar
The Calendar combines the functions of a desktop calendar and
an appointment book to help you keep track of your meetings and
plan your time. The Calendar lets you look at a year or month
display, or to review your scheduled appointments a day at a time.
You can use several calendars for different purposes. For example,
a group might share a calendar for making conference room
reservations.
Calendar also lets you:
• Create calendar entries that look like appointment pages from
a desktop calendar or diary
• Mark special days, such as birthdays or holidays
• Add icons to calendar entries that you can use to associate
with the entry
•

2-8 The User Environment

Send and receive calendar entries through electronic mail

Figure 2-4 shows the Calendar Day view window.
Figure 2-4

Calendar Window

IiOII Calendar X2.0:
File

Edit

View

Entry

Customize

Help

October, 1989

November, 1989

YIk SUI\ Mon Tilt Wed Ttw. Fli S~t

401Z34567
41 8 9 1IJD]11 12 13 14
42 1 5 16 17 18 19 ZO 21
43 22 Z3 Z4 Z5 Z6 Z7 28
44 293031

45 5 6 7 8 9 10 11
4S 1213 14 151617 18
47 19 ZO Zl ZZ Z3 Z4 25
48 26 Z7 Z8 29 30

Tuesday the 10th of October, 1989

I-~·;;;·T-"·"·"-··"····-·······-·····---······""··"···

. . . . . _. ._._. . . . . . . . ._... 0

~ ..............f· .................... · .. · .. · .................... · .......... · .. · .. · ..

~I
~I

.....-..-...-............................_....... _.....- .. _.............................................................................

~I~ 1:00 I
~I

...•..•......• ! ........................................•.......•..................

·---tI. . ·-----·. . ·. ·-. . . ·-. ·. . . . . . . . . ·. . . . . . . . ·. . . . . . . . . . . . . . . . . . . . . . .

~l . . ·-·.

2:00

~···············f····································· ............................. .

~·--·-....I ..·..-..·-....-··..·....-......·....··..........-·..............··....·......................_ .....-.......

I~ :· ·.I--··-.· · · .·t-.· ·-·· .·. .··. .···-·-·-.
· · · ·-.····-.· ·. .·--·· ·. . .·. .·. .·. . .·. ....................
I
. . .__. .__. . . . . . . .
~I·-·-

I Previous Day I

I 2:28pm

Next Day

Cardfiler
The Cardfiler provides a system for organizing information; this
system is similar to using index cards. Using the Cardfiler, you
create cards that contain information, such as names, addresses,
and phone numbers. You can also create files that group cards
with similar information. For example, you might create a file for
business cards and a file for personal cards.

The User Environment 2-9

Figure 2-5 shows the cardfiler windows.
Figure 2-5

Cardfiler Windows
Card: Claude Monet
File

Clallde Monet

Georgia O'Keeffe
James Whistler

Edit

Card

Help
.(>

11840-1926
Impressionist
Civerny, France

[

Vincent Van Gogh

Index for this card:

IPablo Picass~

I Cancel I
In addition to text, you can add graphics, such as those you create
with the Paint program, to Cardfiler cards.

Clock
The Clock displays the date and time in analog, digital, and
military format. You can customize the display to produce
different formats. Clock provides an alarm to remind you of
important events.

CDA Viewer

III

The CDA Viewer displays a Digital Document Interchange Format
(DDIF) file and lets you page through its contents. DDIF is a
standard format for the storage and interchange of compound
documents. Compound documents are documents that contain
multiple elements (for example, text and graphics).

DECterm

I1i!iI
~

The DECterm terminal emulator displays a window that looks
and functions like a VT300-series terminal. Applications written
for VT52, VT100, VT220, or ReGIS terminals run without
modification in the DECterm window. Within a DECterm
window, you can set terminal characteristics and customize
DECterm features such as the window size and screen fonts, the
display background and cursor shape, and special keyboards and
character sets.

2-10 The User Environment

DECterm also lets you
• Copy information within or between terminal windows
• Clear and resize terminal windows
• Compose special characters
See Figure 2-1 for an illustration of a DECterm window.

Mail
The Mail application provides a way to communicate with other
users on the system or network. With this application you can:
• Send messages to any user on the system or network
• Read messages from other users and reply to those users
• Print messages
• File and delete messages
• Forward messages
• Send files
• Extract messages you receive to files
Figure 2-6 shows the main Mail window.

Notepad
The Notepad is an editing program that lets you compose and
manipulate text. You can use the Notepad editor for any writing
task. You can copy text from other windows and paste it into the
Notepad. Notepad also lets you:
• Search for text strings
• Include other files
• Sort text
• Use ULTRIX text filters
• Split your Notepad window into a number of edit windows
• Change the size and style of fonts used to display text
• Recover lost edits

The User Environment 2-11

Figure 2-6

Main Mail Window
I~I§]J

~I Mail: Main inbox

I File

Edit Pick Create-Send
. . drafts wastebasket

Read

Maintenance

Customize

II Read new rna/I II O'eate-Send I
I

.0.

I Deliver mail I~ I l:j)I'"\.(f(W II Prinf II Mmm II 1).}I.}h} I

Paint
Paint is an application that you use to create and save screen
images. Using Paint is much like painting or drawing. You select
a brush or pencil and trace designs. However, Paint makes the
process easier.
With Paint you pick shapes from a menu and let paint draw
the shape; you can also select fill patterns to shade (color) your
picture. To provide greater detail for part of your picture, you can
use the zoom feature to magnify a specified area. If you do not
like your picture, you can erase it and start over; if you like it, you
can print a copy.
Paint stores images as DDIF files or XII Bitmap files.
Applications that display graphics, such as Cardfiler, can use
files that you create using Paint.

PostScript Previewer
The PostScript Previewer lets you display PostScript files on
your workstation screen and page through the contents. Because
the screen fonts correspond to fonts used by PostScript printers,
you can see what a PostScript file looks like before you print it.

2-12 The User Environment

Puzzle
••••
••••
••••
•••

The Puzzle game lets you solve a classic sliding-tile puzzle on your
workstation display.

Other Worksystem Applications
Your work system environment also includes tools for the
programmer and a tool to compare differences between two
files.

Debugger
For more
information
about using the
Debugger see
the Guide to the
dxdb Debugger.

The Debugger is a tool that helps you locate run-time or logic
programming errors in compiled C language source files while
in the DECwindows environment. With the Debugger, you can
display your source code in one window while you set a breakpoint
or examine variables in other windows.

Visual Differences
For more
information
about the Visual
Differences
program see the
Guide to the
dxdiff Visual
Differences
Program.

The Visual Differences application lets you compare ASCII text
files on a line-by-line basis, then provides a graphical display of
the differences between the two files.
The files you want to compare are displayed in two windows
on your screen. Visual Differences highlights the differences it
finds and shows the location of the differences in the two files
by connecting them with lines. You can use scroll bars or control
buttons to move forward or backward through the text displayed
on your screen.
The Options menu lets you change the way differences are
displayed. For example, you can display line numbers or scroll
one file independently of the other.
Figure 2-7 shows how Visual Differences displays the differences
between two files.

The User Environment 2-13

Figure 2-7

The Visual Differences Display

SII Z

ZS-0304-R

2-14 The User Environment

3
The Programming Environment
The XVI offers a rich environment for developing applications for
graphic workstations. This chapter provides an overview of the
programming environment and describes the libraries and tools
available to the DECwindows application programmer.

Overview of the Programming Environment
The XVI programming environment 8llows you to develop
applications that have simple, consistent, graphics-oriented
interfaces. This consistency is important: it allows the user to
transfer knowledge gained from using one application to another,
reducing the amount of learning and subsequent recall.
The core of the graphics programming environment consists of
the Xlib and XVI Toolkit programming libraries. Xlib supplies
low-level routines for performing basic graphic and windowing
functions. The XVI Toolkit supplies high-level routines for
creating and managing user interface objects like menus, scroll
bars, and buttons. Applications can call routines from both
libraries.
The XU! style is
fully defined and
illustrated in the
XU! Style Guide.

XVI Toolkit routines simplify the task of creating a user interface.
For example, you can create a menu with one call to an XVI
Toolkit routine, whereas creating the same menu using Xlib
routines would require many more calls and program lines. V sing
XVI Toolkit routines also ensures that an application interface
conforms to the XVI style, which makes the application easy to
learn and use.

The Programming Environment 3-1

In addition to Toolkit routines, the XUI Toolkit includes the
XUI User Interface Language (UIL) compiler and XUI Resource
Manager (DRM) routines, which, in essence, let you create an
entire interface with one library call. The IDL and DRM let
you separate form and function in an application, giving you the
ability to specify and modify the interface without recompiling the
entire application.

Creating and Managing Windows
Using XUI programming library routines, you can write
applications that create and manage windows. A window is
an interface object that displays output or accepts input for an
application.
From the user's perspective, an application usually consists of
a series of windows. You use library routines to construct and
manage this hierarchy of windows.
Figure 3-1 illustrates the components of the XUI programming
environment. The following sections describe the components.
Figure 3-1

XUI Programming Environment

Application

User Interface I
Language (U IL) I

1------------1
XUI
1
1
1
Resource
1
Manager
1

High-level
Routines

1
1
1
1
1
1
1
1

Low-level
Creation
Routines

I1 Cut and Paste
1
1
1
1

Routines

XUI
Toolki1

~-----------L----------~----------~----------.
X Toolkit (Intrinsics)

I
Xlib
ZS-0302-R

3-2 The Programming Environment

The Xlib Library
li'or more
~nformation

'J,bout Xlib, see
the Guide to the
Klib Library:
C Language
Binding.

The Xlib programming library is Digital's implementation of the X
Window System's C-language graphics programming library. Xlib
is the lowest-level programming interface to the DECwindows
environment. Applications call the following Xlib routines to
perform basic windowing and graphics functions:
• Display routines
• Window routines

For more
information
about the
Display
PostScript
system, see
the Guide to
Developing
Applications
for the Display
PostScript
System.

• Management routines
• Event and error handling routines
• Graphics routines
• Text, font, and cursor routines
DIGITAL has extended Xlib to integrate Xlib Library with
the ULTRIX operating system and to add DECnet support.
In addition, Digital has extended the Xlib library to provide
routines for the Display PostScript system. This extension lets a
C-Language application display images in an X window by calling
functions that send PostScript code.

XUI Toolkit
From a programming perspective, the XVI Toolkit is the key to
the DECwindows environment. XVI Toolkit routines provide a
straightforward way to create a user interface that conforms to
the XVI style. The XVI Toolkit also provides development tools
that allow you to separate form and function in an application;
you can modify an interface without having to recompile and
relink the application.
XVI Toolkit routines allow you to create widgets. From a user's
perspective, a widget is an interface object that displays output or
accepts input. From a programmer's perspective, a widget is an
object that is logically connected to application functions.
When a user interacts with a widget (for example, by making a
menu selection), information in the widget makes the application
respond appropriately. Widgets can be simple interface objects
such as labels and buttons, or complex objects such as menus and
scroll bars.

The Programming Environment 3-3

For more
information
about the XUI
Toolkit, see the
Guide to Writing
Applications
Using XUI
Toolkit Widgets.

You can use the following components of the XUI Toolkit to create
and manage widgets:
• High-level widget creation routines
• Low-level widget creation routines
• XUI Intrinsics Routines
• Cut and paste routines
• Convenience routines
• Compound String routines
• XUI User Interface Language (UIL) Compiler
• XUI Resource Manager (DRM)
The following sections describe the components of the XUI Toolkit.

High-Level Widget Creation Routines
High-level routines let you create a widget hierarchy and specify
initial attributes of a widget. High-level routines provide some
control over widget attributes while ensuring that your application
conforms to the DECwindows style.

Low-Level Widget Creation Routines
Low-level routines also provide ways to create a widget hierarchy
and specify initial attributes of a widget. Compared to the highlevel routines, low-level routines provide more control over widget
attributes, and therefore give you more freedom to customize
the widgets. However, low-level routines can be more difficult to
use. Often, you must specify a lengthy argument list in calls to a
routine.

XUI Intrinsics Routines
XUI Intrinsics routines let you manage and manipulate widgets at
run time. Using intrinsics routines, you can do the following:
• Control the location of widgets
• Map and unmap widgets to the screen
• Process input from the user of the application

3-4 The Programming Environment

Cut and Paste Routines
Cut and paste routines allow application users to transfer data
between windows.

Convenience Routines
Convenience routines provide functions that let your application
format and display messages, such as from the operating system,
in a message window. Convenience routines also provide functions
that let you write upward-compatible applications and widgets.

Compound String Routines
Compound string routines let applications create and manipulate
compound strings and font lists. Using compound string routines,
you can
• Create a font list and font list entries
• Create compound strings
• Compare and manipulate compound strings

XUI User Interface Language Compiler
For more
information
about UIL,
see the Guide
to the XUI
User Interface
Language
Compiler.

The XUI User Interface Language (UIL) is a specification
language that simplifies the creation and customization of an
application's user interface. Using UIL, you create a specification
file that describes the objects (menus, dialog boxes, labels, push
buttons, and so on) that make up the user interface for your
application. This UIL file also specifies the routines to be called
when the interface changes state (as a result of user interaction.)
Using UIL, you can specify the following:
• The widgets that make up the interface
• The characteristics of the specified widgets
• The callback routines for each widget
• The hierarchy of widgets in the application
The UIL compiler provides the following benefits to application
developers:
• You can create a variety of interfaces for a single application.
For example, if you develop applications for international
markets, you can customize the interface for each market.

The Programming Environment 3-5

• The mL compiler detects a variety of errors that high-level
and low-level XUI Toolkit routines do not detect. For example,
the UIL compiler issues diagnostic messages if you specify
the wrong type of value for an argument or if you specify an
unsupported argument.
• The UIL compiler aids in the prototyping of user interfaces for
applications. You can develop and test a variety of interfaces,
even if the application's functional routines are unavailable.

XUI Resource Manager
For more
information
about DRM,
see the Guide
to the XUI
User Interface
Language
Compiler.

The XUI Resource Manager (DRM) is the facility that takes data
from the compiled UIL specification file (called the UID database)
and creates the widgets. DRM translates the information in the
mD database into low-level widget creation calls. If you use UIL
to create a user interface, your application must include a special
set of routines that invoke DRM. Using DRM routines reduces the
time required for applications to create widgets.

3-6 The Programming Environment

4
Customizing Your OECwindows
Environment
You can personalize your DECwindows applications by modifying
entries in the X Resource Manager database file called .Xdefaults.
This chapter introduces the basics you need to customize your
DECwindows environment. For details on individual applications,
see the ULTRIX Worksystem Software Reference Pages.

Why Customize with .Xdefaults?
You can use DECwindows as it comes packaged for you or you
can create a personalized environment. The Session Manager
Customize menu lets you change several options, including
keyboard, window, pointer, and security settings. U sing the
Session Manager Customize menu, you can examine the preset
settings, then choose and save new settings.
However, some preset conditions cannot be changed with menu
items. Such conditions include whether or not the application
starts as a window or icon, and the size and location of an
application's startup window.

Customizing Your DECwindow5 Environment 4-1

Instead, you can modify these preset conditions by registering
your user preferences with the X Resource Database Manager
(xrdb). You can specify these preferences either at the command
line or by way of a database file called .Xdefaults.
For example, by adding the appropriate entries, you can change:
• An application's startup state or screen position
• The height and width, in pixels, of a window
• The background and foreground color of window components
such as push buttons, scroll bars, or title bars
• The fonts that appear in labels or titles
• The way keyboard keys and mouse buttons map to text editing
functions

Getting Started
The XUI Toolkit provides a standard set of window objects
(widgets) that DECwindows applications can use. Some of these
widgets include menus, push buttons, toggle buttons, dialog boxes,
and scroll bars. Figure 4-1 illustrates some of these window
components.

4-2 Customizing Your DECwindows Environment

Figure 4-1

Window Components
Title Bar

Commands

Edit

Dialog Box

CUstomize

Help

all'llosL41> •

DEcterm: Save Current Settings As
File Filter
I/usrlstaff/almostlhume/.... DEc4erm
Select Name For Configuration File:/usrlstafflalmostlhumel
Filter

Cancel

!!ill

DECtenn: Graphics

o Share Color Map Entries
Ij] Enable Backing Store

o Report Macrograph Contents

~ Bit Planes

~~~~='IL#

II I Apply I I Cancel

~~_________ _--------~J

Toggle Buttons

Push Buttons

The X Resource Database Manager (xrdb) is a database
manager that assigns attributes to widgets and groups of
widget components. You manipulate this database by editing
the .Xdefaults file.
The .Xdefaults file contains entries that provide information
about the appearance or characteristics of a widget. These widget
characteristics are referred to as resources. You provide entries
in the file .Xdefaults in the form of resource specification strings.
Most DECwindows applications read the .Xdefaults file during
startup and use the defined entries to customize the appearance
and characteristics of their windows.

Customizing Your DECwindows Environment 4-3

Creating the .Xdefaults File
The Resource Manager and DECwindows applications read the
.Xdefaults from your home directory. You can create an .Xdefaults
file in your home directory or copy a sample .Xdefaults file from
the lusrlskel directory. You can modify, remove, or add to the
entries in the sample file to customize your windows.
Example 4-1 provides a sample .Xdefaults file. Note that
comment lines begin with an exclamation point 0).
Example 4-1

Sample .Xdefaults File

#ifdef COLOR
*highlight:
*background:
#endif

#ffffOOOOOOOO
#bffffffffcOO

*** Session Manager ***
I

•

~m. create terminal:
#ifdef COLOR
sm. pointer_foreground:
sm.pointer background:
#endif
-

1
#000
#fff

*** Customize Icon Box ***
I

•

~. default. sticky:

true

•

~*iconStyle:

~*Geometry:

=150x200-0-0

•

CD ~m*forceBars:

false

*** Customize DECterm ***
I

•

~*DXterm*iconStyle:

•

~m*DXterm*iconName:

My_Node

DXterm*saveLinesOffTop:
DXterm*DECterm.scrollVertical:
DXterm.main.terminal.autoWrapEnable:
!

#ifdef COLOR
DXterm*background:
DXterm*foreground:
#endif

wheat
black

*** Customize Mail ***
I

•

dxmail*initialState:

4-4 Customizing Your DECwindows Environment

on
on
on

The following notes describe the effect that some of the resource
specifications in Example 4-1 have on an application or window.
•

Tells the Session Manager to create one terminal emulator
window at startup

•

Locks your icon box window as the bottom window on the
screen

•

Sets the icon size to small for all applications

Sets the size and location of the icon box

o Specifies that scroll bars will not appear in the icon box
o Sets the DECterm icon size to large
•

Redefines the DECterm icon name to My_Node.

•

Causes Mail to start as an icon.

Specifying Resources
The .Xdefaults file is a list of resource specification strings you
enter or modify to customize your DECwindows application. Each
resource specification in an .Xdefaults file must have the following
format:
[name*] resource:
name

value

Specifies the name or name string representing
the application or widget to which the resource
assignment should apply. If this argument is not
specified, the resource assignment is globally available
to all applications.
You must separate names in this string with either an
asterisk (*) or a period (.), as follows:

resource
value

Specifies that the resource definition applies to
all widgets even if classes or names are omitted
in the specification string.

Indicates that the resource definition applies
only to the widget named.
Specifies the resource (characteristic) you want to
modify.
Specifies the value that is to be assigned to the
resource.

Customizing Your DECwindows Environment 4-5

Each component of a resource specification has an associated
widget class. Several widgets or widget attributes have the
same class. For example, the foreground color used to draw the
pointer and the text cursor are all delivered as instances of the
Foreground.
You can use the name string to restrict the resource specification
to a type of widget, for example, a scroll bar or text window. Each
widget is associated with a widget class. You can specify a type of
widget in one of two ways:

• Class identifier-Widgets classified according to common
properties and functions (for example, main window, scroll bar,
menu bar, or push button)
• Name identifier-Name of a particular item in a widget class
(for example, the Dismiss push button)
Widget classes and names are case sensitive. Most names begin
with initial lowercase letters; compound names use initial capital
letters to separate names, for example:
backgroundPixel

In the resource specification, be sure to specify names in the
following order:
Application name

For more
information
about widgets
and the widget
hierarchy, see
the section
Identifying
Widgets.

Widget class

Additional widget names

Resource name

When specifying widget names, it is important to understand that
widgets are arranged in a hierarchical fashion. The syntax you
use when customizing must match the class and object hierarchy
built into the toolkit widgets.
Depending on how you specify the widget name in your resource
assignment string, the change you assign to one widget can affect
its related widgets. Similarly, if you do not name all of the related
widget components, the change may not take effect.

4-6 Customizing Your DECwindows Environment

'or detailed
7-formation
bout naming
Jidgets and
esources, see
ie section More
lbout Widgets
,nd Resources.

You can find a complete list of resource names, classes, and types
in the file lusr/include/XIl1StringDefs.h. You can find a complete
list of color names in the file lusrllib/Xll/rgb. txt.
When you finish adding resource specifications to your .Xdefaults
file, you must load changes into the server to have them take
effect. To load changes, take one of the following actions:
•

Quit the Session Manager then start a new session
or

•

Run the Resource Manager to reload the .Xdefaults file into
the server. To run the Resource Manager, type the following
command:
% /usr/bin/Xll/xrdb .Xdefaults

Note: Some changes will not take effect unless you quit your
current session and then start new one.

Resource Specification Examples The following examples show
specifications you can add to the file .Xdefaults to customize your
DECwindows applications. These examples illustrate the use of
application names, widget names, and delimiters to control the
effect of the resource specification.

Example I-Specification string that affects all applications:
*background:

green

This specification changes the background color of all
DECwindows applications. Note that without the asterisk,
the resource specification would be ignored.

Example 2-Specification string that affects one application:
dxmail*background: green

The addition of the application name dxmail causes this
specification to change the background color of each of the
Mail application's windows. Other applications are not changed.

Example 3-Specification string that affects one component in
one application:
dxmail.background: green

The use of the period (.) delimiter instead of the asterisk (*)
causes this specification to change the background color of Mail's
main window only. Mail's other windows are not changed.

Customizing Your DECwindows Environment 4-7

Example 4--Specification string that affects one occurrence of a
component in an application.
dxmail*folderArea*background: green

The addition of the widget name identifier folderArea causes this
specification to change the background color of a particular area
only-all of the folder buttons in Mail's main window.

More About Widgets and Resources
The sample .Xdefaults file in Example 4-1 provides enough
information to get you started in personalizing your worksystem
applications. This section provides detailed information about
widgets and resources. You should review this section before
trying more sophisticated customizing.

Locating Resources
Resources are assigned when the application program creates
a widget or by the application's defaults file. You can assign
personal preferences at the command line, through the .Xdefaults
file in your home directory, or any other file. Use the Resource
Manager to load the values into the server. You can assign
resources in any of the following categories:
• General
• Widget-specific
• Application-specific

Precedence for SeHing Resources
Resources are set for widgets in the following precedence:
• Instances take precedence over specific classes. For example,
*scrollbar.background

has precedence over
*scrollbar.Background

• Any instance or class explicitly stated takes precedence over
one that is omitted. For example,
dxmail*Background

takes precedence over
Background

• Name strings bound by a period (.) take precedence over those
bound by an asterisk (*).

4-8 Customizing Your DECwindows Environment

For example,
dxmail.geometry

has precedence over
dxmail*geometry

• An application can have its own set of database files that
provide defaults. These defaults override resource values
assigned when the widget is created.
•

User-supplied resource values supplied on the application
command line or in the personal resource database file
.Xdefaults override any widget or application defaults.

You can find a complete list of resource names, classes, and types
in the file lusr/include/X11/StringDefs.h.
General Resources
resources.

Table 4-1 describes the general widget

Table 4-1

General Resources

Resource

Description

Specifies the placement (in pixels) of the left side of
the widget window relative to the inner upper corner
of the present window. The default is centered in the
parent window.

Specifies the placement (in pixels) of the upper left
corner of the widget window relative to the inner
upper left corner of the parent window. The default is
centered in the parent window.

width

Specifies the width (in pixels) of the widget window.

height

Specifies the height (in pixels) of the widget window.

border

Specifies the border pattern.

borderWidth

Specifies the border width of the widget window.

borderPixMap

Specifies the color of the widget window's border.

foreground

Specifies the color of foreground objects in the widget
window.

background

Specifies the color of background objects in the widget
window.

font

Specifies the text font used in the widget.

Customizing Your DECwindows Environment 4-9

Widget-Specific Resources Widgets also have resources not
specified by general resources for all classes of widgets. Table 4-2
describes the widget-specific resources.
Table 4-2

Widget-Specific Resources

Resource

Description

label

Specifies the string that defines the text of the label.

wordWrap

Specifies a Boolean value of either true (1) or false (0).
If true, lines are broken at word breaks (that is, text
does not go off the right edge of the widget window).

scrollVertical

Specifies a Boolean value of either true (1) or false (0).
If true, a scroll bar is added to allow the user to scroll
vertically through the text.

translations

Specifies the translation table used by the input
module to determine the mapping of keystrokes and
mouse actions.

shape

Specifies a Boolean value of either true (1) or false
(0) that indicates the toggle button shape (either
rectangular or oval). If true, the toggle button shape
is rectangular.

Application-Specific Resources Some applications define
unique resources for widgets. For example:
• The PrintCommand resource in dxmail (Mail).
• The windowManagerName, terminalEmulatorName,
createTerminal, and startupState resources in dxsession
(Session Manager).
• The default.sticky resource in dxterm (DECterm).
You find application-specific resources in the application's
individual default file. The default files for individual applications
are located in /usrllihIX11/app-defaults/application-name.
Customize these widgets by referencing them by name in your
.Xdefaults file.
Example 4-2 and Example 4-3 show sample application default
files similar to those you can find in /usrllibIX11/app-defaults.

4-10 Customizing Your DECwindows Environment

Example 4-2

Default File for the DECwindows Clock Application

! The basics

o
o

::lock.x:
::lock.y:
::lock.width:
::lock.height:

150
105

! Make it pretty
Clock*fontFamily:

*-*-Times-Bold-R-Normal--*-*-*-*-P-*-*-*

! Set the components

Clock.Clock.AnalogOn:
Clock.Clock.DigitalOn:
Clock.Clock.DateOn:

1
1
1

! Set the alarm

Clock.Clock.AlarmOn:
Clock.Clock.AlarmPM:
Clock.Clock.AlarmHour:
Clock.Clock.AlarmMinute:
!Clock.Clock.AlarmMessage:

o
12
00
Alarm Message

!
! You can change colors by either affecting the whole clock

!
Clock*foreground:
Clock*background:

DarkSlateGrey
Turquoise

! or individual parts
!
!Clock.Clock.Analog.background:
! Clock.Clock.Analog. foreground:
!Clock.Clock.Date*background:
!Clock.Clock.Date*foreground:
!Clock.Clock.Digital.background:
!Clock.Clock.Digital.foreground:

DarkSlateGrey
Turquoise
DarkSlateGrey
Turquoise
DarkSlateGrey
Turquoise

Customizing Your DECwindows Environment 4-11

Example 4-3

Default File for the DECwindows Notepad Application

*copyrightMessage:
Notepad - DECwindows Text Editor
notepad. geometry:
500x650+4+120
on
*enableBackups:
!
*Text.font:
-DEC-Terminal-Medium-R-Narrow--14-140-75-75-C-6-IS08859-1
*DwtText.font: -DEC-Terminal-Medium-R-Narrow--14-140-75-75-C-6-IS08859-1
*workArea*scroIIVertical:
*workArea*wordWrap:
*copyright:
*changesUntiICompress:
!
*DwtMenu*New.label:
*DwtMenu*OpenDialog.label:
*DwtMenu*OpenSelected.label:
*DwtMenu*IncludeDialog.label:
*DwtMenu*Save.label:
*DwtMenu*SaveAs.label:
*DwtMenu*Revert.label:
*DwtMenu*Quit.label:
*DwtMenu*Exit.label:
*DwtMenu*Undo.label:
*DwtMenu*Redo.label:
*DwtMenu*UndoDialog.label:

New
Open ...
Open Selected
Include ...
Save
Save As ...
Revert
Quit
Exit
Undo
Redo
Undo ...

*DwtMenu*Cut.label:
*DwtMenu*Copy.label:
*DwtMenu*Paste.label:

Cut
Copy
Paste

TRUE
TRUE
on
1

*DwtMenu*NextSelected.label:
*DwtMenu*PreviousSelected.label:
*DwtMenu*NextDialog.label:
*DwtMenu*PreviousDialog.label:
*DwtMenu*NextlncrementaIDialog.label:
*DwtMenu*PreviouslncrementaIDialog.label:
*DwtMenu*ReplaceOnce.label:
*DwtMenu*ReplaceSelected.label:
*DwtMenu*ReplaceAII.label:
*DwtMenu*GoToTop.label:
*DwtMenu*GoToBottom.label:
*DwtMenu*GoToSelectedLine.label:
*DwtMenu*GoToLine.label:
*DwtMenu*positionMenu.label:
*DwtMenu*fileMenu.label:
*DwtMenu*editMenu.label:
*DwtMenu*findMenu.label:
*DwtMenu*replaceMenu.label:
*DwtMenu*optionsMenu.label:
*DwtMenu*searchOptionsDialog.label:

Next Selected
Previous Selected
Next ...
Previous ...
Next Incremental ...
Previous Incremental ...
Replace Once ...
Replace Within Selected Area ...
Replace All ...
Go to Top
Go to Bottom
Go to Selected Line Number
Go to Line ...
Navigate
File
Edit
Search
Replace
Customize
Set Search Options ...

*DwtMenu*helpMenu.label:

Help

*workArea.borderWidth: 1

4-12 Customizing Your DECwindows Environment

Identifying Widgets
A widget is a window component that displays output or accepts
input. Widgets can be simple interface objects like labels
and buttons, or complex objects like menus and scroll bars.
Widgets are logically connected to application functions. When
you interact with a widget (for example, by making a menu
selection), information in the widget makes the application
respond appropriately.
Widget Hierarchy Widgets are arranged in a hierarchical
fashion. This hierarchy establishes a relationship between widget
components. For example, the top-level widget (parent) of an
application may have several related subwidgets (children).

Depending on how you specify your resource assignment string,
the change you assign to one widget can affect its related
subwidgets, or it may not take effect if you do not name all of
the related widget components. For example, if an asterisk (*)
is used in the specification string, the resource is applied to the
entire subwidget tree.
Figure 4-2 illustrates the widget hierarchy.

Customizing Your DECwindow5 Environment 4-13

Figure 4-2

Widget Hierarchy

ZS-0303-R

4-14 Customizing Your DECwindows Environment

Naming Widgets in Resource Specification Strings Table 4-3
describes some of the widgets you can name in .Xdefaults resource
specification strings. Note that when using a name from Table 4-3
in a resource specification string, you must prefix the name with
the string "Dwt". For example, DwtAttachedDialogBox.
Table 4-3

XUI Toolkit Widgets

Widget

Description

Boxes

AttachedDialogBox

A type of dialog box that when resized,
changes the position of the subwidgets it
contains. Widgets can be attached to any
edge of the attached dialog box. This allows
the subwidgets to remain visible when the
attached dialog box is resized.

CautionBox

A type of dialog box that displays a warning
message before an irreversible action is
executed.

DialogBox

A composite widget that contains subwidgets.
Each subwidget displays information or
requests or handles input from the user.

FileSelection

A type of dialog box that queries the user for
a file specification.

Help

A widget that presents helpful information on
the application you are using.

ListBox

A box that presents the user with a list of
choices. A list box includes a scroll bar, by
default, to aid in viewing list items.

MessageBox

A type of dialog box that displays a message.

PopupAttachedDialogBox A type of attached dialog box that does not
get clipped by its parent.
A type of the dialog box that does not get
PopupDialogBox
clipped by its parent.
RadioBox

A box that presents the user with a list of
choices, only one of which can be selected at
anyone time.

SelectionBox

A box that presents the user with a list of
choices, only one of which can be selected at a
time.
(continued on next page)

Customizing Your DECwindows Environment 4-15

Table 4-3 (Cont.)
Widget

XUI Toolkit Widgets
Description

Boxes
WorkInProgressBox

A type of dialog box that displays a "Work in
Progress" message.

Buttons
PulldownMenu

Presents a list of choices that are not visible
until selected from a menu.

PushButton

Displays a rectangular border around a label.
The label defines the immediate action of
the button, for example, OK or Dismiss in a
dialog box.

ToggleButton

Provides control of an "on" or "off" state.

Menus
Menu

Presents a list of choices to the user.

MenuBar

Presents a list of choices arranged horizontally, each of which contains a set of pull-down
menus.

OptionMenu

Presents a "one of many" choice while
displaying the current status of choices.

Windows
CommandWindow

Creates a command entry area.

MainWindow

Top-level window that contains subwidgets,
for example, a title bar. All other application
windows are subordinate to the main window.

Window

A simple window for an application.
(continued on next page)

4-16 Customizing Your DECwindows Environment

Table 4-3 (Cont.)
Widget

XUI Toolkit Widgets
Description

Miscellaneous

Label

Displays read-only, constant text in a widget.

Scale

Allows the choice of a value from within a
range of values.

ScrollBar

A screen object that the application or user
uses to scroll through display data too large
for the display area.

Separator

Draws a bar or line between list or menu
entries.

TextEdit

Allows lines of text to be edited.

Changing Key Definitions
You can use the .Xdefaults file to customize text widgets by adding
resource specifications that change the way keys are mapped to
text editing commands. Table 4-4 lists the text editing keys you
can redefine and describes the preset text editing function for each
key.
Table 4-4

Text Editing Keys and Preset Functions

Key

Editing Function

=> (Right arrow)

Moves the cursor one character to the right. In a
single-line field, the cursor does not move when
positioned at the end of the line. In a multi-line field,
the cursor moves into the first position of the next
line.

~ (Left arrow)

'ft (Up arrow)

Moves the cursor one character to the left. In a singleline field, the cursor does not move when positioned
at the beginning of the line. In a multi-line field, the
cursor moves into the last position of the previous
line.
In a multi-line field, moves the cursor up one line.

JJ. (Down arrow)

In a multi-line field, moves the cursor down one line.

IF121

Positions the cursor at the beginning of the line.

I SHIFT/F121

Positions the cursor at the end of the line.
(continued on next page)

Customizing Your DECwindows Environment 4-17

Table 4-4 (Cont.)

Text Editing Keys and Preset Functions

Key

Editing Function

IF 131

Deletes characters to the left of the cursor through the
beginning of the word, and shifts to the left all text to
the right of the deleted characters.

I SHIFTIF 13 I

Deletes the characters to the right of the cursor
through the beginning of the word, and shifts to the
left all text to the right of the deleted character.

IDelete I

Deletes the character before the cursor and shifts to
the left all text to the right of the deleted character.

I SHIFTIDelete I

In overstrike mode, deletes the character under the
cursor and shifts to the left all text to the right of the
deleted character.

A translation
specification string in your .Xdefaults file assigns a text editing
command to a named key or mouse button combination. To assign
a new editing command to a named key, use the following syntax:

Assigning New Text Editing Commands

*Text.translations: key: function
key

Specifies the key or mouse button that is used to
invoke the named function.

function

Specifies the function to be invoked when the named
key is pressed.

You can also specify the following mouse buttons in a translation
specification string:
Btnl

Left button or Right button

Btn2

Middle button

Btn3

Right button or Left button

You can assign the following actions to each mouse button:
Down

Action is invoked when the button is pressed

Action is invoked when the button is released

PtrMoved

Action is invoked when the mouse button is
down and the pointer is moved

4-18 Customizing Your DECwindows Environment

Sample Translations Resource Specification Example 4-4
provides text translation entries you can add to your .Xdefaults
file. These resource specifications assign EMACS-like key
bindings to your keyboard keys.
Example 4-4

Sample Text Specifications

DECtoolkit text bindings
*DwtText.translations:
Shift<Key>Oxff53:
<Key>Oxff53:
Shift<Key>Oxff51:
<Key>Oxff51:
<Key>Oxff54:
<Key>Oxff52:
Shift<Key>Oxffff:
<Key>Oxffff:
Shift<Key>Oxffc9:
<Key>Oxffc9:
Shift<Key>Oxffca:
<Key>Oxffca:
<Key>OxffOd:
Shift<Key>OxffOa:
<Key>OxffOa:

forward-word()\n\
forward-character()\n\
backward-word()\n\
backward-character()\n\
next-line () \n\
previous-line()\n\
delete-next-character()\n\
delete-previous-character()\n\
end-of-line () \n\
beginning-of-line()\n\
delete-next-word()\n\
delete-previous-word()\n\
newline () \ n \
delete-next-word()\n\
delete-previous-word()\n\

Shift -Ctrl -Alt<BtnlDown>:
Shift -Ctrl -Alt Buttonl<PtrMoved>:
Shift -Ctrl -Alt<BtnlUp>:
Ctrl -Shift -Alt<BtnlDown>: grab-focus()
Ctrl -Shift -Alt Buttonl<PtrMoved>:
Ctrl -Shift -Alt<BtnlUp>:
-Shift -Ctrl -Alt<BtnlDown>: grab-focus()
-Shift -Ctrl -Alt Buttonl<PtrMoved>:
-Shift -Ctrl -Alt<BtnlUp>:
-Shift -Ctrl -Alt<Btn3Down>:

Ctrl<Key>f:
Ctrl<Key>b:
Alt<Key>f:
Alt<Key>b:
Alt<Key» :
Ctrl<Key> [:
Ctrl<Key>a:

extend-start()\n\
extend-adjust ()\n\
extend-end()\n\
set-insertion-point()\n\
\n\
\n\
set-insertion-point() select-start()\
extend-adjust ()\n\
extend-end()\n\
stuff()\n\

forward-character()\n\
backward-character()\n\
forward-word()\n\
backward-word()\n\
forward-paragraph()\n\
backward-paragraph()\n\
beginning-of-line()\n\

(continued on next page)

Customizing Your DECwindows Environment 4-19

Example 4-4 (Cont.)

Sample Text Specifications

Ctrl<Key>e:
Ctrl<Key>n:
Ctrl<Key>p:
Ctrl<Key>v:
Alt<Key>v:
Alt<Key>\ \<:

end-of-line () \n\
next-line () \n\
previous-line()\n\
next-page () \n\
previous-page()\n\
beginning-of-file()\n\

Alt<Key>\ \>:
Ctrl<Key>z:
Alt<Key>z:
Ctrl<Key>d:
Ctrl<Key>h:
-Shift Alt<Key>d:
-Shift Alt<Key>h:
Ctrl<Key>w:
Ctrl<Key>y:
Alt<Key>y:
Ctrl<Key>j:
Ctrl<Key>o:
Ctrl<Key>m:
Ctrl<Key>l:
Ctrl<Key>k:
Any<Key>:

end-of-file () \ n \
scroll-one-line-up()\n\
scroll-one-line-down()\n\
delete-next-character()\n\
delete-previous-character()\n\
delete-next-word()\n\
delete-previous-word()\n\
kill-selection()\n\
unkill () \ n \
stuff()\n\
newline-and-indent()\n\
newline-and-backup()\n\
newline () \ n \
redraw-display()\n\
kill-to-end-of-line()\n\
self-insert ()

Table 4-5 summarizes the functions you can assign to keys and
describes the text-editing action for each.
Table 4-5

Text Functions

Function

Description

forward-character

Moves the cursor forward one character.

backward-character

Moves the cursor backward one character.

forward-word

Moves the cursor forward one word.

backward-word

Moves the cursor backward one word.

forward-paragraph

Moves the cursor forward one paragraph.

backward-paragraph

Move backward one paragraph.

delete-next-character

Deletes the character after the insertion
point.

delete-previouscharacter

Deletes the character before the insertion
point.
(continued on next page)

4-20 Customizing Your DECwlndows Environment

Table 4-5 (Cont.)

Text Functions

Function

Description

delete-next-word

Deletes the word after the insertion point.

delete-previous-word

Deletes the word before the insertion point.

delete-next-line

Deletes the line after the insertion point.

delete-previous-line
delete-selection

Deletes the line before the insertion point.
Deletes the selection.

insert-file

Inserts a file into the text.

kill-next-word

Kills the word after the insertion point.

kill-to-end-of-line

Kills the characters after the insertion point
to the end of the line.

kill-selection

Kills the selection.

newline-and-indent

Moves the cursor to the next new line and
indent.
Moves the cursor to the beginning of the
previous line.

newline-and-backup
next-page

Moves the cursor to the next screenful of text.

previous-page

Moves the cursor to the previous screenful of
text.
Selects all the text.

select-all
select-word
stuff

Selects the word the insertion point is in.
Inserts the text that was last selected in any
window.

unkill

Inserts the text that was last deleted.

Customizing Your DECwindows Environment 4-21

Index
A
Application default files
location of, 4-10
sample for Clock application, 4-10
sample for Notepad application,
4-12
Applications
creating widgets for, 3-3
Applications, desktop
See also Applications, UWS
Calculator, 2-8
Calendar, 2-8
Cardfiler, 2-9
CDA Viewer, 2-10
Clock, 2-10
DECterm, 2-10
Mail, 2-11
Notepad, 2-11
overview of, 2-7
Paint, 2-12
PostScript Previewer, 2-12
Puzzle game, 2-13
Applications, UWS, 2-13
Debugger, 2-13
Visual Differences, 2-13
Application-specific resources, 4-10
application default files, 4-10
definition of, 4-10

Assigning resources
See resources

c
Calculator, 2-8
Calendar, 2-8
Cardfiler, 2-9
CDA Viewer, 2-10
Clock, 2-10
default file for, 4-10 to 4-11
Compatibility
with VMS, 1-3
Compound Document Architecture
(CDA) Toolkit, 1-5
Compound String routines, 3-5
Convenience routines, 3-5
Customizing applications, 4-1
color, 4-2
color names, 4-6
fonts, 4-2
keyboard mapping, 4-2
resource names, 4-6
sample .Xdefaults file, 4-4
startup state, 4-2
using .Xdefaults, 4-2
window size, 4-2
Cut and Paste routines, 3-5

Index-l

Debugger, 2-13
DECnet, 1-7
DECterm, 2-10
DECwindows
compatibilty with VMS, 1-3
distributed applications
illustration of, 1-3
explanation of applications, 1-5
features of, 1-2 to 1-3
overview of environment, 1-2
Default files, see .Xdefaults file, 4-2
Desktop Applications
See Applications, desktop
Device drivers
types, 1-8
Display PostScript system, 1-3

Library Routines
See Xlib
Low-level routines,

E
Editing keys
See Text editing keys
Editors
Notepad, 2-11

F
Features of XUI
SeeXUI

G
General resources,

4-9

H
Help, 2-6
High-level routines,

M
Mail, 2-11
illustration of window,

2-11

N
Network transport mechanism, 1-7
Notepad, 2-11
Notpad
default file for, 4-12 to 4-13

o
Online help, 2-6
Optimized transport mechanism,

p
Paint, 2-12
PostScript Previewer, 2-12
Programming environment
components of, 3-2
illustration of, 3-2
overview, 3-1
Programming libraries
Xlib, 3-1, 3-3
XUI Toolkit, 3-1, 3-3
Protocol for XII, 1-6
Puzzle game, 2-13

R
3-4

K
Keyboard mapping
redefining in .Xdefaults, 4-17
text editing keys, 4-17

Index-2

3-4

Redefining keys
See Also Text editing keys
assignable values, 4-20
sample EMACS text translation
string, 4-19
Resource names
location of, 4-7

1-7

Resources
Application-specific, 4-10
assigning, 4-5 to 4-8
defined, 4-3
general, 4-9
locating, 4-9
precedence rules, 4-8
widget-specific, 4-10
Resource specification
example of, 4-7
in widget hierarchy, 4-13
order of names, 4-6
syntax for, 4-5 to 4-6
text translation string, 4-18

5
Server, 1-7
controlling access to, 1-3
Session Manager
changing preset options, 2-3
description of, 2-3
illustration of, 2-4
Specification file
UIL, 3-5
Specifying resources
and widget hierarchy, 4-13
in .Xdefaults, 4-5
widget types, 4-6

T
TCPIIP, 1-7
Terminal Emulator, 2-10
Text editing keys
preset functions, 4-17
redefining, 4-17 to 4-18
Text translation string
samples, 4-19
syntax for specifying, 4-18
text bindings, 4-20
Transparent network, 1-3

u
UE (User Executive)
customizing, 2-5
description of, 2-4
illustration of, 2-6
UID database, 3-6
UIL (User Interface Language)
benefits of, 3-5
description of, 3-5
specification file, 3-5
ULTRIX Operating System
accessing using UE, 2-5
User Environment, 2-2
User Executive
SeeUE

v
Viewer
CDA Viewer, 2-10
DDIF document, 2-10
PostScript Previewer, 2-12
Visual Differences, 2-13
illustration of, 2-13
VMS compatibility, 1-3

w
Widget
definition of, 3-3
listing of, 4-15 to 4-17
Widget hierarchy, 4-13
Widgets, 4-13
classes and types, 4-6
defined, 4-2
hierarchy of, 4-14
naming conventions, 4-6
related components, 4-6
related widget components, 4-13
specifying names, 4-6
Widget-specific resources, 4-10
Window
definition of, 3-2
Window Manager, 2-4

Index-3

x
XII protocol, 1-6 to 1-7
.Xdefaults file
assigning resources, 4-5
creating, 4-4
definition of, 4-3
loading changes, 4-7
locating sample, 4-4
redefining keyboard mapping, 4-17
sample file, 4-4
specification examples, 4-7
Xlib, 1-6, 3-1, 3-3
Xlib extensions
for DECnet support, 3-3
for the Display PostScript system,
3-3
X Resource Database Manager (xrdb),
4-3
and .Xdefaults file, 4-3
loading changes into server, 4-7
X Server, 1-6
controlling access to, 1-7
XUI
features of, 1-3
overview of programing environment,
3-1 to 3-2
relationship with DECwindows, 1-2
XUI (X User Interface)
features of, 1-2 to 1-3
XUI Architecture, 1-5
components of, 1-5
device drivers, 1-8
extending, 1-8
illustration of, 1-5
optional libraries, 1-8
server, 1-7
XII protocol, 1-6
Xlib, 1-6
XUI Toolkit, 1-5
X Window System, 1-5
XUI Features
and DECwindows, 1-2
XUI Intrinsics, 3-4

Index-4

XUI Resource Manager (DRM)
definition of, 3-6
XUI Toolkit, 1-5,3-1,3-3
widgets, 4-15
XUI Toolkit routines
compound string, 3-5
convenience, 3-5
cut and paste, 3-5
high-level, 3-4
low-level, 3-4
summary of, 3-4
using, 3-3
XUI User Interface Language Compiler
See UIL
X Window System, 1-5

How to Order Additional Documentation

Technical Support
If you need help deciding which documentation best meets your needs, call 800-343-4040
before placing your electronic, telephone, or direct mail order.

Electronic Orders
To place an order at the Electronic Store, dial 800-234-1998 using a 1200- or 2400-baud
modem from anywhere in the USA, Canada, or Puerto Rico. If you need assistance using the
Electronic Store, call 800-DIGITAL (800-344-4825).

Telephone and Direct Mail Orders
Your Location

Call

Contact

Continental USA,
Alaska, or Hawaii

800-DIGITAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

Puerto Rico

809-754-7575

Local Digital Subsidiary

Canada

800-267-6215

Digital Equipment of Canada
Attn: DECdirect Operations KA02/2
P.O. Box 13000
100 Herzberg Road
Kanata, Ontario, Canada K2K 2A6

International
Internal *

Local Digital subsidiary or
approved distributor
SSB Order Processing - WMO/E15

or
Software Supply Business
Digital Equipment Corporation
Westminster, Massachusetts 01473

* For internal orders, you must submit an Internal Software Order Form (EN-01740-07).

Reader's Comments

ULTRIX WORKSYSTEM SOFTWARE
Introduction to the ULTRIX
Worksystem Software Environment
AA-MA86D-TE

Please use this postage-paid fonn to comment on this manual. If you require a written reply
to a software problem and are eligible to receive one under Software Perfonnance Report
(SPR) service, submit your comments on an SPR fonn.
Thank you for your assistance.

Please rate this manual:

Excellent

Accuracy (software works as manual says)
Completeness (enough infonnation)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find infonnation)

o
o
o
o

Good

o
o

o
o
o

o
o

Fair

o
o
o

o
o
o
o
o

Poor

o
o
o

o
o

What would you like to see more/less of!
What do you like best about this manual?
What do you like least about this manual?

Please list errors you have found in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

What version of the software described by this manual are you using? _ _ _ _ __
Namerritle _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Dept.
Company _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Date _ _ _ __
Mailing Address
_ _ _ _ _ _ _ _ _ _ Email _ _ _ _ _ _ _ _ _ Phone __________

I
1

- - Do Not Tear - Fold Here and Tape • - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - __ I

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 33 MAYNARD MA
POSTAGE WILL BE PAID BY ADDRESSEE
DIGITAL EQUIPMENT CORPORATION
OPEN SOFlWARE PUBLICATIONS MANAGER
ZK03-2/Z04
110 SPIT BROOK ROAD
NASHUA NH 03062-9987

11111111 1111111 II IIlIlIh II 1IIIIIIIIIIIhllilidill 1
-

Do Not Tear - Fold Here

Cut
Along
Dotted
Line