1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

The Focus Of Wayland's Weston Compositor

Wayland

Published on 19 April 2013 08:47 PM EDT
Written by Michael Larabel in Wayland
26 Comments

Kristian Høgsberg has clarified the scope and goals of Weston, Wayland's reference compositor. Now that Weston has become somewhat of its own desktop environment, Kristian has clarified its intentions to benefit future patches.

In hopes of clarifying future development work that could be potentially accepted upstream, Kristian has written on the developer's mailing list about clarifying the scope and goals for Weston.

Here's the heart of Kristian's message:
Part of the confusion around this is that weston started out as just a way to verify the protocol as well as gbm, KMS, evdev etc integration, which implies that it's throw-away code or at best a source for copy and paste. On the other end of the scale, what weston is today is obviously a lot more than just sample code, we even have a toy desktop that makes it look like it's a real desktop environment.

In my mind, the main output of weston is the core compositor and the plug-in API. We have a very efficient GLES2 renderer, very good KMS integration and overlay usage, and a good input stack. We have good infrastructure for writing custom backends and a flexible way to plug-in a higher-level shell component to handle window-manager-like responsiblities. This is the part of weston I consider product quality and we have to maintain high standards when working in that area - strict error checking, handle all corner cases etc. The core compositors goal is to be a base for other projects, similar to how the X server isn't a full desktop environment or mobile/embedded UI, but a core technology to build one upon. It is also still the reference implementation and must implement and exercise all core protocol.

The desktop shell in weston serves three goals: to validate wl_shell protocol, to make weston do something useful when you start it up, and to provide a reference for how to implement a shell module. The desktop shell is not supposed to be a generally useful desktop
environment. When we're implementing something for the weston desktop shell, we go for simplicity and protocol coverage rather than full configurability or external dependencies.

As for xwayland, I'd like this module to be better quality and provide easy integration of X applications for UIs that build on weston. As it is, it's rather spotty in its support for ICCCM and EWMH though, and mainly serves as a validation effort for X integration.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. Scythe Mugen MAX
  2. Intel Core i7 5960X Haswell-E On Linux
  3. Intel 80GB 530 Series M.2 SSD On Linux
  4. With A New Motherboard, The Core i7 5960X Haswell-E Lights Up
Latest Linux Articles
  1. 7-Way Linux Desktop Gaming Comparison On Ubuntu 14.10
  2. Intel P-State vs. CPUFreq Benchmarks On The i7-5960X
  3. RadeonSI GLAMOR Benchmarks With X.Org Server 1.16
  4. RadeonSI Gallium3D vs. Catalyst At 4K UHD On Linux
Latest Linux News
  1. Mesa Gets Closer To Having OpenGL 4.0 Tessellation Support
  2. Uselessd: A Stripped Down Version Of Systemd
  3. F2FS Tools Gain FSCK Support
  4. FreeBSD 10.1 Has The New VT Driver, Hardware Improvements
  5. AntiMicro 2.6 Yields Greater Compatibility For Gamepads On Linux
  6. OpenGL 3.3 / GLSL 3.30 Lands For Intel Sandy Bridge On Mesa
  7. AMD's RadeonSI Gallium3D Driver Sees Some Improvements
  8. Mesa 10.3 Released With The Latest Open-Source GPU Driver Improvements
  9. GNOME 3.13.92 Officially Released
  10. Wine 1.7.27 Is Still Working Towards Direct2D Support
Latest Forum Discussions
  1. New stress testing utility for GPU's
  2. Stop grabbing my keyboard :(
  3. New Group Calls For Boycotting Systemd
  4. X.Org Women Outreach Program Only Turns Up Two Applicants So Far
  5. SSD seems slow
  6. R. Tyler restarts work on FreeBSD launchd port, openlaunchd
  7. Can Linux kill a motherboard?
  8. Glamor now enabled in Debian radeonsi