Browse thread
[Caml-list] version 7 beta typing change?
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Christoph Bauer <c_bauer@i...> |
| Subject: | Re: [Caml-list] Re: Tcl/Tk and RH 9 |
Hi,
>>
>> RedHat is free to decide whatever they want, but Tk is still the
>> simplest way to develop some software. Tcl/Tk itself is in version
>> 8.4, it had unicode support earlier than Gtk, and is still under
>> active development, and I see no need to kill it.
>
> 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.
> Second, whilst the widgets it supports are good, its widget set is
Text widget and canvas widget are great.
> 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
--
proc self {} {foreach c [split [info body self] ""] d {14 -7 0 0 4 -67 4 73 11
69 24 -83 -15 6 -4 -84 78 20 11 -78 -1 -1 79 19 -8 4} { binary scan $c c c
if {[catch {append r [format %c [expr $c+$d]]}]} {return $r};}};puts [self]
-------------------
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