Wayland Window Management Proposal
hramrach at centrum.cz
Wed May 11 06:29:18 PDT 2011
On 11 May 2011 14:31, Mark Constable <markc at renta.net> wrote:
> On 2011-05-11, Michal Suchanek wrote:
>> Maybe in an ideal world each application would be split
>> into two (or more) processes, one taking care of the UI
>> interaction and the other(s) doing the actual work so
>> that the UI is always responsive.
>> However, this is not the case and for moves and resizes
>> to work properly they have to be done in the window
>> manager. For many applications responding to UI events
>> is rather low priority and when they are busy doing
>> something the UI is not going to be handled.
> Perhaps a compromise could be a wayland-client.so lib that
> all compliant Wayland applications must link to at runtime
> and it provides consistant window management functionality.
For that to work the library would have to create an UI thread which
is always ready to respond to resize requests, and it could *not* do
the actual drawing which can be potentially time consuming.
I don't see what you get here.
Many applications will refuse to use that because they cannot accept
multi-threaded operation for some technical reason (usually imposed by
some other library) and you still don't get any guarantee about the
behaviour because the moment this library invokes any application
supplied callback it does not guarantee anything and when it does not
it cannot do anything being virtually useless.
Plus even if you provided such lib and it somehow worked it would be
useless for applications written in sane languages (eg. not C).
More information about the wayland-devel