From: Martin DeMello <martindemello@gmail.com>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Desktop GUI toolkits - current state of the art?
Date: Wed, 24 Nov 2010 15:03:46 +0530 [thread overview]
Message-ID: <AANLkTikiG=nKYccQ-HESy+gijRXCnZFKF1bOFexruVj1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimrGksFy9PpmFZOsmE12m9cQaeN7f_KLWv9FfPJ@mail.gmail.com>
On Wed, Nov 24, 2010 at 4:36 AM, Jacques Garrigue
<garrigue@math.nagoya-u.ac.jp> wrote:
> I'm not sure which examples you looked at for lablgtk2.
> The goals of lablgtk are:
> * be as close as possible to the spirit of Gtk+
> * while providing type and memory safety
> * and allow comfortable use through objects and optional arguments
> This resulted in a 2-layer implementation, with a lower layer
> that just wraps basic Gtk+ calls, and an object layer on top of it.
> Some examples mix the two layers, which may look strange, but
> I think that when you use only the upper layer, this is clean enough.
> (The lower layer is not dirty, but converting between the two may be
> verbose and look clumsy).
That might be the problem, then. I was looking at the examples in the
translation of the gtk tutorial, and a lot of it seemed like C code
translated to OCaml. Could you point me to some example of code
written using the high level API?
> The obvious alternative to lablgtk2 is of course labltk.
> I personally think that labltk is still the easiest way to build a GUI,
> but many do not like Tk's look&feel.
Does labltk have any prospect of being updated for tk 8.5? I tried
using it but discovered I'd have to install tk8.4 first.
martin
next prev parent reply other threads:[~2010-11-24 9:33 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 [this message]
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
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='AANLkTikiG=nKYccQ-HESy+gijRXCnZFKF1bOFexruVj1@mail.gmail.com' \
--to=martindemello@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=garrigue@math.nagoya-u.ac.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