From: Andreas Rottmann <a.rottmann@gmx.at>
To: Ariel Rios <ariel@gnu.org>
Cc: guile-gtk@sources.redhat.com
Subject: Re: (gnome gtk) et al
Date: Fri, 16 May 2003 14:26:00 -0000 [thread overview]
Message-ID: <87n0hnrmqy.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <20030514085929.GA12304@lark> (Andy Wingo's message of "Wed, 14 May 2003 09:59:29 +0100")
Andy Wingo <wingo@pobox.com> writes:
> Ariel! Do check out that url,
> http://ambient.2y.net/wingo/tmp/guile-gobject-0.5.0.tar.gz. It is in
> nice shape, it's ready to release to the world so we can start
> making gtk2 applications from scheme. Just tell me where would be a
> good place to put it and I'll see about importing it into cvs. I
> really want this released because my guile-gstreamer bindings depend
> on it. I want Debian packages for all of this, too -- we need
> official releases for that.
>
Wow! Excellent work!
I played with it a bit, since I need good glib bindings for a project
of mine. I already have made a bit of progress wrapping GError, but
there is one thing that bit me: Wrapping enums that don't have a GType
ID (such as the ones found in GLib, e.g. GIOStatus).
I think one route to wrap these would be to have h2def.py somehow
realize they don't have a GType ID (don't know if that is feasible)
and as a consequence generate a .def entry without (g-type-id
"foobar"). defs-support.scm could then use plain g-wrap gw:wrap-enum
instead of gobject:gwrap-enum.
Thoughts?
Andy
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Packages should build-depend on what they should build-depend.
next prev parent reply other threads:[~2003-05-16 14:26 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
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 [this message]
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=87n0hnrmqy.fsf@alice.rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=ariel@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).