
SCRIPT VS. COMMAND LINE
     The typical xtpanel script contains lines of the form:

     objecttype={ parameter1=value1 parameter2=value2 ... }

     This format is very flexible; the parameters can be supplied
     in any order, or omitted and defaults will be provided. Line
     breaks can occur anywhere.

     From the command line, all objects and all their  parameters
     must be specified on the same line in a precise order:

     -objecttype value1 value2 value3... -objecttype value1 ...


     Some parameters can be omitted; the "-" on the beginning  of
     the next object tells xtpanel to stop reading parameters for
     one object and begin the next. However, in order to  specify
     a  particular  parameter, all those up to it in the sequence
     must be specified. (For instance,  in  the  case  above,  to
     specify  value3  for the first object, one must also specify
     value1 and value2, while in a script they could  be  omitted
     and left to default.)

     For these reasons,  and  because  the  command  line  format
     (where  the  entire  panel is specified on a single line) is
     more difficult to read, it is recommended that a script file
     be  used  for  all  but the smallest examples. The following
     section describes the objects in greater detail, along  with
     the  script  language syntax. If you wish instead to use the
     command line interface, see the COMMAND LINE SYNTAX  section
     below.

     Note that scripts and the  command  line  interface  can  be
     mixed,  and  multiple  script files can be read using the "-
     file" option (see GENERAL COMMAND LINE OPTIONS,  below.)  So
     the following is a valid xtpanel command:
     xtpanel <script1 -file script2 -quit.

     Standard input is read after all the  command  line  options
     have  been  parsed so you cannot refer to a variable defined
     in the file on stdin in an object  defined  on  the  command
     line, but the opposite is OK (and useful).

