On 10/05/11 07:29, Daniel wrote:
El dg 08 de 05 de 2011 a les 09:47 -0700, en/na Bill Spitzak va
escriure:
Though it is possible, I don't like the idea of clients sending hints
about what areas are the close box or window border, since it implies
there are such concepts as "title bar" and "clos
Actually, I think Iskren made a very important point. To take this one step
further: with CSD, we can't force the client to stop drawing the decoration, we
can only tell the client that it should. So we can assume Chrome having a
decoration for example, what shouldn't be possible in a tiling WM.
El dg 08 de 05 de 2011 a les 09:47 -0700, en/na Bill Spitzak va
escriure:
>
> Though it is possible, I don't like the idea of clients sending hints
> about what areas are the close box or window border, since it implies
> there are such concepts as "title bar" and "close box". The compositor
> can
We have both desktop (for general graphics/media stuff) and mobile
tracks at this year's LPC.
So if you're working on a topic related to one of the above areas,
especially one that has open issues or spans multiple parts of the
stack, please submit a topic for discussion at
http://www.linuxplumber
I can't get one thing out of this discussion.
So you are arguing about client side VS server side decorations,
handling of moves/resizes, maybe even buttons scroll bars etc.
But all wayland does is provide a communication channel that enables
"clients" to draw in the GPU memory, and then "composit