[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-imaging
Subject:    [Kde-imaging] feature list for host apps
From:       aurelien.gateau () free ! fr (=?iso-8859-1?q?Aur=E9lien=20G=E2teau?=)
Date:       2004-05-07 15:07:14
Message-ID: 200405071506.40386.aurelien.gateau () free ! fr
[Download RAW message or body]

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.

Aur?lien

[prev in list] [next in list] [prev in thread] [next in thread]