On 08.09.2008, at 08:53, Fabien Costantini wrote:
>> 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 ?
It may well be that I checked that in, but it is possibly for 1.1.5. I
do not think that we can benefit from that anymore (except maybe as an
example, but Doxygen eveolved and so did FLTK).
I did already put some Doxygen comments and a Doxyfle into the current
1.3 svn, including some text pages in .../documentation/*.dox, and all
documentation for Fl_Widget. Not perfect, but somewhat workable.
The first issue I would like to get out of the way is the decission if
Doxygen comments go:
1: all d.comments wherever the definition lives (into the header files)
2: all d.comments into the source files (implementations that exist
only in the header must be cross-referenced)
3: all d.comments wherever the implementation lives (classes, types,
enums, and inlines into the headers, functions into the source)
Next, we must unfortunately wait until I have applied the UTF8 patch,
or patching will be hell and take forever. There is a good chance that
I will have the patch applied pretty soon and merge back. That doesn't
make the library lean and perfect yet, but we can then doxygenate and
streamline the unicode at the same time.
Creating ranges of STR worked very well last time. I suggest that we
simply use a group of STRs, describing the help files that need their
contents copied over. If marked "active" and "done" correctly, we will
not have any duplicate work.
Anyone who can make a list of files in the /documentation directory
and split them into STR's?
----
http://robowerk.com/
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
