<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><br><br>--- On <b>Fri, 1/2/09, kphotoalbum-request@kdab.net <i><kphotoalbum-request@kdab.net></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">Date: Fri, 2 Jan 2009 16:31:04 +0100<span style="font-family: monospace;"><br></span>From: jedd <jedd@progsoc.org><br><pre>Subject: [KPhotoAlbum] (yet another) html front end<br>To: kphotoalbum@kdab.net<br>Message-ID: <200901021631.05484.jedd@progsoc.org><br>Content-Type: text/plain; charset="us-ascii"<br><br> Greetings busy people,<br><br> A couple of months ago I got excited (all over again) at the idea<br> of organising my photos - thanks to a multi-country, 4-month<br> holiday looming. I realised early on that I really wanted something<br> a bit more dynamic than the current web front end offerings, and<br> ideally something that
would 'just work'. The simplest approach I<br> could come up with was to have a php (it's the only appropriate<br> language I'm familiar with) script talking directly to the file system<br> where the pictures and the index.xml file live (it therefore has some<br> security implications, as below). To publish a picture, you simply<br> nominate a Keyword-tag (I use 'PUB - jedd'), save the config, and then<br> hit the web page. The php scripts generate three cached files (I use<br> my own caching system) - the thumbnail, the inline picture, and a<br> 'huge' image (from an original of about 4mb, these cached images<br> are around 16kB, 170kB, and 400kB respectively).<br><br> I have a functioning system cranked up on my server, visible<br> to young and old at :<br><br> http://dingogully.com.au/kphpalbum<br><br>Right now what I'm after is basically some ideas on :<br><br> o whether this is likely to be useful to anyone else. (I see the<br> subject pop
up periodically, and most people seem to write<br> their own custom script, or learn to live with the html export)<br><br> o ideas on functionality - present or missing. (I have a TODO<br> list somewhere that I should put into the footer on that page,<br> but will briefly go through known issues below.)<br><br> o ideas on layout - as I've developed this on my MSI Wind, and<br> in case anyone doesn't know .. this is a painfully small, 8"<br> laptop, with a 1024x600 resolution - so I know that things are<br> going to look quite weird on a Real Machine. I also develop<br> with konqueror, so I expect things will look even weirder with<br> IE (not that many of us use IE, I expect) or Firefox.<br><br><------------------------------------><br> I have tarballed up the code AS IT STANDS - but mind, this is<br> pretty ugly and I'm not proud of the internals (is anyone ever?).<br><br> URL is as above but tack on
/kphpalbum.tgz<br><br> Installation is .. badly documented. But it's painfully simple - just<br> modify the config.php file with the path to your picture repository<br> (that is, the directory with the index.xml file in it). For the sake<br> of security you could have a symlink that is hard to guess, and<br> perhaps several directories deep, that points back to that location<br> (this is what I do).<br><br><br></pre></blockquote>I will have to try this. I like your concept. I especially like all the information that it contains. If I were a graphics artist, I could probably suggest some ways to improve the appearance. The only thing I can suggest is looking at some sites such as Google's Picassa for a ideas on a bit neater appearance. However, I suspect that you are primarily interested in functionality, which appears pretty good to me.<br><br>Murray<br><pre><br></pre></td></tr></table><br>