Hacker News new | ask | show | jobs
by dlitz 4765 days ago
Some more facts about Wayland and client-side window decorations, quoted from here: http://blog.martin-graesslin.com/blog/2013/02/client-side-wi...

- Nothing in Wayland requires them

- QtWayland allows Clients to turn them off

- KWin as a Wayland compositor will use server side decorations

3 comments

Huzzah! That was pretty much my single biggest disappointment with Wayland. Although I like the visual consistency of server-side decorations, one of my favourite things about X11 is that when an app hangs or otherwise does something weird, the close button in the title-bar still gives me control over the app, I don't have to hope that it's still processing its event loop or bust out some arcane interface like Task Manager and guess what the application's executable is named.
> "No aliasing when rotating/wobbling windows"

Has anyone ever used those things for more than a single day? I honestly thought the current compositing window managers don't even support that novelty stuff anymore.

In the context that's not the point -- another plus for client-side decorations is that no synchronization is needed between the decorator and client for resizing.

Personally I think client-side decorations are far easier to implement reliably and would welcome them becoming default.

I use wobbling windows because it makes my interaction with the system seem more transparent. Rigid windows feel unnatural, but wobbly windows let me become absorbed by my task.
Rotating? That's something very common.
Rotating an entire display is very common, but that's not what GP is talking about.
All I want to know what happens if I kill -STOP any client. Doing this under X while clients had various grabs caused problems. Does Wayland fix this?
In the article they specifically say it does.