From: Martin DeMello <martindemello@gmail.com>
To: Yoann Padioleau <padator@wanadoo.fr>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Desktop GUI toolkits - current state of the art?
Date: Sun, 28 Nov 2010 12:08:16 +0530 [thread overview]
Message-ID: <AANLkTin5UeNCUndRCqNgzwOW4+BMbK45KJiNSxj3EG=y@mail.gmail.com> (raw)
In-Reply-To: <4EF2E0B5-58C9-4F1D-ABBF-630863619E17@wanadoo.fr>
On Sat, Nov 27, 2010 at 12:39 AM, Yoann Padioleau <padator@wanadoo.fr> wrote:
> On Nov 24, 2010, at 1:38 AM, Martin DeMello wrote:
>>
>> Both ruby and vala make an effort to provide nice syntactic support
>> for gtk code, so that it looks like a natural part of the language.
>
> Could you give some example of code explaining that ?
> Code in vala/ruby vs same code in lablgtk.
Here's the table packing example in ruby and ocaml:
http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-packing-tables-demo
http://plus.kaist.ac.kr/~shoh/ocaml/lablgtk2/lablgtk2-tutorial/x509.html
They both more or less follow the C API, but the ruby code looks like
natural ruby (perhaps because ruby has a more imperative flavour than
OCaml does), whereas the OCaml code looks there should be a more
declarative, higher-level way of doing things.
Vala is currently experimenting with gtkon, a declarative layout
language that embeds vala code "islands", and is compiled into pure
vala by a preprocessor.
http://code.google.com/p/gtkaml/wiki/Gtkon
This seems like a very promising direction, though I don't know how
well an equivalent approach would work in OCaml.
martin
next prev parent reply other threads:[~2010-11-28 6:38 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 [this message]
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
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='AANLkTin5UeNCUndRCqNgzwOW4+BMbK45KJiNSxj3EG=y@mail.gmail.com' \
--to=martindemello@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=padator@wanadoo.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