[Adium-devl] Plugins - Handling different adium's versions

[Thibault Martin-Lagardette]

Hehe, the -respondToSelector thing was kinda out of question, too much  
ifs to add in the code :p

But seeing these statistics, I think I will, in fact, stay with the  
current version.

Thanks for the quick reply :)

-- 
Thibault Martin-Lagardette



On Jun 12 , 2008, at 00:21, Zachary West wrote:

> On Wed, Jun 11, 2008 at 6:11 PM, Thibault Martin-Lagardette
> <dracognizer at gmail.com> wrote:
>> Hi guys.
>> As of Adium 1.3, I discovered my plugin didn't quite work, and was  
>> wondering
>> why.
>> I re-compiled Adium.framework, and when compiling, saw all those  
>> warning
>> saying my AIAccount object may not respond to
>> [AIAccount setStatusObject:forKey:notify:]
>> and
>> [AIAccount statusObjectForKey:]
>> In fact, it now responds to
>> [AIAccount setValue:forProperty:notify:]
>> and
>> [AIAccount valueForProperty:]
>> So my problem is, if I don't update the code, it won't work for  
>> Adium 1.3
>> and higher. If I do update the code, it won't work anymore with 1.2  
>> or less.
>> Is there any possible workaround, or do you want everybody to  
>> migrate to
>> 1.3, discontinuing 1.2.x "support"?
>
> Most of our users[1] stay current. Don't try and design for
> compatibility with older versions, but if you want to, you can use
> -respondsToSelector.
>
> Zac
>
> [1] http://sparkle.adiumx.com/?year=2008&week=23&graph=bar#appVersion
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com