|
|
Application level definition files define attributes of the application as a whole. There are three optional application level files. The initialization file and the commands file allow you to customize the appearance and functionality of your entire application; the alias file allows you to streamline references to source files in your code. The following sections briefly describe these three types of application level definition files. Detailed explanations of how to write them can be found in ``Application level definition files''.
An initialization file defines attributes of the application as a whole. You can define an introductory frame (such as a copyright notice), changes to the default banner line, the colors of various elements of the FMLI screen, whether users will be able to access the UNIX system directly from your application, and the names of and commands assigned to screen-labeled keys, among other things.
A commands file allows you to define new commands for users of your application, and redefine or disable existing FMLI commands. The new commands can be executed from the FMLI command line or the FMLI Command Menu, as described in the next section.
An alias file contains lines of the form alias=pathname. An alias can be assigned a single path to a file or device, or it can be assigned a series of paths to be searched (similar to the way $PATH is searched in the UNIX shell). Using aliases will make the code in your other definition files more readable.