caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kakadu <kakadu.hafanana@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] lablqt = OCaml + qt
Date: Thu, 22 Sep 2011 13:57:24 +0400	[thread overview]
Message-ID: <CAGmVoG133FoKKVq2f-_sO=SFSUg2By9ZLirfHNCWuMNRmqyBzA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

Hello!

I'm working on Qt bindings for OCaml. You can browse my code at
https://github.com/Kakadu/lablqt

Now qtjambi parses Qt's header files and generates an XML representation of
API. Then binding generator generates OCaml and C++ code of bindings.

Now a big part of Qt's API is stored in aaa.xml, so you don't need to
install qtjambi's generator. Big part of QtCore и QtGui is incapsulated in
this xml file.

You can use build.ml script to compile lablqt. Btw, lablqt depends on
janestreet's core_extended library.

You can see test examples in test_gen/test* directories. For examle:
https://github.com/Kakadu/lablqt/blob/master/test_gen/test5/main.ml

I've implemented almost type-safe connections from signals to slots. Also
I've created tool <https://github.com/Kakadu/lablqt/tree/master/moc>to
simplify creating of user-defined slots: you can connect them like
here<https://github.com/Kakadu/lablqt/blob/master/test_gen/test4/main.ml#L27>
and write your code separately
<https://github.com/Kakadu/lablqt/blob/master/test_gen/test4/UserSlots.ml#L2>
.

Lablqt is compilable only on a few number of machines, so I'll be glad if
you test it on your computer.

It's difficult to me to decide in what direction Qt bindings should be
developed. I you have any ideas or recommendations, I'll be glad to read
them.

Best wishes,
Kakadu

[-- Attachment #2: Type: text/html, Size: 1653 bytes --]

             reply	other threads:[~2011-09-22  9:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22  9:57 Kakadu [this message]
2011-11-24 14:04 ` [Caml-list] " Kakadu
2011-11-24 14:50   ` Jérémie Dimino

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='CAGmVoG133FoKKVq2f-_sO=SFSUg2By9ZLirfHNCWuMNRmqyBzA@mail.gmail.com' \
    --to=kakadu.hafanana@gmail.com \
    --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).