I responded to you in the other thread:

http://www.noscope.com/journal/2005/08/zenphoto#comment-5690

I am also looking for a new Photo Gallery and the articles here are very interesting, to say the least.

I’m looking forward to trying a few of these over the holidays, but I wanted to ask if it is possible to show EXIF data when using Zenphoto?

kind regards

teddy

As Jonas said, get cracking!

I thought of quite the elegant way to monitor new albums and uploaded images.

It does indeed sound elegant. My computer science experience gives a warm thumbs up, so get cracking already ;)

Head shaking in the affirmative

Chris (#11) – I think you’re thinking a little too much into the database – I’ll just be storing metadata. Lots of text, in other words. So, title, description, all comments, tags, etc. It’s independent of the image folder structure. Ideally, I’ll design it so that the data in the database gets initialized to some default values when a new album or image is seen (one that doesn’t already have an entry in the db) and the admin can further customize it once the images are uploaded and albums created.

I thought through the implementation of this a lot last night, and it seems like a managable task. I thought of quite the elegant way to monitor new albums and uploaded images. Essentially, I’ll use an object-oriented model, and each image will be an object, as will each album, and each “group” or arbitrary set of images from the gallery. When the album is viewed, I use the folder structure to find which photos to display (using a single album as an example) and make a new Image object for each of them. The Image object’s constructor takes the filename (full path), looks it up in the database, and if it exists, then it uses the existing metadata. Otherwise, it makes some default info out of the file/folder names and makes a new database entry. Then (this is the cool part) depending on the size of the image requested (thumbnail, normal size, full size, or even custom size) it processes the original image into that size and caches the resized image so it doesn’t have to be processed at that size again. This way, one of photostack’s biggest weaknesses is killed — photos are now processed on the fly as required instead of all at once, which causes server timeouts.

Jonas (#13) – Password protection isn’t something I’m going to implement at least in the first version. I could allow you to hide individual photos or albums from the public, but I’d rather not go further than that. Joen is right about .htpasswd being the best solution for those kind of things – just make a new gallery in a new folder and protect it that way. Pretty easy.

Joen (#14) – I’ll be back to my own site soon enough (with a full spec sheet); it’s just so much easier to post here with your little preview thing. ;-)

I’m not quite sure I understand what you mean. My main reason for thinking we should not put effort into password features is that “people hate having to log in”. They hate even more “secret areas out of their reach”. By that I mean that showing an album that not all people have access to is likely to only irritate them… For the very same reason I’m keeping a personal photo gallery in a non public directory.

Steve,

Great to hear from you. Congratulations on the baby! I hope things are well with you and yours.

I haven’t encountered SlideShowPro?

Edit (Admin privilege): I just logged in to my Bloglines account to check everything was dandy… I couldn’t find any problems? The problem might be related to my feeds changing address, but the old addresses should be redirecting…