Client display configuration notification

[Alan Griffiths]

On 21/10/15 19:15, Thomas Voß wrote:
> On Wed, Oct 21, 2015 at 4:38 PM, Alan Griffiths
> <alan.griffiths at canonical.com> wrote:
>> On 21/10/15 11:38, Thomas Voß wrote:
>>> Well, we always need to satisfy the case of handing configuration up & down a
>>> nested shell scene. If we don't add the respective functionality to
>>> the client api, we end up in
>>> the situation of Unity8 being unable to speak to its parent Mir
>>> instance. With that, configuration API
>>> should live in the client API from my POV.
>> I'm not sure what /you/ are referring to here. The existing APIs and
>> design deals with handing configuration up & down a nested
>> configuration. The discussion is about adding an API to change the
>> Unity8 "base configuration" - the one used when the current client (if
>> any) hasn't selected a configuration itself.
> Hmmm, I fail to see the difference, even having re-read the thread.
> Would you mind
> summarizing where the difference arises?

https://docs.google.com/a/canonical.com/document/d/1wpoHVYdPZGthN2WS8oDvhRlpyuUqrizK1C4quE4XwMk/edit?usp=sharing