Announcement

Collapse
No announcement yet.

Wayland 1.19 Alpha Released

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

  • Wayland 1.19 Alpha Released

    Phoronix: Wayland 1.19 Alpha Released

    As expected, the Wayland 1.19 release dance has begun...

    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
    Without DRM lease no VR. It's not complete at all. At least I won't be able to switch completely.

    Comment


    • #3
      The core Wayland protocol isn't of much interest.

      What Michael should be focusing on is wayland-protocols, which are extensions of the core Wayland protocol.

      Comment


      • #4
        Another Wayland topic. Everyone, get your bingo cards out of the drawer!

        Comment


        • #5
          Is drag-and-drop working now? Or is that planned for an upcoming release?

          Comment


          • #6
            I think Wayland should adopt the Vulkan approach, not the current one.

            Comment


            • #7
              Originally posted by timofonic View Post
              I think Wayland should adopt the Vulkan approach, not the current one.
              Agreed

              I also said this in the last wayland post.

              Comment


              • #8
                Originally posted by furtadopires View Post

                Agreed

                I also said this in the last wayland post.
                This could be a good move, but I'm afraid it's too late now.
                If something like libwayland-compositor was proposed and developed 5 years ago, this could end up inside different compositors.
                But nowadays since every compositor has its own implementation, this library is pointless. New developers may prefer to fork an existing project and start from there.

                Comment


                • #9
                  Originally posted by timofonic View Post
                  I think Wayland should adopt the Vulkan approach, not the current one.
                  Can you expand this? I don't know what is "the Vulkan approach".

                  Comment


                  • #10
                    Originally posted by zxy_thf View Post
                    This could be a good move, but I'm afraid it's too late now.
                    If something like libwayland-compositor was proposed and developed 5 years ago, this could end up inside different compositors.
                    But nowadays since every compositor has its own implementation, this library is pointless. New developers may prefer to fork an existing project and start from there.
                    Maybe it's something for Wayland 2.0?...

                    Comment

                    Working...
                    X