From: Eray Ozkural <exa@kablonet.com.tr>
To: Matt Gushee <matt@gushee.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Tcl/Tk and RH 9
Date: Mon, 11 Aug 2003 04:20:53 +0300 [thread overview]
Message-ID: <200308110420.53523.exa@kablonet.com.tr> (raw)
In-Reply-To: <20030811004129.GB32383@swordfish>
On Monday 11 August 2003 03:41, Matt Gushee wrote:
> > GTK on the other hand, isn't the top notch toolkit out there. The
> > technically superior toolkit is Qt *grin*
>
> Hmph. I suppose. I personally don't care for it because it's very slow
> on older machines, and causes XFree86 to lock up on some. Then there's
> the licensing issue on Windows. But better-designed? I guess it probably
> is.
With GTK, I would worry about its object model, library design, hack-ability,
platform-independence.... The design of gtk seems fairly "backwards" to me. I
remember how bad the C++ bindings were and I don't think the situation has
changed much. This is not to say Qt would be a better "choice" for ocaml
because that too is designed with an imperative PL with a not-very-cool type
system: C++. However, it is more effective in that domain as evidenced by
existing code...
It is now going to sound "bold" to you people, but I don't understand why you
can't write the ultimate portable GUI toolkit in ocaml itself. With a
language as generic as ocaml it should be a no-brainer to efficiently
abstract over peculiarities of windows systems.
Besides, you will find that the limitations of those C/C++ based systems will
be severe. I can make an educated guess because I was designing an ocaml
binding for KDE... If you decide on some kind of binding to a "high level"
toolkit like gtk it's going to be some abstraction layer over black boxes
with a lot of quirks, it's not going to be pretty.
Regards,
--
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara KDE Project: http://www.kde.org
www: http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://mp3.com/ariza
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-------------------
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
next prev parent reply other threads:[~2003-08-11 1:21 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 [this message]
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
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=200308110420.53523.exa@kablonet.com.tr \
--to=exa@kablonet.com.tr \
--cc=caml-list@inria.fr \
--cc=erayo@cs.bilkent.edu.tr \
--cc=matt@gushee.net \
/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