[Kde-imaging] feature list for host apps

[Jesper K. Pedersen]

On Friday 07 May 2004 15:06, Aurélien Gâteau wrote:
| Le Vendredi 7 Mai 2004 12:26, Jesper K. Pedersen a écrit :
| > I think we should stick to the goal that it should be as easy to develop
| > a plugin as possible, and if that makes it harder to make your app kipi
| > aware then let it be like that.
| >
| > Your suggestion, is indeed good and clean, but I'm afraid you will see
| > plugins developed entirely for app A which do support this interface, and
| > then one day someone downloads the plugin and tries it with app B, which
| > simply crashes because the code did not check the albumDescIface pointer.
| >
| > Using enums makes it optional to tailor plugins for the features of the
| > host apps, thus easy to develop a plugin, and if you want to make the
| > plugin really nice you can take it one step further.
| >
| > In the example above KimDaBa would simply return an empty string when
| > asked for a description of an album, and setDescription would simply be
| > implemented as an empty method.
|
| Maybe we can provide the dummy implementations in KIPI::Interface instead
| of making them pure virtuals? This way apps which do not support some
| methods won't have to implement them.
Great idea, I'll implement that.