[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 9:42:45
[Download RAW message or body]

On Sun, Jun 16, 2002 at 11:08:01AM +0200, Martijn Klingens wrote:
> On Sunday 16 June 2002 08:41, Daniel Stone wrote:
> > 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.
> 
> How do you add a new capability without recompiling libkopete? If that is not 
> possible, then I would qualify them as non-extensible. Whatever solution we 
> choose, it *must* be a solution that allows us not to touch libkopete.

No, that's wrong.

How do I add a new contact list without touching libkopete? What about
if I want to add a new UI? Different preferences dialog, maybe?

This is *shared* *code* *between* *protocols*. It's meant to cut down on
code reuse.

-- 
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]