No subject

Thu May 10 10:12:13 PDT 2012

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, and really should be centralized.  All just
my opinion, of course.

Best regards,
Brad Peters
System integration team, OTC Intel

On Thu, May 10, 2012 at 9:58 AM, Tiago Vignatti <
tiago.vignatti at> wrote:

> On 05/10/2012 07:45 PM, Christopher James Halse Rogers wrote:
>> On Wed, 2012-05-09 at 23:31 +0200, Jonas =C3=85dahl wrote:
>>> Hi,
>>> This series of changes introduces better support for touchpads when usi=
>>> 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 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 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
>> crystallising as an input-module ABI compositors could share?
>> I think I'd like the latter to happen, but what are others thinking
>> about this (if anything =E2=98=BA)?
> yeah, there's nothing that prevents us (well.. copyright might be
> something) to have one single consolidated module for input that all
> compositors could dlopen it. At the moment we're not sharing yet because =
> simply doesn't have much, but I'd say once it grows up and some nice
> features get added there, then clutter, qt, efl, etc will want to benefit
> from it.
> Tiago
> ______________________________**_________________
> wayland-devel mailing list
> wayland-devel at lists.**<wayland-devel at

Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

More information about the wayland-devel mailing list