public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: "Neil W. Van Dyke" <nwv@neilvandyke.org>
To: Ariel Rios <ariel@gnu.org>
Cc: Eric Gillespie <epg@pretzelnet.org>,
	guile-gtk@sources.redhat.com, guile-devel@gnu.org
Subject: (Was: guile-gobject 0.3.0 Released)
Date: Mon, 04 Feb 2002 15:05:00 -0000	[thread overview]
Message-ID: <15455.5099.166781.709713@winona.neilvandyke.org> (raw)
In-Reply-To: <1012361923.701.7.camel@soleil>

I'm afraid I'm confused about the future of guile-gtk.

Could Ariel (or perhaps someone else who is also working on it) please
clarify what the intentions for continuing development are?

Reasons for asking:

  * I could not get the guile-gtk 0.21pre4 release to build against GTK
    2 (1.3), and configuration code that appeared to be for GTK 2 was
    disabled.  I had the same problem with CVS version.

  * When built against GTK 1.2 and Guile 1.5.4 CVS, some of the
    guile-gtk widget demos have errors (possibly due to Guile changes).
    It was also unclear how much new functionality has been added in
    recent times.

  * Ariel's true love may be the full Gnome platform in all its glory,
    and it may be asking too much of him -- or anyone -- to burden him
    with separately developing and maintaining *non*-Gnome GTK bindings.

No flame intended; I just need to understand where guilt-gtk is going if
I'm to be able to use Guile at all.  So far it's been confusing.

Please note that guile-gobject won't work for me and some other people,
since anything Gnome-dependent presents technical (e.g., size,
complexity) and/or political issues.  However, Guile bindings for GTK 2
(and perhaps Pango and Libart), are very much desired -- so long as they
are independent of Gnome.

Thanks,
Neil V.

> From: Ariel Rios <ariel@gnu.org>
> To: Eric Gillespie <epg@pretzelnet.org>
> Cc: guile-gtk@sources.redhat.com
> Subject: Re: guile-gobject 0.3.0 Released
> Date: 29 Jan 2002 22:38:43 -0500
> 
> On Tue, 2002-01-29 at 21:54, Eric Gillespie wrote:
> > Ariel Rios <ariel@gnu.org> writes:
> > 
> >     > The rest of the package contains unfinished and untested gtk
> >     > bindings.
> > 
> > The GTK2 bindings will also be available independently, right?  Once
> > it's released anyway.  Not everyone uses GNOME.
> I can continue to disitribute both guile-gtk and gnome-guile.
> This will make happy schemers to many of our users ;)
> 
> ariel

-- 
                                                        Neil W. Van Dyke
                                             http://www.neilvandyke.org/

  reply	other threads:[~2002-02-04 23:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 11:29 guile-gobject 0.3.0 Released Ariel Rios
2002-01-29 19:01 ` Eric Gillespie
2002-01-29 20:39   ` Ariel Rios
2002-02-04 15:05     ` Neil W. Van Dyke [this message]
2002-02-04 21:30       ` (Was: guile-gobject 0.3.0 Released) Ariel Rios
2002-02-04 14:15 ` guile-gobject 0.3.0 Released Neil W. Van Dyke
2002-02-06  5:24   ` Taming the beast [was: Re: guile-gobject 0.3.0 Released] rm
2002-02-08  3:03     ` Neil Jerram

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=15455.5099.166781.709713@winona.neilvandyke.org \
    --to=nwv@neilvandyke.org \
    --cc=ariel@gnu.org \
    --cc=epg@pretzelnet.org \
    --cc=guile-devel@gnu.org \
    --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).