caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jeff Henrikson" <jehenrik@yahoo.com>
To: <caml-list@inria.fr>
Subject: [Caml-list] graphical variant editor widget generator
Date: Sat, 15 Dec 2001 15:33:38 -0500	[thread overview]
Message-ID: <000e01c185a7$c6cde720$0b01a8c0@mit.edu> (raw)

I am thinking that rather than building a bunch of custom GUI behavior for my application, it might be nice to have a tool which
could parse a ocaml datatype of nested variants/records, and generate a custom graphical tree/graph editor widget for it.  Then I
could get my app-specific behavior for cheap, with a UI contract that would make my style self-consistent whether I liked it or
not.  Has anyone done anything similar?


Jeff Henrikson


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


             reply	other threads:[~2001-12-15 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 20:33 Jeff Henrikson [this message]
2001-12-16  9:07 ` Sven
2001-12-16 13:13   ` Warp
2001-12-16 13:13 ` Warp

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='000e01c185a7$c6cde720$0b01a8c0@mit.edu' \
    --to=jehenrik@yahoo.com \
    --cc=caml-list@inria.fr \
    /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).