On Fri, Jan 23, 2015 at 10:06 AM, Sébastien Wilmet <swil...@gnome.org> wrote:
> On Thu, Jan 22, 2015 at 10:01:55PM +0100, Sébastien Wilmet wrote: > > https://github.com/swilmet/gtk-brochure > > https://people.gnome.org/~swilmet/gtk-brochure.pdf > > I've pushed an update. I've simplified the GObject section, and added a > state diagram of the GLib event loop. An event loop and event-driven > programming is not often taught at the university, so with a diagram > readers will better memorize what it is. > I'm not sure you can cover all potential interest in the g* stack with a single two-sided brochure. Nobody cares about GObject except: * die-hard C coders (who are neverthless open-minded enough to want to use an "object" model) * people working on the g* stack itself * people working on the internals of language bindings Event loop programming is simultaneously completely fundamental to all user-interactive software, and as such ought to require no introduction at all, but as you note it is (pathetically) lacking from the education experienced by many in the field. If you're going to draw an event loop then I think you want to capture something a bit less abstract than what you have. Events (keyboard,mouse,touch,network,serial,other data sources) => application response (computation, communication, request drawing changes) => redraw => REPEAT That's the actual useful event loop.
_______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
