From: skaller <skaller@ozemail.com.au>
To: erayo@cs.bilkent.edu.tr
Cc: Matt Gushee <matt@gushee.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Re: Tcl/Tk and RH 9
Date: 11 Aug 2003 12:02:06 +1000 [thread overview]
Message-ID: <1060567325.7474.66.camel@localhost.localdomain> (raw)
In-Reply-To: <200308110420.53523.exa@kablonet.com.tr>
On Mon, 2003-08-11 at 11:20, Eray Ozkural wrote:
> With GTK, I would worry about its object model, library design, hack-ability,
> platform-independence.... The design of gtk seems fairly "backwards" to me.
Me too, though I can't claim great familiarity with it.
> 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.
Yeah, that's a good question. The answer is probably: we could,
but who is going to finance it? Building GUI toolkit is a rather
large job (its difficult enough to *wrap* a toolkit).
> 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.
Sure, but where does one bind? To Xlib? To the X protocol directly?
If you bind that deep, how do you handle a Windows port of the library?
I personally think most widget kits are pretty bad, they're the wrong
idea altogether, especially the stupid callback/event loop paradigm.
I'd be happy to paint buttons myself, etc if the drawing and event
management tools existed in a standard form.
The problem, I think, is that they dont: its actually easier to
standardise widget functionality in the face of distinct underlying
drawing/event primitives/models. But I could be wrong, this isn't my
area of expertise.
OTOH: a portable clean standard Ocaml GUI would be a killer app..
it would make Ocaml the language of choice for deploying user
interfaces and GUI applications.
-------------------
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 2:02 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 [this message]
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=1060567325.7474.66.camel@localhost.localdomain \
--to=skaller@ozemail.com.au \
--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