DESIGN commands


PROGRAM NAME

guise - Direct manipulation GUI design tool

DESCRIPTION

Guise is explained in detail in Chapter 4 of the Khoros Toolbox Programmer's Manual; the information given there will not be repeated here, so you are referred to that document. For reference purposes, a detailed explanation of each argument to guise is as follows:

[-i {UIS file}] OR [-tb], [-oname] and [-uis] When started without the [-i] and without the [-tb], [-oname] and [-uis] arguments, guise begins by creating an empty pane. When started with the [-i] option specifying an input UIS file, guise displays the GUI defined by that UIS file, and allows you to modify it; the output filename is taken from the input file unless otherwise specified. When started with the [-tb], [-oname], and [-uis] arguments, guise will open the specified program object in the specified toolbox, and will look for the *.pane, *.form, or *.cmd file as implied by the [-uis] option. Assuming the implied UIS file is found, guise displays the GUI defined by that UIS file, and allows you to modify it; the output filename is taken from the input file unless otherwise specified. The only difference between using the [-i] argument and the [-tb], [-oname], and [-uis] arguments is that in the former case you must know the path to the desired UIS file, while in the latter case, you must know the toolbox and program with which the UIS file is associated.

[-o {UIS file}] The [-o] argument specifies the name of the output UIS file. When the [-i] or [-tb], [-oname], and [-uis] options are used to specify an input UIS file, the output filename is taken to be the same as the input unless otherwise specified. Therefore, either the [-o] argument should be used or care should be taken to change the output filename if the input file is not to be affected by changes made using guise.

[-force] The [-force] option may be used to suppress prompting before the output file is clobbered. Alternatively, the "Force Over-Write?" logical selection on the master form of guise may be used for the same reason.

REQUIRED ARGUMENTS

none

OPTIONAL ARGUMENTS

-force
type: flag
desc: force output
-o
type: outfile
desc: output UIS file
default: new.pane

Mutually Exclusive Group; if desired, specify ONE of:

-i
type: infile
desc: initial UIS file
default: {none}
OR

ALL OF the Mutually Inclusive Group:

-tb
type: string
desc: toolbox
default: {none}
AND
-oname
type: string
desc: object name
default: {none}
AND
-uis
type: string
desc: UIS file to edit (do not include path)
default: {none}

EXAMPLES

% guise -i spectrum.form

OR
% guise -i tb envision -oname spectrum -uis form

SEE ALSO

preview(1)

RESTRICTIONS

REFERENCES

Guise is covered in Chapter 4 of the Khoros Toolbox Programmer's Manual.

COPYRIGHT

Copyright (C) 1993 - 1997, Khoral Research, Inc. ("KRI") All rights reserved.