Wayland Window Management Proposal
hramrach at centrum.cz
Fri May 13 11:44:23 PDT 2011
2011/5/13 Rui Tiago Cação Matos <tiagomatos at gmail.com>:
> On 13 May 2011 18:59, Mike Paquette <paquette.mj at gmail.com> wrote:
> Completely agree. The compositor/WM has no business in working around
> application bugs. If application programmers are lazy and can't get
> their windows acting timely on input then, the ecosystem (users,
> distributors) will just "naturally select" those apps out and the well
> behaved ones will just be more popular.
> Hiding badly designed applications' problems is just rewarding bad
> work and, in this case, it's even worse. If the compositor acts on
> input before the application draws the final frame it will create
> graphical "flashes" (background color, autofill, junk, whatever) for
> *every* application which actually penalizes the good ones because the
> graphical glitch will be there, even if for a single frame, since this
> is inherently how server side asynchronous actions behave.
Again, do you really know only one transition between two frames - flashing?
With all the effects compositors are capable of today this is the only
thing you can think of?
More information about the wayland-devel