![]() |
![]() |
![]() |
![]() |
Destination of the printed output is controlled by the user's print command, which is configurable via the Print Setup... option of the File pulldown menu.
The defined command will receive the contents of the information to print on stdin. For example, to send output to the printer queue named `eng' a user would define their print command as "lpr -Peng".
Sending e-mail to Tower Concepts via the e-mail dialog is controlled via Xdefaults settings. Refer to "E-mail back to Tower Concepts" on page 289 for details.
To change Razor's compression engine, create the script $RAZOR_UNIVERSE_DIR/Scripts/compress. The script MUST return 0 on success or 2 if the compress worked but made the file bigger. All output MUST go to stdout.
It is possible to customize the Razor help files for each separate database. To do this, perform the following steps:
As with the issues program, we generally encourage people to start with a minimalist approach. Keep the list of attributes down to only those that would be truly handy for people to filter on. For example, if your file naming convention already indicates which sub-system the file relates to then there is little need to define a similar attribute.
By and large, with the exception of STATEs, most attributes are set at the time a file is introduced into the system and seldom change after that. They then serve as convenient mechanisms for filtering the display and doing blanket inclusion/exclusion efforts with the threads program.
The assignment of attributes to files should be illustrative and useful, not simply clerical and bureaucratic.
![]() |
![]() |
![]() |
![]() |
(Part 8 of 9 for this section) (Generated 09/13/99 at 18:03:21) |
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |