[Bug 20774] ConnectionManager: Protocol objects

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=20774

--- Comment #18 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-06-28 10:28:59 PDT ---
(In reply to comment #16)
> After reviewing tp-glib impl and implemented support in tp-qt4 there are just 2
> things that I don't think really fit here.
> 
> IMHO EnglishName and Icon are out of place here, we should probably add them to
> Profile.

They should definitely be in profiles *as well*, but one of the goals of this
work was that random connection managers (particularly, connection managers
that aren't shipped by OS integrators, like the telepathy-extras on Maemo)
should be usable without a profile, and that plugin-based connection managers
that randomly grow new protocols (like telepathy-haze) aren't limited by a
static set of profiles either.

If your desktop locale isn't English, it still seems better to have English
names than (a mangled version of) Telepathy names ("MSN" or "Windows Live
Messenger" are both better than "msn" or "Msn", even if you'd really prefer it
to be "Windows Live メッセンジャー").

> UIs can and will probably have localized versions of EnglishName and
> Icon can easily be parsed by the UI using the protocol name, as
> im-[protocolname].
> But it won't hurt having them here, but I think it is not needed at all.

If im-foo was part of the Icon Naming spec I'd agree, but they're not, and when
they are we'll still need a way to handle any mismatches between Telepathy and
Icon Naming (e.g. Telepathy's 'jabber' should really be 'im-xmpp').

TpProtocol and TpAccount both fall back to im-$protocol if Icon is the empty
string, and I'd suggest that telepathy-qt4 should do the same if it doesn't
already.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.