On Wed, Jul 23, 2008 at 09:14:46AM -0500, John Hunter wrote: > > Related: while I am digging around in there, now is probably the moment > > for me to integrate Paul Kienzle's comments on start/stop_event_loop in > > FigureCanvasBase, etc. I am not sure there is a consensus on this. I > > am currently thinking that the best way to integrate this, while > > minimizing repeated code, is a mixin plus a couple of new classes, > > FigureCanvasBaseGUI and FigureCanvasGUIAgg. These new classes would > > inherit the mixin and the base classes without "GUI". Interactive > > backends would then inherit these. Non-interactive backends would > > inherit versions that throw errors from FigureBaseCanvas. Complex, but > > this assures clean inheritance. Thoughts welcome.
> See my response in the original thread. I'm not sure we ever reached > a consensus on this one, and I'm still uncomfortable with a more > complex hierarchy. I'm willing to be convince if you and Paul and > Gael disagree, but I have yet to see why a flat implementation will > not work here. I actually lean on the simple side for now. If we find as we improve the event-loop related stuff that we need this, we can easily add an abstraction, but right now I don't see a big benefit. Anyhow, whoever does the work gets to decide, as usual. Gaël ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
