4 ms·

Depends on the framework you used. If you used gtk or qt, it is enough for them to support wayland. If you have something homemade, or you talk directly to x11

Depends on the framework you used. If you used gtk or qt, it is enough for them to support wayland. If you have something homemade, or you talk directly to x11 server; well now you have to talk directly to wayland server, using a different protocol. There are also some changes in semantic, most visible & commented in the screen sharing scenario: with x11, you could just silently grab the desktop framebuffer and run to the bank. That's a no-no with wayland, you must ask a privileged process to mediate the access (and that process will ask the user which display or window to share, if any). Some apps are taking their sweet time to switch to this concept.

bravetraveler 3y ago
Speaking of frameworks... it absolutely grinds my gears how many projects are still using such an old version of Electron. Wayland support has been upstream for quite a while, yet most of them I use are relegated to XWayland. Didn't they basically get it from Chromium?
- vetinari 3y ago
  Speaking of Electron... vscode even intentionally ignores .config/electron-flags.conf (or it's own -flags.conf), so you must pass the ozone flags on the command line (i.e. edit the launcher, which will be replaced on next update). There were many issues filled on vscode wrt. wayland support, hidpi, fractional scaling... and they all were closed with half-baked solution that are not really solution. It's tragic, how a project like vscode can ignore wayland and it's features for such a long time.
  - bravetraveler 3y ago
    Argh, that's frustrating. That's been my default (uninformed) state -- those flags files never seem to work for me. I override launchers all the time. I've found some comfort by placing my edited copies in ~/.local/share/applications and informing 'fuzzel' (my launcher) of it by ensuring the parent directory is in $XDG_DATA_DIRS As long as the file names match those in the 'system' directories, these will win.

bravetraveler 3y ago

Speaking of frameworks... it absolutely grinds my gears how many projects are still using such an old version of Electron. Wayland support has been upstream for quite a while, yet most of them I use are relegated to XWayland. Didn't they basically get it from Chromium?

vetinari 3y ago
Speaking of Electron... vscode even intentionally ignores .config/electron-flags.conf (or it's own -flags.conf), so you must pass the ozone flags on the command line (i.e. edit the launcher, which will be replaced on next update). There were many issues filled on vscode wrt. wayland support, hidpi, fractional scaling... and they all were closed with half-baked solution that are not really solution. It's tragic, how a project like vscode can ignore wayland and it's features for such a long time.
- bravetraveler 3y ago
  Argh, that's frustrating. That's been my default (uninformed) state -- those flags files never seem to work for me. I override launchers all the time. I've found some comfort by placing my edited copies in ~/.local/share/applications and informing 'fuzzel' (my launcher) of it by ensuring the parent directory is in $XDG_DATA_DIRS As long as the file names match those in the 'system' directories, these will win.