On Wed, May 16, 2012 at 10:10:37AM +0300, Pekka Paalanen wrote:
> On Wed, 16 May 2012 11:39:06 +1000
> Peter Hutterer wrote:
>
> > On Sat, May 12, 2012 at 01:16:38PM +0300, Pekka Paalanen wrote:
> >
> > [snip]
> >
> ...
> > > You are right about input plugins, but there are couple things
> > >
On Wed, 16 May 2012 11:39:06 +1000
Peter Hutterer wrote:
> On Sat, May 12, 2012 at 01:16:38PM +0300, Pekka Paalanen wrote:
>
> [snip]
>
...
> > You are right about input plugins, but there are couple things
> > that should make it not so bad:
> > - a majority of input devices are evdev, so we m
On Sat, May 12, 2012 at 01:16:38PM +0300, Pekka Paalanen wrote:
[snip]
> > Another drawback of Wayland is, that the compositor is also
> > responsible for reading and dispatching input events. If there's
> > a new class of input device _all_ compositors must be adjusted.
> > You could of course i
On Fri, 11 May 2012 14:40:49 +
datenwolf wrote:
> datenwolf (http://datenwolf.myid.net/) has left a new comment on
> your post "Wayland anti-FUD":
Hello!
(This comment was private and quite long, so I thought it would be
better to reply on the mailing list.)
> Stacking compositors is a bad
