Announcement

Collapse
No announcement yet.

KDE's KWin Just Became A Proper Wayland Compositor

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

  • #11
    Originally posted by edmon View Post
    And then why this suspend didn't happen for me and i've see bad performance with desktop effect enabled?
    Because :
    - Some games don't launch as fullscreen but as borderless windowed mode, thus the window manager won't automatically disable compositing for them.
    - Your window manager isn't configured to automatically suspend effects for fullscreen applications.

    In any case you can suspend desktop effects manually (KWin hotkey is alt-shift-F12) or search in your game options to enable proper Fullscreen.

    Comment


    • #12
      Originally posted by Scias View Post
      - Some games don't launch as fullscreen but as borderless windowed mode, thus the window manager won't automatically disable compositing for them.

      In any case you can suspend desktop effects manually (KWin hotkey is alt-shift-F12) or search in your game options to enable proper Fullscreen.
      fullscreen in X is literally a screen sized window at 0:0 coordinates
      borderless should work fine, if not then its a bug

      in EGL it shouldn't matter, but still fullscreen might be better

      Comment


      • #13
        No no no folks, we're still 2+ years from having good, stable and Wayland-optimized experience. Heck, not even a beta driver supporting Wayland from Nvidia yet, and since Vulkan is the new big thing their resources just got diluted.
        The desktop Working on Wayland, working well on Wayland, and all your main media apps working well on Wayland are 3 different things.
        Last edited by mark45; 08 May 2015, 04:40 PM.

        Comment


        • #14
          Originally posted by Jristz
          Next step Xfwm and MARCO and... whatever LXQT default now.
          KWin. So you got that covered

          But yes, this is just initial work, obviously. Wayland by default will take a while...

          Comment


          • #15
            Originally posted by gens View Post
            fullscreen in X is literally a screen sized window at 0:0 coordinates
            borderless should work fine, if not then its a bug
            Both right and wrong...
            True, in X a fullscreen window is a screen sized window at 0:0. However, It is still managed by the window manager, which is where EWMH[1] comes into play.
            Should a window want to be fullscreen, it should also set the _NET_WM_STATE_FULLSCREEN flag. That's the theory AFAIK...


            [1]http://standards.freedesktop.org/wm-...ec-latest.html

            Comment


            • #16
              Originally posted by phoronix View Post
              Phoronix: KDE's KWin Just Became A Proper Wayland Compositor

              Martin Gr??lin just shared that with the forthcoming KDE Plasma 5.4 update, KWin will serve as a proper Wayland compositor!..

              http://www.phoronix.com/scan.php?pag...Compositor-5.4
              Kudos to the most well written C++ framework out there!

              Comment


              • #17
                Originally posted by Serafean View Post
                Both right and wrong...
                True, in X a fullscreen window is a screen sized window at 0:0. However, It is still managed by the window manager, which is where EWMH[1] comes into play.
                Should a window want to be fullscreen, it should also set the _NET_WM_STATE_FULLSCREEN flag. That's the theory AFAIK...


                [1]http://standards.freedesktop.org/wm-...ec-latest.html
                yes ExtendedWMHints
                it's just to tell the WM to fsck off
                the actual redirecting is done by X and the driver
                except in compositing managers that have to either take the flag as a hint or, better, just take the window position and size as a hint (hint to stop redirecting, that is)
                KWin does bout, afaik, as does the XFCE one and probably all others

                you can test it by getting a game to borderless fullscreen, then moving it
                there should be a twitch
                Last edited by gens; 08 May 2015, 05:55 PM.

                Comment


                • #18
                  This is great news for LXQT as well.

                  Comment


                  • #19
                    The new graphical environment of the phoronix blog is AMAZING . My compliment.

                    Comment


                    • #20
                      Originally posted by mark45 View Post
                      No no no folks, we're still 2+ years from having good, stable and Wayland-optimized experience. Heck, not even a beta driver supporting Wayland from Nvidia yet, and since Vulkan is the new big thing their resources just got diluted.
                      The desktop Working on Wayland, working well on Wayland, and all your main media apps working well on Wayland are 3 different things.
                      Not quite, we're less than a year away in my estimation. GNOME Shell and Plasma should be working well on Wayland by the end of the year. The important gnome apps have been written to GTK3 by this point, and the remaining important KDE apps should have been ported to KF5 by the end of the year, which means that the important desktop application will run on wayland. SDL already supports wayland, so the games that use it should. Chromium already supports wayland and the other stragglers should fall in line soon enough. That said XWayland should provide an adequate experience as they transition.

                      As far as Nvidia goes, they're only going to hold it back for Nvidia users, and more than likely they'll put in support when Fedora moves to Wayland wholesale.

                      Comment

                      Working...
                      X