From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] WxWidgets?
Date: Thu, 16 Sep 2004 22:56:51 +0200 [thread overview]
Message-ID: <20040916205651.GA7343@ours.starynkevitch.net> (raw)
In-Reply-To: <4149F2D0.7040408@ntlworld.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 2001 bytes --]
On Thu, Sep 16, 2004 at 09:08:48PM +0100, chris.danx wrote:
> 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 is also the FOX toolkit www.fox-toolkit.org which claims also to be
both on Unix & Windows. It is a nice (cross-platform) GUI toolkit (in C++)
also (but there is no Ocaml binding to it).
> 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?
If there is a Python binding to it already, you might also consider coding a
WXwidget "server" by coding (in C) the few hooks to make a program using
WxWidgets which listen on a pipe (or whatever the Windows equivalent is) for
Python instructions, and sending back (to your application) some textual
protocol. I already coded this in GUIS (see
http://starynkevitch.net/Basile/guisdoc.html for more) for GTK2 (and you can
borrow some code if you like).
IMHO, the costly coding is to interface all the WXWidget API. If it has been
done once (for Python) you might try reusing it - either with Swig (for
Ocaml) or by pluggin a python interpreter. The GUI could even (as GUIS
suggest) run in a different process than your Ocaml application.
NB: I've got no knowledge on Windows, and no significant experience with
Swig or WxWidgets. So take all above with several grains of salt.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net
aliases: basile<at>tunes<dot>org = bstarynk<at>nerim<dot>net
8, rue de la Faïencerie, 92340 Bourg La Reine, France
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-09-16 20:48 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
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 [this message]
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=20040916205651.GA7343@ours.starynkevitch.net \
--to=basile@starynkevitch.net \
--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).