comparison libpurple/blist.h @ 27480:cbee8aecc90a

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).

27479:5345dfe48272

/**
 * Creates a new buddy list
 *
 * @return The new buddy list.
 */
PurpleBuddyList *purple_blist_new(void);

/**
 * Sets the main buddy list.
 *
 * @param blist The buddy list you want to use.
 */
void purple_set_blist(PurpleBuddyList *blist);

/**
 * Returns the main buddy list.

void purple_blist_show(void);


/**
 * Destroys the buddy list window.
 */
void purple_blist_destroy(void);

/**
 * Hides or unhides the buddy list.

27480:cbee8aecc90a

/**
 * Creates a new buddy list
 *
 * @return The new buddy list.
 * @deprecated In 3.0.0, this will be handled by purple_blist_init()
 */
PurpleBuddyList *purple_blist_new(void);

/**
 * Sets the main buddy list.
 *
 * @param blist The buddy list you want to use.
 * @deprecated In 3.0.0, this will be handled by purple_blist_init()
 */
void purple_set_blist(PurpleBuddyList *blist);

/**
 * Returns the main buddy list.

void purple_blist_show(void);


/**
 * Destroys the buddy list window.
 *
 * @deprecated The UI is responsible for cleaning up the
 *             PurpleBuddyList->ui_data. purple_blist_uninit() will free the
 *             PurpleBuddyList* itself.
 */
void purple_blist_destroy(void);

/**
 * Hides or unhides the buddy list.