[Kde-imaging] ImageCollection or Browser

[Renchi Raju]

On Wed, 23 Jun 2004, Jesper K. Pedersen wrote:

> On Wednesday 23 June 2004 01:10, Renchi Raju wrote:
> | from what i understand with regards to accessing images from the app,there
> | are two classes of plugins:
> |
> | 1) plugins which work on the currently selected images or all the images
> | in the classes. its important to clearly differentiate between the two, as
> | there are plugins (like wallpaper and rotation) where action needs to be
> | taken only on the currently selected images. the currentSelection() and
> | currentAlbum() methods work well for this purpose. i don't understand the
> | concept of currentScope(); what purpose does it serve?
> It returns the selection if there is any otherwise it returns the album.

and what is it useful for? why would any plugin choose to use
currentScope over the other two methods?

> | 2) plugins which work on groups of images (imagecollection/albums) for eg,
> | the cdarchiving plugin which would like to put these groups of images into
> | individual folders on the cd. afaik only digikam has the concept of
> | allalbums() for this purpose. but it would be nice to have the option of
> | providing plugins with a way to select multiple image groups (for eg, in
> | the case of cdarchiving plugin user doesn't want to create cds with single
> | folders). here, jesper's suggestion of the browser class will work well; a
> | widget is provided from the app which provides a way of selecting the
> | image groups or just a single group of images if the host app doesn't want
> | to provide a selection widget.
> Well "my solution" doesn't work out of the box for me, can't remember the
> exact problems right now.

renchi