Design decisions for new Protocol: Adium vs Libpurple

[John Bailey]

On 06/26/2010 10:06 PM, Peter Hosey wrote:
> On Jun 26, 2010, at 12:34:00, Bob Tanner wrote:
>> Where can I find more information regarding the trade-offs between Adium native(?) plugins vs libpurple plugin?
> 
> How's the stability of Libpurple's prpl API? Ours tends to consist of shifting sands, with the result that third-party Adium plug-ins have a nasty habit of breaking between Adium releases.

Our public C-based API has not had any removals or backward-incompatible changes
since 2007-05-03, the release date for libpurple 2.0.0.  We've added a ton,
though.  We won't break backward compatibility until we release 3.0.0, which
isn't going to be any time soon.  Our C API and ABI are stable with well-defined
indicators to users/developers when they are extended or broken--the middle
number increases when things are added, the first number changes when we break
backward compatibility.  Plugins written for and linked against libpurple 2.0.0
still work with libpurple 2.7.1 without needing to rebuild, at least on Windows
and Linux, but I have no idea how frameworks and the way libpurple is used
within Adium affect this.

John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20100626/460330f3/attachment.sig>