James Henstridge writes:
It provides a non GUI base for objects. I have been wondering about
whether to put the base gobject support into a separate module or not, and
whether I should keep it separate from the gtk package (when you import
gtk, it initialises the GUI). Does this sound
James Henstridge writes:
Well, this is one of those things where we won't know how many useful non
gui libraries will use the object model until after the glib/gtk 2.0
release. I have decided to put the GObject wrapper stuff in a separate
module just in case.
There's certainly no way
On Mon, 26 Jun 2000, Fred L. Drake, Jr. wrote:
For quite a while, I have been passing function pointers around as
CObjects in the modules (eg. gtk._gtk._PyGtk_API in the 0.7.0 release),
which means that the different wrapper modules don't need to see each
other's symbols.
I just got the HEAD branch of gtk+ compiled on my system, so was thinking
of starting off binding it. One of the new features is the GObject
system, which is what the GtkObject stuff is based on in gtk+-1.3.
It provides a non GUI base for objects. I have been wondering about
whether to put the
