caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: William Chesters <williamc@paneris.org>
Cc: caml-list@inria.fr
Subject: Re: Preferred GUI Toolkit for O'Caml 3?
Date: Wed, 23 Feb 2000 10:24:46 +0100	[thread overview]
Message-ID: <20000223102446.A24835@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <200002221141.LAA08806@toy.william.bogus>; from williamc@paneris.org on Tue, Feb 22, 2000 at 11:41:06AM +0000

On Tue, Feb 22, 2000 at 11:41:06AM +0000, William Chesters wrote:
> Benjamin C. Pierce writes:
>  > We in the Unison group are also about to embark on a major UI redesign
>  > and have been wondering which toolkit to use.  Besides Thorsten's
>  > points, there are two more that are critical concerns for us:
>  > 
>  >    * seamless portability (Unix and Win32)
>  >    * ability to build statically linked binaries (this is a pretty
>  >      big drawback to the Tk-based solutions)
>  > 
>  > Comments on these points as well as the others would be very useful. 
> 
> There's always QT.  It's nice to work with (at least in C++), very
> widely used and comprehensive (because of KDE), and was written from
> the start to be cross-platform (X & Win).  NB it is uncontroversially
> free these days.

But there are no ocaml bindings of it today, so unless someone write some,
they don't are a candidate for an ocaml programmer.

Sure you can always write your interface in C++, and then write binding to
call ocaml function in the callbacks, but it is so nicer to write all
entirely in ocaml. passing ocaml functions as data to callbacks is very nice
to do a lot of thing that would be more complicated using other languages.

What would be nicest would be a toolkit entirely written in ocaml, but i guess
we will not have such a thing in a long time.

One of the advantages of gtk+ (no qt/gtk+ flamewar please) is that it was
designed from the start to support multiple languages binding, in particular
functional ones also, altough they thought mostly of lisp like stuff, wanting
to link with guile.

Friendly,

Sven LUTHER




  parent reply	other threads:[~2000-02-23 17:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-18 13:54 Thorsten Ohl
2000-02-21 17:22 ` Benjamin C. Pierce
2000-02-22 11:41   ` William Chesters
2000-02-23  7:36     ` Alan Schmitt
2000-02-23  9:24     ` Sven LUTHER [this message]
2000-02-24 10:24       ` Fabrice Le Fessant
2000-02-25 16:22         ` skaller
2000-02-22 13:41   ` skaller
2000-02-22 14:22     ` Benjamin C. Pierce
2000-02-22  1:46 ` Jacques Garrigue
2000-02-22 13:39   ` skaller
2000-02-22 20:13     ` Gerd Stolpmann
2000-02-22  8:17 ` Sven LUTHER
2000-02-22 11:04 ` jean-marc alliot
2000-02-22 17:05 ` Pascal Cuoq

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=20000223102446.A24835@dpt-info.u-strasbg.fr \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=williamc@paneris.org \
    /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).