Keep up the superb work!!

Darren

There should only be one Plogger directory.

It doesn’t matter what you call it, you can call it “Francis” for all I care… it will still work. I’ve repackaged the files, the default directory name should be lower-case “plogger” now.

If you’re on Linux, just move all the files in “Plogger” to the “plogger” directory. If you’re in Windows, you can change the directory name to lowercase and still be ok.

Hope this is not too confusing… if so, you can always just redownload the thing, the package is fixed now.

This is no critique and I don’t want to start a discussion about css/tables (there are better places for that). Like I said, just a quick reply ;).

If there is a better way to do this in CSS (to address the alignment issues), someone please let me know.

You’re right as to the thumbnails, although this is a css problem. Choosing to place the thumbs in a table would solve this. Personally I find that the page gets more symetrical, balanced, when thumbs are the same size and centered instead of a few rows that are shorter dan others. But perhaps I can change that myself in the code. :)

Why can’t you make it so the previous or next image is centered in the user’s browser as that is what s/he wants to see? Scrolling down to view each image is not very convenient. Again, all of the image gallery apps I have seen have this problem. That is why I like Gallery’s javabased fullscreen viewer. It actually lets users go from image to image without having to worry about scrolling.

Still, one does not need to browse images fullscreen. A simple user-friendly feature, like described above, would suffice. I would use Plogger, if I didn’t have to vertical scroll after every image change.

The EXIF data is hidden by default, the user has the choice the reveal it or leave it hidden. It may be useless information to you, but the person browsing your gallery might be interested in the settings you used on your camera to get a particular shot.

Creating albums within albums would involve a complete restructuring of Plogger, so this probably won’t happen. I think you can create a sufficiently complex depth of organization with two levels.

Having a popup instead of _blank for the largest image will be a feature in the next beta.

The reason I chose to specify the height for the thumbnails and not the width pertains to the way that HTML reflows an inline list with variable sized elements. If all the elements are not the same height, rows will get stuck on the protruding elements of the above row. For example, if the second image in the first row is taller than the rest of pictures, the second row will begin in the middle of the page, right after the second picture.

Ultimately, you could change the code quite easily if you wanted it to behave differently. The thumbnail resizing code is designed to keep the proportion of your original photo automatically. Thanks for the suggestions!

- option of disabling the exifdata totally (find it rather useless information)

- possibility of sub-sub-sub albums if necessary (like fauna=>animals=>insects=>beetles)?

- possibility of popup instead of _blank for the largest image?

- option to set thumbnails ‘largest size’ instead of max. height, so 3/4 sized images will always have the same proportion, wether horizontal or vertical.

thanks!