From: skaller <skaller@maxtal.com.au>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: ohl@hep.tu-darmstadt.de, caml-list@inria.fr
Subject: Re: Preferred GUI Toolkit for O'Caml 3?
Date: Wed, 23 Feb 2000 00:39:27 +1100 [thread overview]
Message-ID: <38B2918F.84D822A0@maxtal.com.au> (raw)
In-Reply-To: <20000222104602Q.garrigue@kurims.kyoto-u.ac.jp>
Jacques Garrigue wrote:
>
> From: Thorsten Ohl <ohl@hep.tu-darmstadt.de>
>
> > I soon have to do major surgery (= an almost complete rewrite) on a
> > graphical user interface, currently in O'CamlTK.
> >
> > Since retargeting to incompatible GUIs is such a boring job, I'd like
> > to hear which toolkit do you see in your tea leafs as the future
> > toolkit of choice?
>
> I answer for the two libraries I'm concerned with.
>
> > - LablTK [ (+) more convenient than O'CamlTK
> > (+) part of O'Caml 2.99 ]
>
> This is now an integral part of the ocaml distribution, available on
> both Unix and Windows (in ocaml 3.00). The interface should be stable
> in the future, making it a good choice if portability and
> maintainability matter.
>
> > - lablgtk [ same a mlgtk, plus
> > (-) still beta
> > (+) appears(!) to have the slickest API ]
>
> Beta does mainly mean that it may undergo API changes in the future.
> It is already good enough for writing applications. The next version
> will also support Windows.
> This is a good choice if appearance matters, and you are ready to
> eventually suffer a bit with API changes.
I would beg to differ with this analysis: Tk has some nice widgets,
like the text widget, which are _much_ better than GTK's rather woeful
offering. However, GTK has a tree widget, and while GTK is under
development
-- which is a disadvantage -- it is also under development -- which is
an advantage :-)
Tk is reasonably stable .. but dead. It is also sssllllloooowwwww under
Windows.
IMHO: use Tk if it is enough, and GTK for projects with a serious
future.
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net
next prev parent reply other threads:[~2000-02-22 14:10 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
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 [this message]
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=38B2918F.84D822A0@maxtal.com.au \
--to=skaller@maxtal.com.au \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=ohl@hep.tu-darmstadt.de \
/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