Forsed disabled clienside window decoration

[Bill Spitzak]

I am also interested in methods to either tell the client to not draw 
the "edges" or for the compositor to know the thickness of these so that 
it can clip them off, so that attach-to-output-edge effects (maximize 
height, snap-to-edge, maximize, and full-screen) can be done.

It looks like the window name has been provided as information to the 
compositor. I would recommend a STRICT limiting to this. If you want to 
control the appearance of titlebar buttons or anything about the 
behavior, you MUST draw client-side decorations. Communicating this 
information will quickly become vastly more complex than any client-side 
decorations, as can be seen in the amount of overhead in ICCCM.

On 07/08/2012 07:16 PM, Juan Zhao wrote:
> On Sun, 2012-07-08 at 18:15 +0400, Сергей Волков wrote:
>> 1) Hello, can you add method in the wayland protocol for forced
>> disabled clienside decorations. I think it's would be good idea to add
>> one method for all applications to forced hide client decorations!
>> This is help to make diffirent windows managers like in X server
>> (tailing, floating e.t.c) and enable to costomize window decorations
>> in one place for all toolkits!
>
> The client-side decorations were drawn inside client side(toytoolkit),
> no need to add method in wayland protocol, IMHO.
> To implement it, maybe we could try to add some API in toytoolkit to
> disable it.
>>
>> 2) What about window meta-informations?
>>
>> p.s.
>> sorry for my bad english
>> _______________________________________________
>> wayland-devel mailing list
>> wayland-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
>
>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel