From: "forum@x9c.fr" <forum@x9c.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] A labltk book?
Date: Sat, 13 Oct 2007 11:42:14 +0200 [thread overview]
Message-ID: <4D4FF5DB-A749-400E-8508-AB9618AE1409@x9c.fr> (raw)
In-Reply-To: <348721.45512.qm@web54604.mail.re2.yahoo.com>
Le 12 oct. 07 à 23:58, Dario Teixeira a écrit :
> Hi,
>
>> you have to go via C so it's much work and the available tools to
>> do the
>> automagically aren't good enaugh to do it (ok, there is swig, but
>> I don't
>> like the way the binding is generated).
>> There exists the smoke project, it a lib to interface qt and
>> python or ruby
>> use it to bind to qt (and the next perl qt will also you smoke).
>> Maybe that'a
>
>
> I reckon that native bindings might therefore prove nearly impossible!
> Two alternate routes have occurred to me though. The first involves
> the Ocaml-Java project and Qt-Jambi bindings (basically Qt on the
> JVM):
>
> http://ocamljava.x9c.fr/
> http://trolltech.com/products/qt/jambi
>
> The second route involves the OCamIL project (OCaml on .NET) and
> the Qyoto/Kimono bindings (Qt/KDE bindings for .NET):
>
> http://www.pps.jussieu.fr/~montela/ocamil/index.html
> http://cougarpc.net/qyoto/
>
> We've seen recent annoucements concerning the Ocaml-Java project,
> so I reckon this route might already be feasible or will be so in
> the near future. As for route #2, I don't know the current status
> of OCamIL, so it's hard to say.
>
> Has anyone given any of these routes a try? Perhaps the developers
> of Ocaml-Java or OCamIL would like to share their thoughts?
Well, I never used Qt, so I can't compare what I propose below to
neither Qt nor Jambi.
Using OCaml-Java, you can quite easily access Java Swing by two ways :
- use Nickel (http://nickel.x9c.fr/) to generate OCaml-to-Java
bindings from
an xml file describing the classes you are interested in ;
- use the Cadmium-SwiXml subproject (http://cadmium.x9c.fr/) that
provides
bindings to the SwiXml framework (http://www.swixml.org/) - SwiXml
allows
GUI rendering from an xml description.
Of course, using OCaml-Java may rise performance issues.
If this is a concern, I would consider compiling the "GUI part" using
OCaml-Java
while having the "engine part" compiled with ocamlopt. Then the two
parts could
be glued together in a client/server setting, using marshalling of
values.
Hope this helps,
Xavier
PS: using Nickel, you can of course generate bindings to other
toolkits (e.g. SWT)
next prev parent reply other threads:[~2007-10-13 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 4:50 Jeff Shaw
2007-10-12 6:43 ` [Caml-list] " Jon Harrop
[not found] ` <aee06c9e0710121142p50cb3e17x369afc7f9661f3c6@mail.gmail.com>
2007-10-12 18:43 ` Nathaniel Gray
2007-10-12 18:47 ` Eric Cooper
2007-10-12 20:03 ` Dario Teixeira
2007-10-12 20:13 ` Michael Wohlwend
2007-10-12 21:58 ` Dario Teixeira
2007-10-13 9:42 ` forum [this message]
2007-10-13 10:15 ` forum
2007-10-13 14:43 ` Jon Harrop
2007-10-13 20:29 ` Nathaniel Gray
2007-10-12 20:23 ` Brian Hurt
2007-10-12 22:30 ` skaller
2007-10-13 10:11 ` Mattias Engdegård
[not found] <20071014100005.94A63BC6C@yquem.inria.fr>
2007-10-14 12:21 ` Pascal Cuoq
2007-10-15 20:54 ` Nathaniel Gray
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=4D4FF5DB-A749-400E-8508-AB9618AE1409@x9c.fr \
--to=forum@x9c.fr \
--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