OOF: Finite Element Analysis of Microstructures

The Text Interface

Next: Getting Help Up: Technical Notes Previous: Technical Notes Contents

The Text Interface

All of the commands in the OOF Menus can be executed from a text interface. Executing text commands is very handy if you want to automate a process, or run OOF when logged in from home over a slow telephone line. The format for the text commands is the same, whether commands are being typed interactively, are being read from a log file or command file, or being executed as macros or as arguments to the loop command.

(In principle, the Graphics Drawer functions can be executed from the text interface too, but since the user isn't expected to write scripts using those functions, they aren't documented here. ^6.1The text versions of the graphics commands appear in log files, though. They begin with graphics <x>, where <x> is a number indicating the graphics drawer to which the command applies.)

To run OOF with the text interface, start it up with the -text option. You will be presented with a prompt like this:

OOF >>

All of the Menus, Functions, and Variables in the graphical interface are available in the text interface. In general, to invoke any one of them you just type its name at the prompt. All names can be abbreviated, as long as enough of the name is provided to distinguish it from all other legal options.

The only differences between typing commands at the keyboard and executing them from a command file are that when executing a file (a) the prompt doesn't appear when command files are read, and (b) arguments to Functions must be given explicitly (see Section 6.1.3). This Section is written as if all commands are being executed interactively.

Subsections

Next: Getting Help Up: Technical Notes Previous: Technical Notes Contents

/* Send mail to the OOF Team *//* Go to the OOF Home Page */