• ChristianWS
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    11 months ago

    Not really following what you mean.

    The moment you allow CSD, apps can and will put whatever they want on there, leading to wildly inconsistency in the number of things there.

    CSD will always looks weird cause it takes too much vertical space. It will never look as good as a normal Title Bar, which can be controlled by the server.

    You also lose draggable space, as now buttons are taking space.

    • Fabian � 🏳️‍🌈@mstdn.social
      link
      fedilink
      arrow-up
      4
      ·
      11 months ago

      @ChristianWS It’s not the app that does this. Developer do this, they do this because they think it’s good. The KDE does have a nice visual design group (I was once part of it, So I know :P). It would be possible to define a design guide to follow so apps won’t look out of place, while still are able to make use of CSD.
      Plasma doesnt need to look like GNOMEs implementation of a CSD. The visuals are a completely different thing. The technology is the important part at first.

      • ChristianWS
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        11 months ago

        Design follows technology and vice-versa. Once you allow devs to use CSD they can and will use that space to put buttons on it, and that inevitably leads to inconsistency between apps, because they will never share the same amount of buttons or be divided by the same amount of panels.

        CSD is a Pandora’s box that is best left unopened.

        • Fabian � 🏳️‍🌈@mstdn.social
          link
          fedilink
          arrow-up
          1
          ·
          11 months ago

          @ChristianWS “Design follows technology and vice-versa.” Thats a hard one. Yes, and also no. Things dont need to be the same to behave the same. Take Firefox and Chrome. They do not look the same, they still behave the same. They share a common design guideline. You need to go to the settings to see the parts that differ.
          If KDE provides a good design guideline devs would follow them, because it’s easier and faster to have working patterns instead of putting work into it yourself.

          • ChristianWS
            link
            fedilink
            arrow-up
            3
            ·
            11 months ago

            It doesn’t work for CSD cause you either have a very strict guideline to prevent inconsistency, limiting the number and location of buttons. At which point it is so limiting that Developers need add another bar to hold whatever they can’t put on the header bar, rendering the CSD implementation moot.

            Or you do like GTK and allow inconsistency. You can’t win with CSD.

            And that is not even mentioning if CSD is even a good idea in the first place. Some users deliberately went with Plasma due to the lack of CSD in the first place, those would migrate to LXQT or XFCE.

            • Fabian � 🏳️‍🌈@mstdn.social
              link
              fedilink
              arrow-up
              1
              ·
              11 months ago

              @ChristianWS I think your idea of inconsistency differs from mine. Havin buttons on different locations in a headerbar doesnt have to be inconsistent across apps. Different layouts can be consistent.
              BUT I dont talk about header bars. I do talk about CSD only and they can be whatever a guideline makes them to be. All Qt apps already have a CSD, but they suck and it would be nice if app devs would be allowed to make use of them on the KDE side if they decide that it benefits the app.

              • ChristianWS
                link
                fedilink
                arrow-up
                1
                ·
                11 months ago

                I’m genuinely curious: What exactly do you have in mind with CSDs without the use of a Header Bar?

                CSD and Header Bars are practically synonymous, and I don’t think I’ve seen, or even heard, about CSDs without the context of a header bar

                • Fabian � 🏳️‍🌈@mstdn.social
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  11 months ago

                  @ChristianWS depending on the application different things. Like I said before, the visuals, the design is not what I care about right now. It’s the option to have another talk about that topic in general.
                  Last time, there was no focus on wayland and there wasnt much experience with CSD in general. There also was the proposal of DWD¹ as option, that never came up.

                  1: https://kver.wordpress.com/2014/10/25/presenting-dwd-a-candidate-for-kde-window-decorations/

                  • ChristianWS
                    link
                    fedilink
                    arrow-up
                    2
                    ·
                    11 months ago

                    …how do you hope to have a discussion about a design feature without discussing the visuals? The entire CSD vs SSD debate is one of UX/UI Design

                    You still haven’t provided an example of CSD without a Header bar. I’m familiar with the DWD proposal, the technology used might be different, but the end result is still a Header Bar in all but name.

    • Alex 🇮🇹 💛 🇷🇺@pkm.social
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      As shown by Latte Dock’s Window Buttons widget, apps can display window controls that follow the window decoration theme.

      And in GNOME apps follow some guidelines that include how header bars should be.

      KDE apps do the same for everything but the titlebar that is drawn by KWin. If they are consistent with their content, I don’t see why they wouldn’t stay consistent when making the titlebar/window controls their own responsability.