[Kde-imaging] kdeextragear-libs-1/kipi-plugins [POSSIBLY UNSAFE]

[Jesper K. Pedersen]

On Sunday 02 May 2004 21:07, Aurelien Gateau wrote:
| Le dimanche 2 Mai 2004 20:47, vous avez écrit :
| > | > | > Plugins the user downloads himself from the net can host apps not
| > | > | > do anything about - how should it know about these - on the other
| > | > | > hand. If the user downloads them, then he knows explicit about
| > | > | > it.
| > | > | >
| > | > | > | Aurélien, currently wondering if KIPI is such a good thing
| > | > | > | after all
| > | > | >
| > | > | > Why is that?
| > | > |
| > | > | Same thing as always: just look at the Digikam plugin list. Can you
| > | > | name one of them which could not be implemented as a separate
| > | > | binary? What do we really gain with plugins?
| > | > | I see only one thing: getting the plugin to automatically appear in
| > | > | the app menu. This could be achieved with little pain with
| > | > | binaries. On the other hand, plugins force you to extend your
| > | > | application in C++: one can't easily write plugins in Python, Perl,
| > | > | Ruby or whatever easier language.
| > | >
| > | > Well you would then have to have a lot of communication with the app,
| > | > I mean the host app and the plugin-app would need to communicate
| > | > about changes in selection etc - thats gotta be really ugly.
| > |
| > | I don't see why any communication is needed since at present (and I
| > | doubt it will change) all plugins are modal dialogs which process a
| > | list of images. This could easily be done just by calling a program
| > | with the list of images as parameters.
| >
| > Well first of all, there are plugins which use more than just the URL for
| > the app, second I'm sure we will see more in the future.
|
| Well, I guess you're right. Still it's a pity not to be able to extend host
| apps using other programming langage.
|
| > I foresee plugins which will help say a slideshow go from one image to
| > the next - similar to a screen saver or a slide show in KPresenter.
| > These plugins may get two images to do the transaction or or something
| > like that.
|
| I don't see what you mean here.
Think of KPresenter, its possible to specify that one screen should merge into 
another in a number of ways.

Imagine say kimdaba had similar facilities for its slide show, then it would 
be obvious to make it possible to develop new ways of page changes using 
plugins.