[Development] V8 on iOS

[Ian]

Chris,

Thanks for your answer. So, the low-down is that it's not (practically) 
possible to use QML without V8, and even if V8 did have a interpreter backend, 
it would be too slow to be useable? If so, I guess I'm going to have to find a 
way to get V8 working on iOS...

<christopher.adams at nokia.com> wrote:
(04/02/2012 01:19)
>
>In summary: not very far, with v4 only.
>
>So the question is: could the dependence on v8 within QtDeclarative be changed, so that a naive JS implementation could be used instead, if v8 is not available on that platform?  Theoretically: yes.  Practically: no.  We gain a lot of advantages from tight integration with v8 (and indeed, we want to increase the tightness of that integration in order to improve performance further, eg, caching C++-side property resolution etc) and the performance of a naïve interpreter would probably be a showstopper anyway (even if v4 was improved to handle more cases than it does currently).
>
>Also, it's a huge amount of work to #ifdef out all of the v8 integration within QtQml and QtQuick currently (and even more work to use hypothetical JS-backend-abstracting APIs provided by QtJsBackend as a true JS abstraction, which would also have massive performance implications).
>