Preface

This manual describes the XView^(TM) toolkit code generator (GXV) for the OpenWindows^(TM) Developer's Guide (Devguide). Use this manual to help you generate code for the user interface you build with Devguide. The Programmer's Guide includes a tutorial to introduce you to many of Devguide's features, and shows you how to modify GXV-generated files to customize the tutorial application.

Who Should Use This Book

This manual is written for applications programmers who want to generate XView toolkit code from Guide Interface Language (GIL) files. You should be familiar with your workstation's operating system, the OPEN LOOK^(R) User Interface, Devguide, and the C programming language. To use some of the more advanced features described in this manual, you should also understand the fundamentals of creating user interfaces with the XView toolkit.

SPARC and x86 Differences

Depending on what kind of system you have (SPARC or x86), you may have a different kind of mouse and a different type of keyboard, and devices may be named differently; the differences are described below.

Two- or Three-Button Mouse

Your system may have a two- or three-button mouse. On either type of mouse, the left mouse button is referred to as SELECT and the right mouse button as MENU in this manual. To perform a SELECT function, click the left button; to perform a MENU function, click or press the right button.

On a three-button mouse, the middle button is referred to as ADJUST. To perform an ADJUST function on a two-button mouse, hold down the Shift key and click SELECT (the left button).

Keyboard Alternatives for the Meta and Other Special Keys

Some keyboards do not include the Meta key, the function keys L1 - L10, or a Help key; keyboard alternatives are available for the Meta and Help keys and most of the function keys.

Alternative to the Meta Key

On keyboards without the Meta key (marked as a diamond on most SPARC keyboards), the Alt key is mapped to the Meta key. If you have installed Devguide on an x86 system, use the key labeled "Alt" whenever the Meta key is prescribed.

Note - Functions which require the Alt key itself will not work on systems with keyboards that do not include a Meta key.

Alternatives to Function Keys

On keyboards without the L1 to L10 function keys, Meta-key equivalents are available for most of the functions, as shown below. Use the key labeled "Alt" instead of the Meta key on keyboards without the Meta key. The alternatives are:

Cut	Meta-x
Copy	Meta-c
Paste	Meta-v
Find	Meta-f

Props	Meta-i
Undo	Meta-z
Open	Meta-w

There are no keyboard alternatives for the Front and Again keys.

Alternative to the Help Key

On keyboards without a "Help" key, use the key marked "F1" for help.

Before You Read This Book

Before you read this manual, you should read the following documents:

Software Developer Kit Installation Guide (which includes instructions for installing Devguide)
OpenWindows Developer's Guide: User's Guide, including especially Appendix D, "Devguide 3.0.1 Release Notes," which contains the latest information about changes to and problems with Devguide and GXV

You may also want to consult the following documents before going further:

Solaris Roadmap
Solaris 2.4 Introduction

How This Book Is Organized

The following is a brief description of each chapter and appendix of this manual.

Chapter 1, "Introduction," provides an overview of GXV.

Chapter 2, "Getting Started with GXV," gets you acquainted with how GXV works. It shows you how to generate code and how to compile this code with your application code. It provides a very simple example.

Chapter 3, "GXV Tutorial," describes how to use Devguide and GXV to build a complete OpenWindows application.

Chapter 4, "GXV Functionality in Detail," contains information on generating GXV code, describes GXV's libraries, and provides some programming tips.

Appendix A, "Files Provided with GXV," lists the directory structure and the files on the GXV distribution medium.

Appendix B, "Internationalization," provides information on internationalizing and localizing applications using Devguide and GXV.

Related Books

For background information on knowledge assumed by this manual, consult:

Solaris 2.4 Introduction, Solaris 2.4 System Administrator AnswerBook, and the Solaris Advanced User's Guide for information about the UNIX^(R) and SunOS operating systems
The OpenWindows Reference Manual for information on working in the OpenWindows environment
The OPEN LOOK Graphical User Interface Application Style Guidelines by Sun Microsystems, Inc. (published by Addison Wesley, Inc.), for information about the elements that constitute user interfaces in the OpenWindows environment and the rules and suggestions for creating OPEN LOOK^(R) user interfaces
The C Programming Language by Kernighan and Ritchie (or other reputable C books) for the rules of programming in C
AT&T C++ Reference Manual by Margaret A. Ellis and Bjarne Stroustrup (ISBN 0-201-51459-1)
The C++ Programming Language by Bjarne Stroustrup (published by Addison Wesley, Inc., ISBN 0-201-12078-X)
XView Programming Manual, XLib Reference Manual, XLib Programming Manual, and X Protocol Reference Manual (published by O'Reilly and Associates, Inc.) for information about programming using the OpenWindows XView toolkit

What Typographic Changes and Symbols Mean

The following table describes the type changes and symbols used in this book.

Table P-1

Typeface or Symbol	Meaning	Examples
`Courier`	The names of commands, files, and directories; on-screen computer output	Edit your `.login` file. Use `ls -a` to list all files. .
`Courier` `Bold`	What you type, contrasted with on-screen computer output	% su password:
*Palatino Italic*	Command-line placeholder: replace with a real name or value	To delete a file, type the following: `rm` *filename*`.`
	Book titles, new words or terms, or words to be emphasized	Read Chapter 6 in *User's Guide`.` These are called class* options. You *must* be root to do this.
Code samples are included in boxes and may display the following:
%	UNIX C shell prompt	% or system%
$	UNIX Bourne shell prompt	$ or system$
#	Superuser prompt, either shell	# or system#