On Tue, 2007-02-13 at 14:16 -0500, Tristan Van Berkom wrote: > PS: This is not a personal thing, countless hordes have come in > search of a libglade example without ever consulting the tarball, > its just getting a little frustrating by now - but what can we do > to improve the situation ?
I was pondering that as I wrote my post. Obviously this is an issue with the linux distribution. I feel sheepish myself because while looking for this file on my FC6 box, I discovered an entire directory populated by the various gtk+ devel packages that has complete API docs for gtk, glib, pango, gnome, etc. I had been relying on the web pages for that before (not a bad thing though). One thing that might help here is to have a compiled executable that demonstrates libglade be installed as part of the normal compilation process. This would then be picked up by the packagers and installed as part of the -devel package. The demo program would be similar to gtk-demo where the different aspects of libglade would be demonstrated along with the source code window where users could see the source code and the glade files. That way, rather than pointing files at the .c file, just say "run libglade-demo" and expect it to be self documenting in every way. I think this may be a better thing than just the test-libglade.c file. Of course I'm not sure exactly what things would want to be demoed exactly. Maybe just a couple of glade-created windows and callbacks. Michael > > > _______________________________________________ > gtk-app-devel-list mailing list > gtk-app-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list > _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
