caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: A labltk book?
Date: Thu, 18 Oct 2007 05:19:46 +0100	[thread overview]
Message-ID: <200710180519.46748.jon@ffconsultancy.com> (raw)
In-Reply-To: <47155912.6010403@gushee.net>

On Wednesday 17 October 2007 01:36:34 Matt Gushee wrote:
> Could be ... some time ago (2 years, maybe?) I proposed the idea of (me)
> writing a book on LablTk; there was very little response, favorable or
> otherwise, but at least one person thought it would be nice to have a
> book on GUI programming in OCaml, perhaps including LablTk but with
> greater emphasis on LablGTK. Even if I had agreed with the idea, at that
> time I had little experience with (Labl)GTK. But I don't agree with the
> idea: you could write a book about GUI *design*, but that should be
> neither toolkit-specific nor language-specific. On the other hand, a
> book about GUI programming techniques in a specific language will
> probably appeal mainly to people with specific projects in mind, which
> implies that they probably want to learn one good GUI toolkit ... which
> in the case of OCaml would have to be LablGTK.

I'll write OCaml Journal articles covering GUI programming using LablGTK. 
There is already one very nice example in there (Sudoku solver) but there's 
plenty of scope for more complicated applications with more widgets, 
threading and so forth.

> I realize Tk is progressing and making some much-wanted improvements,
> but to me it seems like too little, too late.

I certainly get that feeling but I'm not a Tk man myself.

> As for Jon's idea, sure, great! But I wonder if any major publisher
> would take it on. After all, O'Reilly *has* an introductory OCaml book;
> it would need to be updated and translated, but that's still much easier
> than creating a new one. Yet they don't seem interested in doing that.
> So some brave soul might have to self-publish something.

Actually, I was reading a blog entry recently where someone from O'Reilly 
explicitly stated that they are interested in publishing more books on OCaml. 
You could easily strip out any deprecated stuff from their current 
(unpublished) book and publish it. I would certainly buy a copy...

With the current uptake of OCaml in industry (and the productization of F#), I 
think there will be ample market for OCaml teaching material, including 
books.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  parent reply	other threads:[~2007-10-18  4:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 16:42 Jeff Shaw
2007-10-15 17:30 ` [Caml-list] " Jon Harrop
2007-10-17  0:36   ` Matt Gushee
2007-10-17  2:33     ` skaller
2007-10-18  4:17       ` Jon Harrop
2007-10-18  3:18     ` Dave Benjamin
2007-10-18  4:19     ` Jon Harrop [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-12 22:23 Jeff Shaw
2007-10-15  1:42 ` [Caml-list] " Matt Gushee
2007-10-15  8:01   ` Christoph Bauer
2007-10-15  8:19     ` Jon Harrop

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=200710180519.46748.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;
as well as URLs for NNTP newsgroup(s).