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

List:       kopete-devel
Subject:    Re: [Kopete-devel] KopeteMessageManager design question
From:       Daniel Stone <dstone () kde ! org>
Date:       2002-04-28 0:24:38
[Download RAW message or body]

On Sat, Apr 27, 2002 at 02:01:51PM -0400, Duncan Mac-Vicar Prett wrote:
> > Dunca, Ryan, any comments on this?
> 
> Well, KMM is still an experiment, it is still not used anywhere and we are 
> still free to play with it.
> The last time I tried to port a plugin to KMM it was a PITA, because the 
> multi-user chat supports makes all things hard to use, even if your protocol 
> doesnt have even multi-user chat.
> 
> I would like more people helping and propossing changes to KMM, since it will 
> benefit all plugins.
> 
> The subclass problem for KCW is real .. but I cant figure a solution right 
> now.

Jabber has been converted to KMM, I'm about to commit to CVS.

As for the initial problem, I suggest a capabilities flag, like so:

#define CAP_FGCOLOUR 1
#define CAP_BGCOLOR 2
#define CAP_URL 4
#define CAP_SUBJECT 8

kopeteapp->whatever->create(foo, bar, CAP_FGCOLOR | CAP_URL | CAP_SUBJECT);

IMHO it should also support widgets - I really, really, really want to
differentiate between messages and chat.

Once all this is done, I don't see why 0.9 shouldn't be announced.

-- 
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://www.kdedevelopers.net/kopete/

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