Announcement

Collapse
No announcement yet.

KDE Now Deals With GTK CSD Headerbars - Improving GNOME App Integration On Plasma

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

  • KDE Now Deals With GTK CSD Headerbars - Improving GNOME App Integration On Plasma

    Phoronix: KDE Now Deals With GTK CSD Headerbars - Improving GNOME App Integration On Plasma

    There is an exciting improvement to the GTK client side decoration handling ahead of the KDE Plasma 5.18 LTS release due out in February...

    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
    ngraham (sorry for ringing you like this each Sunday ): Any news about fixed KWin vsync on Xorg? It's really terrible that you can't recommend Plasma to anybody without adding "But you should replace KWin with Picom or kwin-lowlatency fork.".

    Comment


    • #3
      I don't have any issues with kwin vsync for my part (AMD GPU + latest mesa).
      Does it happen only with some specific hardware?

      Comment


      • #4
        Originally posted by 144Hz View Post
        Finally! Bugs like this comes from Decoration Freedom. 10 years of angry blog posts didn’t fix it. The industry (mac, win & linux) moved to CSD loong ago.
        Or... every user that likes to have a consistent look of all apps should use KDE. And every developer, that doesn't want to deal with the CSD nightmare, can just use now this new behavior to look native even on Gnome ;-)

        Comment


        • #5
          Originally posted by 144Hz View Post
          The industry (mac, win & linux) moved to CSD loong ago.
          No, Linux did not move to CSD. The xdg-decoration protocol is part of wayland-protocols, because some devs clearly do recognize the validity of both CSD and SSD. Same with Windows, it provides SSDs to applications that don't draw decorations themselves. Mac has always been Apple's "we know what's best for you and you'll like it", so the exact opposite of any sort of "freedom".

          Originally posted by 144Hz View Post
          All power to the app devs and users.
          By that logic app developers should have the power to have their app not bother with decorations and have the window manager provide them with SSDs. Which is exactly what the xdg-decoration protocol provides.

          Also, users should have the power to choose whatever applications they want and get a good experience with them. Which they get on window managers that implement the xdg-decoration protocol.

          Comment


          • #6
            Originally posted by 144Hz View Post
            The industry (mac, win & linux) moved to CSD loong ago.
            And the last 24 years have shown that CSD is a bad idea and has only create visual mess and more unnecessary work for developers.

            The touted "gain" from CSD supporters have given some fancy looking "toy" applications like media players, which most of the time are used full screen or minimized anyway. Or the ability to shave of a few rows of pixels at the top of applications. Maybe a gain 15 years ago, but with today's high resolution screens, not so much.

            Comment


            • #7
              Originally posted by 144Hz View Post
              Gusar You mean the unstable xdg-protocol. It’s not supported.
              Every protocol starts as unstable. But the mere fact that xdg-decoration is in wayland-protocols proves you wrong on your "CSD uber alles" mantra. It's not supported by Gnome because they're more concerned about pushing their "vision" rather then giving their users the best possible experience. Unlike the KDE devs who are making sure that even apps that aren't theirs are well integrated.

              What about Windows though? No retort to the fact that it provides SSDs to applications that don't draw decorations themselves? Of course no retort, everything that doesn't fit your "CSD uber alles" mantra you simply ignore.

              If you really mean your "power to the app devs and users" thing, you should be pushing the Gnome devs to implement the xdg-decoration protocol. Because that, and only that, would give actual power to app devs and users. But you of course aren't *actually* interested in that, you are just like the Gnome devs trying to foist your "vision" onto people, even if it's to the detriment of the user experience.

              Originally posted by 144Hz View Post
              Sorry you don’t get to decide on other users’ and dev’s desires.
              But you do? Because that's exactly what *you* are doing. Right after saying "power to the app devs and users". But of course what you actually mean is "power to the apps devs as long as they're doing things my way and screw the users".

              Originally posted by 144Hz View Post
              SSD is dictatorship.
              *You* are the one dictating things here. It doesn't have to be CSD or SSD. It can be both. This article about what the KDE devs have done is proof of that.
              Last edited by Gusar; 01 December 2019, 10:02 AM.

              Comment


              • #8
                Originally posted by 144Hz View Post
                Again, consistency comes with design.
                Surprisingly you get one thing right, it comes with design.
                And the design providing this is SSD.

                Comment


                • #9
                  Originally posted by 144Hz View Post
                  Gusar Your assumptions and guessing about my motives is just wrong, no further comments or reactions to that kind of behavior.

                  Decoration freedom is an anti-feature just like init freedom. There’s very good reasons why the industry moved to CSDs.
                  "XXX Freedom is an anti-feature." Honestly, I thought I was reading a speech from some dictator. That really looks like something that could have been put in Orwell's 1984 ; or in some Stalin's speech.

                  Having more choice is always good.

                  Comment


                  • #10
                    Originally posted by aufkrawall View Post
                    ngraham (sorry for ringing you like this each Sunday ): Any news about fixed KWin vsync on Xorg? It's really terrible that you can't recommend Plasma to anybody without adding "But you should replace KWin with Picom or kwin-lowlatency fork.".
                    Sorry, I'm not smart enough to follow (let alone understand) anything related to KWin graphics! I can read and track bug reports though. Do you happen to have the URL handy for the bug report tracking this issue?

                    Comment

                    Working...
                    X