GNOME Bugzilla – Bug 629912
Better heuristic to pick default individual
Last modified: 2011-08-29 10:12:37 UTC
From the "Ideas I had under my shower" departement. Currently when picking the "default" individual for a text chat, we just sort individuals using their presence. That's good but I think we could do better and try to break presence ties using other heuristic: * Pick the most capable individual. While discussing with the contact, I may have to send him a file at some point or maybe want to start a call. I usually use the "Contact" menu from the chat window to do that. Picking an individual which has extra capabilities would ensure that these options are available. I think we should consider (from the most important to the least important): - file transfer - video call - audio call - share my desktop * We could prefer "xmpp" contacts over other protocols. We all love freedom and open protocols and want to promote XMPP. A more pragmatic reason could be that Gabble is our more mature and stable CM so we can safely expect to have less issues when using it for chatting. Also, it will "soon" grow chat encryption support so we'll want to push that as well. On the other hand, if we implement the first suggestion we'll probably have this one as a side effect as Gabble is our more capable CM.
Created attachment 170478 [details] [review] http://git.Collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/features-629912 libempathy/empathy-contact.c | 111 ++++++++++++++++++++++++++++++++++++------ 1 files changed, 96 insertions(+), 15 deletions(-)
Review of attachment 170478 [details] [review]: Apart from a typo, it looks good to me. Please commit, assuming you get permission for a freeze break. ::: libempathy/empathy-contact.c @@ +1831,2 @@ +/* Sort by presence as with presence_cmp_func() and then break ties using the + * most "capabable" individual. So users will be able to pick more actions on s/capabable/capable/
Thanks I fixed the typo. It's not really a critical fix to get in so I think we can merge it for 2.32.1
Merged. Will be fixed in 2.32.1. This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.