Greg Ercolano wrote:
> Fabien writes:
>> The most important thing is to focus on correctness and completion
>> of the documentation, more than on aesthetics. As an example, I would
>> probably prefer that Greg adds first some details on Fl_Browser use
>> as he proposed, rather than correcting a grouped get/set comment ...
>
> I'm going to start on this, adding a few simple \code snippets
> to Fl_Browser.
Done; checked in mods to Fl_Browser.{cxx,H}.
Update to r6696 to get the changes.
I've put the resulting doxygen doc here:
http://seriss.com/people/erco/fltk/tmp/classFl__Browser.html
Comments welcome.
Brought all methods and funky parameter names into compliance as much
as possible, made sure the index reads nicely, strengthened docs,
added a few code examples.
Only did Fl_Browser, not the base Fl_Browser_, or any of the subclasses.
If all looks well, I'll proceed to others, and I'll merge what we've
figured out over the last few days into the evolving fltk doxygen
standards on google docs for posterity sake.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
