Antw.: client side decorations

Bill Spitzak spitzak at
Sun May 8 09:49:23 PDT 2011

Certainly there should be an easy way to get the "default window  
decorations". I think the correct way is for the client to call an  
client-side "appearance library" that can draw these, tell the client  
about the sizes, and also can draw all the buttons and scroll bars and  
so on.

On May 8, 2011, at 9:27 AM, andre.knispel at wrote:

> Of course it is server side decoration, but it eliminates its main  
> problem.
> ----- Reply message -----
> Von: "Bill Spitzak" <spitzak at>
> Datum: So., Mai. 8, 2011 18:18
> Betreff: Antw.: client side decorations
> An: "andre.knispel at" <andre.knispel at>
> Cc: <wayland-devel at>
> On May 8, 2011, at 8:25 AM, andre.knispel at 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.
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at

More information about the wayland-devel mailing list