I'm not an expert on the internals of fltk, but I would quite like to contribute to 1.3 by having a go at the initial doxygenation of the source code.
I started to look at this before the summer, before things became a little unclear with the possible change of direction from 1.3 to the common library idea. I'm no doxygen expert, but I found that trying to group methods as they are in the current documentation was not as easy as it looked. That's why I'm only volunteering to do the initial doxygenation for the class reference pages. Does anyone have any tips/guidelines apart from the Coding Standards in the Configuration Management Plan document? Cheers Duncan _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
