4 ms·
Client-side decorations, visible in the screenshot, are a true PITA. It's stupid that each widget set has to replicate this behavior. It results in visual diffe
by lkiux 10y ago
Client-side decorations, visible in the screenshot, are a true PITA. It's stupid that each widget set has to replicate this behavior. It results in visual differences, and it's doubly stupid that this is touted as an "advancement" just for the rate case that you want to override the title bar.
You could have done the inverse, as currently done with X11 (server-side decoration by default, but overridable).
This incurs in stupid behavior for all tiling window managers in wayland, as they cannot enforce the client to remove the title bar. For a tiling window manager user, this a significant downgrade in wayland. The WM protocol in X11 is one of the few areas that let X11 innovate a lot compared to all other desktops. The number of (wonderfully) different window managers is proof. Server-side decorations, in particular, should have been a no-brainer!
- cm3 10y agoAnother unsolved feature in Wayland is ssh-agent/gpg-agent support. I haven't found a way to make it work yet. It's either multiple agents or many fresh agents running.
- jorams 10y agoWhy does Wayland need any sort of ssh-agent/gpg-agent support? I can't think of any reason for Wayland to have anything to do with their functionality, but I'm not at all familiar with Wayland.
- cm3 10y agoThe way this works in X11 is that you usually start your X11 env such that the environment variable pointing to the agent (which got started) is shared and the agent is accessible by applications. That way running ssh or gpg in any xterm will just work. This is not possible at the moment in Wayland. Think of it like OSX's keychain.
- eeZi 10y agoWhy shouldn't it be possible? You can just setup your agent before you start Wayland, it inherits the environment.
- cm3 10y agoHuh, I'll try that. I never thought of it like that because due to conventions the agent was always part of xinit. Might need to come up with a different way of running wayland compositors to keep the actually TTY shell free of the agent.
- sho_hn 10y agoFWIW, we use server-side decos in the Wayland implementation of KDE Plasma and KDE/Qt apps, for these reasons and many others. If anyone says it can't be done, feel free to point them our way :-)
- cm3 10y agoHow?
- naasking 10y ago> It results in visual differences, and it's doubly stupid that this is touted as an "advancement" just for the rate case that you want to override the title bar. Which is a stupid idea in and of itself. It means there's no trusted path to the window manager that programs can't spoof.
- zokier 10y ago> This incurs in stupid behavior for all tiling window managers in wayland, as they cannot enforce the client to remove the title bar But neither can X11 WMs really enforce in any way client to remove title bar. Of course the WM might refuse to render its own decorations, but it can't really deny the client of rendering whatever it wants.
- lkiux 10y agoTrue, but in practice nobody really has a reason to override the title bar, because it forces you to implement dragging and resizing behavior as well. People that do this know the pain. It also works poorly unless you do it at a pretty low level (within the toolkit itself). The only program(s) that do this are chromium and firefox in my machine, and both can disable this because it doesn't look native.
- timidger 10y agoYeah, they really are a pain, hopefully we can transfer to another terminal emulator for it (I'm one of the main developers). Also as an aside, that's actually a linked video, github just does a REALLY bad job of showing that off. I'm going to have to make that more clear.
- Asooka 10y agoI seriously suspect we'll have a WM protocol in wayland before long. Nobody wants to have to reinvent decorations for their application or toolkit over and over. KDE already do server-side decorations, so it's just a matter of time.