Things to do

This is a movable list of main jobs which need to get done. It's a very inefficient project management tool.

In no particular order:

1. Lists of Page objects for siblings and children.

2. List of Page objects from a Directory.

3. Lots of ugliness to be gotten rid of in the styling and templates.

Handling image collections

This is a major project, requiring a class to handle image files, and mods to the Directory class to handle lists of them. It may also require a class to handle collections of image files, like a specialised version of the Directory. Maybe something called Gallery.

I'm thinking specifically of handling collections of photos from digital cameras.

It should be able to extract EXIF data from image files, and handle metafiles for an image in a similar way a Page object does.

I will have to write the simple syntax rules for handling collections of image files.

Thumbnail and view copies

For dealing with photos, we keep the full-sized version, and create copies at 1024 px and maybe 512px as well. These will live in predictable directories, and be used for thumbnail and inline display. An Image object will have to know about all of these copies.

Specifying a Gallery class

This is given a directory pathname, and then catalogues image files in that filespace. So it will recursively scan the directory looking for image files, building a catalogue of these.

I want to be able to drop a folder full of photos from my camera into a filespace, then go to the web interface, and have it process these, creating the two view copies, and a folder full of metafiles. If you include GPS files in the source, it should apply gpscorrelate to the photos.

The interface should step through this. Here's a new folder, do you want to catalogue the pictures? Oh, there are GPS files in it; what is the GPS camera time offset in seconds, and the timezone of the camera?