From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: Benjamin Monate <Benjamin.Monate@lri.fr>
Cc: florian@hars.de, lablgtk@kaba.or.jp, caml-list@inria.fr
Subject: [Caml-list] Re: To glade or not to glade (Was: [Caml-announce] Mlglade prerelease announce)
Date: Wed, 28 Nov 2001 17:42:08 -0500 [thread overview]
Message-ID: <3C056840.5080505@inria.fr> (raw)
In-Reply-To: <20011128103320.7c1a9dc5.Benjamin.Monate@lri.fr>
>
> I agree with Jacques. At some point in the future lablgtk libglade support
> and mlglade
> should be compatible. This has been discussed on the lablgtk mailing list
> sometime ago.
> As for zoggy, I do not know if it has any kind of glade-like xml output.
Zoggy has a xml output, but not the same as glade. The main reason is that
properties for values are ocaml code in zoggy, instead of just predefined
constants in glade.
A zoggy->glade translator would be possible but some properties values
would be lost when the given ocaml code is different from the predefined
ocaml code values. Parameters to generated classes defined in zoggy
would be lost too :-(
A glade->zoggy translator would be possible, but zoggy doesn't support
all the information that glade does. All Gtk widgets will soon be
supported in zoggy, as well as the menu definitions, but i don't know if
i'll add the connection of functions to events in zoggy.
--
Maxence Guesdon
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-11-28 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 19:08 [Caml-announce] Mlglade prerelease announce Benjamin Monate
2001-11-28 8:06 ` [Caml-list] To glade or not to glade (Was: [Caml-announce] Mlglade prerelease announce) Florian Hars
[not found] ` <20011128172124X.garrigue@kurims.kyoto-u.ac.jp>
2001-11-28 9:33 ` [Caml-list] " Benjamin Monate
2001-11-28 22:42 ` Maxence Guesdon [this message]
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=3C056840.5080505@inria.fr \
--to=maxence.guesdon@inria.fr \
--cc=Benjamin.Monate@lri.fr \
--cc=caml-list@inria.fr \
--cc=florian@hars.de \
--cc=lablgtk@kaba.or.jp \
/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 NNTP newsgroup(s).