public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Ariel Rios <ariel@arcavia.com>
To: Rob Browning <rlb@cs.utexas.edu>
Cc: Marius Vollmer <mvo@zagadka.ping.de>, Ariel Rios <jarios@usa.net>,
	guile-gtk@sourceware.cygnus.com,
	Miroslav silovic <silovic@zesoi.fer.hr>
Subject: Re: g-wrap and guile-gnome/gtk
Date: Sun, 12 Nov 2000 11:07:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10011121404010.8430-100000@soleil.gnome.org> (raw)
In-Reply-To: <87lmupf7je.fsf@raven.localnet>

On 12 Nov 2000, Rob Browning wrote:

> Marius Vollmer <mvo@zagadka.ping.de> writes:
> 
> 
> > 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.
There is a new spec file format that was created for general use.
The document is located somewhere in the GTK+ module. It is important
that g-wrap works with these new format. I think that in the case
of Guile-gtk / Gnome-guile we do want to keep using these format.
 
> Well, I want to make it clear that I'm not hung up on g-wrap as it is.
> If we need to change things, or even if we decide that we need to work
> on some other common effort, it sounds to me like a joint solution
> would benefit everyone.
I am especially interested in knowing how fast do libraries
binded using g-wrap is.
 
> 
> Perfect sense.  One thing we might want to decide is if it's OK that
> the API spec files are just scheme code.  G-wrap handles it that way
> right now, but that could be changed.  
We can even have some macros to deal with the defs file if necessary...

ariel

  parent reply	other threads:[~2000-11-12 11:07 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 ` g-wrap and guile-gnome/gtk Marius Vollmer
2000-11-12  9:02   ` Rob Browning
2000-11-12  9:42     ` Michael Livshin
2000-11-12 11:07     ` Ariel Rios [this message]
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=Pine.LNX.4.10.10011121404010.8430-100000@soleil.gnome.org \
    --to=ariel@arcavia.com \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=jarios@usa.net \
    --cc=mvo@zagadka.ping.de \
    --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).