[Kde-imaging] RFC: next kipi & co. generation

[Caulier Gilles]

Le Mardi 26 Septembre 2006 23:49, Aurélien Gâteau, @orange.fr a écrit :
> >> From my point of view there is no problem. Since Gwenview is file system
> >> based, it would be enough to be able to specify a base folder and let
> >> the user browse it. On the other hand, I think applications like Digikam
> >> or KPhotoAlbum will probably need a way to provide the widget with their
> >> own hierarchy, to let the user browse the tag hierarchy. Am I wrong?
> >
> > yes. About digiKam, this is a is file system based like gwenview,
> > excepted for
> > the tag of course witch are virtual folders (using a hierarchy).
>
> I think this could be implemented by introducing the concept of recursive
> image collections. We could extend the ImageCollection interface so that
> it's possible for an ImageCollection to return its sub collections.
>
> A simplistic API could be something like this:
>
> class ImageCollection {
> ...
> public:
>   const QValueList<ImageCollection>& subCollections() const;
> ...
> }
>
> But it might not be very efficient. At least for the image collection
> dialog, it would be nice to have a method like this:
>
>   bool hasSubCollections() const;
>
> So that ImageCollectionDialog can make its items expandable without
> retrieving the full list of sub collections.
>
> It could be made more flexible and efficient by introducing an
> ImageCollectionIterator class, similar to QListViewItemIterator. This
> iterator would be implemented by the host app, allowing it to store the sub
> collections in the best way possible.
>

Sounds good for me Aurélien. 

Jesper, can you give us your viewpoint please ?

Gilles