• 2 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle




  • Oh, you was talking about resizing. I see. Yes, Btree does not allow resizing. Trying so will snap window back to position, just as you were saying. When I read “drag”, I thought you meant placing the window. The default “Tile” or “Quarter” could be used instead if window resizing is a requirement. But off course they do not function exactly like Btree.


  • Krohnkite

    In krohnkite I can’t use btree while also keeping the tiling part. If I drag a tile while in btree in krohnkite they just snap back to their previous position.

    I use a 3 different layouts, one of them Btree. And drag and drop one window over the other will swap position of both windows. So functionally, it is working (for me) and maybe another plugin or configuration in Plasma is in the way?

    Polonium

    Closing all windows and relaunching them is from users perspective actually not too different from logging out and in again, at least from my view. From time to time I’m looking at the source in Github to see what the recent advancements are. But it seems development is on halt at the moment, with only minor changes over longer period of time.

    On KDEs side I saw some update notes specifically mentioning fixes for Polonium, which is a good sign. My hope is that development of Polonium will take off soon.


  • Krohnkite

    https://github.com/anametologin/krohnkite

    https://store.kde.org/p/2144146/

    I would try a few Plasma based tiling scripts before switching to anything like Sway or i3.

    Agreed. I used tiling window managers for years before coming back to Plasma. Right now on Wayland I highly recommend giving Krohnkite a shot, its stable without any problems and has even multiple layouts to choose (and switch) from. I used Polonum before, but that one is not stable and was problematic. Krohnkite plugin (can be found in KWin Scripts > Get New… > then search for “krohnkite”, by anametologin) is pretty good in my opinion.

    The only problem with these plugins is, that they are not well documented as a standalone tiling window manager and cannot be configured as deeply. And they might interfere with other plugins or shortcut setups and so on. I knew what I wanted and I knew how to configure stuff, that’s why its easy for me. At least it can be easily disabled without replacing entire desktop environment.

    Little tip: One thing to mention, unlike Polonium, with Krohnkite one does not need to logout and login from current user session whenever settings are changed. It’s enough to disable Krohnkite in KWin Scripts, Apply, then enable and Apply again. This is basically a reload of the plugin to take any changed settings in effect.


  • You can easily install and configure a tiling window manager on any distro, so you should not switch an entire distribution and your base because of that. Unless off course you want to, but its not difficult. If you install a tiling window manager from your repository, then read the documentation how to set it up correctly and log out your current user session. Then in the login screen, you should be able to select what window manager or desktop environment you want to use.

    But be careful, lot of window managers are still not supported in Wayland and the other way, some of the new window managers are Wayland only. The usual suspects would be probably Sway or Hyprland on Wayland? There is also Qtile, but that is for people who want to configure and write Python source code, as the configuration is in Python language (BTW my favorite tiling window manager, but not for everyone). EndeavourOS used to have a Qtile spin, but they stopped that not long ago.

    But if you really must switch the distribution, then there might be a few preconfigured tiling window manager distributions:



  • No, I did not. After my post I got an mlt update too, which didn’t help with Kdenlive, but Inkscape stopped working… Right after that Inkscape got an update and now it works again. It all looks like an known issue they are aware off? Couldn’t find anything related in KDE and Archlinux forums a few hours back.

    Last time Kdenlive broke, I used Flatpak until that was resolved. Maybe I’ll wait a bit again. But will have in mind to downgrade mlt, but I’m hesitant to downgrade libraries other tools may depend on.



  • Presumably its only opt-in to the application you want to use it with. If this new system was applied to all applications by default, yeah it could become a problem. The reason why the permission control in Android and Flatpak works is, because those applications and packages are designed and built with these limitations by default and the user should not need to modify the permissions. There are a few cases (in Flatpak) where you need to change the permission, which is annoying, especially if you don’t know. How worse will it be with applications that are not designed with these limitations in mind and force them with permissions taken away with this new tool?

    Overall I don’t think it’s such a bad idea to have a technology on your hand to limit permissions and access, but it needs to be opt-in. In example this could be useful for AppImages, that are downloaded from the web and not managed by your operating system or a community like Flathub.