Unsure why the blog article itself is in an iframe? https://public.amplenote.com/embed/TnE3JJDDy5QDo5aZAYtqyHz4?hostname=bill.harding.blog https://public.ample

Unsure why the blog article itself is in an iframe? https://public.amplenote.com/embed/TnE3JJDDy5QDo5aZAYtqyHz4?hostname=bill.harding.blog https://public.amplenote.com/embed/TnE3JJDDy5QDo5aZAYtqyHz4?... This plan has also has a huge flaw, that can be shortened to one letter: X. > Add gesture support to the Xorg display server > A "fun" fact: if all of this work was already done today, it would appear on Ubuntu as of next April's release. I'm betting you a drink that next April's release won't have an updated X server package. I haven't been following ubuntu packaging too closely, but last major x.org release was in 2018, and the next one hasn't been discussed: https://en.wikipedia.org/wiki/X.Org_Server#Releases https://en.wikipedia.org/wiki/X.Org_Server#Releases I expect Wayland to be the default on even more systems by then, maybe even KDE could default to it? Though Qt has been weighting them down with the transition, there are less and less rough edges remaining. So, this is probably going the hard way, for little at the end. It sounds like it caters more to the author's system configuration of choice (well, it's their money, though not really). As the author said, Wayland has most of the bits in place, we mostly need to tweak toolkits into supporting this (Qt, SDL, wx, fltk, Gtk?, etc). Starting there would lead early results, and the code path might be reusable is X is worth implementing later. On the other hand, X.org probably nears its final release, so if you want it to be burried with multitouch support, it's probably a good strategy to hurry. Let's see who is left in the X ecosystem: * GNOME: moved on to wayland, mostly, though strangely not with Ubuntu * KDE: moving along, a lot needs to be done in Qt * i3: sway is mostly compatible and quite nice to use (typing this there) * XFCE/LXDE: not sure, I think the projects have merged into LxQt, which has wayland support comming along. XFCE itself meanwhile doesn't have a timeline for wayland, but I think it's on the horizon * Openbox/fluxbox/Windowmaker: you're probably not into wayland. But there's a myriad of Wayland compositors that caters to the same * firefox: starts to work quite nicely, has hw-accelerated video decoding now under wayland. * Inkscape: supports it as of the 1.0 release * Gimp: On the roadmap for 3.0 with the GTK3 port (same situation as Inkscape) Tablet support is here (mostly), network transparency now has an alternative, albeit quite young, with waypipe ("network transparency" has never been a fundamental issue with Wayland, waypipe was bound to happen, I expect a lot more rough edges will disappear once 90% of the users are on Wayland). The missing pieces of the puzzle now are probably xdg-desktop-portal+pipewire support in the web browsers, that I often see people complaining about (and GNOME having their own screenshot interface doesn't help). That is coming. And the last piece, unified color correction with HDR support, I don't know that much about it to comment, but I've at least seen some work on HDR support for sway.