Show more

@tanfonto @LukaszHorodecki @noodlejetski Apple kaลผe sobie pล‚aciฤ‡ za wrzucanie i utrzymywanie aplikacji w App Store.

@pup It's now published in the KDE Store and can be installed with "Get New Plugins" button in Plasma. It's also in AUR as "plasma6-wallpapers-application"

store.kde.org/p/2318884

And here it is! Welcome back as my screensaver, Asciiquarium ๐Ÿ˜Š

I could have reimplemented it in Qt, as it was done back in the KDE 3/4 days... or I could just run the original thing in a Konsole window and call it a day ๐Ÿ˜

Show thread

@jwz This one is a simple nested compositor indeed, as that's what was easy to do with the available ready-made building blocks :) But technically it doesn't even have to be a "compositor" at all to do this. Wayland itself is a buffer-passing protocol with some optional extras on top after all, so it could pass the client's wl_buffer straight to the server.

@pup Sure, as soon as I tame the build system and move what's hardcoded to config options.

@jwz This is Plasma specific - it's effectively making kscreenlocker outsource its background rendering to another process, which doesn't even have to be aware that it's being used as a screensaver (or a wallpaper, it's the same there). That said, there's no reason other DEs couldn't handle it the same way. A ext-session-lock-v1 locker could also become a simple compositor like this and just pass the buffer forward.

How it works? It's a Plasma wallpaper plugin which is an extremely simple QtWayland compositor that only handles a single fullscreen window and draws it - so any Wayland window can be drawn as a background. This window can of course also belong to Xwayland ๐Ÿ˜„

This means we can go beyond xscreensaver. How about... Wine? ๐Ÿ˜

Show thread

I had a random thought - "what would it take to support arbitrary old screensavers in Plasma 6 again?" ๐Ÿค” So here's xscreensaver safely rendered as a background for Plasma screen locker, working on both Wayland and X11 sessions. Turned out so much simpler than I expected ๐Ÿ˜ Just some 70 lines of pure QML and a tiny glue to launch the process.

I would say I'm a Wayland developer. I've had some hand in libwayland and the foundational protocols in the past years, and I still have a hand in some protocols today.

That is why, when someone publicly vents that Wayland makes the touchpad feel wrong, or Wayland breaks the picture on the TV, or Wayland uses wrong fonts, it feels like they are blaming me personally.

I understand how it is easy to come to the conclusion that Wayland is to blame. Despite reasoning otherwise, it still hurts.

Last weekend, we reached another milestone in our efforts to have all Debian packages versioned in Salsa (Debian's GitLab instance). Out of around 39000 packages, less than 2000 are not in Salsa! Check trends.debian.net/#vcs-hosting for some cool graphs #debian #salsa #09

@debacle @opensourceopenmind @jonah It's the PinePhone Pro that's discontinued, not the regular PinePhone, isn't it?

@pocketvj @opensourceopenmind @enriquericos OLS doesn't make GPS fixes faster, it just provides alternative methods to estimate location (just like Geoclue does with BeaconDB as well).

@agx @ev Yeah, that's the one thing I miss in git gui. I find what's there to be enough most of the time, but sometimes it just stubbornly doesn't want to put the line where it belongs when splitting a bigger change into smaller commits ๐Ÿ˜„ But it's still valuable to me to be able to quickly browse both staged and unstaged changes and to non-destructively switch between authoring a new commit and amending the previous one with a single checkbox click.

@opensourceopenmind @enriquericos It's not integrated in the OS, but you can get fast fixes by uploading fresh AGNSS data to the module manually: source.puri.sm/-/snippets/1207

@agx @ev That's what I typically use for interactive staging (right-clicking on diffs) - I think it's the only git operation that's usually more comfortable to do from a GUI for me

Show more
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml