Is the same code faster in the device's web browser? Most likely a Sencha
issue.
--
Michael
Forget the emulator. It _is_ terribly slow, not comparable to an actual
device. I gave up testing in the emulator unless when I needed to test
screen resolutions or Android versions I don't have on a device.
--
Michael
Sencha does take a few seconds to initially render from my experience.
But is pretty fast after this. I believe u can customise the actual
build stripping out components u dont use. Which in theory should
speed things up.
Also only suitable for higher end android os 2.2
Sent from my iPhone
> --
> You received this message because you are subscribed to the Google
> Groups "phonegap" group.
> To post to this group, send email to phon...@googlegroups.com
> To unsubscribe from this group, send email to
> phonegap+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/phonegap?hl=en?hl=en
>
> For more info on PhoneGap or to download the code go to www.phonegap.com
What device? I've been running an app on a ZTE Blade (2.1, 600MHz), and
it's really slow. But it would fly on the HTC Desire (2.2) or Samsung
Galaxy S (2.1).
--
Michael
--
You received this message because you are subscribed to the Google
Groups "phonegap" group.
To post to this group, send email to phon...@googlegroups.com
To unsubscribe from this group, send email to
phonegap+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/phonegap?hl=en?hl=en
For more info on PhoneGap or to download the code go to www.phonegap.com
.x-panel { -webkit-backface-visibility: hidden; }
it could be that transitions are too much for the older phones to handle.
i use jqtouch and it runs pretty good on my motorola droid 1