saving off display config

Christopher James Halse Rogers chris at cooperteam.net
Tue Jan 20 22:42:28 UTC 2015



On Wed, Jan 21, 2015 at 1:36 AM, Alan Griffiths 
<alan.griffiths at canonical.com> wrote:
> On 20/01/15 14:19, Kevin Gunn wrote:
>>  hi all -
>>  Just catching up on some bug house cleaning & found an open question
>>  on this bug
>> 
>>  https://bugs.launchpad.net/mir/+bug/1401916
>> 
>>  Is there an architectural preference for where to save off display
>>  configs ? and reasons for the preference ?
> 
> I would think that persistence in general is outside the scope of Mir
> (or at least libmirserver[1]) as different display servers might
> reasonably have different ideas on if and how it should be done.
> 
> Having said that, Mir providing a default mechanism for
> serialization/deserialization of the display config could make sense.
> 
> [1] I seem to remember discussing other things that would make a 
> useful
> "helper" library that were not Mir proper - maybe we should attempt to
> collate them.

I think this would be an excellent candidate for a helper library. It's 
something that nearly every shell is likely to want to do, but which is 
probably not in scope for mirserver.




More information about the Mir-devel mailing list