Re: [SailfishDevel] Is it worth it to use the Sailfish namespace functions/functions defined in sailfishapplicatoin.cpp instead of creating a QML/QtQuick application the default way?

Hi, the MDeclarativeCache used by sailfishapplication.cpp is supposed to give you a boost at application startup. Besides that sailfishapplication.cpp contains a few more optimizations (e.g. rendering flags for the graphics view). Its purpose is about the same as the qmlapplicationviewer from Harm

Re: [SailfishDevel] Is it worth it to use the Sailfish namespace functions/functions defined in sailfishapplicatoin.cpp instead of creating a QML/QtQuick application the default way?

Hi Superpelican When programming Qt, you can mix and match QML, C++, and Javascript freely, using whichever of these that is best for the particular task you have in mind. I don't think SailfishOS changes this in any way. With your questions in mind, I ran through my major app which is ma

[SailfishDevel] Is it worth it to use the Sailfish namespace functions/functions defined in sailfishapplicatoin.cpp instead of creating a QML/QtQuick application the default way?

Are there any big benefits to using the functions/classes defined in sailfishapplication.cpp compared to just creating a "normal" QML application (by just creating a QDeclarativeView object etc.). Does doing it the Sailfish specific way give you a performance optimization advantage? When readin