From: Ariel Rios <ariel@arcavia.com>
To: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: The ROAD-AHEAD: GNOME 2.0 and guile-gtk
Date: Wed, 30 Aug 2000 20:02:00 -0000 [thread overview]
Message-ID: <a3222d8990944b84e8396a0044b7c4b5@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <87r976poqv.fsf@zagadka.ping.de>
> Ariel Rios <ariel@arcavia.com> writes:
>
> > 2)Change of the .defs file format
>
> Can you quickly describe what you mean by that?
Oh yes, sure.
A new defs file format was proposed to be used as a standard.
They are based in guile-gtk with major modifications to
include some other nice things. The proposal is included
in CVS Gtk+ HEAD in gtk+/docs/defsformat.txt
ariel
next prev parent reply other threads:[~2000-08-30 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000830171310.451.qmail@zagadka.ping.de>
2000-08-30 11:52 ` Marius Vollmer
2000-08-30 12:03 ` thi
2000-08-30 12:46 ` Marius Vollmer
2000-08-30 20:02 ` Ariel Rios [this message]
[not found] ` <20000831173532.438.qmail@zagadka.ping.de>
2000-09-03 7:32 ` Marius Vollmer
2000-09-03 20:07 ` Ariel Rios
2000-08-29 19:33 Ariel Rios
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=a3222d8990944b84e8396a0044b7c4b5@NO-ID-FOUND.mhonarc.org \
--to=ariel@arcavia.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=mvo@zagadka.ping.de \
/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).