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

List:       kopete-devel
Subject:    Re: [Kopete-devel] capabilites design
From:       Daniel Stone <dstone () kde ! org>
Date:       2002-06-16 6:41:34
[Download RAW message or body]

On Sat, Jun 15, 2002 at 09:47:51PM +0200, Martijn Klingens wrote:
> On Saturday 15 June 2002 20:41, Andres Krapf wrote:
> >  * the buttons like color and fonts should be capabilities (because some
> > plugins might not have them, see msn-bg color for example)
> 
> Capabilities are non-extensible unless you found a magic wonder-potion to 
> solve that. If not I think capabilities are not an option. Not to mention 
> that 'capabilities' is not a requirement, but a possible implementation...

I think you're perceiving capabilities wrongly. They're meant as an
opportunity to share code - the colours, for example. Where code can be
shared, it should. It's not meant for every protocol to add its own
cracked-out extensions.

Thus, superficially it seems resources was a misuse of capabilities.
However, it could easily have been used for the KopeteUberContact
thingy. Think about it, it's just sane code re-use.

-- 
Daniel Stone	   <daniel@raging.dropbear.id.au>   http://raging.dropbear.id.au
KDE Developer	   <dstone@kde.org>	                      http://www.kde.org
Kopete: Multi-protocol IM client	    		   http://kopete.kde.org

[Attachment #3 (application/pgp-signature)]
_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel

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