touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Every large toolkit already has it's own preferred config storage and
API to access that. Putting a redundant implementation in Mir is not
helpful. You would either end up with the old problem of many different
config file formats in unrelated places accessed using unrelated APIs,
or a redundant config API that real shells will never use.

The best outcome for Unity8 would be for it to have a nice GUI that talks GSettings (or whatever it prefers) directly. Such an implementation would bypass any storage features in Mir. It should not exist in Mir. If you look at the thread, most people are saying what I'm saying here:
https://lists.ubuntu.com/archives/mir-devel/2015-January/thread.html#1018

There is a compromise that might make sense however...
While libmir* should not have any feature that touches the disk or writes files, it might provide a serialization function to convert a config structure into a string (and vice versa). And a string is something that any configuration API can use; QSettings, GSettings, gconf, INI, XML. So we can make it easier for shells, without imposing any particular file structure from Mir.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1401916

Title:
  Configuration of screens positions and geometry

Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  New
Status in Ubuntu UX bugs:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Under unity7/xorg it's possible to configure the position of the screens and their geometry, that includes
  - resolution of each screen
  - rotation possible
  - relative position (external on top of laptop, or on the right)
  - definition of a "primary" monitor (the one containing the launcher if you decide to have that UI element only on one screen)
  - etc

  Under unity7 the configuration is applied on login by unity-settings-
  daemon using xrandr. In the new world unity8 should probably be the
  one setting up the configuration at start

  It would be useful to have input from design as well, on what should
  happen when connecting an unity8 powered device to an external screen.
  Should it mirror by default? Do we need settings control to configure
  what to do, ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1401916/+subscriptions