| >> Is the internal format of FileView's startup files (.VUE$DAT)
>> documented somewhere ?
No. (Actually, yes, but only in the code.) The only supported way to
create or change a VUE$DAT file is through the FileView "Customize" dialog
boxes.
The file is an indexed RMS file, where the key contains a record
type and a name. The record types are things like:
SavedView, SavedMenu, SavedVerb, SavedFileType, SavedName,
SavedState, and SavedSymbol.
Each time that you add a verb, menu, or filetype, a new record is
added to the file. Each time that you save a view, a record is
added. Each time that you use a verb dialog box (like Copy or Search, for
example) a SavedState record is written with the settings in that
dialog box. SavedSymbol and SavedName records can be accessed through
VUE .COM file callbacks.
User munging of this file is not supported. If you have a need, let me know
what it is and we might be able to work something out.
Since we do not guarantee upward compatibility of this file (only that we
will be able to read old files and convert them to the "current" format),
documenting it publicly would likely cause problems. Or are we being
too cautious?
-steve-
|
| Hi Steve,
we intend to use DECwindows as the Human Interface for a CASE
environment. Even for our own tools (CMS, SCA, LSE, ADA ...) we
have to write several DCL procedures to knit the tools together,
it will become quite a mess when we start integrating 3rd party
products. There will be lots of procedures, logical names, directories
etc., and we must keep track how all this works together. It's even
more complicated, different people will need different 'views',
a project manager needs another view than someone who does coding,
someone might be involved in several projects etc.......
So the problem is
o generate the VUE$DAT files
o check their contents
o track and understand dependencies
If we could interpret the contents of the VUE$DAT files we had a
solution for points 2 & 3, and we could write a Mickey Mouse program
(even a DCL procedure might do the job ...) to generate the files
for a new project & to modify them more quickly.
Another point of view: when it comes to installing a certain flavour
of an integrated CASE environment at a customer's site we would
like to do as much as possible of that job in an automatic way,
with a command procedure or so. It should be possible to generate
the VUE$DAT files from a command procedure.
Thanks for any help Ruediger Schuetz
SWAS Munich
|