Configuration ============= A (hidden) file exists in each album directory, holding information about each image and each sub-album. For both images and albums the key is the filename and the order in which each is listed determines the ordering in the album. Common to both we have the following attributes: - Caption, a text fragment explaining what's in the picture/album. Special to images additional attributes stored are: - Rotation (floating point number) - Mask, represented by the four border sizes; top, left, bottom, right. All floating point. - Thumbnail mask. Same as above, but applies to thumbnail images. As these are very small there may be a need to focus on a detail of the original image to have a visual cue about the subject of the photo. For albums the additional attributes are: - Cover picture, the picture (or album) representing the album as a whole for the purpose of a thumbnail. Web Interface ============= The theory of operation is that the directory holding all the subdirectories with albums maps to a webapp. The URLs accepted by the webapp reflect the directory structure of the photo directories, but adds some twists to make it possible to represent thumbnails, medium sized images and large images in addition to the album pages themselves. URLs for the albums are: /album/index-num.html There is a configuretion switch indicating how many thumbnails to show per album page. This makes "num" in index-num.html represent the associated subset of images. There are also one picture per page pages. These have the pattern: /album/filename.html The individual pictures are accessed with URLs like the following: /album/.../size/filename.ext In this URL size has to be one of the following: "thumb", "medium", "large". The (global?) configuration determines the actual size constraints for each of the sizes. Only certain file extentions are supported. Notably "jpeg" and "png". "html" can not be allowed as it would destroy the page per picture setup.