On Thu, Dec 15, 2011 at 10:32:20AM +0100, Stefan Weil wrote: > Am 15.12.2011 06:22, schrieb Andreas Färber: > >Their website has the following: > > > >"GTK-Doc wasn't originally intended to be a general-purpose > >documentation tool, so it can be a bit awkward to setup and use. For a > >more polished general-purpose documentation tool you may want to look at > >Doxygen. However GTK-Doc has some special code to document the signals > >and properties of GTK+ widgets and GObject classes which other tools may > >not have." > >http://www.gtk.org/gtk-doc/ > > > >Don't know if Doxygen has less restrictions though. > > > >Andreas > > With doxygen, the documentation looks like this: > http://qemu.weilnetz.de/doxygen/
I don't know about others, but I find Doxygen output really unpleasant to read & navigate. I really despair whenever I find an API I need to learn that uses Doxygen. The output of GTK-DOC by comparison is so much more pleasant to consume. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|