caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: bluestorm <bluestorm.dylc@gmail.com>
To: "Hezekiah M. Carty" <hcarty@atmos.umd.edu>
Cc: Martin DeMello <martindemello@gmail.com>,
	OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Desktop GUI toolkits - current state of the art?
Date: Sun, 28 Nov 2010 09:28:04 +0100	[thread overview]
Message-ID: <AANLkTinF9og-1rpLz1jwCFwxqyRiOmLaLZRJTiFL2ycK@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikz+r3WhqFRn2D=-xOhOdRk7kBogGGTjJKK7RTx@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

There was also a project by Chris King to develop a GUI based on lablgtk in
a Functional Reactive Programming style.

http://lambda-the-ultimate.org/node/1918

On Wed, Nov 24, 2010 at 4:57 PM, Hezekiah M. Carty <hcarty@atmos.umd.edu>
 wrote:

> On Wed, Nov 24, 2010 at 4:47 AM, Martin DeMello <martindemello@gmail.com>
> wrote:
> >
> > I was surprised not to see much interest in GUI DSLs in OCaml.
>
> It's not complete or a full-blown DSL, but I started a small Gtk-light
> module a while ago.  I haven't had the time to complete it, but it
> shouldn't be too difficult to modify for your needs:
>
> http://0ok.org/cgit/cgit.cgi/gtk-light/
>
> Here is a brief example (uses the "open Module in" syntax extension):
>
> http://0ok.org/cgit/cgit.cgi/gtk-light/tree/basic_gui_test.ml
>
> With OCaml 3.12 the "open Module in" could be replaced by the new "let
> open Module in" or Module.(...) syntax.
>
> Hez
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>

[-- Attachment #2: Type: text/html, Size: 2351 bytes --]

  reply	other threads:[~2010-11-28  8:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 14:19 Martin DeMello
2010-11-23 23:06 ` [Caml-list] " Jacques Garrigue
2010-11-24  9:33   ` Martin DeMello
2010-11-24 14:06     ` Michael Ekstrand
2010-11-24 15:56       ` Andrei Formiga
2010-11-23 23:28 ` Yoann Padioleau
2010-11-24  9:38   ` Martin DeMello
2010-11-26 19:09     ` Yoann Padioleau
2010-11-28  6:38       ` Martin DeMello
2010-11-28  7:40         ` Yoann Padioleau
2010-11-29 14:21           ` Martin DeMello
2010-11-23 23:32 ` Alain Frisch
2010-11-24  9:47   ` Martin DeMello
2010-11-24 15:57     ` Hezekiah M. Carty
2010-11-28  8:28       ` bluestorm [this message]
2010-11-28 22:20         ` Adrien
2010-11-29 13:20           ` Adrien
2010-11-29 14:02           ` Martin DeMello
2010-12-10  6:04             ` Maxence Guesdon
2010-11-29 16:47         ` Hezekiah M. Carty
2010-11-24 21:37     ` Alain Frisch
2010-11-24 22:32       ` Jeremy Yallop
2010-12-01 11:43     ` Alain Frisch
2010-11-24 10:21 ` Mihamina Rakotomandimby
2010-11-26 18:59 ` Richard Jones
2010-11-28  6:40   ` Martin DeMello

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=AANLkTinF9og-1rpLz1jwCFwxqyRiOmLaLZRJTiFL2ycK@mail.gmail.com \
    --to=bluestorm.dylc@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=hcarty@atmos.umd.edu \
    --cc=martindemello@gmail.com \
    /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).