Since people are starting to want to contribute photos the Oxford Guide, I've been thinking about what level of integration is appropriate with OpenGuides.
My initial plan is as follows:
Config var image_base is a partial URL defining where to find images. Standard subdir scheme $image_base/thumb and $image_base/normal for a simple two-size hierachy of images.
A macro #EMBED_PHOTO [imagename] or similar, which would do, approximately:
<a href="$image_base/normal/$imagename"><img src="$image_base/thumb/$imagename width="$width" height="$height" border="0" alt="Image for $node_name"></a>.
A new special field in the node "photo" which would be used to define the "primary" image for the node. This could be automagically displayed, if present, for example to the right of the metadata in the standard web layout.
Photo uploading I am leaving as a separate problem for now. If people have any particular ideas I'd be interested in them, but the way I see it the photos probably want to be reviewed rather than made public straight away, and there is no particular need to have uploading integrated into OpenGuides itself. I may investigate DAV, or a simple CGI script for POSTing files.
An example hierachy is http://www.ox.compsoc.net/openguides/oxford/photos/. Note that I also have a full/ directory for the full-size photos (useful for "remastering" the guide into print, for example) and a simple note of who took the photo.
Any comments before I start trying to code this?
Cheers,
Dominic.
On Sun, 2004-07-11 at 00:11, Dominic Hargreaves wrote:
Photo uploading I am leaving as a separate problem for now. If people have any particular ideas I'd be interested in them
I am starting to use CGI::Uploader and it's a very interesting package. It generates thumbnails on the fly (using ImageMagick and its Perl package) and stores all information in a database. It's kind of a heavyweight solution, though.
http://search.cpan.org/~markstos/CGI-Uploader-0.76_02/
openguides-dev@lists.openguides.org