Announcement

Collapse
No announcement yet.

KDE KWin Introducing Item-Based Scenes For Improved Wayland Support

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

  • KDE KWin Introducing Item-Based Scenes For Improved Wayland Support

    Phoronix: KDE KWin Introducing Item-Based Scenes For Improved Wayland Support

    More KDE KWin Wayland improvements are coming down the pipe...

    https://www.phoronix.com/scan.php?pa...nd-Item-Scenes

  • #2
    Again KDE moving forward...Thank you devs.

    Comment


    • #3
      If this means that tabs can be detached and reattached to browsers/file managers/etc. like they already could be done previously in X11 then I'm all in favor of it.

      Comment


      • #4
        I had deja vu reading this description. Oh yes, here it goes:

        https://subdiff.org/blog/2021/the-windowing-revolution/
        https://subdiff.org/blog/2021/window-kindergarten/
        https://subdiff.org/blog/2021/curious-child/

        Comment


        • #5
          Honestly I am impressed how nothing they managed to do nearly nothing for 6 years and now put such a speed on the road.
          I like whatever helpes the ecosystem to move away from X on Metal ASAP

          Comment


          • #6
            Yep. Also the first thing that came to my mind, and exactly the design KWinFT's contributor was criticizing in his blog post.

            I really wonder if KWinFT will keep up against KWin. I'm also in favor of simplification over addition. We'll see how it pans out.

            Comment


            • #7
              I finally worked around all the DPI issues I had when using KDE/Wayland just to notice that GTK applications like Firefox don't export global appmenus when launched under a Wayland session. Is there anything that can be done about that?

              Comment


              • #8
                Originally posted by Alexmitter View Post
                Honestly I am impressed how nothing they managed to do nearly nothing for 6 years and now put such a speed on the road.
                I like whatever helpes the ecosystem to move away from X on Metal ASAP
                Not doing what you want doesn't mean they did nothing. They broke down the whole KDE Frameworks into smaller, more maintainable modules, instead of chasing wild geese.

                Comment


                • #9
                  Originally posted by Alexmitter View Post
                  Honestly I am impressed how nothing they managed to do nearly nothing for 6 years and now put such a speed on the road.
                  I like whatever helpes the ecosystem to move away from X on Metal ASAP
                  GNOME had glaring performance issues and sat on their asses for years, until Canonical stepped up. The guy writing a gargantuan GJS patch right now is also a Canonical employee.

                  If you're going to criticize KDE for being slow, at least be coherent.

                  Comment


                  • #10
                    Originally posted by Alexmitter View Post
                    Honestly I am impressed how nothing they managed to do nearly nothing for 6 years and now put such a speed on the road.
                    I like whatever helpes the ecosystem to move away from X on Metal ASAP
                    It took them almost 10 years to create the Wayland protocol (it's just a protocol), it is not clear why the support of compositor should be faster.

                    Comment

                    Working...
                    X