Re: Euphoria 4.0 docs
- Posted by DanM Aug 10, 2010
- 1380 views
<snip>
Dan, I have previously tried a few variations using your ideas. I did this by writing a few utilities that would rewrite the html before the docs got converted to pdf. The result was that creating documentation became very convoluted. Probably mostly due to my lack of programming skills, and partially due to htmldoc not letting me think in terms of desktop publishing. I admit that I got lazy when I put the last pdf up at RapidEuphoria, using just default settings for everything.
--
I just melted down my computer--beware of Foxconn. When I win the lottery I will get a new computer. This is to say sorry in advance for the slow progress in improving the documentation.
--
"I have no words"
This goes nicely with (automatically) easy, which is a symptom of my reaction to a dead computer. My math professor would torture us with "it's intuitively obvious."
I remember working a little bit, quite a while ago, for some reason, on a MUCH earlier version of makedoc, so I have a vague, fuzzy sense of how *it* worked; so I'd wonder, since eudoc similarly extracts the text from the source code, couldn't you "just" hold the major "chapter" headings, and their next level items, as they're extracted, and then use that data to create an alternate page based on those, with a link to it from the main page?
Dan
