
preview(1)                   Khoros                    preview(1)

PREVIEW

     OVERVIEW

     This program is intended for use by someone who is familiar
     with the editing and building of graphical user interfaces
     using the Khoros user interface specification.  Preview is
     intended to aid the application programmer or the data pro-
     cessing programmer prototype a user interface.  Its func-
     tionality is rather simple: it takes a user interface
     specification (UIS) file and displays it.

     There are three basic actions that can be taken when running
     preview. They are REVISIT, EDIT and input a new file.  An
     input file can be specified at start up, as shown in the
     example below or can be read in after preview is running
     using the "live" file input widget.  Once a file has been
     selected and its pane or form has been placed on the screen,
     editing can begin.

     The file name that has been specified is "watched" to see if
     any changes are made.  If a change is determined to have
     occurred, preview automatically revisits or redisplays the
     graphical user interface.  With this in mind, a quick sum-
     mary of the possible "use" scenarios are presented.

     Method 1)
          First an input file is selected and displayed.  Then
          the EDIT action button is clicked on; this causes an
          xterm to pop up running the vi editor on the selected
          user interface file.  (NOTE: preview checks your
          environment variables for the string EDITOR to be set.
          If it is, then your editor is used; if not, then vi is
          used.)

          While you are editing the file, the displayed graphical
          user interface will be automatically redisplayed when-
          ever you write (:w) the file.  This provides a great
          deal of flexibility, as other files can be read into
          your edit session and temporary files by another name
          can be saved at any time.

     Method 2)
          In this scenario, the EDIT command with preview is not
          used.  Instead you run an editor separately.  If you
          are displaying the same file that is being edited, then
          any modification will trigger the REVISIT mechanism.

     The REVISIT action button can be used at any time to expli-
     citly cause the user interface file specified to be
     redisplayed.  This is often used when the QUIT button on the
     displayed form is clicked on (not the QUIT button on pre-
     view.

     SEE ALSO

     Chapter 2 of the Khoros Programmer's Manual, on the Khoros
     User Interface Specification, and Chapter 1 of the Khoros
     Programmer's Manual, on Writing Programs in the Khoros
     Environment.

     ghostreader(1), ghostwriter(1), composer(1)

     RESTRICTIONS

     None currently known.  It can get confusing to the user if
     more than one edit session is run concurrently.

     Copyright 1991, University of New Mexico. All rights
     reserved.

Version: 0                 Release: 1                           1

