Comments on: MUPhotoView 1.1

By: blake

blake — Sat, 13 May 2006 16:48:52 +0000

Whamoo - I’m not sure what you mean?

By: whamoo

whamoo — Sat, 13 May 2006 10:53:01 +0000

Hi blake,

first of all thanks for this class, it’s really interesting!
Second i’ve noticed a bug (or better an unwanted behavior), when loading the photo in your view, the last photo is selected by begin (also in your demo), if i have time i will discover the problem and send you the patch, if you are more fast than me, i will be happy to use the revised version!

Bye

By: blake

blake — Sun, 07 May 2006 07:59:22 +0000

Steven - Hmmm, well, titles are my next “to do”. If you want it to be generic, then there are really 3 ways. The first is via bindings, by including another array of NSString titles. The second is by asking the delegate for the title at a given index. The third is somewhat new for MUPhotoView and involves looking for a title key inside one of the other, already bound, elements - i.e. allowing somebody to bind an object that provides an image and a title. I plan to try and provide all three methods and allow implementers to supply whichever works best for them… but since I have no idea when I’ll get around to adding that, please feel free!

By: Steven

Steven — Sun, 07 May 2006 07:09:13 +0000

Looks great - but what would be the shortest path to putting text beneath these? I may dive into the code but I’m sure you might have some pointers on the quickest route to putting –for example– the image name beneath the photo.

By: blake

blake — Tue, 02 May 2006 21:31:19 +0000

Hey Marc,

Every time the view gets a drawRect: call, it determines which photos fit inside that rect, and then attempts to draw them. When the view first displays, it’s probably getting a -drawRect call with it’s entire frame as the rect. You may be able to muck around the code and see if there’s a way to bypass that first draw and instead attempt to just draw the visible rect.

-Blake

By: marc

marc — Tue, 02 May 2006 19:44:02 +0000

Hi Blake,

I have an NSImage array created via initByReferencingFile: which actually takes no time as NSImage objects are loaded lazily only when needed.
Using setPhotosArray: somehow seems to force loading all of the NSImage objects even though this would not be necessary.

Cheers
marc

By: blake

blake — Tue, 02 May 2006 00:27:31 +0000

Hey Marc,

The view itself does not load any images - that’s something it defers to your application. If you’re using delegation, it directly asks for them. If you’re using bindings, it expects an array of NSImage objects. In both cases, it’s the app’s responsibility to load the images from their appropriate location - file, url, etc.

So any speed hit in the initial display is your app (or my app, in the case of the demo) reading the images from disk to start with. It should be fairly easy to NOT load them all at once - which should be pretty quick.

-Blake

By: marc

marc — Mon, 01 May 2006 22:55:57 +0000

Hey Blake, why does it take so long to show the images initially? Even a modest number of images (say 100) takes minutes on my machine.
I would really like to use the MUPhotoView in a project of mine but it needs to get a lot faster on loading. Are there any chances?

Cheers
marc

By: Michael Black

Michael Black — Mon, 01 May 2006 05:52:38 +0000

Thanks

By: blake

blake — Mon, 01 May 2006 02:43:43 +0000

Hey Michael - give it another try. Somehow I lost that whole directory while mucking around with another project on my site today. MUPhotoView is back up…