Linked by martini on Tue 23rd Oct 2012 22:02 UTC
X11, Window Managers Wayland 1.0 was officialy released on October 22. Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.
Permalink for comment 539953
To read all comments associated with this story, please click here.
RE[3]: Comment by stabbyjones
by ssokolow on Thu 25th Oct 2012 04:29 UTC in reply to "RE[2]: Comment by stabbyjones"
ssokolow
Member since:
2010-01-21

It's an either/or situation, both have advantages and drawback:
-client side decoration: looks better but can be a problem if the application is blocked and resizing can be "jerky" if the application is slow.
-server side decoration: resizing the window is smooth but the content of the window can be ugly if the application is slow, less pretty for transformed windows.


I never really minded the desync between window borders and window contents. I considered it a necessary (and possibly even desirable) alternative to the risk of jerky resizing.

(For similar reasons to why I prefer tactile switches on a keyboard when feasible. User feedback must NEVER desync to a degree the user notices, even if that means ugliness. On a keyboard, desync means the user never builds the habit of trusting their muscle memory and must visually double-check their actions, resulting in slower interactions. With a mouse, desync means waiting to see if the system will "catch up" beyond what they intended, rather than just committing to the action as it looks at that instant.)

Hence why I'll be giving KDE 4 (or at least KWin) another chance unless I see another featureful WM promise Weston support with the option to force server-side decorations.

Let's just hope that someone will be able to patch whatever client-side decoration system wins out so that it can do the "use D-Bus to request WinDeco widgets from the WM" thing if it needs them.

(As with Canonical's AppIndicators, I think the idea of using D-Bus to have the WM draw in-border widgets is a good one and a big step forward for UI consistency... I just refuse to use apps which only support libindicator because I insist that left-click toggle application visibility and right-click show a context menu on my tray icons.)

Edited 2012-10-25 04:36 UTC

Reply Parent Score: 3