Summary: | Move miscellaneous information from profiles to CMs | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | see 20774 | ||
i915 platform: | i915 features: |
Description
Simon McVittie
2008-09-30 04:19:51 UTC
We also need to represent things like message length limits (like SMS, for instance). (In reply to comment #0) > The move of "profiles" from mandatory to optional in Mission Control 5 leaves > us with nowhere to put various misc information about the protocols, which > should really have been in the CM in the first place. > > Things to consider: > > * static CM protocol capabilities (bug #17312) > * icon (or define a way to construct an icon name, e.g. im-jabber-gabble > falling back to im-jabber) > * protocol name in at least the C locale, with a note saying that UIs SHOULD > pass it through gettext (in their own domain) before displaying it (we sort of > have this from GetProtocol, e.g. jabber, although the capitalization is wrong) This is bug 20774 and 20775. > * vCard field represented by this CM (e.g. X-JABBER) Bug 20774 covers this for the "primary" v-card field; for other fields, bug 26866 is the place. > * URI schemes supported by this CM? (e.g. xmpp: - but for that to work, we need > a way to turn a URI into a handle) I think bug 26866 is the place for this, too. The rest of profiles is covered by bug 24897. I'm going to mark this as a dup of that bug. *** This bug has been marked as a duplicate of bug 24897 *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.