home *** CD-ROM | disk | FTP | other *** search
- @video
- @macro A," "
- @macro B," "
- @macro C," "
- @MACRO D,"@COL CHAR'
- @macro e,"@outline cyan"
- @nf MAIN_MENU
- @bbimenu white,red
- @bright
- @win line0,column0,depth1,width80
- {Menus }{Forms }{Applications }{Examples }{Portability }{Save and Restore }
- @end
- @nf FO
- @bbimenu cyan,blue
- @win line1,column0,depth1,width80
- {Types of field }{Validation }{Function keys }{Overlays }{Insertion variables }
- @end
- @nf FO-
- $D$,yellow,blue
- @win line4,column10,depth7,width60
- $E$
- FORMS-GENERAL
- Forms are used to solicit information from the user. They
- consist of text and 'fields'. Users may only type into
- fields. There are many types of field each defining a
- type of data. Forms provide a totally consistent method
- of data entry (with an editing capability).
- @end
-
- @nf FOT
- $D$,white,red
- @win line18,column1,depth6,width60
- $E$
- FORMS-TYPES-OF-FIELD
- Many types of data capture "Fields" are provided which
- include:$B$$A$
- DATE (US or UK), TIME (HH:MM), FILENAME (d:ffffffff.ttt),
- PATH, NUMBER (with MIN and MAX), STRING, LOGICAL (YyNn).
- @end
- @nf FOV
- $D$,white,blue
- @win line12,column15,depth7,width61
- $E$
- FORMS-VALIDATION
- When a form is displayed containing one or more data
- capture fields, the user is prompted to complete it by
- filling in the fields. All validation is automatic. The
- task will not resume execution until valid data is entered.
- The task writer may allow him to QUIT or leave fields blank
- @end
- @nf FOF
- $D$,blue,cyan
- @win line5,column5,depth6,width60
- @out blue
- FORMS-FUNCTION-KEYS
- As an alternative to completing the form by entering
- valid data the user may (if allowed by the task writer)
- press one of the function keys. The task is informed of
- this and may take appropriate action.
- @end
- @nf FOO
- $D$,black,cyan
- @DIM
- @win line15,column20,depth7,width60
- $E$
- FORMS-OVERLAYS
- Taskmaster screens may be overlayed. There are 2 types:
- OVERLAYS and WINDOWS. Windows allow specific placement of
- overlayed information. Using OVERLAY the text is placed
- exactly as per its placement in the form. This is a
- WINDOW at line15,column 20, depth 7 and width 60.
- @bri
- @end
- @nf FOI
- $D$,BLACK,GREEN
- @DIM
- @win line9,column2,depth7,width60
- $E$
- FORMS-INSERTION-VARIABLES
- If required,the text of a form may be changed at run-time.
- This is very powerful as the position of inserted text may
- be changed by simply editing the form source. The
- task writer doesn't have to know the precise LINE and
- COLUMN numbers at which to place the text. Time is {hh:mm}
- @end
- @nf PO
- @bbimenu cyan,blue
- @win line1,column0,depth1,width80
- {CDOS }{MS-DOS }{Unix }{Xenix }
- @end
- @nf PO-
- @win line4,column10,depth4,width60
- $E$
- PORTABILITY-GENERAL
- Users who have a mixture of machines particularly value
- the consistency offered by Taskmaster.
- @end
- @nf POC
- @win line4,column10,depth4,width60
- $E$
- PORTABILITY-CDOS
- Taskmaster is also available for CDOS, there is a CDOS
- specific version supporting Multi-User operation.
- @end
- @nf POM
- @win line8,column10,depth4,width60
- $E$
- PORTABILITY-MS-DOS
- The MS-DOS version will run on any DOS machine from DOS
- 2.0 onwards.
- @end
- @nf POU
- @win line12,column10,depth5,width60
- $E$
- PORTABILITY-UNIX
- FmP have a Unix version of Taskmaster. Unlike the MS-DOS
- version which is written in assembler, the Unix version is
- written in C making it highly portable.
- @end
- @nf POX
- @win line17,column10,depth4,width60
- $E$
- PORTABILITY-XENIX
- The Xenix version of Taskmaster is developed in the C
- language under SCO Xenix. It is standards compliant.
- @end
- @nf ME
- @bbimenu cyan,blue
- @win line1,column0,depth1,width80
- {Conventional }{Bounce-Bar }{Search }{Function keys }{Arrows }{Home }
- @end
- @nf ME-
- $D$,yellow,blue
- @win line4,column0,depth6,width60
- $E$
- MENUS-GENERAL
- Menus provide the basic 'multiple choice' mechanism within
- Taskmaster. Taskmaster imposes no restrictions on the
- task writer as to their appearance, which is in marked
- contrast with most menu products.
- @end
- @nf MEC
- $D$,blue,yellow
- @win line6,column4,depth6,width60
- $E$
- MENUS-CONVENTIONAL
- A conventional menu has a list of topics each identified
- by a number and a field to receive the users selection
- number. If required CONVENTIONAL and BOUNCE-BAR menus may
- be mixed in any Task.
- @end
- @nf MEB
- $D$,CYAN,BLUE
- @win line8,column8,depth4,width60
- $E$
- MENUS-BOUNCE-BAR
- All the menus in this task are of the Bounce-Bar type.
- Conventional menus are also fully supported.
- @end
- @nf MES
- $D$,WHITE,RED
- @win line10,column12,depth7,width60
- $E$
- MENUS-SEARCH-CAPABILITY
- All bounce-bar menus have a first character search
- capability. This means that you may simply press the
- first character of a menu topic to cause that topic to be
- highlighted. Duplicated first characters are
- automatically handled.
- @end
- @nf MEF
- $D$,black,cyan
- @DIM
- @win line12,column16,depth5,width60
- @out black
- MENUS-FUNCTION-KEYS
- All FUNCTION keys may be individually enabled or disabled.
- Each menu may have a different "Function key mask". This
- is controlled via the BBMASK system variable.
- @bri
- @end
- @nf MEA
- $D$,GREEN,BLACK
- @win line14,column19,depth6,width60
- $E$
- MENUS-ARROW-KEYS
- The arrow keys may be used to select the NEXT or PREVIOUS
- topic. If required the LEFT and RIGHT keys may be
- programmed to have a special meaning (used to drop down an
- adjacent menu).
- @end
- @nf MEH
- $D$,BLUE,CYAN
- @win line16,column22,depth4,width51
- @out black
- MENUS-HOME-KEY
- The HOME key simply highlights the first topic of
- the current bounce-bar menu.
- @end
- @nf AP
- @bbimenu cyan,blue
- @win line1,column0,depth1,width80
- {Loading }{Parameters }{Data }{Strategy }{Breakin }
- @end
- @nf AP-
- $D$,WHITE,RED
- @win line4,column10,depth5,width60
- $E$
- APPLICATIONS-GENERAL
- Taskmaster is capable of 'Launching' any application that
- is normally invoked from the command line or a batch/shell
- script file.
- @end
- @nf APL
- $D$,white,BLUE
- @win line8,column10,depth7,width60
- $E$
- APPLICATIONS-LOADING
- There are 2 commands in Taskmaster used to load programs.
- The RUN command loads an application beneath the
- Taskmaster (which stays resident). The LARGE command can
- load programs that require the maximum RAM possible,
- Taskmaster shrinks to ~2k to allow this.
- @end
- @nf APP
- $D$,white,MAGENTA
- @win line14,column10,depth4,width60
- $E$
- APPLICATIONS-PARAMETERS
- Fixed (literal) or variable command line parameters can be
- given as parameters to the run command.
- @end
- @nf APS
- @win line17,column10,depth6,width60
- $E$
- APPLICATIONS-STRATEGY
- The STRATEGY command allows the task to dictate to MS-DOS
- what strategy to use for RAM allocation for the program
- next loaded. This maps on to the facilities found in the
- operating system (best fit, first fit etc).
- @end
- @nf APD
- $D$,WHITE,RED
- @win line4,column10,depth5,width60
- $E$
- APPLICATIONS-DATA
- Run-time data can be passed to applications after they
- have been loaded. There is a BEHAVE command used to
- dictate the method to be used to accomplish this.
- @end
- @nf APB
- $D$,cyan,blue
- @win line4,column10,depth3,width60
- $E$
- APPLICATIONS-BREAKIN
- Taskmaster can disallow the use of CTRL/C and CTRL/break
- @end
-
- @nf EX
- @bbimenu cyan,blue
- @win line1,column0,depth1,width80
- {WORDPROC }{NATO }{TMDEV }{MENUONE }{SMART }{HOTEMENU }{CONFIG/STANDARD}
- @end
- @nf EX-
- $D$,yellow,BLUE
- @win line4,column10,depth10,width42
- $E$
- EXAMPLES-GENERAL
- The Taskmaster manual describes a
- growing set of example tasks, many of
- which are single-sourced (that is they
- run unchanged under various operating
- systems). Though no suite of examples
- can accurately mirror all uses to which
- customers may put the product they do
- provide an insight into what can be done
- @end
- @nf EXW
- $D$,cyan,blue
- @win line4,column10,depth10,width33
- $E$
- EXAMPLES-WORDPROC
- The WORDPROC task is a useful
- real working example program.
- It remembers details of upto 10
- files with descriptions, and
- dates and times of edits. It
- could be easily modified to
- handle spreadsheets or graphic
- images etc.
- @end
- @nf EXN
- $D$,white,MAGENTA
- @win line15,column50,depth9,width27
- $E$
- EXAMPLES-NATO
- This task implements the
- NATO PHONETIC ALPHABET.
- It is an example of the
- use of the LOCATE and
- CURSOR commands and
- also shows the use of a
- table of variables.
- @end
- @nf EXT
- $D$,GREEN,BLACK
- @win line4,column0,depth8,width37
- $E$
- EXAMPLES-TMDEV
- TMDEV is intended for Taskmaster
- application developers. It
- remembers the name of the current
- application being developed and
- provides an EDIT, INTERPRET, CREATE
- FORMS harness.
- @end
- @nf EXM
- $D$,BLACK,GREEN
- @DIM
- @win line10,column47,depth7,width32
- $E$
- EXAMPLES-MENUONE
- MENUONE is a simple menu where
- the application names may be
- changed at run time and are
- stored in a disc file for
- subsequent re-use.
- @bri
- @end
- @nf EXS
- $D$,yellow,red
- @win line16,column20,depth6,width60
- $E$
- EXAMPLES-SMART
- SMART shows how to implement in a single task what has
- been taken to a logical conclusion by CONFIG and STANDARD.
- It is a logical extension of MENUONE, the other
- enhancements concern interfacing with the EUC catalogue.
- @end
- @nf EXH
- $D$,black,yellow
- @DIM
- @win line7,column2,depth9,width42
- $E$
- EXAMPLES-HOTEMENU
- HOTEMENU is just for fun. It does
- however show how to implement menus
- using the PUT command. Notice that the
- task remembers the text of the selection
- as well as the topic number and that
- topic numbers are used to highlight the
- correct topic on re-entry.
- @bri
- @end
- @nf EXC
- $D$,cyan,blue
- @win line15,column15,depth7,width60
- $E$
- EXAMPLES-CONFIG-AND-STANDARD
- CONFIG and STANDARD are complementary to one another. The
- CONFIG task allows a system administrator to set up
- application details which are stored for use by STANDARD.
- Together they provide a quick and easy (interactive) way
- of customising your PC.
- @end
- @nf SA
- @bbimenu cyan,blue
- @win line1,column0,depth1,width80
- {SAVE command }{RESTORE command }{Audit Trail }
- @end
- @nf SA-
- $D$,cyan,BLUE
- @win line4,column0,depth7,width32
- $E$
- SAVE-AND-RESTORE-GENERAL
- The SAVE and RESTORE commands
- add an extra dimension to
- Taskmaster. They set it apart
- from the crowd and make it an
- order of magnitude more useful
- @end
- @nf SAS
- $D$,black,yellow
- @DIM
- @win line4,column32,depth7,width48
- $E$
- SAVE-AND-RESTORE-SAVE-COMMAND
- The SAVE command allows any variable data such
- as filenames, the time and date, last menu
- selection, error response, etc etc to be
- stored in a nominated file for subsequent
- restoration.
- @bri
- @end
- @nf SAR
- $D$,blue,cyan
- @dim
- @win line11,column0,depth7,width52
- $E$
- SAVE-AND-RESTORE-RESTORE-COMMAND
- The RESTORE command is complementary to the SAVE
- command. It allows any variable data previously
- saved (usually in a previous run of the same task
- but could be another task altogether) to be
- restored into user datatypes.
- @bri
- @end
- @nf SAA
- $D$,cyan,blue
- @win line11,column52,depth9,width28
- $E$
- SAVE-AND-RESTORE-AUDIT
- The save and restore
- commands can easily be
- employed to implement an
- audit trail, where details
- of runs and actions
- performed may be saved for
- later restoration
- @end
- @nf HELP
- $D$,WHITE,RED
- @win line4,column10,depth7,width60
- $E$
- HELP-GENERAL
- Press <esc> to quit any menu. If you are on the main menu
- you will leave Taskmaster. You may use the <space bar>
- and press <return> to make selections. Alternatively
- press the first character of a topic, or the arrow keys to
- highlight required topic and press <return>
- @end
- @EOF
-