On Tue, 2006-11-28 at 04:57 +0100, John K Luebs wrote: > > The idea is to reuse GObject facilities where possible (e.g. types, > > inheritance, signals, GValues), and simply implement the > appropriate > > vtable semantics overridable at runtime. I was wondering if anyone > else > > has stumbled on this and already solved it. > > This is precisely what pygtk tries to do. [...] > I can't see what is wrong with the way pygtk does things
The PyGTK approach requires writing a piece of glue C code for every class whose methods need to be overridden. See the example of GtkCellRenderer. _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
