From: Pierre Weis <Pierre.Weis@inria.fr>
To: luther@dpt-info.u-strasbg.fr (Sven LUTHER)
Cc: caml-list@inria.fr
Subject: Re: OCaml's long range graphical direction?
Date: Wed, 7 Feb 2001 22:30:10 +0100 (MET) [thread overview]
Message-ID: <200102072130.WAA13125@pauillac.inria.fr> (raw)
In-Reply-To: <20010206191902.B11976@lambda.u-strasbg.fr> from Sven LUTHER at "Feb 6, 101 07:19:02 pm"
[...]
> > I expect the Caml-TK interface to be supported (and included in the
> > standard OCaml distribution) for quite a while, but not actively
> > developed.
The original Camltk (which is slightly different from labl/tk) is also
used and supported by Jun and me. It is stable and works very well.
As Xavier mentioned (and as the Caml examples at
http://pauillac.inria.fr/caml/Examples/oc/camltk demonstrate) Caml/tk
is a must for simple GUIs (with a slightly simpler than MMM way of
abusing of the text widget).
[...]
> and a gtk+ one. Both are aimed at different uses, and well, as
> Pierre said the tcl/tk bindings are not so much work, as they are
> following a stable tcl/tk. (well sortof, don't know exactly what
> it's status is with regard of the different tcl/tk versions. is
> anything above 8.0 supported ?)
Camltk is maintained up to date: it works also with the 8.3 version of
tcl/tk, including for the Caml Light version of the library.
[Personnal alleluia and auto compliment]
The Caml team's support to Caml users is decidedly incredibly good:
we effectively maintain what we promised to maintain :)
> > > To what degree does threading affect the answer?
> >
> > No idea. I've heard plenty of claims that multithreading helps
> > building good GUIs (see e.g. BeOS), yet most popular GUIs (including
> > TK and I think GTK too) seem to manage fine without multithreading.
>
> Well, from Jacques message, gtk+ is thread safe, while tcl/tk is not.
>
> Now i don't know if that helps a lot. Personnally i don't use threads when
> writing GUIs, and am still strugling with modules and functors for it ...
> Sven Luther
As Sven, I don't use threads for writing GUIs.
Friendly,
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/
next prev parent reply other threads:[~2001-02-07 22:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 17:48 Daniel Ortmann
2001-02-06 9:28 ` Xavier Leroy
2001-02-06 18:19 ` Sven LUTHER
2001-02-07 21:30 ` Pierre Weis [this message]
2001-02-08 7:32 ` Sven
2001-02-08 1:59 ` Jacques Garrigue
2001-02-08 7:55 ` Sven
2001-02-09 8:47 ` Claudio Sacerdoti Coen
2001-02-09 10:00 ` Sven LUTHER
2001-02-08 20:35 ` Brian Rogoff
2001-02-09 1:28 ` Jacques Garrigue
2001-02-09 18:11 ` Brian Rogoff
2001-02-10 13:01 ` Jacques Garrigue
2001-02-09 20:01 ` Marcin 'Qrczak' Kowalczyk
2001-02-12 14:52 ` Nicolas barnier
2001-02-12 23:47 ` Jacques Garrigue
2001-02-15 12:21 ` [Caml-list] " Sven LUTHER
2001-02-08 10:28 ` Alan Schmitt
2001-02-09 1:24 ` bcpierce
2001-02-06 20:30 ` Dale Arntson
2001-02-07 0:39 ` John Max Skaller
2001-02-08 20:01 ` Francois Rouaix
2001-02-09 9:41 ` Sven LUTHER
2001-02-09 9:49 ` Jacques Garrigue
2001-02-09 19:58 ` Jerome Vouillon
2001-02-10 12:36 ` Jacques Garrigue
2001-02-10 21:25 ` Pierre Weis
2001-02-09 17:50 ` John Max Skaller
2001-02-06 19:33 Maxence
2001-02-09 23:31 Arturo Borquez
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=200102072130.WAA13125@pauillac.inria.fr \
--to=pierre.weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.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