Talk:GTK+ By Example/Beginning

You should put in a link in the first chapter on how to get the Gtk+ API code for various platforms.

Also, it would be a good idea to establish some best-practices. What bought me here is trying to decide if I should be using one of the Glib object collections to pass multiple data in callbacks, or if I should be using a custom data structure. On the one hand, the custom data structure seems to be more in vogue, but then all of those collections were implemented for a reason, and I'm thinking one such reason was to store links to all the various data one might want to pack into the gpointer data argument in the callback. Only I've only seen two other people using it that way.

Finally, you should have both a hierarchy of the layout (at least of the widgets, if not the various libraries), and a breakdown explanation of all the libraries and their purpose and usefulness, in the intro.

Of course, as you continue to write this, I'm sure you'll find sections and even chapters make more sense when you move them around. So perhaps the intro is the wrong place, but the intro looks a little anemic, so it looks like a good place to start.

And perhaps this is just me, but it would probably be better to pick a rather large scale project -- something ambitious -- that would use most or all of the stuff the user would need, and slowly build piece by piece, compile, run, explain, explore, discuss and then continue by adding the next piece. When I tried to learn to play guitar, I spent years learning the scales before I finally gave up. It wasn't until someone tried to teach me to play specific songs that I had to motivation to actually learn the scales, why they were important and useful. I had a practical goal, not just a hello world. Don't get me wrong, hello world's a nice start. But then, it's already been done before. Dozens of times. Do something different.