Announcement

Collapse
No announcement yet.

KWin On Wayland Making Progress, Now Has A Virtual Backend

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

  • KWin On Wayland Making Progress, Now Has A Virtual Backend

    Phoronix: KWin On Wayland Making Progress, Now Has A Virtual Backend

    Martin Gr??lin has shared a monthly status update about the work accomplished in recent weeks for running KDE/KWin atop a native Wayland environment without depending upon any X11 code-paths...

    http://www.phoronix.com/scan.php?pag...tember-Wayland

  • #2
    It's not that it allows KWin to be run without hardware restrictions, it's that it allows KWin to be run while discarding each frame instead of pushing it to a monitor, allowing it to be used in a headless environment (e.g. CI tests). There is, however, an option to save each frame as an image in a directory.

    Comment


    • #3
      Originally posted by Daktyl198 View Post
      ...There is, however, an option to save each frame as an image in a directory.
      As in, if it is running at 60Hz, it's saving 60 image files per second?

      Comment


      • #4
        Originally posted by kaprikawn View Post
        As in, if it is running at 60Hz, it's saving 60 image files per second?
        no. The frames rendered are saved. KWin hardly ever renders at a constant 60 fps. It renders when something changes on screen. So if you run e.g. a video, then it could happen, but that's certainly not what one wants. During my tests for that feature (starting with a konsole or kwrite) it saved about 10 to 20 frames before I killed it again.

        Comment


        • #5
          mgraesslin

          Hi Martin

          Kind of cool to see you posting here.
          Thanks for your great work on KDE / KWin.

          Looking forward to the openSUSE release, properly supporting Wayland KDE. (For a production computer.)

          Greetings from Switzerland,
          Rolf

          Comment


          • #6
            Would this mean that, if VNC server functionality were somehow integrated into this, one could start an arbitrary number of KWin instances (all with VNC, listening on different network ports) on a system with no graphics hardware at all (say, a headless server), to allow many clients to connect via VNC to independent, simultaneous KWin sessions?

            Comment

            Working...
            X