[Telepathy] AccountManager API?

[Murray Cumming]

On Tue, 2008-10-21 at 11:37 +0100, Simon McVittie wrote:
> On Tue, 21 Oct 2008 at 11:36:24 +0200, Murray Cumming wrote:
> > There is apparently an AccountManager D-Bus interface that has
> > information about all telepathy accounts.
> > http://telepathy.freedesktop.org/spec.html#org.freedesktop.Telepathy.AccountManager
> 
> AccountManager and the currently-in-draft ChannelDispatcher are
> implemented by beta versions of Mission Control 5. They are not yet
> considered sufficiently stable for telepathy-glib to generate code (we'd
> have to break ABI all the time).

Do you know roughly when Mission Control 5 will be released? What
version numbers are these "beta versions of MC 5"? Is 4.67 a beta
version of 5 or a late stable version of 4?
I see these releases:
http://sourceforge.net/project/showfiles.php?group_id=190214&package_id=224579

Do you know roughly when telepathy-glib might provide API for this.

> Mission Control 4 (the version currently recommended for use) provides
> roughly analogous functionality, but most of it is via a C API rather
> than D-Bus.

I assume that that MC4 API is not worth documenting now. 

> This is currently an area of heavy development; we're aware that the
> current situation isn't very good. MC 5 isn't yet ready for
> desktop use (it has no ABI guarantees at the moment).
> 
> > I was hoping that I could use this interface to get all the
> > parameters needed by 
> > tp_cli_connection_manager_call_request_connection()
> > http://telepathy.freedesktop.org/doc/telepathy-glib/telepathy-glib-connection-manager.html#tp-cli-connection-manager-call-request-connection
> 
> The idea is that the AccountManager (or MC4 if that's what you're using)
> calls RequestConnection for you, so (for instance) the Empathy contact
> list/notification area icon only ever needs to interact with accounts,
> not with RequestConnection parameters.
> 
> The account creation/editing UI (e.g. Edit->Accounts in Empathy) is still
> expected to be able to cope with RequestConnection parameters (they have
> to be supplied to MC somehow). It finds out the required/optional
> parameters using TpConnectionManager, and uses protocol/CM-specific
> knowledge to provide a suitable UI to ask for them.

-- 
murrayc at murrayc.com
www.murrayc.com
www.openismus.com