Actually, I would be interested in helping out on a class reference.
In going through the code I think it would be useful for me to do docs
as a way of solidifying my understanding of each class. We could
easily split this up if someone wants to come up with a template for a
class document. We could each choose a class when we have some time to
burn and fill in the details.
Of course, the new code would be useful, but if you could give us a
list of classes that won't change much from 0.3.1 to 0.4 then we could
start this with the current drop.
One of us should serve as the documentation librarian, just to keep us
from working on the same thing...
Matt
On Thursday, October 10, 2002, at 02:55 PM, Philippe C.D. Robert wrote:
On Dienstag, Oktober 8, 2002, at 07:30 Uhr, Brent Gulanowski wrote:
Anyway, that's a lot to digest. I'll have written a book by the time
this is done with. Actually, being 1)the newbie and 2)a trained
writer, I restate my willingness to take over any documentation
tasks. Phil, please include documentation objectives amongst those
other project objectives I mentioned last message.
It would be very useful if you could do that! What do you propose,
would you ie. be interested in writing a white paper ( and later a
users' guide or programmers' guide)?
-Phil
--
Philippe C.D. Robert
http://www.nice.ch/~phip
_______________________________________________
Gnu3dkit-dev mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/gnu3dkit-dev
_______________________________________________
Gnu3dkit-dev mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/gnu3dkit-dev