Revision 7.10
2/28/2012
Each action is coded as an <action> element nested within the <transition>
element. The <action> element has two attributes labelled “type” and
“command”. For glider actions, the type is “glider”. For Dock Server actions, the
type is “dockserver”.
For glider type actions, the command attribute must be a GliderDOS or PicoDOS
command, or the “dockzr” command (refer to section 4.2).
For example, the action associated with <initialState>’s only transition sends the
glider command “s *.sbd” to the glider when the character sequence “Hit Control
R to RESUME” is detected in the glider’s output.
Command line parameters can appear in the command attribute of the <action>
element. The user enters command line arguments via Glider Terminal's Add
Script Dialog. Dock Server substitutes these arguments for parameters found in
the script at the time the script is added to the glider's script queue. Parameters
are specified using the $n or ${n} syntax where n is the position of the
corresponding argument on the command line.
For example, suppose the user adds a script, filesToDock.xml, to the queue and
enters the following command line arguments.
*.sbd *.tbd
Suppose filesToDock.xml contains the following <action> element.
<action type=”glider” command=”s $0 ${1}” />
When Dock Server adds this script to the queue, it replaces $0 with *.sbd and
${1} with *.tbd to produce the following <action> element.
<action type=”glider” command=”s *.sbd *.tbd” />
For Dock Server type actions, the only implemented command attribute is
“gliderConsoleOutInsert”. This command inserts the text located in the body of
the <action> element into the glider console output stream. Thus, the inserted
Page 199 of 228
