From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: Feeding the OCaml GUI troll (was: Re: [Caml-list] Does LablTk have a future?)
Date: Wed, 31 Aug 2005 15:27:43 +0100 [thread overview]
Message-ID: <200508311527.44346.jon@ffconsultancy.com> (raw)
In-Reply-To: <3d13dcfc05083101487092acd5@mail.gmail.com>
On Wednesday 31 August 2005 09:48, David MENTRE wrote:
> Well, in option (1), as somebody else underlined it, it is a lot more
> than just skinning. How do you handle i18n and l10n issues? How to
> display bidirectionnal languages? How to write Arabic, Hebrew or
> Chinese characters? How to take input in Japanese or Tamil? How to
> handle copy/paste and drag & drop with other applications of the
> platform? Or to print PDF with Arabic and Indian characters in the
> same document?
Those features would require a substantial amount of work for either (1) or
(2), AFAIK.
> Maybe you don't have those issues for you local market, Jon. But as
> soon as you are writting graphical applications to be used worldwide,
> those issues are coming out pretty quickly. This is at least a
> requirement for my application.
Then your requirements are quite different from my own and, I believe, many
other people's. To start with, I am just interested in a minimal working
library that would let me knock up simple applications. Cross-platform drag
and drop is way down the line...
> I really fear your under estimate the amount of work needed to
> accomplish such a job. And the OCaml community seems pretty fragmented
> on this GUI front.
If you're talking about supporting all languages and all features on all
platforms then of course it is an enormous undertaking. From my point of
view, that is such a difficult task that it simply isn't worth discussing. I
believe we can only do a decent job if we attack a small problem.
> ...
> 3. (Jon option) write a pure GUI from scratch, in pure OCaml. A
> project similar to Qt or WxWidgets for C++. It seems doable to have a
> basic GUI but handling all i18n and desktop interoperability issues
> seems pretty complicated;
If you're talking about my option (2) then it is more like GLUI and not like
Qt and wxWindows.
--
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-31 15:24 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 15:38 Does LablTk have a future? Matt Gushee
[not found] ` <aefe758210f7fa0b9846b0ea4278cf3a@rouaix.org>
2005-08-28 23:21 ` [Caml-list] " Matt Gushee
2005-08-29 22:33 ` Jon Harrop
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 ` Jon Harrop [this message]
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=200508311527.44346.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