On 01/08/2010, at 3:38 PM, Steve Christensen wrote: > If you manage a thumbnail cache to supply those images, you could restrict > the maximum memory footprint and reduce the likelihood that you'll keep > getting expensive (time-wise) delays trying to generate/draw an image in the > browser.
It's also well worth loading the images using a background thread, then when the load has completed, inform the view that the image is now ready to display. If you provide the browser view with the image path (IKImageBrowserPathRepresentationType), it does this for you (briefly displaying a placeholder image), but if supplying the actual image you have to do this. It can really speed up scrolling because the view is never left waiting for an image to be loaded and decoded, it only has to spend time drawing it, and because this approach will spawn as many threads as images needed at a time, it scales really well to those new 12-core Macs ;-) --Graham _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
