From: Andrei Formiga <andrei.formiga@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Desktop GUI toolkits - current state of the art?
Date: Wed, 24 Nov 2010 12:56:27 -0300 [thread overview]
Message-ID: <AANLkTikKFr1HXUR3TKMW=Rz7K3wV4kV+=9icc85CYQpo@mail.gmail.com> (raw)
In-Reply-To: <4CED1BCA.3050606@elehack.net>
On Wed, Nov 24, 2010 at 11:06 AM, Michael Ekstrand <michael@elehack.net> wrote:
> On 11/24/2010 03:33 AM, Martin DeMello wrote:
>> 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
>>
>> 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 LablGTK tutorial I am aware of[1] uses the high-level API. The
> high-level API isn't notably higher-level than the base API in terms of
> what calls are necessary, but it wraps everything up in objects and
> makes the data structures nicer. The API call sequences are roughly the
> same.
>
> - Michael
>
> 1. http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
>
It's a design decision. As the author of LablGTK said above, one of
its goals was to stay as close to possible as the original C API. This
has advantages (easy to transfer knowledge and documentation to the
OCaml side), and disadvantages (you miss on providing a nicer API that
would be possible with a more expressive language).
In the end the LablGTK API is only a bit nicer than the C API, so the
GUI part of a LablGTK program would be similar to the equivalent C
version. Unfortunately if you want a higher-level GUI library, I don't
see any viable alternative in OCaml right now.
--
[]s, Andrei Formiga
next prev parent reply other threads:[~2010-11-24 15:56 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 [this message]
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='AANLkTikKFr1HXUR3TKMW=Rz7K3wV4kV+=9icc85CYQpo@mail.gmail.com' \
--to=andrei.formiga@gmail.com \
--cc=caml-list@yquem.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