Re: [SailfishDevel] where did the template sailfishapplication.cpp/h go?
W dniu 06.12.2013 11:58, Wim de Vries pisze: Hi, Just looking at the template and documentation of the latest SDK and found out that sailfishapplication.cpp and sailfishapplication.h were removed from the sources. I used to redefine them (using MyQQuickview etc.). Am I overlooking sth? Hi Wim, There were some changes in latest SDK. Both sailfishapplication.h and sailfishapplication.cpp were replaced. The intention was to simply things. Now standard template uses sailfishapp.h. You can find sailfishapp.h in your SDK path (it's not visible in your project) SailfishOS/mersdk/targets/SailfishOS-i486-x86/usr/include/sailfishapp/sailfishapp.h I think Thomas Perl can tell you more as he is the contact person for newest application templates. Regards, Filip ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] where did the template sailfishapplication.cpp/h go?
On 12/06/2013 12:34 PM, Robin Burchell wrote: Hi, They were moved into libsailfishapp so that we are easier able to roll out improvements to all applications if there’s a need. For instance, we ran into a bug with QtWayland that we had to temporarily work around in there a while ago. I would recommend *not* subclassing QQuickView (since then you won’t get some of the performance enhancements on startup that libsailfishapp provides when you use createView and so on), but if you absolutely *must* subclass QQuickView, then just don’t use createView, and subclass QQuickView directly ( new it yourself). Well, that means moving all C++ callback functions out of my inherited QQuickview ;-( Just to be sure, will SailfishApp::createView() return a QQuickView pointer ? I need to set returnedQQuickViewPointer-rootContext()-setContextProperty(myNewCPP, myNewCPPclass ); Thanks. BR, Robin On 06 Dec 2013, at 11:58, Wim de Vries wsvr...@xs4all.nl wrote: Hi, Just looking at the template and documentation of the latest SDK and found out that sailfishapplication.cpp and sailfishapplication.h were removed from the sources. I used to redefine them (using MyQQuickview etc.). Am I overlooking sth? thanks. wim ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] where did the template sailfishapplication.cpp/h go?
sure QGuiApplication *app = SailfishApp::application(argc, argv); QQuickView *view = SailfishApp::createView(); view-rootContext()-setContextProperty(view, view); view-setSource(SailfishApp::pathTo(qml/main.qml)); view-showFullScreen(); app-exec(); On 06.12.2013 18:50, Wim de Vries wrote: On 12/06/2013 12:34 PM, Robin Burchell wrote: Hi, They were moved into libsailfishapp so that we are easier able to roll out improvements to all applications if there’s a need. For instance, we ran into a bug with QtWayland that we had to temporarily work around in there a while ago. I would recommend *not* subclassing QQuickView (since then you won’t get some of the performance enhancements on startup that libsailfishapp provides when you use createView and so on), but if you absolutely *must* subclass QQuickView, then just don’t use createView, and subclass QQuickView directly ( new it yourself). Well, that means moving all C++ callback functions out of my inherited QQuickview ;-( Just to be sure, will SailfishApp::createView() return a QQuickView pointer ? I need to set returnedQQuickViewPointer-rootContext()-setContextProperty(myNewCPP, myNewCPPclass ); Thanks. BR, Robin On 06 Dec 2013, at 11:58, Wim de Vries wsvr...@xs4all.nl wrote: Hi, Just looking at the template and documentation of the latest SDK and found out that sailfishapplication.cpp and sailfishapplication.h were removed from the sources. I used to redefine them (using MyQQuickview etc.). Am I overlooking sth? thanks. wim ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
