Announcement

Collapse
No announcement yet.

Better Input Device Support Is Coming To KDE's KWin On Wayland

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Better Input Device Support Is Coming To KDE's KWin On Wayland

    Phoronix: Better Input Device Support Is Coming To KDE's KWin On Wayland

    Martin Gräßlin's latest focus on KDE development has been improving the input device support under KWin, particularly for when it's acting as a Wayland compositor...

    http://www.phoronix.com/scan.php?pag...and-Plasma-5.7

  • #2
    What about making wayland plasma 5 to work?

    Comment


    • #3
      Already works. Usability of Xorg is still better, but you can download Neon - wayland to try it. So With lastest DDX driver based EGL (just like Wayland's) you can't better experience on Wayland compared to Xorg, Wayland will be the future

      Comment


      • #4
        Nice progress. Looks like so far it's the proprietary drivers that are lagging behind a bit.

        Comment


        • #5
          Originally posted by GreatEmerald View Post
          Nice progress. Looks like so far it's the proprietary drivers that are lagging behind a bit.
          Anyone is free to add support for proprietary drivers.

          Comment


          • #6
            Originally posted by magika View Post
            Anyone is free to add support for proprietary drivers.

            You mean proprietary drivers are free to add proper support for wayland compositors?

            Comment


            • #7
              Originally posted by bvbfan View Post
              Already works. Usability of Xorg is still better, but you can download Neon - wayland to try it. So With lastest DDX driver based EGL (just like Wayland's) you can't better experience on Wayland compared to Xorg, Wayland will be the future
              that's great for people using neon, but on normal distros is where is still not working (at least on intel)
              Last edited by edoantonioco; 05-11-2016, 05:57 PM.

              Comment


              • #8
                Originally posted by Krejzi View Post


                You mean proprietary drivers are free to add proper support for wayland compositors?
                No, I mean exactly what I said. You may not like proprietary drivers and the way they did things, but it is unfair to complain about them not supporting every Wayland compositor out there when Wayland is supported by the driver. And there is probably more wayland compositors already than we ever had for X.

                Comment


                • #9
                  Discussion seems to gone into confusion. GreatEmerald meant missing support for Wayland. If I didn't miss anything, NVidia devs last time were arguing their implementation of Wayland with devs of Weston, thus its not ready yet. Krejzi, magika drivers doesn't have to know anything about a compositor — they implement Wayland API, and compositors uses the implementation in whatever way they want.

                  Comment


                  • #10
                    Originally posted by edoantonioco View Post
                    What about making wayland plasma 5 to work?
                    Why do people feel the need to tell developers what to prioritize?
                    He worked on it, made it (kwin, not anything else because he's the kwin guy) work. It works about as well as anything Wayland-powered does right now.
                    He wants to work on other areas, it's not like he's got a short list of things he could work on.
                    If you want to pay a developer, you then have some right to claim to be able to say what they work on.

                    Comment

                    Working...
                    X