3 ms·
> The only downside is if your app is the first qt app installed on an ios / android device, it forces a download of the shared libraries which are quite large.
by lukifer 13y ago
> The only downside is if your app is the first qt app installed on an ios / android device, it forces a download of the shared libraries which are quite large.
How does this get around sandboxing on iOS? My fuzzy understanding is that components would need to be downloaded for each app independently. And is there a reason those shared libraries can't be bundled?
- zanny 13y agoNo idea, never tried it. A cursory browsing of qt documentation suggests it can't, and it also can't use qtquick2, which is where qml becomes really useful (which is also when it starts using v8).
- sho_hn 13y agoThat's incorrect. QML has used v8 since its initial appearance in Qt4. In fact, it will move away from v8 in Qt 5.2 is the current plan.
- zanny 13y agohttp://blog.qt.digia.com/blog/2013/03/05/qt-for-ios-preview/ http://blog.qt.digia.com/blog/2013/03/05/qt-for-ios-preview/ According to the qt blog, only qtquick2 depends on v8.
- sho_hn 13y agoYou're right, sorry - replacing JavaScriptCore with v8 indeed only happened for Qt 5. However, v8 is indeed on the way out again, as mentioned: http://blog.qt.digia.com/blog/2013/04/15/evolution-of-the-qml-engine-part-1/ http://blog.qt.digia.com/blog/2013/04/15/evolution-of-the-qm...