Mercurial > pidgin.yaz

comparison ChangeLog.API @ 27556:cbee8aecc90a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Free the buddy list data some more at shutdown and some deprecations. I think these deprecations are reasonable. Basically, purple_blist_init should create a PurpleBuddyList*, so each UI doesn't need to do that. The UI data for the PurpleBuddyList is more tightly coupled with the PurpleBuddyList and purple_blist_destroy is called in purple_blist_uninit (and is fully cleaned up now). As libpurple works currently, I believe it's not really possible to have multiple PurpleBuddyLists around (blist.c relies on a single global variable) and when it was discussed on the mailing list a few months ago, nobody was using it as such. Refs #9253 (going to milestone 3.0.0 it).
author Paul Aurich <paul@darkrain42.org>
date Sun, 12 Jul 2009 02:55:36 +0000
parents 8c41a23e6b44
children bff61dad9a6b
comparison
equal deleted inserted replaced
27555:5345dfe48272 27556:cbee8aecc90a
80 core.h for details. 80 core.h for details.
81 * Added introspection of signals exposed via the D-Bus API. 81 * Added introspection of signals exposed via the D-Bus API.
82 82
83 Deprecated: 83 Deprecated:
84 * buddy-added and buddy-removed blist signals 84 * buddy-added and buddy-removed blist signals
85 * purple_blist_destroy
86 * purple_blist_new
85 * purple_buddy_get_local_alias 87 * purple_buddy_get_local_alias
88 * purple_ip_address_is_valid
86 * purple_notify_user_info_remove_entry 89 * purple_notify_user_info_remove_entry
87 * purple_ip_address_is_valid 90 * purple_set_blist
88 * purple_status_type_set_primary_attr 91 * purple_status_type_set_primary_attr
89 * purple_status_type_add_attr 92 * purple_status_type_add_attr
90 * purple_status_type_add_attrs 93 * purple_status_type_add_attrs
91 * purple_status_type_add_attrs_vargs 94 * purple_status_type_add_attrs_vargs
92 * purple_status_type_get_primary_attr 95 * purple_status_type_get_primary_attr