[Kde-imaging] New category 'COLLECTIONSPLUGIN' ?

[Gilles Caulier]

Le mercredi 16 Juin 2004 01:24, Aurelien Gateau a écrit :
> Le lundi 14 Juin 2004 18:47, Caulier Gilles a écrit :
> > Le lundi 14 Juin 2004 11:14, Jesper K. Pedersen a écrit :
> > > On Monday 14 June 2004 11:10, Gilles Caulier wrote:
> > > | Hi all,
> > > |
> > > | I have checked all categories for all KIPI plugins. I think there is
> > > | a missing category for Collections actions. This is the list :
> > > |
> > > | acquireimages               --> TOOLPLUGIN (no change)
> > > | imagesgallery                 --> EXPORTPLUGIN (no change)
> > > | wallpaper                         --> IMAGESPLUGIN (no change)
> > > | commentseditor             --> BATCHPLUGIN (no change)
> > > | diroperations         (*)      --> COLLECTIONSPLUGIN (actually
> > > | IMAGESPLUGIN) mpegencoder                  --> BATCHPLUGIN (recently
> > > | changed by me) sendimages                    --> IMAGESPLUGIN (no
> > > | change) batchprocessimages      --> BATCHPLUGIN (no change)
> > > | findimages            (*)       --> COLLECTIONSPLUGIN (actually
> > > | IMAGESPLUGIN) jpeglossless                     --> IMAGESPLUGIN (no
> > > | change) slideshow                         --> TOOLPLUGIN (no change)
> > > | calendar                           --> TOOLPLUGIN (no change)
> > > | gammacalibration          --> TOOLPLUGIN (no change)
> > > | printwizard                       --> EXPORTPLUGIN (no change)
> > > | timeadjust                        --> IMAGEPLUGIN (no change)
> > > | cdarchiving                      --> EXPORTPLUGIN (no change)
> > > | rawconverter                   --> TOOLPLUGIN (no change)
> > > |
> > > | Why this new category : for a best menu integration in the host
> > > | application. Why apply this new category on 'diroperation' and
> > > | 'findimage' plugins : because this plugins work on the collections
> > > | not on the images directly.
> > > |
> > > | You viewpoints ?
> > >
> > > Fine by me.
> >
> > Aurelien, it's good for you ?
>
> Sorry for the delay, I'm catching up my email.
>
> I'm having difficulties to see the difference between the "Images", "Batch"
> and "Collection" categories. I think we need a clear definitions of all
> categories. Here is a draft, along with the way I think plugin should be
> grouped.
>

This is the actual categories associate with the plugins :

> * Import
> Plugins which get images from an external source and give them to the host
> app.
>  - acquireimage
-> tools

>  - rawconverter
-> batch(RAWbatch) and tools(RAWSingle)

> * Export
> Plugins which take a collection of images provided by the host app and
> produce something else.
>  - imagesgallery
OK 

>  - mpegencoder
Batch 

>  - printwizard
OK

>  - cdarchiving
OK

>  - calendar
->tools.



>
> * Batch processing
> Plugins which manipulate a collection of images provided by the host app.
>  - commentseditor
>  - batchprocessimages
>  - jpeglossless
-> Image
>  - timeadjust
-> Image

>
> * Tools
> Plugins which work with a collection of images provided by the host app,
> but do not modify the image and do not produce anything.
>  - diroperations
--> Collections

>  - sendimages
--> Images

>  - findimages
--> Collection

>  - slideshow
OK

>  - gammacalibration
OK

>  - wallpaper
--> Images

>
> What do you think about this?

The 'collection' category is dedicaced for the tasks based only on 'Albums' 
works (diroperations for example). This concept have a sence for Digikam. For 
another hosts, it's easy to merge the plugins at your conveignence.

The 'batch' category is dedicaced for the plugins who works on a group of 
images at the same time...

I will try to make a plugins categories table in according with the host type. 
With this, we can choise to change/merge the plugins categories if 
necessary...

Regards
-- 
Gilles Caulier