caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] A labltk book?
Date: Sat, 13 Oct 2007 15:43:04 +0100	[thread overview]
Message-ID: <200710131543.04954.jon@ffconsultancy.com> (raw)
In-Reply-To: <348721.45512.qm@web54604.mail.re2.yahoo.com>

On Friday 12 October 2007 22:58:42 Dario Teixeira wrote:
> > you have to go via C so it's much work and the available tools to do the
> > automagically aren't good enaugh to do it  (ok, there is swig, but I
> > don't like  the way the binding is generated).
> > There exists the smoke project, it a lib to interface qt and python or
> > ruby use it to bind to qt (and the next perl qt will also you smoke).
> > Maybe that'a
>
> I reckon that native bindings might therefore prove nearly impossible!
> Two alternate routes have occurred to me though.  The first involves
> the Ocaml-Java project and Qt-Jambi bindings (basically Qt on the JVM):

The LablGTK2 bindings to GTK2 by Jacques Garrigue et al. are simply superb 
(robust, efficient and easy to use):

  http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html

SooHyoung Oh has kindly written an awesome tutorial about LablGTK2:

  http://compiler.kaist.ac.kr/~shoh/ocaml/lablgtk2/lablgtk2-tutorial/

> The second route involves the OCamIL project (OCaml on .NET) and
> the Qyoto/Kimono bindings (Qt/KDE bindings for .NET):

Might I suggest that using Microsoft's F# and Microsoft's Windows Forms 
from .NET is an infinitely saner way to approach GUI programming on 
Microsoft's platforms. :-)

Only now that I'm working on Java and Scala code in Eclipse have I come to 
appreciate the awesome combo that F#'s VS mode and Windows Forms provide. 
Although the final GUI code is similar in size between LablGTK/OCaml and 
F#/Windows Forms, developing code in Visual Studio is vastly easier because 
Intellisense lets you explore APIs graphically with no effort.

I would dearly love to see a GUI IDE for OCaml written in OCaml that combined 
simplicity with such a rich form of information throwback.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  parent reply	other threads:[~2007-10-13 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12  4:50 Jeff Shaw
2007-10-12  6:43 ` [Caml-list] " Jon Harrop
     [not found]   ` <aee06c9e0710121142p50cb3e17x369afc7f9661f3c6@mail.gmail.com>
2007-10-12 18:43     ` Nathaniel Gray
2007-10-12 18:47   ` Eric Cooper
2007-10-12 20:03     ` Dario Teixeira
2007-10-12 20:13       ` Michael Wohlwend
2007-10-12 21:58         ` Dario Teixeira
2007-10-13  9:42           ` forum
2007-10-13 10:15           ` forum
2007-10-13 14:43           ` Jon Harrop [this message]
2007-10-13 20:29             ` Nathaniel Gray
2007-10-12 20:23       ` Brian Hurt
2007-10-12 22:30         ` skaller
2007-10-13 10:11           ` Mattias Engdegård
     [not found] <20071014100005.94A63BC6C@yquem.inria.fr>
2007-10-14 12:21 ` Pascal Cuoq
2007-10-15 20:54   ` Nathaniel Gray

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=200710131543.04954.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.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;
as well as URLs for NNTP newsgroup(s).