On Sun, Apr 15, 2012 at 7:45 PM, Alan Alpert wrote:
> QtQuick 1 is not. Perhaps the iOS port could start with the QPA enabled Qt
> 4.8?
Until Apple changes iOS terms, which I personally highly doubt it's
going to happen any time soon, we will have to stay with QtQuick1
only, for iOS. So, no Scene
On Sun, 15 Apr 2012 12:04:39 ext Thiago Macieira wrote:
> On domingo, 15 de abril de 2012 08.32.54, Hai Phaikawl wrote:
> > Again, how would the "v8 on iOS" problem be solved? Falling back to the
> > good old Qt4 js intepreter??
> > QtQuick not being able on iPhone or iPad is a big loss.
>
> There
On domingo, 15 de abril de 2012 08.32.54, Hai Phaikawl wrote:
> Again, how would the "v8 on iOS" problem be solved? Falling back to the
> good old Qt4 js intepreter??
> QtQuick not being able on iPhone or iPad is a big loss.
There's currently no known solution.
QtQuick2 is too dependent on V8.
-
Again, how would the "v8 on iOS" problem be solved? Falling back to the
good old Qt4 js intepreter??
QtQuick not being able on iPhone or iPad is a big loss.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listin
