Re: Design for showing ridiculously huge number of images in Table View
Re: Design for showing ridiculously huge number of images in Table View
- Subject: Re: Design for showing ridiculously huge number of images in Table View
- From: Corbin Dunn <email@hidden>
- Date: Thu, 11 Dec 2008 09:33:16 -0800
On Dec 11, 2008, at 8:55 AM, rajesh wrote:
Hi All,
I implemented NStableView which contains few "columns" with
NSImageCells , there are huge number of rows ( for the nightmare )
images are requested over the network and hence images are never
readily available.
but part of my framework intimates me whenever an image is
downloaded and i precisely know for which of the rows image has
been downloaded.( so far good ).
I am trying to register an observer in the custom cell class of the
ImageCell I mentioned.
So whenever display is requested on the cell , it checks for the
image in downloads , if it isn't available it draws empty image else
it places an request and waits for the image.
After image is downloaded observer tries to invoke the drawing again.
This way only cells which are actually in "screen display" get
drawn , hence I am supposing there would less traffic and leads to
efficient drawing.
Is this a right practice ? or completely unethical ?
I think it is okay. Some applications watch the scrolling and cancel
previous requests that are no longer needed.
I strongly recommend implementing the type select delegate methods to
avoid loading images on cells for type selection.
Also see this demo (I'm going to see how many times I can reference it):
<http://developer.apple.com/samplecode/PhotoSearch/>
Which does what you want -- except, it loads images in a background
thread using CG, but the concepts are the same.
corbin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden