On Tuesday 14 July 2015 20:34:21 John C. Turnbull wrote:
> It's well known that iOS does not support executable memory which means that
> any scripting language would not be able to use a JIT compiler.
>
> Given this, wouldn't it mean that Qt's JavaScript implementation would run
> like a one legg
That would be a technical case, not a business one.
> Sent: Tuesday, July 14, 2015 at 7:11 AM
> From: "Robert Iakobashvili"
> To: "Gian Maxera"
> Cc: "interest@qt-project.org"
> Subject: Re: [Interest] Performance of Qt scripting on iOS
>
> N
Not about JS/QML performance, but my Qt widget-based apps on iOS are
very fast where
long operations on new iOS devices are about twice faster (average for
several long operations)
than on latest Android devices of the same class.
Note, that the same apps on iPad Air-2 is about 10 times faster tha
Yes … that’s the reason. Of course having only a dual core does not help.
To avoid bad user experience, I wrap the delegates into Loader items, or the
whole view into a Loader, and I create a fast overlay displaying a “Loading”
message that disappear when the Loader complete to load everything.
Is that the reason for the sluggish performance of Qml delegate instantiation?
My app runs awesomely on Android but no on iOS. Specially regarding ListView
delegate installation process. It completely hangs. I have always thought that
the main reason was the fact that the Android device is a qua
