[KPhotoAlbum] A few stacking issues

[Johannes Zarl]

On Sunday 27 January 2013 05:21:47 Robert Krawitz wrote:
> Found another problem with export/import: it doesn't preserve the
> directory hierarchy.  It appears to want to put everything in one
> directory, which isn't very useful for synchronizing databases.

Ok. That's not so nice.

Regarding import/export in general, I see two options:

a) Add stacking and directory support to .kim export

Pros:
 + hopefully less work
 + could use any concepts in KPA (i.e. stacks, tokens, different kinds of 
tags)

Cons:
 - the .kim format is meant to be compatible between versions, yet lacks any 
version information. Adding features most likely results in files that older 
versions of KPA will choke upon.


b) Create a kipi-plugin for DB-export

Pros:
 + kipi has a much simpler DB-concept (only one kind of tag)
   -> exchange format would also be simpler and unlikely to change
 + could also be used to convert between KPA and digikam
 + Less likely to be "forgotten" when new features/concepts are added to KPA

Cons:
 - Extra logic inside KPA needed to convert things like Stacks into vocabulary 
that kipi can understand

Personally, I would prefer solution b), because it has a generally better 
maintainability, and would directly benefit the kipi-support in KPA.


Any thoughts? Jesper, Miika? Also: any takers?

If nobody has a better alternative to b), and if nobody volunteers to do it, I 
will probably start implementing it end-of-february-ish.

Cheers,
  Johannes


P.S.: What I said earlier in the thread about filing bugs: I meant that. 
Looking into the bugtracker for things to do is much easier for me than 
digging through the mailing list.