I tried on an iPhone 3GS and I don't see the performance problems.
Maybe in the 3G the processor has problems keeping up when trying to
perform an Ajax request and do a transition at the same time,
depending on how much you're doing. Can you try delaying your request
until the trainsition is done?
What I do see is a lot of flashing during transitions. Could be a bug
in the rendering engine. Could you please file a bug (bugreport.apple.com
) and attached a minified reproducible case? Just take out as much
stuff as you can while the problem still reproduces and attach the
dashcode project.
Also, is this with Dashcode 2.x?
Daniel
On Jul 10, 2009, at 8:55 AM, John Maxwell wrote:
Developing on the iphone 3.0 release (non-beta) sdk
I've been working on a web app that makes it easy to browse the
MARTA (Atlanta's public transit) schedule on mobile phones. For the
iPhone interface, I decided to implement it with Dashcode because it
offered the slick native-iphone-looking UI.
The first cut of Dashcode UI was essentially a modified "Browser"
template with three list views. It's the view that you browse to http://rideatl.com
with your iphone or iphone simulator. For the first big revision
to this interface, I was looking at adding help screens and a intro/
splash page. So I decided to nest the browser inside another stack
layout. The overall layout is organized something like this
Top Stack Layout
- Intro view
- Help view
- Schedule Stack Layout
--- Terminals Selection view
--- Terminal view
--- Run view
I started developing this revision on the 2.2.1 sdk, and hit some
bumps that resulted in me joining this list, submitting an email (http://lists.apple.com/archives/safari-iphone-web-dev//2009/Jun/msg00013.html
), and eventually filing a bug report with Apple. These issues were
fixed in the iPhone 3.0 sdk, but I mention it because I've seen some
wonkiness with nested layouts. (If you have the patience to read the
aforementioned long, detailed post, you'll see that one of the
things that was causing the problems was nested layouts).
Anyway, now what I'm seeing is bumpiness and flickering in
transitions between my views, and sometimes even just scrolling up
and down a view. In some cases AJAX requests are being sent in
between the transitions, so you'd of course expect to see some
asyncronous refreshing. That's the kind of thing that I see and
accept in Dashcode UI that is currently live. That's not what I'm
talking about though. I'm talking about jerkiness and poor
performance animating the transitions between views that already
have their data loaded. The particularly bad transition is when
going from the Intro view to the Terminals Selection view by
clicking the big "Jump to the schedule" arrow on the Intro view. In
this case, the AJAX request to populate the data in the Terminal
Selection View has already been populated via a call in the load()
method. This jerkiness occurs in both the iphone simulator and on a
real iphone 3G (running 3.0). And then even the transition from the
Terminal Selection view to the Terminal view is pretty jerky;
whereas it really isn't in the release Dashcode UI that just uses a
single stack layout.
I've made the latest cut of this Dashcode UI accessible here: http://rideatl.com/iphone_beta/index.html
Could someone check this on their iPhone hardware and see what
they think? Also, could you compare that to the release UI
accessible here: http://rideatl.com/ ? Are nested stack layouts a
known performance killer? What would you recommend?
thanks,
john
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Safari-iPhone-Web-Dev mailing list (email@hidden
)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Safari-iPhone-Web-Dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
