aw-watcher-window VS cage

The conflict probably stems from the Asahi leader having caught a bad case of Wayland Derangement Syndrome[0]. This case is particularly bad because his distro aims to give Apple hardware users FREEDOM to use an open source distro. Yet he has nothing but contempt and anger for anyone that wants freedom to use Linux the way they want, they way it was intented. E.g. allowing software to control other software, rather than being sandboxed into discreet, tightly controlled "apps". God forbid, anyone should need cross-application monitoring or time-tracking.

[0] https://social.treehouse.systems/@marcan/110354541574112092

https://help.rescuetime.com/article/117-common-linux-issues

https://github.com/ActivityWatch/aw-watcher-window/issues/18

We have the same issue for ActivityWatch, see: https://github.com/ActivityWatch/aw-watcher-window/issues/18

Btw I just found this thread, which mentions the wlr-foreign-toplevel-management protocol I meant in my previous comment and also that they found some Gnome-specific solution. I could imagine they’d just write a Gnome extensions which provides all the data they want.

You... might be able to, kind of, depending on your goal... So the thing is, if all you need is a single screen (or at least, I've not run this multi-monitor) and you're just working around drivers that don't support Xorg, you can just run cage ( https://github.com/cage-kiosk/cage ), run xwayland on that, and run your real GUI on that. Of course, then you're skipping all the advantages of wayland except hardware/driver compatibility.

For "real" wayland, sibling comments are correct that you'd need a wayland compositor that reimplemented awesome.

> As a developer, I needed to port a custom Linux system to hardware that only has Wayland drivers and it was a giant pain. Wayland offers no advantage at all for that system but it broke a lot of functionality that relied on X in terms of window placement, etc.

FWIW, I've had decent luck running cage ( https://www.hjdskes.nl/projects/cage/ ), then on that xwayland, and then just ignoring wayland and running X clients. The result does still have some slight quirks, but it mostly works fine.

That did help me find https://github.com/cage-kiosk/cage/wiki initially I'm here there's other going down that path. Thanks

I thought this was going to be some development news with Wayland compositing going further: https://emacsconf.org/2022/talks/wayland/. Maybe it's because 29.1 was on my mind with the full Wayland client support being released.

If you want to just run one application in a modern way (yes, I'm assuming you agree that Wayland is desirable), then check out https://www.hjdskes.nl/projects/cage/.

You can run Wayland inside Xorg via cage[1] so you don't need to use a Wayland compositor.

[1]: https://github.com/cage-kiosk/cage

Just ran into cage, seems useful.

It's kiosk mode. Sometimes related to POS. You can use https://github.com/cage-kiosk/cage (Wayland) for example.

Maybe starting with reimplementing something like this: https://github.com/cage-kiosk/cage would be the easiest?