Mercurial > pidgin.yaz
diff ChangeLog.API @ 21225:e967fd47baa5
propagate from branch 'im.pidgin.pidgin' (head 26e91b9e80a9d63c85455f11102f75f36cb95afc)
to branch 'im.pidgin.pidgin.next.minor' (head 437f2181e715cb65bbeaede6e8d80a4656a6cf05)
| author | Richard Laager <rlaager@wiktel.com> |
|---|---|
| date | Fri, 12 Oct 2007 03:53:58 +0000 |
| parents | 086b6e3e5015 693c485a1983 |
| children | cc8bdfb16ddf fa3c4c5dea66 |
line wrap: on
line diff
--- a/ChangeLog.API Fri Oct 12 03:49:39 2007 +0000 +++ b/ChangeLog.API Fri Oct 12 03:53:58 2007 +0000 @@ -1,5 +1,27 @@ Pidgin and Finch: The Pimpin' Penguin IM Clients That're Good for the Soul +version 2.3.0 (??/??/????): + libpurple: + Added: + * purple_request_field_blist_nodes_new and its accessory functions. + * a PurpleConversation field in PurpleConvMessage + * account-authorization signals (see account-signals.dox for + details) (Stefan Ott) + * libpurple/purple.h, which includes #define's and #include's + required to compile stand-alone plugins + * purple_plugin_disable(), which is intended to be called when + a purple_plugin_unload()--which was called when a user tried + to unload a plugin--fails. This then prevents the plugin + from being saved in the saved plugins list, so it'll won't + be loaded at the next startup. + + Changed: + * purple_plugin_unload() now honors the return value of a + plugin's unload function and can actually return FALSE now. + * purple_plugin_unload() no longer does its own notifications + when a dependent plugin fails to unload. The UI should do + something appropriate. + version 2.2.2 (??/??/????): libpurple: Changed:
