Integration of XScreensaver with Wayland
Hi, I am a developer working on a project with XScreensaver and I would really like to find a way to implement XScreensaver with Wayland enabled. By default, I have to disable Wayland in order to run XScreensaver. I maintain the NetWare SMP based screensaver collection on Linux. See below for my current XScreensaver and linux projects: https://github.com/jeffmerkey/netware-xscreensaver https://github.com/jeffmerkey/xscreensaver-6.08-netwaresmp https://github.com/jeffmerkey/netware-screensaver-linux I am willing to develop support for Wayland into my XScreensaver code base for my customers and users of my software and work with Jamie to get it into XScreensaver. I have reviewed Wayland and it has some distinct advantages over X and I can see why folks would want to switch to it. Its architecture provides better security and hardware performance than X, and appears well designed. At present the obstacles to using Wayland with XScreensaver involve support for screen locking and detecting application activity under the Wayland model. There are several approaches that I can take with this including monitoring io events from /proc. What suggestions can you folks provide about what would be the best approach to using Wayland with XScreensaver. Right now, it has to be disabled in order for XScreensaver to work properly.The basic requirement is detecting application events, keyboard, and mouse and also being able to lock the screen. Jeff
[ANNOUNCE] wayland-protocols 1.34
wayland-protocols 1.34 is now available. This release comes with three new staging protocols: * xdg-toplevel-drag This protocol enhances regular drag and drop by allowing attaching a toplevel window to a drag. This can be used to implement e.g. detachable toolbars and browser tab drag behavior that can be seen in other platforms. * xdg-dialog This protocol allows setting dialog specific hints on a toplevel, more specifically marking them as modal. * linux-drm-syncobj This protocol will allow explicit synchronization of buffers using DRM synchronization objects. While being a protocol that is unlikely to be widely used directly by applications and toolkits themselves, it is an important building block for improving Vulkan and OpenGL drivers. Other than this, the tablet and foreign toplevel list protocols also received clarifications and fixes. Enjoy! Carlos Garnacho (1): staging/dialog: Add "dialog" protocol David Redondo (1): Add xdg-toplevel-drag protocol Jonas Ådahl (1): build: Bump version to 1.34 Poly (1): Fix typo in ext-foreign-toplevel-list-v1 Simon Ser (3): tablet-v2: clarify that name/id events are optional linux-drm-syncobj-v1: new protocol linux-explicit-synchronization-v1: add linux-drm-syncobj note git tag: 1.34 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/1.34/downloads/wayland-protocols-1.34.tar.xz SHA256: c59b27cacd85f60baf4ee5f80df5c0d15760ead6a2432b00ab7e2e0574dcafeb wayland-protocols-1.34.tar.xz SHA512: d180eaaf87281dc7adade19070ee8308a5cb3dc2f60cff077960436ad647d3d207eb63fa0b079b7b315109654ad6e6b5e2588bfe859900e67edf8c67b1c3ad20 wayland-protocols-1.34.tar.xz PGP: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/1.34/downloads/wayland-protocols-1.34.tar.xz.sig signature.asc Description: PGP signature
