Rudolf Potucek wrote:
>I could, if there is enough interest (i.e. anough ANSWERS), set up
>something like what php.net has: the API docs with user comments for each
>page (a little database back end, php interface for searching and
>posting). And maybe that sort of thing could ultimately be hosted at the
I looked at what they have there and it's not a bad idea. The only thing I saw that I didn't like was that you had to wade through questions and comments about questions (not answers) to find information.
I think a good balence would be to have a similar system as php.net but have it to post information ONLY. No questions or requests, we can still use the mailing list for that.
The original programmer would post the internal documentation when the code is summitted to CVS. If any additional questions are raised later the answers could be posted to the internal documentation, preferably by the one who raised the question. Also when changes are made to the code, the new information about the code would be posted by the author to the internal documenation.
>Could ... but maybe just posting that info to the mailing list would be
>better. After all there is an archive of that list and the point of
>documantation is EASY access. I don't want to read the whole xx megabayte
>of documentation. I just want to start DOING.
The problem with posting just to the mailing list is that it can be more dificult to get the info you want. If you go to look in the archives, it can take ALOT of time to sort through all of the information that has been posted.
Also, if you post a question about what you are currently working on, there is a chance (in the case of wanting class information) that the programmer will not remember exactly why it was implimented that way. Also, it takes away from the programmer's current task to rehash was was done months ago.
BTW, you can find some class information by looking at the CVS repository.
>Yes ... it would be nice if there were a short commentary about the
>develoment etiquette, who's doing what, how to contribute, what not to
>touch etc. I assume if I hang around long enough I may find out just by
>assimilation ... but I might not have the perseverance!
You can find some coding and development etiquette in the docs. But as far as knowing who is doing what, I'm not sure how this works out either.
Richard D Shank
Make A Buck Or Two @ TheMail.com - Free Internet Email
Sign-up today at http://www.themail.com/ref.htm?ref=898251