From: Kevin Ryde <user42@zip.com.au>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-gtk@sources.redhat.com
Subject: Re: The GTK2 line of development
Date: Sun, 25 May 2003 23:31:00 -0000 [thread overview]
Message-ID: <8765nymwnm.fsf@zip.com.au> (raw)
In-Reply-To: <20030524114111.GC24132@lark> (Andy Wingo's message of "Sat, 24 May 2003 12:41:11 +0100")
Andy Wingo <wingo@pobox.com> writes:
>
> I'm curious about the place of the GTK2 line of development within the
> whole guile-gtk project. It seems that some folks are not interested in
> GTK2 at all -- is this right?
Speaking only for myself, I arrived at the 1.2 branch because I wanted
to write a program, and that stuff was what seemed to work.
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.
> 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.
(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.)
next prev parent reply other threads:[~2003-05-25 23:31 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 [this message]
2003-06-02 6:51 ` Andy Wingo
2003-06-02 12:05 ` Dale P. Smith
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=8765nymwnm.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-gtk@sources.redhat.com \
--cc=wingo@pobox.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).