I could probably contribute in this way some.
By the way, do you mean "documentation" in the /* explaining what the code nearby does */ sense or the "what an end-user should read" sense? I think I could help much more on the latter than the former....
If anyone is up for the former, it would be helpful also, for the viewer, to get developers oriented with the code.
One option would be to use doxygen for the source documentation, so that some nice browsable documentation could be generated for working with the code.
The Plucker Desktop source is documented with doxygen which is helpful to know how things fit together. The output can be browsed at:
http://desktop.plkr.org/docs/developer/hierarchy.html
_______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
