| ▲ | chongli a day ago | ||||||||||||||||
Yes, but why is the compositor dealing with this? Shouldn't the compositor simply be deciding which windows go where (X, Y, and Z positions) and leave the rendering to another API? Why does every different take on a window manager need to re-do all this work? | |||||||||||||||||
| ▲ | hedgehog a day ago | parent | next [-] | ||||||||||||||||
Turning the question around, what other part of the system _could_ do this job? And how would the compositor do any part of its job if it doesn't have access to both window contents and displays? I'm not super deep in this area but a straight-forward example of a non-managed app and a color-aware graphics app running on a laptop with an external display seems like it is enough to figure out how things need to go together. This neglects some complicating factors like display pixel density, security, accessibility, multi-GPU, etc, but I think it more or less explains how the Wayland authors arrived at its design and how some of the problems got there. | |||||||||||||||||
| |||||||||||||||||
| ▲ | zahlman a day ago | parent | prev [-] | ||||||||||||||||
I mean, when I hear the word "compositing" I definitely imagine something that involves "alpha" blending, and doing that nicely (instead of a literal alpha calculation) is going to involve colour management. | |||||||||||||||||
| |||||||||||||||||