3 ms·

> which means for you are no longer say supporting Windows, Mac and Linux; but Windows, Mac, X11, Gnome, KDE, Mate, Cina... At a toolkit level, you don't reall

> which means for you are no longer say supporting Windows, Mac and Linux; but Windows, Mac, X11, Gnome, KDE, Mate, Cina... At a toolkit level, you don't really have to worry about that. When developing GTK or Qt apps, most of the DE integration and Wayland/x11-specific features are handled for you automatically. Basic trackpad gestures, copy/paste and windowing heuristics are handled by the toolkit, and so is accessibility software if your toolkit supports it. If an app doesn't work well on a desktop's Wayland implimentation, it is less often a Wayland problem and more a desktop/toolkit problem. We had the same issue with non-conformist x11 software, unfortunately.

superkuh 3y ago
>most of the DE integration and Wayland/x11-specific features are handled for you automatically... Just no ability to launch windows at absolute positions or do non-standard input stuff (like special mice, keyboards, or keyboard/mouse sharing) unless your particular wayland flavor has libei. And some waylands like sway are actively hostile to libei. Which is kind of microcosm of the waylands as whole.
- smoldesu 3y ago
  It's a microcosm of Linux. x11 had wildly non-conformant desktops since forever, having a larger spec doesn't inherently fix things or force desktops to abide by the rules. Projects like GNOME would have dropped AppIndicator and server-side decorations whether it was included in Wayland or not. Drilling-down on a minimal set of secure features was the only path forward if Wayland wanted developers to take the protocol seriously.