Re: [Development] C++ QML Interface thoughts

2015-01-20 Thread techabc
I don't think so. for example, the GUI of the qt creator, can purely implemented by qml? and, if I will developa GUI like visual studio, can I use qml instead of c++? 2015-01-21 2:33 GMT+08:00 Tomaz Canabrava : > > > On Tue, Jan 20, 2015 at 3:32 PM, techabc wrote: > >> Is there any plans to com

Re: [Development] C++ QML Interface thoughts

2015-01-20 Thread Tomaz Canabrava
On Tue, Jan 20, 2015 at 3:32 PM, techabc wrote: > Is there any plans to complite QT QUICK for desktop as QWidgets as well? > It already is. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] C++ QML Interface thoughts

2015-01-20 Thread techabc
Is there any plans to complite QT QUICK for desktop as QWidgets as well? 2015-01-07 22:11 GMT+08:00 Luke Parry : > Hi Bo, > > Thank you for your advice. I think one fault lies is my confidence of > whether QML is right for the job due to my inexperience. > > Currently my GUI is QML which is fanta

Re: [Development] C++ QML Interface thoughts

2015-01-08 Thread Luke Parry
Hi Bo, Thank you for your advice. I think one fault lies is my confidence of whether QML is right for the job due to my inexperience. Currently my GUI is QML which is fantastic but I'm still unsure on the best approach I will take for the backend. The motivation for the question is justifying the

Re: [Development] C++ QML Interface thoughts

2015-01-07 Thread Bo Thorsen
Den 06-01-2015 kl. 12:47 skrev Luke Parry: > I am having issues trying to implement a c++ qml interface/wrapper that > supports virtual overrides. Something functionally similar to > boost::python would be excellent. > > This should be generic enough to also support non-QObject classes too so > it

[Development] C++ QML Interface thoughts

2015-01-07 Thread Luke Parry
I am having issues trying to implement a c++ qml interface/wrapper that supports virtual overrides. Something functionally similar to boost::python would be excellent. This should be generic enough to also support non-QObject classes too so it rules out signals and slots. On first glance, it is fa