Results 1 to 9 of 9

Thread: Weston-Forked Libinput Is Moving Forward With Input

  1. #1
    Join Date
    Jan 2007
    Posts
    13,420

    Default Weston-Forked Libinput Is Moving Forward With Input

    Phoronix: Weston-Forked Libinput Is Moving Forward With Input

    X.Org input expert Peter Hutterer is moving forward with his work on libinput, a fork of the Weston input handling code into its own library so that it's independent of the compositor...

    http://www.phoronix.com/vr.php?view=MTU4NTI

  2. #2
    Join Date
    May 2012
    Posts
    342

    Default

    yay
    this was one big thing i know is/was missing with wayland

  3. #3
    Join Date
    Dec 2011
    Posts
    1,932

    Default

    They should have named it libwayland-input instead...

  4. #4
    Join Date
    Aug 2013
    Posts
    30

    Default

    Quote Originally Posted by uid313 View Post
    They should have named it libwayland-input instead...
    Why? It has nothing to do with wayland.

  5. #5
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,748

    Default

    Quote Originally Posted by uid313 View Post
    They should have named it libwayland-input instead...
    If I remember correctly Wayland deals directly with Evdev and udev events (please correct me if Im wrong), there's no "XInput" or similar layer above it. So yes, this library probably has a Wayland-leaning focus, It should also work as a generic "Im low level but dont want to deal with evdev / udev myself personally for input"

  6. #6
    Join Date
    Jul 2009
    Posts
    256

    Default

    it's a library to sit in between your display server (weston, xorg, mutter-wayland, etc) and your hardware. it's not tied to any particular window system, and also has zero impact on clients.

  7. #7
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,748

    Default

    Quote Originally Posted by daniels View Post
    it's a library to sit in between your display server (weston, xorg, mutter-wayland, etc) and your hardware. it's not tied to any particular window system, and also has zero impact on clients.
    Thank you Daniel

  8. #8
    Join Date
    Jan 2009
    Posts
    1,196

    Default

    Quote Originally Posted by Ericg View Post
    If I remember correctly Wayland deals directly with Evdev and udev events (please correct me if Im wrong), there's no "XInput" or similar layer above it. So yes, this library probably has a Wayland-leaning focus, It should also work as a generic "Im low level but dont want to deal with evdev / udev myself personally for input"
    Libinput, which seems like it should be integrated with the common compositor library that was created recently, registers with udev and is event based thus I'd imagine it's using evdev directly.
    Just read Daniel's post and I see why they didn't integrate the code.

  9. #9
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,748

    Default

    Quote Originally Posted by liam View Post
    Libinput, which seems like it should be integrated with the common compositor library that was created recently, registers with udev and is event based thus I'd imagine it's using evdev directly.
    Just read Daniel's post and I see why they didn't integrate the code.
    just to clarify: it -was- integrated but it was now ripped out and made separate after it was field tested in Weston and they are comfortable with it

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •