Reflector should be rewritten in terms of cc::Surfaces |
|||||||||||||||||||||||
Issue descriptionReflector currently uses ui::Layer and ui::Compositor which Mus will likely not use. Likely, Reflector should be rewritten in terms of surfaces.
,
Apr 18 2016
,
Apr 22 2016
,
Oct 4 2016
,
Dec 1 2016
rjkroege: Do we feel this is a blocker for Mus+Ash or a nice-to-have?
,
Dec 1 2016
kylechar@ and I chatted about how to do this. It's surprisingly easy! We can introduce FrameGenerator::SetMirrorDisplay(...) which will change the behavior of "GenerateCompositorFrame" to instead generate a SurfaceDrawQuad that refers to another display's CompositorFrame. There are plenty of corner cases: What if device scale factors don't match? What if the two displays don't match in size? What if the vsyncs don't match? What happens if you remove a monitor while mirroring? What happens if you add a monitor while mirroring?
,
Dec 2 2016
I like this idea. But... the corner cases are what make it interesting / hard. And: it's conceivable that the existing code could be made to work in Mash? We should investigate that too.
,
Dec 7 2016
Possibly, but it seems like mirroring is a properly of display server and not a property of the window manager? Sticking the code in FrameGenerator is closer to the right architecture IMO.
,
Dec 7 2016
fsamuel@: I agree. I merely noted that it's possible that we could get the reflector operating sooner by re-using the existing code. In the long term, mirroring is definitely something that should be implemented entirely in mus.
,
Dec 7 2016
s/properly/property
,
Dec 9 2016
,
Dec 9 2016
,
Mar 27 2017
,
Apr 24 2017
,
May 25 2017
We will likely need this for mushrome...maybe we can use layers if it turns out to be too much work, but I'd like us to consider this.
,
Jun 7 2017
,
Jun 7 2017
I have been working on it a bit over the last week.
,
Jun 7 2017
,
Jun 8 2017
,
Jun 12 2017
,
Jul 11 2017
,
Feb 26 2018
,
Mar 9 2018
,
Apr 24 2018
Deprecating label Proj-Mustash-Mus-WS in favor of Components.
,
Aug 2
I don't think we need this for Viz. How to make reflector work for OOP-ASH is a different matter. I'm going to close this bug. There should be a different bug tracking reflector for OOP-ASH.
,
Aug 2
Isn't it needed for OOP-D on Chrome OS? Reflector doesn't work with OOP-D, and is needed for display mirroring.
,
Aug 29
This is needed for mash. I don't know enough the bug history to say if it should be this bug, or a new one. If this bug is closed and a new one filed, please tag with Proj-Mash-MultiProcess.
,
Aug 29
It's actually needed for oop-d on CrOS. kylechar@ is working on it.
,
Sep 17
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by fsam...@chromium.org
, Apr 8 2016