Photos Section

Nested Photo Album with simple updating. All of the photo related extensions are basically composed of two parts, 1) thumbnail list, and a larger 2) Selected picture. THis also seems to come with a preprocessing step where tumbnails are generated. This is fine for displaying a single folder of pictures. I'd buy an extension for photos that starts with the idea of a BIG set of pictures that will be added to continuously and over the years. To implement this I'd like something that works with nested folders. Assume every folder is an album, and each file in a folder is a picture (if its extension is .jpg, .tiff, .png, .gif). Put no restrictions on how deep the nesting can go. If you click on a folder your thumbnails change to list the contents (I'd suggest that sub-folders be represented as tumbnails also and, use either a simple folder icon for folders with no picture files in them, or a folder icon with a small photo on it for a folder with at least one picture file in it). The titles on the folders and files should be taken from the file name but without the file's extension. Assume that the entire picture gallery will be uploaded to the server. Once the page with the extension is on the server, it should automatically handle growth. The web site manager should only need to upload more folders with their associated image files. The manager can change the names on folders and files. Add or delete files and folders changing the folder structure and its contents. Ideally the extension should handle all of this on-the-fly. If it did it would allow this extension to tie in transparently with the Pure upload extension if the web site developer wanted to allow users to create folders and upload picture files. But I would not object to requiring the manager, after he has uploaded the new files and folder, from being required to chick an 'update button' somewhere to automatically create any support files that might be needed for use by the extension. If this approach is taken it should again be dead simple. The update process should traverse the folder and file structure to determine what needs to be recreated. Hopefully all of this can be done without the user having to deal directly with any sql database creation issues, although the creation of such a file, if created and put into the 'root' folder automatically when the user clicks 'update' is probably acceptable.