comparison libpurple/prpl.h @ 22776:01e375e9b681

disapproval of revision '8086f2cffaab6ed17431381836b9227a64a53270' This really needs to happen with the appropriate magic necessary to allow adding newer functions when necessary without forcing a bump in the major. I am not necessarily succumbing to 'fear of incrementing a version number' or anything, I just don't think this particular feature is important or useful enough. I would be interested to see if there's still any confusion left after the change from 'Screenname' to 'Username'.
author Sadrul Habib Chowdhury <imadil@gmail.com>
date Wed, 30 Apr 2008 11:27:17 +0000
parents 0be4c1f0fa55
children 3fee7e01e51c
comparison
equal deleted inserted replaced
22775:0be4c1f0fa55 22776:01e375e9b681
396 396
397 /* Attention API for sending & receiving zaps/nudges/buzzes etc. */ 397 /* Attention API for sending & receiving zaps/nudges/buzzes etc. */
398 gboolean (*send_attention)(PurpleConnection *gc, const char *username, guint type); 398 gboolean (*send_attention)(PurpleConnection *gc, const char *username, guint type);
399 GList *(*get_attention_types)(PurpleAccount *acct); 399 GList *(*get_attention_types)(PurpleAccount *acct);
400 400
401 /* This allows protocols to specify a more specific term for the "ScreenName" field 401 void (*_purple_reserved4)(void);
402 * in the add account window. This helps avoid confusion for users using protocols
403 * such as MySpace or MSN
404 */
405 const char *(*account_login_label)(void);
406 }; 402 };
407 403
408 #define PURPLE_IS_PROTOCOL_PLUGIN(plugin) \ 404 #define PURPLE_IS_PROTOCOL_PLUGIN(plugin) \
409 ((plugin)->info->type == PURPLE_PLUGIN_PROTOCOL) 405 ((plugin)->info->type == PURPLE_PLUGIN_PROTOCOL)
410 406