> Mike (or someone), can you add me to svn? If it's not done already, just fill the application form on the website, I'm sure you'll get an answer rapidly ;-)
> > Duncan, if you want, I can join the dox effort. As the doxygen dox 1.3 initiator, I'd also welcome your efforts in that field. > Maybe even fix a few simple bugs. Yes please, go for it. > > If you're still in the initial stages of working out the > dox style, I can hold off, or avoid certain parts you're > still working on. We can synchronize by email. Not sure I understand what you mean here, but I would prefer that you harmonize with existing dox style first which is no looking bad imho. Then any suggestions are welcome to improve it of course. > > I'd like to help address some long standing doc omissions, > go through the old 1.1.x "User Comments" and try to bring in > any obvious stuff from those. Sounds great to me, I guess you could get lot of inspiration from your existing cheat pages too. > 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. > > Such a document should probably describe the rational behind > whether to put dox in .H or .cxx files.. (my guess is they > should be near the implementation, ie. if a method is implemented > in the .H then dox should be there, if in the .cxx, dox go there..) We discussed that at the beginning when I started the dox doc initiative, and we indeed gave some directives though it has never been formalized yet in a dedicated readme file. But again, please feel free to write such a doc, getting inspired of the (light) existing material already discussed in the documentation todo's and readme's. Thanks for you help ! Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
