Re: [PATCH weston 0/5] Touchpad support

2012-05-15 Thread Peter Hutterer
On Thu, May 10, 2012 at 07:13:09PM +0100, Daniel Stone wrote: > Hi, > > On 10 May 2012 17:45, Christopher James Halse Rogers > wrote: > > Is Weston going to essentially fold in all the interesting bits from all > > the input DDXs to the core (and require this to be duplicated in all > > other com

Re: Code sharing between compositors and some anti-FUD (Re: [PATCH weston 0/5] Touchpad support)

2012-05-11 Thread Christopher James Halse Rogers
On Fri, 2012-05-11 at 10:41 +0300, Pekka Paalanen wrote: > On Thu, 10 May 2012 09:45:44 -0700 > Christopher James Halse Rogers > wrote: > > > This brings up something that I've been wondering: what (if anything) is > > the long-term plan for input in Weston - and Wayland compositors in > > genera

Code sharing between compositors and some anti-FUD (Re: [PATCH weston 0/5] Touchpad support)

2012-05-11 Thread Pekka Paalanen
On Thu, 10 May 2012 09:45:44 -0700 Christopher James Halse Rogers wrote: > This brings up something that I've been wondering: what (if anything) is > the long-term plan for input in Weston - and Wayland compositors in > general? > > Is Weston going to essentially fold in all the interesting bits

Re: [PATCH weston 0/5] Touchpad support

2012-05-10 Thread Bill Spitzak
Though I usually want the client in charge of everything, I think Wayland can, and should, do a lot of input processing. The only requirement is that any processing must be done in such a way that the client can ignore it, get the raw input events, and do it's own. The primary reason is becau

Re: [PATCH weston 0/5] Touchpad support

2012-05-10 Thread Daniel Stone
Hi, On 10 May 2012 17:45, Christopher James Halse Rogers wrote: > Is Weston going to essentially fold in all the interesting bits from all > the input DDXs to the core (and require this to be duplicated in all > other compositors), or should these conceptually be modules, eventually > crystallisi

Re: [PATCH weston 0/5] Touchpad support

2012-05-10 Thread Jonas Ådahl
On Thu, May 10, 2012 at 6:58 PM, Tiago Vignatti wrote: > On 05/10/2012 07:45 PM, Christopher James Halse Rogers wrote: >> >> On Wed, 2012-05-09 at 23:31 +0200, Jonas Ådahl wrote: >>> >>> Hi, >>> >>> This series of changes introduces better support for touchpads when using >>> evdev for input handl

Re: [PATCH weston 0/5] Touchpad support

2012-05-10 Thread Peters, Brad T
>From a distro-development feature, have one input framework would definitely be preferable. Especially for the more complicated touchscreen/pad devices, which require some mechanism for gesture interpretation. That's a lot of code and complexity which is currently duplicated in every UI toolkit, a

Re: [PATCH weston 0/5] Touchpad support

2012-05-10 Thread Tiago Vignatti
On 05/10/2012 07:45 PM, Christopher James Halse Rogers wrote: On Wed, 2012-05-09 at 23:31 +0200, Jonas Ådahl wrote: Hi, This series of changes introduces better support for touchpads when using evdev for input handling. Some of the ideas and algorithms used comes from the xserver and xf86-input

Re: [PATCH weston 0/5] Touchpad support

2012-05-10 Thread Christopher James Halse Rogers
On Wed, 2012-05-09 at 23:31 +0200, Jonas Ådahl wrote: > Hi, > > This series of changes introduces better support for touchpads when using > evdev for input handling. Some of the ideas and algorithms used comes from > the xserver and xf86-input-synaptics repositories. This brings up something that

[PATCH weston 0/5] Touchpad support

2012-05-09 Thread Jonas Ådahl
Hi, This series of changes introduces better support for touchpads when using evdev for input handling. Some of the ideas and algorithms used comes from the xserver and xf86-input-synaptics repositories. The various functionality implemented are anti-flicker (avoid jumping around), smoother motio