caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@ozemail.com.au>
To: Christoph Bauer <c_bauer@informatik.uni-kl.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Tcl/Tk and RH 9
Date: 12 Aug 2003 14:14:33 +1000	[thread overview]
Message-ID: <1060630629.16392.88.camel@localhost.localdomain> (raw)
In-Reply-To: <m3llu05z9c.fsf@diebuntekuh.de>

On Mon, 2003-08-11 at 19:17, Christoph Bauer wrote:

> > I do. First, it isn't threadable. 
> 
> That's neither true (configure your Tcl/Tk with --enable-threads) nor
> necessary for GUI stuff. I'm quite happy with after and fileevent
> mechanism.

It is true. Tcl is reentrant and threadable, Tk is not
and never will be .. and that's quoting its author.

If you happen, for example, to run GUI apps using
threads in Python you're in for a rude shock.

Of course most people don't run this model, even though
its by far the best way to handle certain GUI things.
Certainly better than the idiotic event loop/callback 
mechanism.

> > Second, whilst the widgets it supports are good, its widget set is
> 
> Text widget and canvas widget are great.

Agree. Tk has some superb widgets, text and canvas being
particularly excellent. But there is no tree widget,
which in todays world is untenable (yes, there is Tix).


> > not only small, it doesn't have certain crucial widgets.  There is
> > no tree widget, for example, you need Tix for that.
> >
> > The extension model is unusable. No one can write
> > Tk extensions. In the whole of its life, hardly any
> > have been written.
> >
> > OTOH, there is wide community support for Gtk.
> 
> With Tk it's much easier to create a GUI than with gtk (and even
> labtgtk). There is a project called Gnocl (gtk for Tcl)> It tries
> to combine the best of both toolkits: (loosly) modeled after the
> Tk API, but based on the better looking and more complete gtk.
> 
> regards,
> Christoph

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-08-12  4:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09  2:03 [Caml-list] version 7 beta typing change? skaller
2003-08-09 12:10 ` Jacques Garrigue
2003-08-09 16:15   ` skaller
2003-08-09 16:33   ` [Caml-list] Tcl/Tk and RH 9 skaller
2003-08-09 16:59     ` Matt Gushee
2003-08-10 15:57       ` Eray Ozkural
2003-08-10 20:18         ` skaller
2003-08-10  1:43     ` [Caml-list] " Jacques Garrigue
2003-08-10  1:53       ` Alexander V. Voinov
2003-08-10 21:26         ` skaller
2003-08-10 23:15           ` Eray Ozkural
2003-08-10 23:24             ` Eray Ozkural
2003-08-11  0:41             ` Matt Gushee
2003-08-11  1:20               ` Eray Ozkural
2003-08-11  2:02                 ` skaller
2003-08-11  8:38                   ` Sven Luther
2003-08-11  9:41                 ` Christoph Bauer
2003-08-10 20:15       ` skaller
2003-08-11  9:17         ` Christoph Bauer
2003-08-12  4:14           ` skaller [this message]
2003-08-10 22:11     ` [Caml-list] " Olivier Andrieu
2003-08-10 22:45       ` Matt Gushee
2003-08-10 23:16         ` Eray Ozkural
2003-08-11  1:33         ` skaller
2003-08-12  7:11 [Caml-list] " Jason Gibson

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=1060630629.16392.88.camel@localhost.localdomain \
    --to=skaller@ozemail.com.au \
    --cc=c_bauer@informatik.uni-kl.de \
    --cc=caml-list@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).