[Interest] QtQuick for mobile - any experience to share?

[ekke]

Am 02.06.18 um 18:46 schrieb Jason H:
> I never noticed the differnce On AES encryption, the iOS devices were
> faster, but in terms of Qt, I did not observe anything notable.
>  
> > In Qt, do you know how costly is the bridge?
> It's usually C++/ObjC or C++/JNI, so it's fast.
>  
> > how fast is V4 vs javascriptcore?
> It's not terrible. And it's getting better all the time. Note that the
> "proper way" is to do it all in C++ and only use QML for glue code,
> not to write a lot of app logic in it. (I don't think anyone follows
> that though)
I'm always trying ;-)
while developing I'm doing many things in QML because it's easy done
but later the final code I always try to 'move' as much as possible from
QML to C++ to publish performant Apps
(this year I'm doing again the QtWorldSummit Conference App and will try
only to have some glue code in QML)
BTW: started Qt for mobile apps with BB10 Cascades and first I learned
from Cascades developers at BlackBerry to do as much as possible in C++
>  
> I understood that the native objects are only communicating with the
> js via the signal/slot right. How would you compare it with RN? 
> No, sometimes you do direct API. Like for wake locks, notifications,
> etc. But 99% of the time, you just roll that into a C++ QObject and
> expose that to QML, so it's highly re-usable and use signals and
> slots. So it doesn't matter where you can use it, from QML or C++...
>  
>  
> *Sent:* Saturday, June 02, 2018 at 4:37 AM
> *From:* "Sylvain Pointeau" <sylvain.pointeau at gmail.com>
> *To:* "Jason H" <jhihn at gmx.com>
> *Cc:* "Vlad Stelmahovsky" <vladstelmahovsky at gmail.com>, interest
> <interest at qt-project.org>
> *Subject:* Re: [Interest] QtQuick for mobile - any experience to share?
> On Wed, 30 May 2018 at 20:38, Sylvain Pointeau
> <sylvain.pointeau at gmail.com <mailto:sylvain.pointeau at gmail.com>> wrote:
>
>     I have still not made any decision yet, I am doing some testing to
>     get a better idea. Thanks a lot so far to all for your feedback.
>
>  
> I investigated into React Native, as I know Qt quick by reading a lot
> about it and trying time to time through the years.
>  
> RN has 3 parts: the js, the native and the bridge. 
>  
> the native is specific for a plateform, objective c for ios and java
> for android
> the js is with javascriptcore but without the jit on ios
> the bridge is basically a serialisation, I read that this is the most
> costly.
>  
> the js and the native are asynchrone so every call between them must
> be returned by a callback or with a future
>  
> so if I need something in my app that requires something special, long
> calculation, threads, queued database writes, it will probably require
> the native and I will have to write it for each platform.
>  
> I have some pain to see how fast is the js, I also heard that Android
> is much slower than ios. Did you observe that with Qt?
>  
> In Qt, do you know how costly is the bridge? how fast is V4 vs
> javascriptcore? I understood that the native objects are only
> communicating with the js via the signal/slot right. How would you
> compare it with RN? 
>  
>
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20180602/8148ec67/attachment.html>