Comments for markjnet

Comment on UITables with Downloaded Images – Easy Asynchronous Code by Neha

Neha — Sat, 31 Jul 2010 13:58:12 +0000

Thanx markj.. Worked like a charm..

Comment on UITables with Downloaded Images – Easy Asynchronous Code by links for 2010-07-30 at ≈ Relations

links for 2010-07-30 at ≈ Relations — Sat, 31 Jul 2010 01:06:49 +0000

[...] UITables with Downloaded Images – Easy Asynchronous Code | markjnet (tags: software opebsource objectivec images async) [...]

Comment on UITables with Downloaded Images – Easy Asynchronous Code by Lamo

Lamo — Thu, 29 Jul 2010 03:19:57 +0000

Thanks for responding Mark!

That sounds really great – don’t suppose you have an ETA for the code update/repost? Sorry normally don’t like to beg but now I’m very anxious to implement what you have described just now :)

Cheers

Comment on UITables with Downloaded Images – Easy Asynchronous Code by markj

markj — Wed, 28 Jul 2010 17:11:01 +0000

Hi Deepak and Lamo, we faced this too in our commercial apps. For the photo browsing part of our facebook app we use a ‘3 photo’ load ahead system so that while looking at photo #4, #5,6,7 are loading too. This code has ‘cancel behind’ too, so that if you scroll ahead quickly it cancels the loading of the photos you passed by. Works nicely. I took that small feature as part of the inspiration of the re-write of the async photo loading code. The new version, which is not yet published here, features a custom circular buffer of images it is loading. The buffer is of configurable size, and it functions to limit how many photos are being loaded at once. As you scroll down the table, images that haven’t finished loading yet (and probably never even started loading) get pushed out of the buffer and their URLs are cancelled. This new library does a lot more, too – caches images in local file storage, shares image objects between multiple table cells, etc.

Comment on UITables with Downloaded Images – Easy Asynchronous Code by Lamo

Lamo — Wed, 28 Jul 2010 16:52:44 +0000

Good question deepak – I noticed this too. I was hoping to show 50+ records/images in a table – but now noticing long wait when scrolling fast to bottom – if anyone has ideas on how best to only load content within current viewpoint of table without loading prior images on route would be appreciated.

I imagine this will be tricky to resolve as I believe would need to detect users scroll speed

if scrolling fast then don’t load sequentially just load images in view etc but if scrolling slow load in sequence – wish i knew where to begin to code that but just learning myself at this stage.