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 like a good idea?
I like the idea. The real question is how many libraries will be
built with it that don't also require GTK+? I have little idea about
this, especially since I'm largely disconnected with the C-only
world.
> I don't know how many non gui libraries will be using gobject, and how
> many of those will be useful to python programmers. If we want to wrap
> those libraries and not require gtk be loaded, it will have to be compiled
> as a separate module.
Overall, it's probably best to assume that at least some interesting
libraries will be built, especially if "interesting" includes "we have
to support X because Y is interesting and requires X objects". I
think the biggest problem we'll have to deal with is the addition of
symbols from libraries required by extension modules to the global
symbol table; I've not played with enough of the recent code to know
if that's still a big problem. I'll try and spend a little time on it
in about three weeks (I'm waiting for a motherboard for my machine
before I can do much on Unix ;( ).
-Fred
--
Fred L. Drake, Jr. <fdrake at beopen.com>
BeOpen PythonLabs Team Member
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
