Announcement

Collapse
No announcement yet.

Wayland Back-End For GTK+ Pushed Forward

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

  • Wayland Back-End For GTK+ Pushed Forward

    Phoronix: Wayland Back-End For GTK+ Pushed Forward

    While busy discussing Sandy Bridge Linux support, it's been brought to my attention en route to Las Vegas that the Wayland back-end for GTK+3 has been merged!..

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Also cool is that GTK+ has the multiple backend support now, so the fear that your GTK+ applications will only work with Wayland is gone. The same binaries can work on Wayland natively or work with X11 for people wanting X-style network transparency.

    Comment


    • #3
      Originally posted by elanthis View Post
      Also cool is that GTK+ has the multiple backend support now, so the fear that your GTK+ applications will only work with Wayland is gone. The same binaries can work on Wayland natively or work with X11 for people wanting X-style network transparency.
      Yeah, this could have potentially been a big problem. Luckily the multiple backend work made it into GTK 3.0 (which is getting close to release now) or it may have had to wait until the next major version, which could have been two or three years away...

      Comment


      • #4
        The cruncher will be Wine working on Wayland. Most will not see any usable difference between XORG and Wayland, unless it's 3D gaming or 3D desktop use.

        Comment


        • #5
          Speaking of 3D gaming or desktop use, does anyone know if there are plans for Wayland to support OpenGL in addition to OpenGL ES, which is currently supported (or at least is being worked on)?

          Comment


          • #6
            Originally posted by Prescience500 View Post
            Speaking of 3D gaming or desktop use, does anyone know if there are plans for Wayland to support OpenGL in addition to OpenGL ES, which is currently supported (or at least is being worked on)?
            Is there any reason it would need to?

            Any OpenGl apps would still working on Wayland regardless

            Comment


            • #7
              Originally posted by 0e8h View Post
              The cruncher will be Wine working on Wayland. Most will not see any usable difference between XORG and Wayland, unless it's 3D gaming or 3D desktop use.
              Shouldn't that work with a rootless X server (if not natively)?

              Comment


              • #8
                Wouldn't OpenGL in addition to OpenGL ES allow for greater performance in things like high graphics gaming and what not?

                Comment


                • #9
                  Originally posted by Prescience500 View Post
                  Wouldn't OpenGL in addition to OpenGL ES allow for greater performance in things like high graphics gaming and what not?
                  Afaik when you use OpenGL in your app you don't need Wayland's blessing since OpenGL draws directly to the screen. At most Wayland could tell your app _where_ to draw, but Wayland itself doesn't participate in the drawing process of the apps which use OpenGL for (their own 2D/3D) rendering stuff.

                  Wayland as in "display manager" as opposed to "new standard" does use "OpenGL ES" instead of "OpenGL" to render stuff but that is simply because it wants to run on mobile devices with as little changes as possible and unless you mean OpenGL 4.x there's virtually no big performance difference between OpenGL 1x-3x and OpenGL ES 2.0.

                  Comment


                  • #10
                    Originally posted by Prescience500 View Post
                    Wouldn't OpenGL in addition to OpenGL ES allow for greater performance in things like high graphics gaming and what not?
                    I think ES 2.0 is just the minimum requirement for the compositor (so it's able to run on mobile devices). Since it's just a subset of OpenGL, it's the same performance, just less features.

                    But applications can use any OpenGL version that their graphics driver supports.

                    Comment

                    Working...
                    X