[mir] Need to expose geometry for autopilot consumption

[Michał Sawicz]

Minimal implementation for platform-api:

http://bazaar.launchpad.net/~autopilot/autopilot/trunk/view/head:/autopilot/display/_upa.py

We'd need to expose similar stuff from unity-mir and wrap in platform-api.

[Thomi Richards (thomir-deactivatedaccount)]

Hi - some more information about what we need:

at a minimum, we need the X and Y resolution of the screen.

If at all possible, making the existing ubuntu platform api bindings "just work" would be the best solution - it would require zero changes in autopilot. Second best would be a dbus API, on a well-defined dbus connection name that exposes the information we need.

Additional information that will come in useful in the future (probably not worth adding now though) includes screen position, additional screen information (relative location, rotation etc).

Finally, in the future we're likely to need more things like this from the shell (off the top of my head: input bindings (tracked in a separate bug), screen capture & video recording services, application API (essentially replacing BAMF)), so maybe there's some things you can do now to make this easier for yourself in the future?

Cheers,

[Gerry Boland (gerboland)]

Am updating platform-api so existing code just works.

Agreed on all those extra requirements, could you write those up somewhere so we can have a concrete list to consider in future?
Thanks
-G

[Gerry Boland (gerboland)]

Change of plan: quick fix is adding a fixed list of screen resolutions to the UPA. A proper unity8 autopilot plugin will soon be made, making this redundant

[Didier Roche-Tolomelli (didrocks)]

I think this one landed