[Bug 28197] Account.I.External: support for immutable accounts in Mission Control

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Sjoerd Simons <sjoerd at luon.net> 2010-06-07 10:07:00 PDT ---
(In reply to comment #0)
> +++ This bug was initially created as a clone of Bug #28192 +++
> 
> With the introduction of account plugins for MC it is now possible to have MC
> exporting accounts that cannot be edited directly (i.e. account parameters are
> calculated using some other information, e.g. for single-sign-on style
> accounts).

Why is this called external? what does external mean? Using Backend as a name
might be better (then we can have one for MC itself as well with just a default
value and we don't have an interface that's only sometimes there)

> This patch adds a new optional interface, Account.Interface.External, which
> presents 3 properties:
>  - b:External - indicates whether the account is external, and thus immutable;

I'm not sure if this implication is correct. We might need a bit more
fine-grained control. For some backend we might be able to disable and enable
the account for example, but not change it's parameters. 

>  - s:ExternalName - a name for the interface that will be opened to edit the
> account; and

It seems like this is a human readable name, which i'm not entirely sure of as
we have no way to actually launch the external helper atm?

Could this be the (dbus like name) name of the backend instead? In that case a
UI could have a translation internally (like we do for protocols) and/or know
how to edit it.

>  - s:ExternalEditor - a D-Bus well-known name for a program that can be
> activated to edit the account -- the mechanism for doing this hasn't been
> specified yet, in the short term we intend to simply use these as unique
> identifiers.

In that case it might be best to leave it out for now? In general i'm not sure
if we'll always ahve some external thing to edit it or you UI might internally
load some widgets/helper to edit it itself.. I'm not generally against this but
if you add it also specify how to use it please :) 

Also can we add:

a{sv}: BackendAccountProperties, which contains a backend specific mapping for
misc? (Could included for example the account ID from the perspective of the
backend and some other backend specific meta-data)

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