We’ve finally moved the API documentation for gtkmm and the other C++ bindings to library.gnome.org’s C++ Reference section. These are all created with Doxygen. Using library.gnome.org means that it’s updated every time we do a tarball release and we don’t lose old versions when it’s updated. We also have both the stable (on distros) and unstable (in progress) API documentation available.
We’ve also moved the gtkmm book, libsigc++ manual, and libxml++ tutorial to the Guides section. These all use DocBook XML.
library.gnome.org is a wonderful system, giving developers what they need, thanks to Frederic Peters’ hard work and responsiveness. I like it so much that Openismus might soon offer to set up library instances for other projects or companies.
Moving the API documentation to library.gnome.org made it obvious that we needed proper introductory text for each module. So each one now lists:
For instance, see the glibmm API reference’s main page. I regularly complain that non-GNOME libraries don’t provide clues about what include or linker flags should be used, or how to include them, let alone API documentation, causing application builds to be inconsistent and fragile. It’s the least that should be done, so it’s good that I can now point to something consistent.
There are some small problems still to work out:
Very good news. Other step on the objective of convert our platform
bindings in first class citizens.
Also, just curious. Can doxygen be used by other C GNOME libraries? All the projects I know use gtk-doc.
> Can doxygen be used by other C GNOME libraries? All the projects I know use gtk-doc.
Not really. I guess someone could write a doxygen backend that understood the GObject system, but I don’t think anybody has. gtk-doc is fine for C GNOME libraries.
Hi Murray,
I made a basic main page for gtkglextmm. Please apply the patch.
https://bugzilla.gnome.org/show_bug.cgi?id=620659
Thanks, but I am not the gtkglextmm maintainer. I thought you were.