gala VS AppImageKit

Or with some manual compiling of things: https://github.com/elementary/gala/wiki/Experimenting-with-Wayland

As you can see here, here, here and here some work was done long ago to introduce different tiling options but this feature was never top priority for head dev.

it was broken here https://github.com/elementary/gala/pull/1304/commits. I'm too lazy to revert that code but it's possible to fix the gtk2 dimm bug (which possibly also fixes the rest too)

Report this issue on GitHub, please https://github.com/elementary/gala/issues

[2] https://github.com/elementary/gala/wiki/Experimenting-with-W...

For hiding applications from overview, or showing only windows of the focused app you would need to patch gala, the window manager. It is written mostly in vala, and uses libmutter (the same lib for gnome-shell's window management) underneath. Apparently it has a "plugin" system, but I'm not versed enough that those plugins have to be there at compile time or can be separately compiled. Here's the code: https://github.com/elementary/gala

There’s a link to a wiki on that project board with that info :) https://github.com/elementary/gala/wiki/Experimenting-with-Wayland

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here