public inbox for
 help / color / mirror / Atom feed
From: thi <>
Subject: Re: adding "dump" opsym to build-guile-gtk
Date: Wed, 08 Nov 2000 09:46:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

   From: Marius Vollmer <>
   Date: 23 Oct 2000 00:07:41 +0200

   thi <> 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

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

thanks for any clues,

  reply	other threads:[~2000-11-08  9:46 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 [this message]
2000-11-11 15:11     ` Marius Vollmer
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).