Yes. This is what I'd do in Wiki. After all the Wikipeida does much more
content that we'd do in 1000 lives, yet still all is done in Wiki
(amazing, isn't it?).
I found in my hard drive old circa 2002 aolserver docs, including C-
API,
Tcl-API and other overviews. Not bad documentation and still
apllies to
naviserver as well. It is html already, converting it to doctool does
not make sense but not using it does not make sense for me either. And
correting these old docs is not that hard, the question is: where
we put
it? CVS? SF mane page? Wiki?
Wiki.
But how we can put existing docs into Wiki, i guess starting from the
scratch is very frightening(at least for me)
For the problem where do i start: man pages or Wiki or another
document,
too many different ways and still it will be kept in pieces in
different
places.
Both :-)
We (I'm afraid to say I) can start ref-doc immediately and
never finish (i.e. we just add content as we *can*).
The "bad" thing about the other (Wiki) is: it just takes
lots of time! I personaly can add to the ref docs by
filling in the man pages but I can't write top-level
overview type of docs. I just have no time for that.
Yes, SF Wiki site is so slow, almost unusable, not even for developer
but for regular users as well
So, to do:
1) Making templates for all Tcl commands, i.e. creating .man files
2) Converting existing .n pages into .man files
3) Importing/collecting all existing docs about AS and NS
4) Create top level structure and put all docs there or links
.
. ... slowly adding stuff ...
.
Concerns:
1) SF Wiki, this is my big concern, slow, no way to easily correct, need
to login, how to download original source to keep in CVS for example
2) I would like to generate Wiki from source files, from doctools, if we
have all command as .man files, we can easily generate Wiki page similar
to AS wiki on panoptic.com (BTW, this is good source of docs as well)
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
