Bug 202504 - Handle creating accounts with a protocol supported by more than 1 CM better
Summary: Handle creating accounts with a protocol supported by more than 1 CM better
Status: RESOLVED FIXED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: accounts-kcm (show other bugs)
Version: git-latest
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: 0.4.0
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-04 17:36 UTC by George Goldberg
Modified: 2012-07-06 12:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George Goldberg 2009-08-04 17:36:03 UTC
Often, users might have two Telepathy Connection Managers installed for the same protocol, e.g. telepathy-haze and just about any other single-protocol CM, like gabble or butterfly, will result in two CM's offering jabber or MSN support. In this case, we should make it as simple as possible for the user to specify which one to use.

Some ideas:
- We should avoid bothering the user with the choice of CM unless it is strictly necessary. We should ask to choose a protocol first (with the current protocol list only displaying each protocol once, no matter how many CM's support it).

-Iff the user selects a protocol that is offered by more than one CM, we should present them with a choice of CM's.

- We should make the choose CM screen simple to use, preselecting a default and explaining to the user that "THe default choice of Connection Manager is usually the best one" so they can just prod OK and carry on, but can still change it if they are a power user, or have problems with the other CM.

- We should try and make an intelligent choice of default CM for a protocol:
-- A hard coded list of preferred CM's is a possibility, although this would suffer from the problems of going out of date, or not including all CM's ever written.
-- Another possibility is to dynamically introspect (if telepathy supports this) what capabilities the CM's support, and defaulting to the one with the most. However the weakness with this is a crappy CM which claims to do everything would take priority over a less featured but more reliable one.
Comment 1 David Edmundson 2011-06-16 14:16:13 UTC
Profile files pretty much fix this.