This is the mail archive of the guile-gtk@sources.redhat.com mailing list for the Guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: The GTK2 line of development


On Mon, 26 May 2003, Kevin Ryde wrote:

> But gtk 1.2 is a bit of a dead end unfortunately.  I'd like to see the
> main guile-gtk support basically whatever is the current gtk.  Perhaps
> with some conditionals to support a few past versions, if that's of
> interest and if it's not too hard.

Unfortunately the codebases are, as you know, completely separate. The
underlying type systems are also different enough to prevent easy
adaptation of either codebase to the other version. It's not worth it.

> > So we have (gnome gobject),
> 
> That's the glib gobject I take it.  Perhaps glib should have an
> independent existance (glib glib), (glib gobject), etc.

I was wondering myself about that. The thing that binds the projects
together are the binding generation code (defs-support, gw-utils, etc)
and that they are all based on the GObject type system, with the
exception of GLib. Gnome is the overarching project under which all are
being developed though, and if I had to choose a name that would be it.

Of course, glib doesn't depend at all on gnome, the current module name
notwithstanding.

> (But within one project.  I think all in one would be easiest for
> development, mainly since I think each higher interface is going to
> need to know a good deal about how the lower ones are implemented, and
> there's probably a good amount of common stuff anyway.)

Yeah. I think, though, since it is all one project, why not have it
under one namespace?

regards,

wingo.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]