Chrome OS Version: Trunk

In theory, applications with Ozone in Chromium can choose its backends such as X11, DRM/GBM, Wayland, or headless at runtime. However, if we build content_shell with ozone-gbm(DRM/GBM) backend, it does not work well because it does not implement a display configurator to configure displays, but also needs to manage multiple displays. Those display configuration/management features are tightly coupled with ChromeOS so
need to separate those features from ChromeOS so that any ozone-gbm clients could use them more easily.

First, we need to implement a single Interface for Display Configuration and Management so ui::DisplayManager can be the single interface for ozone-gbm clients by moving DisplayConfigurator and DisplayChangeObserver under DisplayManager, which can simplify the relationship between CrOS shell and ui/Display/Manager. Ozone-gbm clients can easily use display configuration/management features by only accessing DisplayManager.

For more details, see the design document at http://bit.ly/2FBXL2c

 

Chrome OS Version: Trunk

In theory, applications with Ozone in Chromium can choose its backends such as X11, DRM/GBM, Wayland, or headless at runtime. However, if we build content_shell with ozone-gbm(DRM/GBM) backend, it does not work well because it does not implement a display configurator to configure displays, but also needs to manage multiple displays. Those display configuration/management features are tightly coupled with ChromeOS so
need to separate those features from ChromeOS so that any ozone-gbm clients could use them more easily.

First, we need to implement a single Interface for Display Configuration and Management so ui::DisplayManager can be the single interface for ozone-gbm clients by moving DisplayConfigurator and DisplayChangeObserver under DisplayManager, which can simplify the relationship between CrOS shell and ui/Display/Manager. Ozone-gbm clients can easily use display configuration/management features by only accessing DisplayManager.

In addition, this change will allow ui::DisplayManager to directly use ui::DisplayConfigurator without ash::WindowTreeHostManager.

For more details, see the design document at http://bit.ly/2FBXL2c

 

Chrome OS Version: Trunk

In theory, applications with Ozone in Chromium can choose its backends such as X11, DRM/GBM, Wayland, or headless at runtime. However, if we build content_shell with ozone-gbm(DRM/GBM) backend, it does not work well because it does not implement a display configurator to configure displays, but also needs to manage multiple displays. Those display configuration/management features are tightly coupled with ChromeOS so we need to separate those features from ChromeOS so that any ozone-gbm clients could use them more easily.

First, we need to implement a single Interface for Display Configuration and Management so ui::DisplayManager can be the single interface for ozone-gbm clients by moving DisplayConfigurator and DisplayChangeObserver under DisplayManager, which can simplify the relationship between CrOS shell and ui/Display/Manager. Ozone-gbm clients can easily use display configuration/management features by only accessing DisplayManager.

In addition, this change will allow ui::DisplayManager to directly use ui::DisplayConfigurator without ash::WindowTreeHostManager.

For more details, see the design document at http://bit.ly/2FBXL2c