2 ms·
>This is because the semantics of the Wayland protocol have taken over some of the functions previously handled (on X11) by a separate piece of software, called
by charcircuit 3y ago
>This is because the semantics of the Wayland protocol have taken over some of the functions previously handled (on X11) by a separate piece of software, called a "window manager", which contributed heavily to the look, feel, and behavior of a particular desktop GUI.
Window managers can be separate with Wayland too. It just seems like the Wayland people don't want to unify under one implementation and have separate window managers.
- yjftsjthsd-h 3y agoIn practice, I'm not aware of anyone trying to write a compositor for wayland that doesn't include the window manager (other than xwayland, I guess).
- LoganDark 3y agoThis is because unifying the display manager, compositor, and window manager allows for each implementation to be far more integrated. For example, this opens up the door to virtual-reality or mixed-reality Wayland display managers, that can run desktop apps without the usual overhead of screen capture. Xorg can't do that. Trying to make Xorg do that will only end in misery.
- charcircuit 3y agoBeing much more integrated isn't actually that valuable. VR compositors already render a full screen frame that goes straight to the display. The window manager for VR is typically in a separate process from the compositor. You could add Wayland support to an existing VR compositor, but that wouldn't force you to combine the window manager into the same process.
- LoganDark 3y agoExcuse me, but try to actually use any VR window manager, today, on an OS like Windows. It will bog down and eventually crash your GPU when you open too many windows, because it has to capture those windows from the regular desktop. A Wayland display manager on Linux would not have this issue, because it would already be the window server, so it wouldn't have to perform any extra captures. I only know about this because I have experience trying to do this exact thing.
- charcircuit 3y agoWayland would have the same exact problem as you described if it was implemented by copying a window's surface to the surface you are submitting to the compositor. The solution in both cases is to just submit the original surface to the compositor. >I only know about this because I have experience trying to do this exact thing. Did you use Windows Mixed Reality? If you want deep integration with the operating system, you should use the implementation that is part of the operating system.
- LoganDark 3y ago> Wayland would have the same exact problem as you described if it was implemented by copying a window's surface to the surface you are submitting to the compositor. Sure, but as far as I can tell, Wayland seems to be the only architecture that would allow you to not do this. Windows does not hand you the original surface. Xorg does not hand you the original surface. But if you are the Wayland display server, you have the original surface because you're the one who created it. So if you start drawing to an HMD, you can place existing windows on it with no extra overhead. > Did you use Windows Mixed Reality? If you want deep integration with the operating system, you should use the implementation that is part of the operating system. Yes. I do use Windows Mixed Reality. Which does not support opening desktop windows into the virtual space; it only supports mirroring an entire display onto a surface, and not even capturing individual windows. For that purpose I tried XSOverlay and OVR Toolkit running on SteamVR, which have that capturing issue.
- charcircuit 3y ago>Wayland seems to be the only architecture that would allow you to not do this All modern operating systems use this same architecture where apps render into a texture which the compositor can use. Wayland is not unique in having applications just render to a surface which the compositor composites into the final ouput for the display. We have been doing things this way for decades. Saying that xorg cannot do it doesn't mean much because xorgs design is bad and decades behind. This ability has nothing to do with why wayland compoaitors have a wm built in instead being able to easily interface many different ones. >Which does not support opening desktop windows into the virtual space Look at this video. He has blender open without mirroring a display. https://www.youtube.com/watch?v=gPkcDg8IECU https://www.youtube.com/watch?v=gPkcDg8IECU