Announcement

Collapse
No announcement yet.

XWayland 21.1 Release Candidate Offers Split From The X.Org Server

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

  • #71
    Originally posted by curfew View Post
    Responsibility of drawing (and possibly window management) is separate issue from extended features. There should be no obstacle why there couldn't be a centralized library that every WM used and adhered to. It's simply a design issue that can be solved but so far nobody has cared to try solving.
    I did mention libdecoration, and all I care about is results. So far, the results have been underwhelming.

    Comment


    • #72
      Originally posted by oiaohm View Post
      There is a big elephant in the room with this idea.
      1. Even if the WM doesn't support ignoring the "undecorate" flag (which a secure WM may do), Wayland+SSD allows the window manager to draw a window border that the application can't predict and fake, hijack, or overdraw. Wayland+CSD allows the application to call out to whatever common rendering code is there and then hijack the resulting functionality unless the DE goes out of its way to provide a way for the common rendering code to mark regions as "delegated back to the WM. Process events without them ever reaching the application." (And, even then, the application could still snapshot the controls and then fake a dialog using them overlaid on its body.)
      2. CSD by default encourages designers to design applications that don't deal well with a window manager that forces SSD, resulting in the need for something like the Arcan developer's "If you try to force this on me, I'll implement WM-level cropping and a "hide/show" toggle button to get my SSD back.
      Originally posted by oiaohm View Post
      Yes I would like if someone would take libdecoration and implement a matching proxy wayland compositor implementing xdg-decoration using it.
      I'll agree with that. As I said to curfew, what I care about is results.

      Comment


      • #73
        Originally posted by ssokolow View Post
        1. Even if the WM doesn't support ignoring the "undecorate" flag (which a secure WM may do), Wayland+SSD allows the window manager to draw a window border that the application can't predict and fake, hijack, or overdraw. Wayland+CSD allows the application to call out to whatever common rendering code is there and then hijack the resulting functionality unless the DE goes out of its way to provide a way for the common rendering code to mark regions as "delegated back to the WM. Process events without them ever reaching the application." (And, even then, the application could still snapshot the controls and then fake a dialog using them overlaid on its body.)
        2. CSD by default encourages designers to design applications that don't deal well with a window manager that forces SSD, resulting in the need for something like the Arcan developer's "If you try to force this on me, I'll implement WM-level cropping and a "hide/show" toggle button to get my SSD back.
        Point 1 for you have the problem that you have applications that do in fact need to draw their own. Wine to run particular applications has to draw their own decorations or its not going to work under X11 this will be true under Wayland as well.

        The point2 by Arcan developers is kind of on the right track with "If you try to force this on me, I'll implement WM-level cropping and a "hide/show" toggle button to get my SSD back."
        Except this how SSD should be implemented if you want SSD done securely and be able to deal applications that have customised CSD decorations. So this should not be force to this should be how SSD is implemented.

        Please note if a WM doesn't support undecorate flag applications under X11 using the right parts of the X11 protocol can render window by the X11 server without the windows manager knowing about it so CSD again.

        It may seam horrible to make CSD the default but this requires those wanting to SSD to really consider the problem of how todo it properly with all the required functionality. Existing implementations of SSD on Windows X11 and Mac OS are all broken from a security point of view because you cannot tell what is SSD and what is CSD this is very important.

        There is another side to CSD you miss that relates to data secruity. You do want applications at time to be able to resist the kill button on windows boarder. Think about it WM/compositor sees that you have sent kill to application and it decides its waiting long enough and kills it this may be too early. There is more than one right choice how long should you wait for a kill to process. So some applications having SSD for timed kill and CSD for as long as application takes todo the kill could be a great feature.

        I will admit doing SSD in a secure way with proper support for applications that have to be CSD so they will not look absolutely horrible will have extra overhead.

        SSD done for security should have supported cropping always.

        CSD default of Wayland I don't see as wrong. SSD presumed to be there has resulted in Windows Managers not having the functionality to deal with CSD windows in either a secure way or a tidy way.

        Comment


        • #74
          Originally posted by curfew View Post
          Responsibility of drawing (and possibly window management) is separate issue from extended features. There should be no obstacle why there couldn't be a centralized library that every WM used and adhered to. It's simply a design issue that can be solved but so far nobody has cared to try solving.


          That's fake news and only noobs buy it. Apps consist of multiple widgets, not just window decorations. I would much more prefer the decorations to integrate with the rest of the app window. Forced uniform decorations break the look-and-feel on everything else than native-to-DE apps. Gnome decorations look shit on anything else than Gnome / GTK apps. KDE decorations look shit on anything else than KDE / Qt apps.

          This is an issue that cannot be solved simply through theming, especially since the feature gap between GTK and Qt is constantly growing thanks to Qt being perpetually stuck in the '90s. Even KDE folks are working to replace "native" Qt widgets with QML and their own designs.
          That's bullshit.... Consistent look and feel was solved at least 15 years ago. It was Gnome that intentionally broke it.

          Comment


          • #75
            Originally posted by oiaohm View Post

            The reality is a X11 desktop can look the same level of disaster mess of miss matched theming between toolkits. Really look closer. QT based application is on a light theme and GTK is on a dark theme..

            CSD vs SSD really not majority of the problem. In that picture Shiba the person did not open up the different file dialog and other levels of major learning curve miss alignment.

            Theming has been a on going disaster.
            Not in a Plasma X11 session. Theming is a disaster because -GNOME- keeps breaking it.

            Comment


            • #76
              Originally posted by Shiba View Post

              Because not all developers come from the same place. I actually prefer CSD, but I don't have the power to control other people's mind (yet).

              I don't care if it's optional or not, this looks like sh*t and unless you intentionally plan to develop a desktop that looks like sh*t it is a big blocker ↓
              .. what I get. Not sure if SSD vs CSD is the problem

              Comment


              • #77
                Originally posted by duby229 View Post
                Not in a Plasma X11 session. Theming is a disaster because -GNOME- keeps breaking it.
                Can you post a screenshot with some any of the following applications: gimp, musicbrainz, mpv, vlc, and any java app?
                I'm genuinely interested.

                Comment


                • #78
                  Originally posted by Mez' View Post
                  By the way, I was talking about a touchpad 2-finger scroll, not a mouse scroll wheel (I haven't tried). Don't know if it changes anything for you.
                  I would be surprised if I was an isolated case for whom it doesn't work, since it doesn't work only on wayland in 4 case scenarios (computer A + Ubuntu, Computer A + Manjaro, Computer B + Ubuntu, Computer B + Manjaro), unless I have a common denominator that interferes with it.
                  Of course, I could try to switch off extensions to see if there's an impact. But, in the end, it doesn't change much for me. It works with X, not with wayland. Why changing things that work (see list) for things that don't? Why would I want that?
                  No idea, sorry. Multi-touch touchpad and multi-touch touchscreen gestures work flawless with Debian testing (Gnome 3.38 Wayland) on my DELL XPS 13. No configuration required.

                  Comment


                  • #79
                    Originally posted by mppix View Post

                    No idea, sorry. Multi-touch touchpad and multi-touch touchscreen gestures work flawless with Debian testing (Gnome 3.38 Wayland) on my DELL XPS 13. No configuration required.
                    Mine too (on both Xorg and wayland), just that ctrl + 2 finger scroll for zooming in gthumb on wayland is problematic.

                    Comment


                    • #80
                      Originally posted by Mez' View Post
                      Mine too (on both Xorg and wayland), just that ctrl + 2 finger scroll for zooming in gthumb on wayland is problematic.
                      Confirm, happens to me too (but I rarely use gthumb) -> looks like a gthumb bug.

                      Comment

                      Working...
                      X