address bar hiding on ios/safari

[maitriyogin]

Hi, setting mblHideAddressBar and mblAlwaysHideAddressBar to true hides the address bar. However the containers are not resized to with the new space. It seems that the layout is done before the address bar is hidden.. Any ideas? Cheers, Stephen.

[cjolif]

other comment from Stephen:

"when using a container for a scroll view it's scroll performance compared to the mobile.ScrollView is pretty bad. "

[edchat]

Hi Stephen, Thanks for reporting this, I opened the issue against dojox/app here: https://github.com/dmachi/dojox_application/issues/122

The scroll performance on ios6 has been addressed with this commit https://github.com/dmachi/dojox_application/commit/9a00b4b488d95c7b0dbe17f06012bd41e936e375 which is in the latest in the 1.8 branch and will be included in 1.8.2 . And this commit which is in trunk/master and will be in 1.9: https://github.com/dmachi/dojox_application/commit/167336257acd85608ce415b13b9f3ce025c5b5ac

[maitriyogin]

Hi Ed, Huge thanks for the reply! I'll try out the scroll with the latest commit as soon as. Although, we did test it on iOS5, but it was worse on ios6. We really love the structure that the app in forces but kind of need the performance of just a standard dojox.mobile app with widgets. Do you think we should hold off dojos.app until it gets released in 2.0? Many thanks, Stephen.

On 11/3/12 18:14 , "Ed Chatelain" notifications@github.com<mailto:notifications@github.com> wrote:

Hi Stephen, Thanks for reporting this, I opened the issue against dojox/app here: dmachi/dojox_application#122https://github.com/dmachi/dojox_application/issues/122

The scroll performance on ios6 has been addressed with this commit dmachi/dojox_application@9a00b4bhttps://github.com/dmachi/dojox_application/commit/9a00b4b488d95c7b0dbe17f06012bd41e936e375 which is in the latest in the 1.8 branch and will be included in 1.8.2 . And this commit which is in trunk/master and will be in 1.9: dmachi/dojox_application@1673362https://github.com/dmachi/dojox_application/commit/167336257acd85608ce415b13b9f3ce025c5b5ac

— Reply to this email directly or view it on GitHubhttps://github.com/cjolif/dojo-todo-app/issues/102#issuecomment-10041527.

[edchat]

Hi Stephen, dojox/app is still experimental, so it is likely that the apis will be changing some going forward, and it is not that surprising that you may find issues like the one you ran into here with things like layout. But I am not aware of any issues (other than the scrolling on ios6) where you will have performance problems with dojox/app with dojox/mobile compared to using dojox/mobile without dojox/app. In either case you will want to setup a dojo build for your app if you have not already done so. And in the 1.9 release we are planning to add support to make setting up a build for dojox/app very easy based upon the config.
So for me, the question on whether or not to use dojox/app would probably boil down to your tolerance for api changes, and whether or not the layout support is flexible enough for your needs. Regards, Ed

[maitriyogin]

Hi Ed, Many thanks for the prompt reply. Well, it's a tough one, we love the dojox/app structure and would like to keep to it, we're testing 1.8.2 just now to see if we can get a performance boost on the scroll, but we haven't managed to create a build yet. I'm guessing the build will boost performance even more but any ideas how much? In short we really want to stick, to dojox/app and are not too worried about api changes, lets hope 1.8.2 does the trick. One thing that I should mention is that we're using dojox.mobile.ScrollableView instead of dojox/app/widgets/Container, is there a preferred? Cheers, Stephen.

On 11/5/12 15:21 , "Ed Chatelain" notifications@github.com<mailto:notifications@github.com> wrote:

Hi Stephen, dojox/app is still experimental, so it is likely that the apis will be changing some going forward, and it is not that surprising that you may find issues like the one you ran into here with things like layout. But I am not aware of any issues (other than the scrolling on ios6) where you will have performance problems with dojox/app with dojox/mobile compared to using dojox/mobile without dojox/app. In either case you will want to setup a dojo build for your app if you have not already done so. And in the 1.9 release we are planning to add support to make setting up a build for dojox/app very easy based upon the config.

So for me, the question on whether or not to use dojox/app would probably boil down to your tolerance for api changes, and whether or not the layout support is flexible enough for your needs. Regards, Ed

— Reply to this email directly or view it on GitHubhttps://github.com/cjolif/dojo-todo-app/issues/102#issuecomment-10071934.

[edchat]

Hi Stephen, I am not sure how much the build will improve performance, but it should be significant.
Regarding dojox.mobile.ScrollableView vs. dojox/app/widgets/Container, if you take a look at this new dojox/app test dojox/app/tests/scrollableTestApp/ you will see scrollable tests using both. But note that the comments on the main page, (although the last problem listed related to i0s6 has been fixed), specifically the problems with ScrollableView and orientation changes. So given that problem which has not been addressed at this time I would recommend you use dojox/app/widgets/Container.

[edchat]

I wanted to leave a comment here that https://github.com/dmachi/dojox_application/issues/122 has been fixed.