Of course it is server side decoration, but it eliminates its main problem. ----- Reply message ----- Von: "Bill Spitzak" <spitzak@gmail.com> Datum: So., Mai. 8, 2011 18:18 Betreff: Antw.: client side decorations An: "andre.knispel@gmx.de" <andre.knispel@gmx.de> Cc: <wayland-devel@lists.freedesktop.org> On May 8, 2011, at 8:25 AM, andre.knispel@gmx.de wrote: > As far as I can tell, the main problem with server side decoration > is that applications cannot modify them and thus they create their > own decoration. Please correct me if I'm wrong. > So why can't we enforce the WM to provide an API for modifying the > decorations? If a WM wouldn't implement it, we'd use some default > decoration for applications that need to use the API. Chrome could > for example get a surface to draw its tabs from KWin, and KWin would > ensure the tabs don't overlap with the buttons, etc. > I hope this wasn't proposed in the thousands of CSD posts before ;) No. What you are describing *IS* server-side decorations. I fully agree with the majority here that client-side is the way to go.