Click on FTP to download from the FTP archives.
![[FTP]](http://www2.encompassus.org/hidedecus/graphics/i_ftp.gif)
NOTE: The following has been supplied to the DECUS library
by Digital Equipment Corporation. This software has
been supplied as is, with no expressed or implied
commitment to maintain, update, or support it or
its use. By supplying this, DEC and the author(s)
of the following are not responsible for damage,
consequential or inconsequential, which may result
from its use.
*****************************************************************
Files referenced in this guide which are necessary for tailoring
the LIMSSM screen logos are:
DEC_LOGO.FRM
BLANK_LINE.FRM
DEC_LOGO.FLG
BLANK_LINE.FLG
LOGO.BAS
LOGO.OBJ
LOGO.EXE
TAILOR.COM
DEC_LOGO.DOC (this guide)
To obtain an executable from LOGO.BAS:
$ BAS LOGO
$ LINK LOGO
The LOGO utility can be used to remove the Digital logo from
the all the forms in the forms library or it can be used to
put a different logo in its place as well. It follows the
same format as the other form tailoring utilities in that it
references the forms as 'formname'.
The utility manipulates .FLG files. It requires the forms
library be in the form LIMSSM.FLG as well as two other .FLG files,
one to specify what is to be removed and one to specify what
will go in its place. The .FLG file that is used to remove the
logo is in the utility directory and is called DEC_LOGO.FLG .
Another .FLG file has been supplied to the DECUS library --
BLANK_LINE.FLG, that can be used when nothing is to be put in
place of the DEC logo.
This utility only allows replacement on the forms in the
rows and columns that had something removed from them. It
sets up replacement ranges from the .FLG file that specifies
what to remove. This will become apparent from the example
run of the utility at the end of this appendix.
**** NOTE ****
If you need to put something in place of the
logo, you should copy the the form DEC_LOGO (to
MY_LOGO.FLG) and use it as a template. Use
FMS/TRANSLATE to create a .FRM file, use FMS/EDIT
to modify the logo, then use FMS/DESC to make an .FLG
file of your replacement logo. You would then use
your .FLG file with the utility in place of BLANK_LINE.
**** NOTE ****
1. The first step is to create an .FLG file from the forms
library. This can be either the forms you have already
tailored from another tailoring session, or a set of forms you
are preparing to tailor.
Set default to a work area directory:
$ SET DEFAULT [project directory]
Copy the LIMSSM forms libraries to this work area:
$ COPY LIMSSM$LIBRARY:LIMSSM.FLB
Create the .FLG files.
$ FMS/DESCRIPTION LIMSSM.FLB
The result will be:
LIMSSM.FLG
2. The next step is to prepare the required .FLG files
needed to run the logo utility.
Get the file DEC_LOGO.FLG from the DECUS library.
This is the file you need to let the utility know
what to remove from the forms.
Get the file BLANK_LINE.FLG from the DECUS library.
This is the file you would use to put nothing in place of
the logo.
Or create MY_LOGO.FLG from DEC_LOGO.FLG as described
above if you want to modify the logo instead of remove
it, and use MY_LOGO.FLG in place of BLANK_LOGO.FLG in
the following instructions.
3. You can now run the utility. It will ask you to specify the
the two .FLG files and the name of the forms library (defaults
are shown). The utility will first parse the old logo and
new logo files to assure that no conflicts occur. The new logo
file must not attempt to replace text not described in the old
logo file. If a conflict occurs, the program stops, and no
files are created. The utility will create new .FLG files in the
form formname as the other utilities do.
It will also create a .LOG file to document what was done and
any errors that occur. Any forms flagged with an error will
show the text that interfered with the replacement. operation.
No replacement is performed on any forms where conflicts occur.
These forms will properly translate back to .FRM files but
without modifications. You can use LOGO.LOG to check the names
of the forms that caused a conflict.
$ RUN LOGO
***** SEE EXAMPLE RUN AT THE END OF APPENDIX ****
The result will be:
LOGO.LOG
ALGORITHM.FLG
ALGORITHM_HLP.FLG
APPROVE1.FLG
|
V
ETC....
4. This utility should also be run against the menu forms.
Return to step #1 using LIMS$MENU$FORMS.FLB
5. You now have the forms with the new logo (blank or otherwise).
6. The next utility converts the translated FLG files to
actual forms. Any errors encountered during this
utility indicated a problem with the translation done
in STEP 3. This usually involves a field prompt now
overrunning the edge of the screen or into a field.
If this error occurs, recheck the LOGO.LOG file and/or tailor
the form individually. This may entail abbreviation or
the moving of fields to accommodate the longer prompt.
$ @TAILOR (Choose TRANSLATE option)
The result of will be:
formname.FLG ----> formname.FRM
A log of this activity is written to a file,
TRANSLATE.LOG. The translation errors that took
place will be logged here. By examining which
forms had problems, TRANSLATE.LOG, and what was done
to them (from LOGO.LOG), You should be able to narrow
down the trouble with the form.
Work out any difficulties with the form which usually
involves abbreviations or moving of fields. Then
translate the problem form(s) using the command:
FMS/TRANS formname.FLG
NOTE: Don't forget about the menu forms...Return to the
beginning of step 6 and use LIMS$MENU$FORMS.FLB.
7. This step builds the tailored forms library.
$ @TAILOR (Choose BUILDLIB option)
The result will be:
ALGORITHM.FRM ------> LIMSSM.FLB
ALGORITHM_HLP.FRM
APPROVE1.FRM
|
V
ZPSET.FRM
If menu forms were tailored, run this against the menu
forms library also.
8. The final step in the form tailoring process is to
clean up the directory your working in. Once the forms
library is completed, there should be no further need for
files with extensions of .FRM, .FLG, .LIS. These should
be deleted to conserve disk space.
EXAMPLE OF LOGO.LOG FILE:
Note that the .LOG file specifies the ranges to be removed.
The utility does not permit you to replace anything unless
you remove it via DEC_LOGO.FLG
LOGO.LOG - created on 22-Sep-86 at 01:44 PM
%LOGO-I, Parsing old logo file
Line and Column Ranges to be DELETED:
Line Min Max
1 1 65
2 1 65
3 1 81
%LOGO-I, Parsing new logo file
%LOGO-I, Parsing Form Library
%LOGO-I, FORM NAME='ALGORITHM' written to file ALGORITHM.FLG
%LOGO-I, FORM NAME='ALGORITHM_HLP' written to file ALGORITHM_HLP.FLG
%LOGO-I, FORM NAME='APPROVE1' written to file APPROVE1.FLG
.
.
%LOGO-I, FORM NAME='KEYPAD' written to file KEYPAD.FLG
--- Line = 1 Min = 40 Max = 81 -- Conflicting old text Not Deleted ---
TEXT (1,40) 'lqqqqqqqqqwqqqqqqqqqwqqqqqqqqqwqqqqqqqqqk'
CHARACTER_SET=RULE
;
%LOGO-I, FORM NAME='LOCATION' written to file LOCATION.FLG
%LOGO-I, FORM NAME='LOCATION_HLP' written to file LOCATION_HLP.FLG
%LOGO-I, FORM NAME='LOGGER' written to file LOGGER.FLG
.
.
%LOGO-I, FORM NAME='PARAM' written to file PARAM.FLG
%LOGO-I, FORM NAME='MAPSID' written to file MAPSID.FLG
%LOGO-I, FORM NAME='MAPTEST1' written to file MAPTEST1.FLG
--- Line = 2 Min = 19 Max = 81 -- Conflicting old text Not Deleted ---
TEXT (2,19) 'MAP TEST ENTRY/EDIT Page 1 of 2'
;
%LOGO-I, FORM NAME='MAPTEST_GENERIC' written to file MAPTEST_GENERIC.FLG
--- Line = 2 Min = 19 Max = 81 -- Conflicting old text Not Deleted ---
TEXT (2,19) 'MAP TEST ENTRY/EDIT (GENERIC) Page 2 of 2'
;
%LOGO-I, FORM NAME='PARAM_HLP' written to file PARAM_HLP.FLG
%LOGO-I, FORM NAME='BLOGIN_HLP' written to file BLOGIN_HLP.FLG
%LOGO-I, FORM NAME='MAPSID_HLP1' written to file MAPSID_HLP1.FLG
%LOGO-I, FORM NAME='MAPTEST1_HLP' written to file MAPTEST1_HLP.FLG
%LOGO-I, FORM NAME='MAPTEST_AA' written to file MAPTEST_AA.FLG
%LOGO-I, FORM NAME='ARCHIVE_HLP2' written to file ARCHIVE_HLP2.FLG
%LOGO-I, Successful RUN - 184 forms written
Click on FTP to download from the FTP archives.