1. [Win32Lib] makeDoc
Derek,
I think I have gotten MakeDoc to correctly make multiple htm files with all
correct link references, but I was thinking that maybe the distribution
should be organized slightly differently, as shown below.
And I also can't figure out exactly where/how MakeDoc knows how to *find*
the Win32Lib.ew file to parse, which I would need to know if things were put
into different places as I'm suggesting. What I find in "fMain" in MakeDoc
seems to relate only to command line arguments to contain the file to parse,
which aren't used in the windows app. Version 57.0 has:
inFile = "win32lib_full.ew"
but 57.9 just has the command line "kArgs" stuff to set inFile.
SUGGESTION:
Main Win32Lib folder should maybe only have 4 files:
a. Win32Lib.ew
b. ReadMe.txt
c. RunDemos.exw
d. Win32LibManual.htm (would be made by MakeDoc & jump to separate files)
with the following sub-folders:
a. Docs -- all the separate doc files & changes.txt
b. Demos
c. Includes (would have all the includes presently in the main folder)
d. Utilities (or some such name; would have Eucompress & MakeDoc here)
The general idea is to have the main folder have nothing but what the
beginner needs to see & use.
Then in relation to the creation of the documentation, MakeDoc from within
"Utilities" folder would work on Win32Lib from main folder, putting all the
separate files into "Docs" and the main manual htm in the main folder.
What do you think of that idea, & how does MakeDoc *find* Win32Lib to parse?
Dan
ps. writing to the list instead of direct because I think you are still
"commuting"(!!) & can read the list easier than direct email?
