Mercurial > pidgin
changeset 19724:36d5d5048b53
Dont spam the buddy info window with esoteric capabilities
author | Sean Egan <seanegan@gmail.com> |
---|---|
date | Tue, 11 Sep 2007 00:10:02 +0000 |
parents | eedf2918aace |
children | 30e4912e4a27 2643bd295495 |
files | libpurple/protocols/jabber/buddy.c |
diffstat | 1 files changed, 11 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/libpurple/protocols/jabber/buddy.c Mon Sep 10 23:54:49 2007 +0000 +++ b/libpurple/protocols/jabber/buddy.c Tue Sep 11 00:10:02 2007 +0000 @@ -799,6 +799,12 @@ purple_notify_user_info_add_pair(user_info, _("Operating System"), jbr->client.os); } } +#if 0 + /* #if 0 this for now; I think this would be far more useful if we limited this to a particular set of features + * of particular interest (-vv jumps out as one). As it is now, I don't picture people getting all excited: "Oh sweet crap! + * So-and-so supports 'jabber:x:data' AND 'Collaborative Data Objects'!" + */ + if(jbr && jbr->caps) { GString *tmp = g_string_new(""); GList *iter; @@ -907,15 +913,16 @@ feature = _("Hop Check"); else if(g_str_has_suffix(feature, "+notify")) feature = NULL; - if(feature) - g_string_append_printf(tmp, "%s\n", feature); + g_string_append_printf(tmp, "%s<br/>", feature); } + if(strlen(tmp->str) > 0) purple_notify_user_info_add_pair(user_info, _("Capabilities"), tmp->str); g_string_free(tmp, TRUE); } +#endif } else { for(resources = jbi->jb->resources; resources; resources = resources->next) { char *purdy = NULL; @@ -957,6 +964,7 @@ purple_notify_user_info_add_pair(user_info, _("Operating System"), jbr->client.os); } } +#if 0 if(jbr && jbr->caps) { GString *tmp = g_string_new(""); GList *iter; @@ -1074,6 +1082,7 @@ g_string_free(tmp, TRUE); } +#endif } }