Hmm, okay. Perhaps I lack some fundamental understanding here. If so I apologize for the noise.

Going back to the original Wayland protocol merge itself, we see it's pretty toolkit-agnostic at this point:

Qt client support: https://codereview.qt-project.org/c/qt/qtwayland/+/321246
KDE server framework: https://invent.kde.org/plasma/kwayland-server/-/merge_requests/130
KWin's implementation: https://invent.kde.org/plasma/kwin/-/merge_requests/434
Mutter: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1845
GTK: http://gitlab.gnome.org/GNOME/gtk/commits/wip/carlosg/xdg-activation-3-24
wlroots: swaywm/wlroots#2718

And currently has been, or is being requested to be, implemented by apps across these various frameworks Electron recently was a biggee for many folks, similar to this year's Chromium support.

As for chromium, FF, Libreoffice apps, I think you're correct but referring to their rendering engines, whereas they all use GTK to present their windows/decorations and widgets?

Firefox has been GTK3 for 7 years now.

Libreoffice (GTK3):
Version: 24.2.6.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 24; OS: Linux 6.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 24.2.6-4 Calc: threaded

Off-topic here... but I'm sure you can find relatable... they all have their respective user's clamoring for a GTK4 port haha!

Both LibreOffice and Chromium have experiment support for GTK4:
https://wiki.documentfoundation.org/Development/GTK4
https://chromium-review.googlesource.com/c/chromium/src/+/1187197

Firefox not so much:
https://bugzilla.mozilla.org/show_bug.cgi?id=1701123

Anyhow, I'll investigate further my assertion that some change needs to be made to the Geany client to support the activation mechanism. Thanks for taking time with meaningful responses here.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.