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