The reason why Google doesn't use V8 on iOS is that the Apple restriction is
that their JS engine must be used to run any JS that is downloaded from the
net.
That is an issue for a web browser, but not a sand-boxed application. In any
case, you'd use Qt's embedded resources for your JS, so Appl
It's completely possible (in theory) to get V8 working on "stock" iOS. Just
non-trivial. The problem is that V8 tries to allocate memory with RWX
permissions (which stock iOS doesn't support). V8 needs to allocate with RW,
and
then change to RX when it wants to execute that code. This works (th
Just an FYI, as of today, V8 has been ported to and is running successfully on
iOS. It currently requires a "jail break", but it is (theoretically) possible
to
get it running on a "stock" device without breaking any Apple App Store rules...
The problem is that iOS does not allow RWX protections
On quarta-feira, 12 de dezembro de 2012 18.31.47, Trismer Technologies wrote:
>
>Does anyone has information about roadmap of Qt5 for iOS ? Digia promises
> this port in next year but I'd like to know how the current blockers will
> be removed: the most important one - V8 javascript for iOS
haven't looked at it much yet), that it would be fairly obvious
as to where the memory protection stuff would need to go in V8?
Thiago Macieira wrote:
(04/02/2012 15:25)
>On segunda-feira, 2 de abril de 2012 16.17.35, Ian wrote:
>> Hmmm, so from what I understand, there may be a b
ril de 2012 13.02.08, aaron.kenn...@nokia.com wrote:
>> Hi,
>>
>> On 02/04/2012, at 2:21 PM, ext Ian wrote:
>> > Chris,
>> >
>> > Thanks for your answer. So, the low-down is that it's not (practically)
>> > possible to use QML without V8
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...
wrote:
(04/02/2012 01:19
Apologies for the repost, wrong subject used.
>This[1] is not the ABI that is used?
>
>[1]
>http://developer.apple.com/library/ios/documentation/Xcode/Conceptual/iPhoneOSABIReference/iPhoneOSABIReference.pdf
I have enough information about the ABI to know that it's similar to (but not
the same a
>This[1] is not the ABI that is used?
>
>[1]
>http://developer.apple.com/library/ios/documentation/Xcode/Conceptual/iPhoneOSABIReference/iPhoneOSABIReference.pdf
I have enough information about the ABI to know that it's similar to (but not
the same as) EABI (IIRC IOSABI uses an additional registe
hout GUI, Declarative or OpenGL, then that
may be a starting point at least, because IMHO there's no point in starting a
platform plugin until this issue is resolved.
Thanks for your input,
Ian
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
e you just are paying
developers to give competitors a leg up in competing with you. That return
would be help in maintaining said features (and in this case, Qt's QA). Very
little of what has been done in Scrivener would have been accepted into the 4
series so we didn't even look
e you just are paying
developers to give competitors a leg up in competing with you. That return
would be help in maintaining said features (and in this case, Qt's QA). Very
little of what has been done in Scrivener would have been accepted into the 4
series so we didn't even look
12 matches
Mail list logo
