public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-gtk@sources.redhat.com
Subject: The GTK2 line of development
Date: Sat, 24 May 2003 12:04:00 -0000	[thread overview]
Message-ID: <20030524114111.GC24132@lark> (raw)

Hello all,

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? In that case, we have two separate
projects (and in fact they share hardly any code, although I have used
some ideas, as well as event-repl.scm from guile-gtk) and should put
them in different places. What's the deal?

I suppose we can enumerate some options,

 - within savannah.nongnu.org
   * has the advantage that all guile-gtk stuff is in the same place
    (maybe it's an advantage, who knows)

 - in gnome cvs
   * keeps continuity with guile-gobject 0.2.0, although that work was
     likely placed in gnome cvs just out of convenience for martin

 - where else? those seem to be the options. we could do sourceforge,
   but that's subject to the whims of va software; that doesn't seem as
   stable as savannah

In any case, the web page needs cleaning and updating so that we can
make sense out of this mess. And that tarball really needs to make it
into CVS somewhere.

Also, we need to decide on some module namespace issues, don't we? Right
now all the GNOME 2 side is under (gnome). So we have (gnome gobject),
(gnome gtk), (gnome gstreamer) [see gst-guile in gstreamer cvs], etc. Is
this ok?

Can we get some input in here from those working on the 1.2 side of
things as well as from 2.x? The sooner this gets settled, the sooner we
can get some good work (and play) done :-)

regards,

wingo.

             reply	other threads:[~2003-05-24 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24 12:04 Andy Wingo [this message]
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
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=20030524114111.GC24132@lark \
    --to=wingo@pobox.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).