On Wednesday 05 November 2008, Jérémie Dimino wrote: > Jon Harrop <[EMAIL PROTECTED]> writes: > > I'd forget about that and just focus on making the whole of Qt4 available > > safely from OCaml in any form first. Even this is an unsolved problem in > > the OCaml world! > > I suggest an idea. I know that Qt4 offer some facility to export > objects trough DBus [1]. So one can write a small C++ application that > allow other applications to create Qt objects and export them, then > use Qt in ocaml via DBus. > > Here are the advantages i see: > > - the C++ code and the ocaml code would run in different processes, so > we do not have to care about all the C++isms of Qt in the ocaml > application. > > - this would make Qt available to any languages that have DBus. > For ocaml i am currently writing a pure ocaml DBus implementation [2].
The biggest problem is that this limits you to what's exposed by Qt's signal/slot interface. That's too little to actually use Qt but for very simple applications that pass either relatively simple data types around, or pass QObjects around. If you want to create and pass something less-than-simple, say a QList<> of some custom type, you're screwed and this functionality is necessary for any real Qt interoperability. Cheers, Kuba _______________________________________________ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
