Comments on: More Glassy Scrolling with UITableView http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/ Defender of Corporate Headquarters Sun, 11 Jul 2010 13:50:39 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Alfredo http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/comment-page-1/#comment-154812 Alfredo Sat, 21 Feb 2009 18:33:48 +0000 http://www.fieryrobot.com/blog/?p=111#comment-154812 <p>sorry what's the _item.identifier? O.o?</p> sorry what’s the _item.identifier? O.o?

]]> By: mike http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/comment-page-1/#comment-147820 mike Mon, 12 Jan 2009 21:21:24 +0000 http://www.fieryrobot.com/blog/?p=111#comment-147820 <p>I hope you can create a post on how to make a UIScrollView respond to touches and swipes at the same time and still scroll like glass... I am trying to figure out how to implemente touchesbegan, touchesmoved, touchesended and scrollViewDidScroll on the same controller. I have subclassed UIScrollView but it stopped scrolling like glass... very frustrating...</p> I hope you can create a post on how to make a UIScrollView respond to touches and swipes at the same time and still scroll like glass… I am trying to figure out how to implemente touchesbegan, touchesmoved, touchesended and scrollViewDidScroll on the same controller. I have subclassed UIScrollView but it stopped scrolling like glass… very frustrating…

]]> By: Ed http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/comment-page-1/#comment-147186 Ed Fri, 09 Jan 2009 04:08:38 +0000 http://www.fieryrobot.com/blog/?p=111#comment-147186 <p>Is there more or less room in said shared memory?</p> Is there more or less room in said shared memory?

]]> By: Andrew Ebling http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/comment-page-1/#comment-147054 Andrew Ebling Thu, 08 Jan 2009 11:41:47 +0000 http://www.fieryrobot.com/blog/?p=111#comment-147054 <p>Try using a layer rather than a bitmap images. Layers get cached in the shared video memory, whereas bitmaps do not.</p> Try using a layer rather than a bitmap images. Layers get cached in the shared video memory, whereas bitmaps do not.

]]> By: Ed http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/comment-page-1/#comment-144706 Ed Wed, 24 Dec 2008 18:10:15 +0000 http://www.fieryrobot.com/blog/?p=111#comment-144706 <p>Yeah, this will definitely fail miserably if you have a lot of rows. As mentioned, it's a rather extreme approach. Definitely better suited for data sets where you know the size will be relatively small (1-200 items).</p> <p>In the end, I didn't end up using this solution myself (mostly because I had some sharing issues), but I couldn't see a lot of user-noticeable performance improvement in the end after playing with it turned on and off.</p> <p>But I do know that there are other products that use an ever more extreme case of this: they buffer the entire view into a giant scrollable bitmap. The performance is super-smooth, but clearly they can't deal with variable length tables without making the phone explode.</p> Yeah, this will definitely fail miserably if you have a lot of rows. As mentioned, it’s a rather extreme approach. Definitely better suited for data sets where you know the size will be relatively small (1-200 items).

In the end, I didn’t end up using this solution myself (mostly because I had some sharing issues), but I couldn’t see a lot of user-noticeable performance improvement in the end after playing with it turned on and off.

But I do know that there are other products that use an ever more extreme case of this: they buffer the entire view into a giant scrollable bitmap. The performance is super-smooth, but clearly they can’t deal with variable length tables without making the phone explode.

]]> By: Raj http://www.fieryrobot.com/blog/2008/10/08/more-glassy-scrolling-with-uitableview/comment-page-1/#comment-144672 Raj Wed, 24 Dec 2008 13:49:17 +0000 http://www.fieryrobot.com/blog/?p=111#comment-144672 <p>nice trick for light weight applications, however have you tried it with heavy applications (say 1000+ rows and lots of text columns and multiple tables)?</p> <p>my only fear is the app might end up with multiple calls to didReceiveMemoryWarning this loading and freeing data multiple times</p> <p>i am also juggling between more memory versus faster scroll performance. for the time being, i am going the apple way (loading data from db only when needed, displaying it, releasing it - no caching) as my app is dealing with a lot of data</p> <p>i am also exploring the option of not closing the db connection (i know its risky) but having it open makes the db reads a lot faster i guess</p> <p>it would be cool if you could give me some insight as to how many rows and columns are you caching in memory</p> <p>cheers, raj</p> <p>http://www.iphonekicks.com</p> nice trick for light weight applications, however have you tried it with heavy applications (say 1000+ rows and lots of text columns and multiple tables)?

my only fear is the app might end up with multiple calls to didReceiveMemoryWarning this loading and freeing data multiple times

i am also juggling between more memory versus faster scroll performance. for the time being, i am going the apple way (loading data from db only when needed, displaying it, releasing it – no caching) as my app is dealing with a lot of data

i am also exploring the option of not closing the db connection (i know its risky) but having it open makes the db reads a lot faster i guess

it would be cool if you could give me some insight as to how many rows and columns are you caching in memory

cheers, raj

http://www.iphonekicks.com

]]>