From: Richard Jones <rich@annexia.org>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] WxWidgets?
Date: Thu, 16 Sep 2004 21:25:11 +0100 [thread overview]
Message-ID: <20040916202511.GA24789@annexia.org> (raw)
In-Reply-To: <4149F2D0.7040408@ntlworld.com>
[-- Attachment #1: Type: text/plain, Size: 2148 bytes --]
On Thu, Sep 16, 2004 at 09:08:48PM +0100, chris.danx wrote:
> Hi,
>
> Was looking on the web for an alternative to using GTK+ on Windows (no
> flames please) and found WxWidgets. It looks like a quite nice GUI
> toolkit. There seemed to be some interest in developing a OCaml binding
> via Swig according to the net, but I can't find any such binding.
>
> Has anyone made such a binding? If not I was thinking about using swig
> and the wxpython interfaces as the starting point for a wxwidgets
> binding for ocaml. Has anyone tried to do this in the past? Any
> thoughts on the issue?
I've looked into this in the past, but we ended up using Gtk +
Gtk-Wimp on Windows, which worked quite well. Here are my
observations on going the WxWindows route though:
(1) WxWindows is pretty good. (Ah, looking at their website, I see
they've renamed it to WxWidgets!). WxWIDGETS is pretty good. It's a
very complete way to develop cross-platform applications. In
particular, it has platform-specific file and print dialogs, which you
won't get if you use Gtk. In fact if you use Gtk you won't get print
dialogs at all - I had to write my own print dialog for Windows which
was no fun at all.
(2) There seem to be three decent approaches to using WxWidgets under
OCaml: Python, Perl or native. Native is going to be the best, but is
going to take a heck of a lot of effort.
(3) Python or Perl: it's easiest just to use PyCaml or Perl4Caml to
interface with the Wx* libraries under those languages. I don't see
why you'd want to go through SWIG for this.
(4) Native: definitely the best performance and the cleanest approach,
however it's lots of work. (Now of course if you wanted to *hire*
Merjis to do the work, contact me off-list ... :-)
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
"One serious obstacle to the adoption of good programming languages is
the notion that everything has to be sacrificed for speed. In computer
languages as in life, speed kills." -- Mike Vanier
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-16 20:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 20:08 chris.danx
2004-09-16 20:25 ` Richard Jones [this message]
2004-09-16 21:29 ` chris.danx
2004-09-16 21:39 ` Richard Jones
2004-09-16 22:00 ` Daan Leijen
2004-09-17 0:06 ` SooHyoung Oh
2004-09-17 4:39 ` skaller
2004-09-17 7:13 ` Daan Leijen
2004-09-17 8:04 ` Jean-Marc EBER
2004-09-19 21:46 ` François-Xavier HOUARD
2004-09-16 23:58 ` chris.danx
2004-09-17 8:10 ` Richard Jones
2004-09-17 12:38 ` Olivier Andrieu
2004-09-17 13:11 ` chris.danx
2004-09-17 13:51 ` skaller
2004-09-17 18:31 ` Brian Hurt
2004-09-17 7:53 ` Benedikt Grundmann
2004-09-16 20:44 ` Micha
2004-09-16 20:56 ` Basile STARYNKEVITCH
2004-09-20 1:02 ` [Caml-list] WxWidgets? - wxcaml SooHyoung Oh
2004-09-21 23:21 ` Zeno
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=20040916202511.GA24789@annexia.org \
--to=rich@annexia.org \
--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;
as well as URLs for NNTP newsgroup(s).