[Adium-devl] Metacontact Plans for Adium 1.1

[Colin Barrett]

On Sep 28, 2006, at 4:13 PM, Augie Fackler wrote:

> I'm still a little hesitant on CK. I think things like CK will be  
> less valuable as we start getting some of the more intricate VV  
> things happening, but we'll burn that bridge when we come to it.  
> *If* a good solution for that can be found without making multiple  
> heads asplode, then I think we're OK. Perhaps consulting the Vorlon  
> again will help with that.

I'm not sure I follow your logic here -- in fact, things like CK would  
seem *more* valuable once VV starts getting involved. Want video and  
audio conferencing in your app? CK offers that nearly for free. I  
don't see how this is a Bad Thing. Either way, it's still a good idea  
to re-organize the Adium API this way, regardless of what CK is doing  
-- the CK stuff is just bonus points, really.

>> In general, I think this is a good idea, and would be a good excuse  
>> to
>> clean up AIContactController.m (ugh). All the more reason we should
>> get started on this ASAP: i.e. branch for this as soon as we have an
>> API outline finalized.
>
> Excuse nothing, we'll *have* to make changes anyway, I say we fix as  
> much of it as we can and take the black magic out while we're in  
> there. I shouldn't be able to stare at an object for several B5 eps  
> in a row and *still* have no concept of how it works internally.  
> It's time for prettifying that particular block of code. With  
> doxygenation.

By "excuse" I meant "motivation to touch that evil, evil hunk of code  
that nobody sane would touch normally." Although I suppose none of us  
are really 100% sane anyway (we *do* work on Adium ;)

-Colin