[KPhotoAlbum] New features for testing and discussion

[Jesper K. Pedersen]

> > > On discussion side, the annotation window is a bit annoying nowadays.
> > > [...] The and/or selection is the only one that is specific to each
> > > category and makes sense to have multiple times. On the other hand
> > > only one set of buttons would be sufficient to select the display mode
> > > and toggle search mode.
> > 
> > I like to keep the buttons repeated, as it makes it more obvious that it
> > is
> > for those lists, than if they were located elsewhere in the window.
> 
> I find the button behaviour counter-intuitive, as well. Having them on the
> annotation dialog instead of the ListSelect would seem more natural to me.

I dont feel strong about it, so if you feel strong about it, fell free to 
change.

> > > course the default behavior is a matter of taste and changing the icon
> > > from {} to ^ would also be sufficient for me.
> 
> I chose the "{}" icon because MatchFromBeginning effectively matches the
> whole tag name, whereas MatchFromWordStart splits the tag name. If you find
> a better icon in the standard KDE icon set, I'll be happy to use that
> instead.

Dude, I have two director titles on my business card, you do not want to 
challenge me in the delegation game :-)
Seriously, please find something better than the {} icon, even with your 
description I don't understand your icon (or at least would not be able to 
memorize it)

> > Johannes, this is your work, pleas work Miika to improve the usability of
> > this. Please also add a tooltip to the button to explain what it does,
> 
> Actually, there already is a tooltip. I'll also add a "what's this" to the
> button (and to the other buttons on the AnnotationDialog).

Oh, my bad, did not see that.

> And now for something completely different: One refactoring on my backlog
> still is to pull out the DB part of KPA into its own library. On the other
> hand the dependencies from the DB to the GUI-part seem to grow rather than
> shrink. This begs my question: are other developers also interested in
> seperating the database part, or should I just fork the database code if I
> need a standalone library?
No comment really. When you say separate library, you do not mean something 
shipped separate from KPA, do you?

Cheers
-- 
Having trouble finding a given image in your collection containing
thousands of images?

http://www.kphotoalbum.org might be the answer.