From: "Dale P. Smith" <dsmith@altustech.com>
To: guile-gtk@sources.redhat.com
Subject: Re: The GTK2 line of development
Date: Mon, 02 Jun 2003 12:05:00 -0000 [thread overview]
Message-ID: <20030602080532.0956ebbf.dsmith@altustech.com> (raw)
In-Reply-To: <20030526173126.GB6014@lark>
On Mon, 26 May 2003 18:31:26 +0100
Andy Wingo <wingo@pobox.com> wrote:
> On Mon, 26 May 2003, Kevin Ryde wrote:
> 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?
Maybe I'm misunderstanding this, but please make sure that gtk/glib
can be used (and built!) without gnome.
-Dale
--
Dale P. Smith
Senior Systems Consultant, | Treasurer,
Altus Technologies Corporation | Cleveland Linux Users Group
dsmith at altustech dot com | http://cleveland.lug.net
440-746-9000 x239 |
next prev parent reply other threads:[~2003-06-02 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 12:04 Andy Wingo
2003-05-24 14:08 ` Stan Pinte
2003-06-02 6:51 ` Andy Wingo
2003-06-02 10:06 ` Stan Pinte
2003-05-25 23:31 ` Kevin Ryde
2003-06-02 6:51 ` Andy Wingo
2003-06-02 12:05 ` Dale P. Smith [this message]
2003-06-02 13:04 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030602080532.0956ebbf.dsmith@altustech.com \
--to=dsmith@altustech.com \
--cc=guile-gtk@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).