Who is working on the non-drawing parts?
j.glisse at gmail.com
Wed Nov 24 07:38:38 PST 2010
On Wed, Nov 24, 2010 at 8:42 AM, Marty Jack <martyj19 at comcast.net> wrote:
> This is all good that the drawing and input event path is cleaned up. I am concerned that will be elegant, and the parts that aren't drawing will be tacked on in a poor way. I would be interested in helping make sure this comes out well. Having worked on LXDE and a potential follow-on for a few years now, I have come away with a very good understanding of all the existing X mechanism.
> Maybe this is all understood and I simply haven't found where it is written down.
> I am interested in what will replace things like
> - ICCCM/EWMH, where a desktop environment can enumerate and control the display clients
> - the things that root and application window properties are used for under X
> - some of the things that selections are used for under X (poor man's system-wide lock manager)
> - Accessibility knobs ("AccessX features")
> - Window states (Iconify, deiconify, "I'm a dock", fullscreen, and such)
Up to toolkit, wayland is about compositing buffer and sending input.
I would advice to leave wayland out of this business and to encourage
some common platform on freedesktop for window properties valid
accross toolkits (gtk, qt, ...)
> - DPMS, XRandR, mouse and keyboard properties (the new xset, xinput, and xrandr, if you will)
Not sure about those.
More information about the wayland-devel