[KPhotoAlbum] New features for testing and discussion

Johannes Zarl isilmendil at gmx.net
Wed Aug 1 19:10:05 BST 2012

On Wednesday 01 August 2012 15:04:18 Jesper K. Pedersen wrote:
> > > > 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.

Let me rephrase that: this was the best fitting icon in KDE I could find for 
the job. If somebody knows of better one, please point me to it. I can rework 
it as a text-button, though.

> Dude, I have two director titles on my business card, you do not want to
> challenge me in the delegation game :-)

Sorry to break the news to you: being the primary author of KPA gives you some 
leverage with me. Your titles give you the same importance as your middle name 
or hair color, unless the person signing my paycheck says otherwise...

> 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)

As said above. If it's that bad, I'll just change it to a text-button. (Which 
might have been the better choice from the start on)

> > 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?

Potentially, yes. I would like a clean interface between GUI and database. 
This makes it way easier to set up unit-tests for the database part, to write 
a commandline-client (my use-case) or to write a KIO slave. Also I would hope 
that less interdependencies would make writing other backends (SQL) feasible.


More information about the Kphotoalbum mailing list