From: Sebastien Ferre <Sebastien.Ferre@irisa.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml-java + lablgtk2
Date: Wed, 14 Mar 2012 18:34:15 +0100 [thread overview]
Message-ID: <4F60D697.7070206@irisa.fr> (raw)
In-Reply-To: <A28524A8-583D-449E-9E3D-FA5CCD45BB36@x9c.fr>
On 03/09/2012 06:48 PM, forum@x9c.fr wrote:
>>> I am considering developping an OCaml
>>> application using Lablgtk2 for the GUI,
>>> and using ocaml-java/Nickel for calling
>>> a Java library (namely, OWL-API). I am
>>> working on Linux.
>>>
>>> Has anybody tried this ? I am a bit afraid
>>> of potential dependency problems...
>>
>> This cannot work. ocaml-java is running in a JVM, but lablgtk2 is
>> written for the standard runtime, and assumes standard conventions for
>> the C bindings it needs.
>
> A first option would be to use a Java toolkit to develop the GUI
> (AWT, Swing, SWT…).
I forgot to mention it, but I already have a lablgtk2 GUI,
which I want to reuse in a different setting.
> I have spent quite a lot of time lately on OCaml-Java and made
> some important improvements. Performances are now quite
> acceptable (always faster than OCaml bytecode and "not so far"
> from native code), and it is possible to call Java libraries without
> using Nickel.
>
> However, it is still now clear when OCaml-Java 2.0 will be released ;
> moreover, it will be of "alpha" quality at first.
OK, this is still good to know.
Regards,
Sébastien Ferré
prev parent reply other threads:[~2012-03-14 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 13:58 Sebastien Ferre
2012-03-08 14:12 ` Gerd Stolpmann
2012-03-09 14:09 ` Sebastien Ferre
2012-03-09 15:53 ` CHAAR Rabih
2012-03-09 16:06 ` Stefano Zacchiroli
2012-03-09 22:31 ` Sebastien Ferre
2012-03-09 17:48 ` forum
2012-03-14 17:34 ` Sebastien Ferre [this message]
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=4F60D697.7070206@irisa.fr \
--to=sebastien.ferre@irisa.fr \
--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).