RE: [gtkmm] Comments on tutorial

[Murray Cumming Comneon com]

> I don't think it's a good idea in a tutorial to 
> call something "kit" for 13 chapters and then start calling 
> it "main_runner" for no particular reason. In fact,  perhaps 
> this is a place where a general convention might make 
> sense,  since I assume almost every gtkmm program needs such 
> a variable.

Patches are gratefully accepted:
http://www.gtkmm.org/bugs.shtml


> I had in mind something 
> simple,  like painting a 
> small circle at a point where you double click the mouse.  A 
> bigger example would be a simple "object-oriented" paint 
> program that draws movable rectangles and ellipses.

Yes, that sounds like a good idea.

> What it says is clear enough.  It's probably me who's not 
> being clear. It just seems to me that the emphasis is in the 
> wrong place and the 
> examples are slightly artificial.  I would expect 
> on_expose_event to be as minimal as possible,  just invoke 
> some paint routines that paint 
> something determined by some stored state.  It shouldn't have details 
> in it.  And painting in general has to be separate from 
> on_expose_event anyway,  because normally you'll be painting 
> in response to some kind of interaction,  like mouse clicks,  
> so you won't be getting expose events.

I am not personally an expert on the DrawingArea but I am happy to see
patches for the documentation and/or examples.

Murray Cumming
www.murrayc.com
murrayc usa net