Opened 8 years ago

Closed 6 years ago

#14234 closed enhancement (invalid)

Dojox.Mobile : Please improve view transitions

Reported by: mc007ibi Owned by: mc007ibi
Priority: high Milestone: 1.9
Component: DojoX Mobile Version: 1.7.0b1
Keywords: Cc:
Blocked By: Blocking:

Description

Hi,

regardless how my app is structured, build or optimized, when I click just on "Back" it last over 1.5 seconds before anything happens(iOS). Also moving into a complete cached view with nothing inside its pretty slow compared with Sencha. I am just comparing it with Sencha to let you know that it is possible to improve.

Please don't laugh about the 1.5 second delay but I showed the mobileGallery and our app to users and they also say, its not smooth and makes a bad impression in general.

Is there anything I can do by self ?

I checked with the Safari profiler and figured out that dojo.setStyle and dojo.setClass is called a few hundred times when moving into a new view. When i move into a cached view, its just around 100 times.

On iPad its around 800ms. On iPhone 3GS and iPhone 4 and iPhone 4S it has just the same speed of 1.5 - 2.0 secs.

On low-budget Android tablets its even 2-4 seconds. On better tablets its like on iPad.

In used in my test enviroment custom, dynamic and cached and empty views but there is really no noticable difference.

Any suggestions are welcome ! In the meantime, I am rewriting the dojox.mobile.View class and removed as much I could. I also figured out that the bottleneck seems to be in the button classes.

Thanks a lot, Guenter.

Change History (5)

comment:1 Changed 8 years ago by Chris Mitchell

Owner: set to ykami

comment:2 Changed 8 years ago by ykami

Component: GeneralDojoX Mobile

What about this test case?
http://archive.dojotoolkit.org/nightly/checkout/dojox/mobile/tests/test_iPhone-Animation.html
Do you also see such a bad performance?

comment:3 Changed 7 years ago by bill

Milestone: tbd

comment:4 Changed 6 years ago by dylan

Milestone: tbd1.9
Owner: changed from ykami to mc007ibi
Status: newpending

Need more info on this, or else we'll assume it's been resolved by the recent work over the past year.

comment:5 Changed 6 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.