From: Ariel Rios <ariel@gnu.org>
To: Andy Wingo <wingo@pobox.com>,
mvo@zagadka.de, guile-gtk@sources.redhat.com
Cc: Stan Pinte <stan@altosw.be>
Subject: Re: (gnome gtk) et al
Date: Mon, 07 Apr 2003 19:57:00 -0000 [thread overview]
Message-ID: <1049743589.1933.21.camel@tosca.elektra.com.mx> (raw)
In-Reply-To: <20030407144511.GA1489@lark>
On Mon, 2003-04-07 at 09:45, Andy Wingo wrote:
> Hi Ariel,
>
> I'm real interested in getting the guile-gtk bindings in a proper
> working order. I'm interested on a number of levels, but mainly because
> I'd like to make some nice GStreamer scheme bindings. I've been hacking
> on the cvs guile-gobject, fixed a bug in guile 1.6.3 along the way, and
> have generally been having a good time. I wanted to give you a heads-up
> on this; when I get my defs->gwrap code working properly I'll send you a
> large patch.
>
Ok. I'd been receiving some comments and want to put things back in
order. I am very happy that interest in guile-gobject has aroused so if
we work together we can have the bindigs working correctly very soon.
We have several code base. We have several modules:
guile-gtk: Currently on savanah forGtk1.4
gnome-guile: Also on savanah for Gnome 1.4 (??)
guile-gobect: Still under gnome CVS and ioncludes the work for GTk 1.4
The first branch is being worked by Marius. I think no one is working
ong the gnome-guile.
All the interesing work is donde under guile-gobect
I worked in a defs->gwrap translator but did not finish it. I don't
rememember if i commited that one but maybe you are using it as the
basis for yours. IIRC, the only thing that guile-gobject was lacking was
that translator.
> One thing: do you mind us moving to the latest g-wrap code rather than
> keeping a forked copy in our cvs? that would make more sense. It would
> also be nice for the directory structure of the repository to mirror the
> layout of the installed modules, so that we can develop by changing
> GUILE_LOAD_PATH instead of making install all of the time. I've got a
> number of other things on my mind, but I really want to get this code
> working nicely so I can start doing real work again.
That would absolutely make sense. I really would prefer to use latest
g-wrap to keep on with latest changes. Although I had never used them we
should give them a try.
Let's bring back gnome fun to scheme again!
--
Ariel Rios <ariel@gnu.org>
next parent reply other threads:[~2003-04-07 19:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030407144511.GA1489@lark>
2003-04-07 19:57 ` Ariel Rios [this message]
2003-04-07 20:15 ` Andreas Rottmann
2003-04-08 10:34 ` Marius Vollmer
2003-04-08 14:56 ` Stan Pinte
2003-04-08 20:03 ` Andreas Rottmann
2003-04-08 21:33 ` David Pirotte
2003-04-11 4:48 ` Steve Tell
2003-04-11 10:00 ` Andreas Rottmann
2003-04-09 15:24 ` Stan Pinte
2003-04-10 17:05 ` Andreas Rottmann
2003-04-10 17:10 ` David Pirotte
2003-05-06 6:52 ` Stan Pinte
2003-05-06 15:33 ` Marius Vollmer
2003-05-06 15:45 ` Stan Pinte
2003-05-07 13:07 ` Stan Pinte
2003-05-07 14:02 ` Stan Pinte
2003-05-07 14:10 ` Marius Vollmer
2003-05-07 14:38 ` Stan Pinte
2003-05-07 15:17 ` Stan Pinte
2003-05-07 18:16 ` Marius Vollmer
2003-05-08 11:43 ` Stan Pinte
2003-05-12 14:18 ` Stan Pinte
[not found] ` <1052750737.26632.4.camel@tosca.elektra.com.mx>
2003-05-12 16:48 ` Stan Pinte
2003-05-14 9:17 ` Andy Wingo
2003-05-16 14:26 ` Andreas Rottmann
2003-05-20 20:08 ` Andreas Rottmann
2003-05-23 22:00 ` Kevin Ryde
2003-05-26 13:04 ` Andreas Rottmann
2003-06-23 14:14 ` 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=1049743589.1933.21.camel@tosca.elektra.com.mx \
--to=ariel@gnu.org \
--cc=guile-gtk@sources.redhat.com \
--cc=mvo@zagadka.de \
--cc=stan@altosw.be \
--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).