public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
To: ttn@glug.org
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: adding "dump" opsym to build-guile-gtk
Date: Sat, 11 Nov 2000 15:11:00 -0000	[thread overview]
Message-ID: <871ywinmq7.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200011081743.JAA09789@revel.glug.org>

thi <ttn@revel.glug.org> writes:

> i would like to translate glade xml files to guile-gtk code using
> the defs files and build-guile-gtk.  could you suggest a good
> approach (or perhaps a pre-made solution) to this 

I don't know about Glade or XML but isn't there glade support in
gnome-guile already?  Ariel?  But maybe that is not what you want.

Do you want to compile a XML file into Scheme ahead of time, or do you
want to to interpet the contents of the XML file at run-time?

> my current thinking is to build widgets by taking a constructor
> function def and filling in its args using properties mapped over
> from the xml file.

Aha, hmm, so you need the information in the defs files to generate
valid Scheme code, right?  Can you give an example?  

Maybe it is easiest to just slurp in the defs file without support
from build-guile-gtk.  Or maybe you don't need the defs files after
all.

> what is the difference between "imported" types and non-imported
> types?

Imported types can be used in definitions, but there will be no code
generated for them.  For non-imported types, there will be some tables
generated that contain useful information about the type.

  reply	other threads:[~2000-11-11 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22 11:36 thi
2000-10-23 15:32 ` Marius Vollmer
2000-11-08  9:46   ` thi
2000-11-11 15:11     ` Marius Vollmer [this message]
2000-11-11 17:03       ` Ariel Rios
2000-11-08  9:47   ` thi

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=871ywinmq7.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=ttn@glug.org \
    /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).