Hello, I would like community opinions about the need of QML semi-automatic wrapping and to know if it’s planned as future Qt internal roadmaps..
My basic idea was to use QT MetaModel in order to do the same as cppintrospection [google.fr]…
But QML seamed quite promising in order to bring both wrapping and graphical boxing
So I develop some kind of preprecompiler (before moc) that read cpp headers and generates customisable QMLplugin code in order to handle:
-Nodal logic ( via config file:copy/paste+fx ambiguities leverage)
-Pointer life cycle ( via config file: handle smartpointer/normalpointer)
-Native object boxing (put native object in QT boxes)
-QML method wrapping (not finished..I’m doing it by hand for the moment)
I tryied to explain a test case applying code generation to OpenSceneraph library on the website osg4noob.olympe.in but it’s not very technically detailled….(and written in French)
Here’s a video rush
http://youtu.be/yAYs5-lYj7k
So the purpose of the underlying tool is not restricted to osg but almost all cpp libraries (without twisted stuff…ex: I have some grammar problems parsing Bullet headers)
So Before you tell it “Yes, the interface is ugly” because osg is my testbench and I have lower level things to do like improve the generated code for ex…
Here’s an incomplete external reference about something near to what i’m doing (https://www.qtdeveloperdays.com/2013/sites/default/files/presentation_pdf/QtDevDaysSFO-2013_WrappingCppForQml_final.pdf)
↧
