From: "Jeffrey Loren Shaw" <shawjef3@msu.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] labltk for tk 8.4 BETA release
Date: Sat, 12 May 2007 10:37:47 -0400 [thread overview]
Message-ID: <E1HmsjE-0007z5-8P@sys15.mail.msu.edu> (raw)
* ease of installation
http://downloads.activestate.com/ActiveTcl/Windows/8.3.5/
or for the beta labltk...
http://downloads.activestate.com/ActiveTcl/Windows/8.4.14/
Yup that link should be updated. I don't think it should be bundled with
ocaml, however. The end-user might already have it installed, or might not
need it. But this is a decision for the ocaml devs.
* Documentation
You're right, it's not very good. I used the ocamlbrowser extensively to
learn how to use labltk. It took me a lot of experimenting, and I'm still
terrible at getting widgets laid out the way I want.
I'm not sure how to do the documentation in an automated way without
changing the grammar for widgets.src to allow ocamldoc comments. That's
beyond my abilities, but I suppose it's a worthy project for someone. On the
other hand, widgets.src is already very cluttered.
* Other libraries
I don't know anything about these, but again these are questions for the
ocaml devs.
Anyway, my focus right now is getting this beta version of labltk working
correctly... there's a lot of functions to test.
Now here's an idea...
Instead of documenting labltk, which is difficult for the beginner ocaml
programmer anyway, make a wrapper to make it more ocaml-y. I'm not sure if
this would be easy or possible, but coercing labltk into one style of
programming (preferably functional) could go a long way towards making it
easier to learn for the beginner. Also the wrapper would potentially be
easier to document. As I recall, the most difficult aspects of labltk are
those that are imperative, eg:
event functions are unit -> unit, (maybe this can't be avoided)
pack is difficult to deal with,
the need to use optionmenu and Textvariable.handle together is not obvious
Another huge but useful project would be a type-safe parser for the outputs
given by the Widget.configure_get functions.
Now back to testing.
next reply other threads:[~2007-05-12 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 14:37 Jeffrey Loren Shaw [this message]
2007-05-14 21:48 ` David Teller
2007-05-15 8:08 ` Richard Jones
2007-05-18 12:35 ` David Teller
-- strict thread matches above, loose matches on Subject: below --
2007-05-12 2:56 Jeffrey Loren Shaw
2007-05-12 9:19 ` [Caml-list] " David Teller
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=E1HmsjE-0007z5-8P@sys15.mail.msu.edu \
--to=shawjef3@msu.edu \
--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