I generally feel that the docs for various language bindings like pygobject and gtk-rs are much better then the docs for C.
I really want to complain that the current status of GTK is just “black art” with many parts lacking documentation. The many parts of GTK like gtkbuilder, gresources, gobject are completely confusing for newcomers, yet these are essential for GTK applications to work. The gtkbuilder’s xml format is even undocumented (not even those xml tags and attributes already supported by GTK, let alone create out-of-tree subparsers) , and glade does not even recognize the official demo’s xml definition.
I’m in the process of moving more documentation to the same model, and under the docs.gtk.org domain, to ensure that it’s easier to go through the various bits of our platform.
You’ve mentioned three things, and two of them are not part of GTK.
That is true. I’d be happy to review your contributions on how to improve the documentation for newcomers. Additionally, with the new developer documentation website, adding guides and tutorials should be easier.
Glade is not going to work for GTK4; it’s a known issue, and there are replacements currently being worked on.
FYI, the book “Scalable C” from the czmq author describes syntax very similar (in fact I believe almost identical to, except that zmq does not use GObject; zmq has a formal specification here) to those GLib and GTK. https://hintjens.gitbooks.io/scalable-c/content/index.html
Chapter 2 is about “Scalable C” syntax.
(Other topics are git, public project’s license, build systems, etc, and are not directly linked to programming GTK in C)
Sorry for misusing the word “documentation” here but I mean “tutorials”.
The new domain docs.gtk.org is indeed better than the old gnome developers website.