On Thu, 13 Jul 2006 22:40:18 +1200
Andrew Errington <[EMAIL PROTECTED]> wrote:
> I quite like Kimdaba, now known as KPhotoAlbum. In particular, it allows
> you to tag images with multiple tags, and you can view your pictures by
> date or tag or group (a superset of tags). It will export to HTML, but the
> version I used would set up gallery thumbnail images in a grid on a
> selected screen size. I think that the gallery should wrap to fit the
> current viewing size, and not assume the user is browsing full-screen at a
> particular resolution.
>
> Kimdaba does nothing with your files on disc, but instead catalogues them
> in an XML index file, which also contains the tags and other information
> for each image. It also plays nicely with Kipi (the KDE Image Plug-ins)
> for handy dandy image fiddling.
>
> It's certainly worth a look.
>
> A
The tagging interfcae is fast, intuitive and all round good.
The XML indexing is a dog with lots of photos - it does not scale well.
BUT good news on the horizon, from the kphotoalbum site (25 May 2006 news):
"Yesterday the google summer of code projects was chosen, and I'm happy to
announce that Tuomas Suutari (thsuut AT utu DOT fi) was elected to work on
KPhotoAlbum. Here is his description of the project:
As you maybe already know, currently KPhotoAlbum stores its data in an XML
file. This file is read into memory on start up, and is written to disk when
saving.
Jesper suggested on the KPhotoAlbum mailing list that someone would add
support for SQL database back-end as a Google Summer of Code project. He has
already made a proof of concept implementation for making the back end
pluggable.
When I got that mail, I immediately realized that this would be a cool
project for me, because I use KPhotoAlbum regularly and love programming.
Adding possibility to save image database into SQL database could provide
at least following improvements:
* scale better for large photo collections (uses less memory)
* make KPhotoAlbum start and close faster (no loading/saving of the XML
file)
* add possibility to access the database by multiple users at the same
time
The last bullet is really the biggest improvement to many users, who might
want multiple people to tag the set of images at the same time, and perhaps
allow for adding information from say a web interface."
