From: Marius Vollmer <mvo@zagadka.ping.de>
To: Rob Browning <rlb@cs.utexas.edu>, Ariel Rios <jarios@usa.net>
Cc: guile-gtk@sourceware.cygnus.com, Miroslav silovic <silovic@zesoi.fer.hr>
Subject: Re: g-wrap and guile-gnome/gtk
Date: Sat, 11 Nov 2000 12:11:00 -0000 [thread overview]
Message-ID: <87lmuqnud4.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20001111173022.14524.qmail@nwcst322.netaddress.usa.net>
> From: Rob Browning <rlb@cs.utexas.edu>
> Subject: g-wrap and guile-gnome/gtk
> To: Ariel Rios <jarios@usa.net>
> Date: 02 Nov 2000 13:28:49 -0600
>
>
> What I'm wondering is if we ought to at least discuss whether or not
> we could collaborate on a common solution. Right now I think your
> solution has a few things g-wrap doesn't and vice-versa.
If I remember correctly, build-guile-gtk is actually derived from a
early version of g-wrap. I quickly decided to `roll my own' because
that was easy to do and I didn't know what I wanted precisely.
Build-guile-gtk is still a one-off hack and needs to be redone
completely to make it reasonably clean. This includes the syntax of
the defs files themselves, but hopefully we can clean that up in a
backward compatible way because they are already defs files out there
that are distributed independently from guile-gtk.
Working towards g-wrap would be the right thing, this time.
Because g-wrap def files are just Scheme code, I think we should start
by trying to write implementations for define-object, define-func etc
in terms of the normal g-wrap features. A *.defs file could then
start like this
(use-modules (gtk g-wrap-defs))
(define-object GtkObject
(fields ...))
or build-guile-gtk could be a thin wrapper that invokes g-wrap in the
right way.
Does that make sense?
next prev parent reply other threads:[~2000-11-11 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 9:30 Fwd: [g-wrap and guile-gnome/gtk] Ariel Rios
2000-11-11 12:11 ` Marius Vollmer [this message]
2000-11-12 9:02 ` g-wrap and guile-gnome/gtk Rob Browning
2000-11-12 9:42 ` Michael Livshin
2000-11-12 11:07 ` Ariel Rios
2000-11-12 12:09 ` Rob Browning
2000-11-12 12:14 ` Ariel Rios
2000-11-12 13:54 ` Rob Browning
2000-11-15 6:42 ` Marius Vollmer
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=87lmuqnud4.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=jarios@usa.net \
--cc=rlb@cs.utexas.edu \
--cc=silovic@zesoi.fer.hr \
/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).