From: Christoph Bauer <c_bauer@informatik.uni-kl.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Tcl/Tk and RH 9
Date: Mon, 11 Aug 2003 11:41:42 +0200 [thread overview]
Message-ID: <m3ekzs5y5l.fsf@diebuntekuh.de> (raw)
In-Reply-To: <200308110420.53523.exa@kablonet.com.tr> (Eray Ozkural's message of "Mon, 11 Aug 2003 04:20:53 +0300")
Eray Ozkural <exa@kablonet.com.tr> writes:
> 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.
It's just too boring to create another platform independent GUI toolkit.
What about to extend lablgtk through camlp4 quotations so that
something like the following line is possible:
let window = << Button ~label:"Quit" ~callback:GMain.Main.quit >>
(equivalent to Tcl/Tk code:
pack [button .b -text Quit -command quit])
or
let editor_window =
<< VBox
[Menu ["File" ["Open" ~callback:open;
"Save" ~callback:save];
"Help" ["About" ~callback:about]];
text = Text ~width:80 ~height:24;
HBox [Button ~label:"Open" ~callback:open;
Button ~label:quit ~callback:Main.quit]] >>
The Camlp4 had to
* create implizit the window widget
* generate unused symbols (like the button name)
but export the widget "text"
* generate packing (vbox#add)
Such code is better to maintain and it needs less time
to write. What do you think?
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
next prev parent reply other threads:[~2003-08-11 9:39 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 [this message]
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=m3ekzs5y5l.fsf@diebuntekuh.de \
--to=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