From mboxrd@z Thu Jan  1 00:00:00 1970
From: thi <ttn@revel.glug.org>
To: mvo@zagadka.ping.de
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: adding "dump" opsym to build-guile-gtk
Date: Wed, 08 Nov 2000 09:46:00 -0000
Message-id: <200011081743.JAA09789@revel.glug.org>
References: <200010220920.CAA02382@revel.glug.org> <87hf645y36.fsf@zagadka.ping.de>
X-SW-Source: 2000-q4/msg00009.html

   From: Marius Vollmer <mvo@zagadka.ping.de>
   Date: 23 Oct 2000 00:07:41 +0200

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

   > the below diff adds "dump" command support to build-guile-gtk.  it is
   > based on the "glue" command defs-reading code.

   Can you say a bit more why you need this?  It is not totally obvious
   to me that what you did is the right thing, because you lose the
   options and may not know which types have been defined and which have
   just been imported by looking at the dumped data.

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 problem?

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.

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

thanks for any clues,
thi