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
Hi,
On 02/04/2012, at 3:04 PM, ext marius.storm-ol...@nokia.com wrote:
> On 02/04/2012 08:06, ext Thiago Macieira wrote:
>> On segunda-feira, 2 de abril de 2012 13.02.08,
>> aaron.kenn...@nokia.com wrote:
>>> On 02/04/2012, at 2:21 PM, ext Ian wrote:
Chris, Thanks for your answer. So, the lo
Too many technical terms that I don't have (or want) intimate understanding
of...
:/
What I'm going to take away from this discussion is that it is expensive and
complex to implement anything other than what there is right now, and if any
work would be done on that in the forseeable future, it
On segunda-feira, 2 de abril de 2012 16.17.35, Ian wrote:
> Hmmm, so from what I understand, there may be a bytecode backend for V8 at
> some point (for platforms like MIPS for example), but that work hasn't
MIPS has opted instead to write an assembler backend.
The effort would have to be for yet
On segunda-feira, 2 de abril de 2012 14.04.24, marius.storm-ol...@nokia.com
wrote:
> > I don't think Apple will ever allow that. I don't think Apple will
> > allow executing any code that isn't loaded strictly from disk.
>
> What do they use themselves for their own webkit JS engine?
Probably Java
Hmmm, so from what I understand, there may be a bytecode backend for V8 at some
point (for platforms like MIPS for example), but that work hasn't begun in any
way other than "maybe some time in the future", and even if it was decided to
implement that, it's quite some time off.
AFAIK Apple blo
On 02/04/2012 08:06, ext Thiago Macieira wrote:
> On segunda-feira, 2 de abril de 2012 13.02.08,
> aaron.kenn...@nokia.com wrote:
>> 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, and e
On segunda-feira, 2 de abril 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, and even if V8 did have a interpreter
> >
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, 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
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
Hi,
>> At this point, I'm either looking for an alternative to V8
>
> This is more of an follow-up question for the list than a reply:
>
> QtDeclarative includes the V4 javascript interpreter that (as far as I know)
> can
> handle simple javascript expressions. How far can you get with V4
On Mar 30, 2012, at 2:54 PM, ext Ian wrote:
At this point, I'm either looking for an alternative to V8
This is more of an follow-up question for the list than a reply:
QtDeclarative includes the V4 javascript interpreter that (as far as I know)
can handle simple javascript expressions. How far
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
On 03/30/2012 02:24 PM, Ian wrote:
> There is another (possibly even bigger) issue in the ARM BI used by Apple on
> iOS.
> It's not EABI (which AFAIK V8 on ARM is written for), and it's not even
> documented AFAIK, so even though it's similar to EABI (from what I've seen so
> far), it's not the
Hi all,
The first tentative steps for getting iOS support into Qt5 have been made (
really it's only a few small patches to get the build working - there's nothing
it could be used for yet). There's a possible issue with running any Javascript
interpreter on iOS (IIRC one of the App Store rules
18 matches
Mail list logo
