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

List:       kopete-devel
Subject:    Re: OSCAR Roadmap (was: Re: [Kopete-devel] CRASH (with BT))
From:       Christopher TenHarmsel <tenharmsel () staticmethod ! net>
Date:       2003-03-31 23:29:15
[Download RAW message or body]

On Monday 31 March 2003 12:11, Stefan Gehn wrote:

> It would also be cool if Christopher could help me a bit of properly
> seperating AIM and ICQ inside the code, I still don't know if I should use
> OSCARContact as a base for ICQContact and AIMContact and then cast around
> all the time (that'd would be ton of if() constructs in OscarAccount I
> fear) or if I should just have a bool in every contact that states if it's
> a ICQ contact or not (OTOH that'd waste memory as the ICQ-specific vars
> aren't used for AIM contacts and the other way round).

I would love to help figure this out, the problem is that I'm not very 
familiar with the ICQ stuff, so you might have to be a little more verbose in 
explainations when the time comes.

Right now, OSCARContact is pretty tied to AIMBuddyList, et al.  In fact, it 
keeps an internal AIMBuddyList and uses it quite frequently.  The idea of 
removing all references to AIMBuddy* has been brought up, and I think it's a 
good idea, but it (right now) looks like it'll take some non-trivial work 
(mostly just refactoring work).  Is the contact management for ICQ pretty 
close to that of AIM?

-Chris

-- 
Christopher TenHarmsel, KDE Developer
Public Key on www.keyserver.net
Don't be irreplaceable, if you can't be replaced, you can't be promoted.

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