Announcement

Collapse
No announcement yet.

SDL2 Adds Wayland HiDPI Support

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

  • #21
    'everyone is for themselves, because all the burden is on compositors to implement core system features. That's why things are so excruciatingly slow with switch to Wayland'
    Firefox and Chromium are not slow at getting to native Wayland because there are different compositors to target. They are slow moving to modern widgets and components which are Wayland ready. At least, this is how I understand it.

    Comment


    • #22
      Originally posted by treba View Post
      This is really good news. One step closer to having acceptable fractional scaling support. I hope more steam games pick up more recent versions of SDL (or use the runtime one to begin with) so we can use the wayland backend.
      If the games you're thinking about are not linking SDL2 statically (which was generally illegal with the SDL1), you should be able to swap out the SDL2 shared library since its API is pretty stable. I may be wrong though. Also, this may depend on the Steam runtime.

      Comment


      • #23
        Originally posted by 144Hz View Post
        Fedora keeps pushing wayland. Ubuntu keeps polishing x11. And third parties like SDL helps as well. Next Fedora and Ubuntu is all we need. Small steps on drivers, the desktop and the games support. Giant leap for Linux.
        *Cough*Standard Linux Desktop*cough*

        Comment


        • #24
          Originally posted by shmerl View Post
          It's not about Fedora or Ubuntu. It's about compositors. The benefit of Xorg (despite all of its mess) - everyone works on the same thing, so efforts are pooled. In Wayland's world - everyone is for themselves, because all the burden is on compositors to implement core system features. That's why things are so excruciatingly slow with switch to Wayland. DEs are still basically not ready, and modern features take years to materialize.

          For Mutter, KWin, Sway and etc. it would be good if the amount of non shared effort was reduced.
          Isn't that what Mir is for?
          Last edited by Vistaus; 06-13-2019, 11:53 AM.

          Comment


          • #25
            Originally posted by shmerl View Post

            Yeah, that's quite clear he is a troll by now.
            Yeah, he's basically debianxfce's cousin

            Comment


            • #26
              Originally posted by Vistaus View Post

              Isn't that what Mir is for?
              I don't think so. Mir itself is a compositor, not a sharable compositor base. I.e. it's too high level. wlroots is more like what's needed. And if compositor developers don't like it, let them come together and make something else that's truly shared. It's seriously what's needed to speed up Wayland switch.

              Comment


              • #27
                Originally posted by shmerl View Post

                I don't think so. Mir itself is a compositor, not a sharable compositor base. I.e. it's too high level. wlroots is more like what's needed. And if compositor developers don't like it, let them come together and make something else that's truly shared. It's seriously what's needed to speed up Wayland switch.
                But everyone keeps saying projects like MATE will use Mir to get Wayland support because Mir is a good compositor base...

                Comment


                • #28
                  Originally posted by Vistaus View Post

                  But everyone keeps saying projects like MATE will use Mir to get Wayland support because Mir is a good compositor base...
                  I don't think it's a good base. It's a whole compositor already, with specific design decisions and limitations. Base should be more generic.

                  Comment

                  Working...
                  X