From: Kakadu <kakadu.hafanana@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Interfacing with QtQuick 2.0 from Qt5, RFC
Date: Wed, 31 Jul 2013 20:04:05 +0400 [thread overview]
Message-ID: <CAGmVoG0j2Vtb+BxY4Cqfd8e4NAajNFz_7c3mJ7M4s=o2XeDqvw@mail.gmail.com> (raw)
In-Reply-To: <20130709145845.GA25897@frosties>
QtQuick runtime allowsinterfacing only using QObject subclasses.
That's why I force user to write API in file and than I generatae C++
and Ocaml sources to use them in interfacing with QtQuick. Some C++
code is needed but I don't need to write it, it's autogenerated (like
C++ moc tool does).
Kakadu
On Tue, Jul 9, 2013 at 6:58 PM, Goswin von Brederlow <goswin-v-b@web.de> wrote:
> On Sat, Jun 01, 2013 at 10:16:13PM +0400, Kakadu wrote:
>> Hey!
>>
>> 'Hello world' tutorial have become longer and more copy-pastable. See you
>> on github pages: http://kakadu.github.io/lablqt/qtquick-helloworld.html
>>
>> RFC
>>
>> Best wishes,
>> Kakadu
>
> At the start you say that no c++ is needed and ocaml code is connected
> directly to QtQuick. Then later you say `Controller_c.h`,
> `Controller_c.cpp` and `Controller.ml` will be generated.
>
> So what is it now? Is that c++ code just a unused side product of the
> moc compiler?
>
> MfG
> Goswin
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2013-07-31 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 10:18 Kakadu
2013-05-09 10:22 ` Fabrice Le Fessant
2013-05-09 18:31 ` Kakadu
2013-06-01 18:16 ` Kakadu
2013-07-09 14:58 ` Goswin von Brederlow
2013-07-31 16:04 ` Kakadu [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='CAGmVoG0j2Vtb+BxY4Cqfd8e4NAajNFz_7c3mJ7M4s=o2XeDqvw@mail.gmail.com' \
--to=kakadu.hafanana@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
/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).