Proposals for 3.0.0 API changes

Mark Doliner mark at kingant.net
Fri Jan 4 02:20:15 EST 2008


On Sun, 30 Dec 2007 22:02:23 -0500, John Bailey wrote
> In the msn-pecan thread, Gary and I agreed that an API freeze after 
> 2.4.0 in order to implement struct member hiding would be a good way 
> to help us on the road to having libpurple's objects implemented 
> purely as GObjects.  Ka-Hing voiced support for the proposal.
> 
> To that end, I propose a few changes, some of which have already 
> been proposed previously by Sadrul, Richard, Will, Gary, and 
> probably others.  3.0.0 is obviously the perfect time for massive 
> changes such as these, because they will break API and ABI 
> compatibility with 2.x:
> 
>   * Kill the Gaim compatibility headers.  Plugin authors have now 
> had almost 8 months to update their code--this is ample time.
> 
>   * We have some deprecated functions in libpurple, mainly some 
> logging stuff and the stuff deprecated by Will's disconnect reason 
> stuff.  Kill all deprecated API.
> 
> These next two are far less important and could be overlooked if desired:
> 
>   * The plugin prefs API and the request fields API overlap.  Merge 
> them into a simpler, more coherent API.

All of the above sound like fantastic ideas to me.

>   * I'd like to rename the purple_notify_user_info stuff.  Maybe
> purple_user_info or similar.  I realize that right now this is only 
> used within the notify API, but I expect its use will have wider 
> applications in the future.

I don't understand this one.

-Mark




More information about the Devel mailing list