From: Richard Jones <rich@annexia.org>
To: David Teller <David.Teller@ens-lyon.org>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] labltk for tk 8.4 BETA release
Date: Tue, 15 May 2007 09:08:47 +0100 [thread overview]
Message-ID: <20070515080847.GA30352@furbychan.cocan.org> (raw)
In-Reply-To: <1179179330.6092.17.camel@Blefuscu>
On Mon, May 14, 2007 at 11:48:49PM +0200, David Teller wrote:
> On Sat, 2007-05-12 at 10:37 -0400, Jeffrey Loren Shaw wrote:
> > Yup that link should be updated. I don't think it should be bundled with
> > ocaml, however. The end-user might already have it installed, or might not
> > need it. But this is a decision for the ocaml devs.
>
> Of course. The congratulations were for you. The wish list was for OCaml
> Devs.
>
>
> > Instead of documenting labltk, which is difficult for the beginner ocaml
> > programmer anyway, make a wrapper to make it more ocaml-y. I'm not sure if
> > this would be easy or possible, but coercing labltk into one style of
> > programming (preferably functional) could go a long way towards making it
> > easier to learn for the beginner.
>
> I'm currently thinking about the best way to write the equivalent of
> JavaFX for OCaml : both the user-interface and the "new features" (e.g.
> list comprehension, SQL-ish selections from data structures, etc.). The
> user-interface part doesn't look too difficult. I'll start to work on
> it... well, if I ever get time.
PG'OCaml does the SQL part: http://merjis.com/developers/pgocaml
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2007-05-15 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 14:37 Jeffrey Loren Shaw
2007-05-14 21:48 ` David Teller
2007-05-15 8:08 ` Richard Jones [this message]
2007-05-18 12:35 ` David Teller
-- strict thread matches above, loose matches on Subject: below --
2007-05-12 2:56 Jeffrey Loren Shaw
2007-05-12 9:19 ` [Caml-list] " David Teller
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=20070515080847.GA30352@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=David.Teller@ens-lyon.org \
--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