I believe this kind of work could be really successful in a short period of
time if we partake the task into small work packages in the team.
I guess the idea behind this is to achieve this relatively painful & somewhat
sometimes boring task much more rapidly by dividing the number of source files
to treat in an organized, collaborative way.
A straight forward method and first increment could be:
-------------------------------------------------------
- Divide all src files into 4 or 5 small packets of files
- get volunteers for each packet
- extract the api doc. content from the current doc html files and put it into
the source guided by our CMP and latest feedback.
(I also think the existing html class member doc extraction could partially be
automated by macros or by a small tool ...)
> Membergroups are created by putting functions in order and bracketing
> them with //@{ and //@}
Matt, I think there's a private branch with doxygen content in the repository,
is it yours and if yes, is it worth (re-)starting from it or getting some stuff
out of it ?
Fabien
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
