From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Does LablTk have a future?
Date: Mon, 29 Aug 2005 23:33:59 +0100 [thread overview]
Message-ID: <200508292333.59714.jon@ffconsultancy.com> (raw)
In-Reply-To: <4311DA63.4010104@havenrock.com>
On Sunday 28 August 2005 16:38, Matt Gushee wrote:
> Regardless of the status of Tk itself, LablTk seems to be going nowhere
It is odd that you should bring this up now. I've spent the past week writing
a simple database for a new veterinary surgery in OCaml using labltk. I had
tried lablgtk before but failed to get to grips with it. By comparison, the
labktk examples explained everything that I needed and I had a decent GUI up
and running within a few hours.
May I add another question to this thread: What do people think of OCaml's GUI
libraries in terms of stability?
> 1) A Quick Reference
>
> This document would outline (with little or no explanation) the
> complete LablTk API, including all widget commands and the possible
> values of all LablTk-specific types. Currently the latter information
> can only be obtained by digging through the source code.
>
> Actually, I wrote a LablTk quick reference some time ago. It may need
> a bit of work, but no more than a couple of hours, I'm sure. So I
> *will* do this if there is any interest at all in it.
I haven't used anything exotic (or even non-trivial) but it seems to me that
the API is already so simple that there isn't really a need for a quick
reference.
> 2) A Book
>
> This would be an in-depth tutorial on how to develop useful
> applications with LablTk. It would assume some programming
> experience, but it would not require advanced knowledge of OCaml, nor
> any knowledge of Tcl.
>
> I'm thinking to publish both a print edition and an inexpensive
> electronic edition. Though I need to research the costs a bit more, I
> believe I can offer the print edition--self-published using Print On
> Demand--at a reasonable price, comparable to what you pay for
> programming books at a bookstore (no, I don't hope to get rich off
> this--just to be modestly compensated for my efforts ;-).
I think labltk is too specific to be commercially viable. Also, unless I've
missed some hidden complexities in Tk programming, I think you'd have a job
filling enough pages to call the result a book.
However, I would be very interested in a book that described how to write GUIs
using OCaml. I'm still learning how to write and factor "conventional" GUI
code in OCaml. I have also written custom GUIs using OpenGL (via lablGL) and
OCaml is superb for this task.
As I'm the author of the only existing self-published book on OCaml, you may
be interested to know that it is doing well (~500UKP per month for 6 months
so far). So I would recommend that other people take the plunge and write
more books on OCaml.
> 3) A Community-based Modernization Project
>
> The idea here is to provide a Tk-based GUI library that is complete
> and in sync with the latest stable version of Tk. Other features that
> would be nice to have include (a) support for a few Tcl commands that
> are not strictly part of Tk, but are useful and commonly used in Tk
> programs--in particular I'm thinking of the 'after' command; and (b)
> a framework that allows downstream developers to create custom
> widgets with interfaces analogous to the builtin widgets. I'm not
> sure if (b) is feasible or not within the constraints of the OCaml
> type system--I've tried and failed in the past--but I imagine
> there's some way to do it.
>
> Two other interrelated questions are whether this project should be
> done in parallel with LablTk or as a replacement, and whether the
> LablTk API should be preserved or something new designed. But it's
> probably not necessary to decide these questions immediately.
I think it would be more constructive to create a decent cross-platform GUI
library from the ground up for FPLs/OCaml. This wouldn't need to be anything
fancy, just easy access to the simplest GUI elements to start with. I'd like
to see GUIs described by purely functional data structures. I'm still
factoring my current code so I'll let you know what I come up with. Also,
despite GUI code being a pedagogical example for OO, I'm not yet convinced
that OO adds anything useful.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-08-29 22:36 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 15:38 Matt Gushee
[not found] ` <aefe758210f7fa0b9846b0ea4278cf3a@rouaix.org>
2005-08-28 23:21 ` [Caml-list] " Matt Gushee
2005-08-29 22:33 ` Jon Harrop [this message]
2005-08-30 4:39 ` Matt Gushee
2005-08-30 11:39 ` Yaron Minsky
2005-08-30 11:48 ` Jon Harrop
2005-08-30 12:22 ` David MENTRE
2005-08-30 13:45 ` Jon Harrop
2005-08-30 15:47 ` David MENTRE
2005-08-30 16:08 ` Jon Harrop
2005-09-01 4:25 ` Matt Gushee
2005-09-01 11:20 ` Matt Gushee
2005-09-01 11:26 ` Matt Gushee
2005-09-01 14:09 ` Chris Campbell
2005-08-30 16:21 ` Bardur Arantsson
2005-08-30 17:47 ` [Caml-list] " David Thomas
2005-08-30 18:06 ` Tyler Eaves
2005-08-30 19:01 ` Jon Harrop
2005-08-30 22:55 ` Chris Campbell
[not found] ` <c22844d10508301553b54841b@mail.gmail.com>
2005-08-30 22:56 ` Fwd: " Chris Campbell
2005-08-30 23:04 ` Doug Kirk
2005-08-31 0:08 ` Fwd: " Jon Harrop
2005-08-31 0:31 ` Olivier Andrieu
2005-08-31 8:48 ` Feeding the OCaml GUI troll (was: Re: [Caml-list] Does LablTk have a future?) David MENTRE
2005-08-31 9:06 ` Proposal a GUI from Ocamlsdl Christophe Raffalli
2005-08-31 14:39 ` [Caml-list] " Jon Harrop
2005-09-01 19:27 ` Nathaniel Gray
2005-08-31 14:27 ` Feeding the OCaml GUI troll (was: Re: [Caml-list] Does LablTk have a future?) Jon Harrop
2005-09-01 4:49 ` Feeding the OCaml GUI troll Matt Gushee
2005-09-01 13:15 ` [Caml-list] " skaller
2005-09-01 13:28 ` David MENTRE
2005-09-01 13:50 ` skaller
2005-09-01 14:43 ` Chris Campbell
2005-09-02 7:40 ` Ville-Pertti Keinonen
2005-09-02 12:39 ` skaller
2005-09-03 10:34 ` Damien Bobillot
2005-09-03 12:30 ` skaller
2005-09-04 14:08 ` Richard Jones
2005-09-03 11:10 ` yoann padioleau
2005-09-03 11:30 ` Jonathan Roewen
2005-09-03 17:23 ` Doug Kirk
2005-09-04 14:01 ` Richard Jones
2005-09-01 19:23 ` Feeding the OCaml GUI troll (was: Re: [Caml-list] Does LablTk have a future?) Nathaniel Gray
2005-09-01 4:31 ` [Caml-list] Does LablTk have a future? Matt Gushee
2005-09-01 4:17 ` Matt Gushee
2005-09-01 13:25 ` Jon Harrop
2005-08-30 7:16 ` GUI for OCaml (was: Re: [Caml-list] Does LablTk have a future?) David MENTRE
2005-08-30 9:53 ` GUI for OCaml Christophe Raffalli
2005-08-30 10:28 ` [Caml-list] " David MENTRE
2005-08-30 13:04 ` Bünzli Daniel
2005-08-30 17:13 ` David Thomas
2005-08-30 11:18 ` Mark Shinwell
2005-08-30 14:22 ` Jacques Carette
2005-08-30 23:12 ` Pietro Abate
2005-08-30 14:14 ` GUI for OCaml (was: Re: [Caml-list] Does LablTk have a future?) Richard Jones
2005-08-30 15:33 ` mmzeeman
2005-08-30 15:44 ` Jon Harrop
2005-08-30 22:34 ` yoann padioleau
2005-09-01 4:58 ` Matt Gushee
2005-08-30 16:01 ` Jon Harrop
2005-08-30 16:25 ` Chris Campbell
2005-08-30 22:49 ` yoann padioleau
2005-08-30 16:03 ` Chris Campbell
2005-08-30 22:31 ` yoann padioleau
2005-08-31 8:19 ` About Lablgtk2 (was: e: GUI for OCaml) David MENTRE
2005-09-03 11:41 ` yoann padioleau
2005-08-30 17:35 ` [Caml-list] Does LablTk have a future? Olivier Andrieu
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=200508292333.59714.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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