Greg Ercolano wrote: > Greg Ercolano wrote: >>>> I'd also be happy to start or assist in the creation of an >>>> FLTK doxygen "standards" page that describes how docs should >>>> appear, so that new docs follow a certain format. >> Great; I'll see if I can give it a start. > > BTW, looks like there's already a bit mentioned in the FLTK > coding standards already.. "Source File Documentation" in: > http://www.fltk.org/cmp.php#CODING_STANDARDS > > We obviously want to flesh out from there, but it's a good start.
I've always wanted to try out 'google docs' as a way to publicly manage text documents. For info, see: http://docs.google.com/ As a start, I've created a new doc, copying in the doxygen part of the FLTK coding standards, and will add some stuff from this thread, as well as some other notes from the last few days. The google docs editor looks a lot like Word, and has all the usual bold/font changing stuff, and can publish as HTML, PDF, etc. It has a revision tracker too. If nothing else, it'll be fun to see if it works. Later when it's 'done', we can merge the result back into the FLTK coding standards, or as a developer article, or whatever. I just need your "Google Account" name so I can add you as collaborators, so that we can all participate in editing it. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
