5 ms·

Khronkite is another "honorable mention" for KWin tiling and I prefer it over the one mentioned in TFA: https://github.com/esjeon/krohnkite https://github.com/e

by rrix2 5y ago

Khronkite is another "honorable mention" for KWin tiling and I prefer it over the one mentioned in TFA: https://github.com/esjeon/krohnkite https://github.com/esjeon/krohnkite With KDE+X11 it's trivially easy to change the window manager away from KWin and still get the benefits of suspend/resume, multi-monitor auto-configuration, wifi, system tray, etc, by just setting the KDEWM environment variable in your profile. https://userbase.kde.org/Tutorials/Using_Other_Window_Managers_with_Plasma https://userbase.kde.org/Tutorials/Using_Other_Window_Manage... But with things moving to Wayland, etc, this simple swap out method isn't possible right now, so I've been keeping tabs and playing with Khronkite and KWin-tiling every so often for when I inevitably swap over to Wayland. It's basically a perfectly serviceable tiling WM OS without having to deal with any of the screen locker, systray, R&R, that Sway et al force you to contend with yourself. Most of the setup is in unbinding system defaults + rebinding window management shortcuts in to better "places". I still use KDEWM=/usr/bin/i3 equivalent for now.

indymike 5y ago
I can second the Khronkite suggestion. It's extremely flexible.
kbknapp 5y ago
Setting KDEWM to something other than KWin no longer works in Fedora as of 35 (and other "leading edge" Plasma distros like OpenSUSE are quickly approaching this turning point as well). There are several spots in the Plasma code base that KWin is hard coded. Those distros that still allow functional KDEWM only do so because their version of Plasma is either not yet new enough to be affected, or they have deliberately held back parts of Plasma (which means at some point they'll have it give in as well).
- RMPR 5y ago
  Using Fedora 35 here, still using i3. The trick is to modify /usr/lib/systemd/user/plasma-kwin_x11.service, here's mine. [Unit] Description=KDE Window Manager #Wants=plasma-kcminit.service PartOf=graphical-session.target [Service] ExecStart=/usr/bin/i3 BusName=org.kde.KWin Slice=app.slice Restart=on-failure The only downside is that you will need to wait a bit more for it to start.
MayeulC 5y ago
Hmm, with layer-shell, you can run some parts from other DEs under a given wayland compositor. I'm not sure what parts support the protocol, but I'm fairly sure you can run krunner, and probably the KDE status bar under sway. I think you can also run xfce's equivalents. I don't see why all of that couldn't be integrated in nice, modular packages and sets of configuration. Some say that wayland made everything more monolithic. If anything, I think it helped make everything more modular by forcing to specify the interfaces into wayland protocols. Now, of course some DE prefer using private interfaces instead of proper protocols...
onnyyonn 5y ago
You may want to have a look at Bismuth https://github.com/Bismuth-Forge/bismuth https://github.com/Bismuth-Forge/bismuth . It's the successor to Khronkite.
- justemre 5y ago
  I didn't used any of them before, is this any better than Kröhnkite?
- rrix2 5y ago
  thanks; i spent some time yesterday trying to build this from source in NixOS but didnt get it enabled. i'll keep it on my shortlist and keep working on packaging it when i have spare cycles. it looks like a nice shine-up of khronkite

by rrix2 5y ago

indymike 5y ago

I can second the Khronkite suggestion. It's extremely flexible.

kbknapp 5y ago

Setting KDEWM to something other than KWin no longer works in Fedora as of 35 (and other "leading edge" Plasma distros like OpenSUSE are quickly approaching this turning point as well). There are several spots in the Plasma code base that KWin is hard coded. Those distros that still allow functional KDEWM only do so because their version of Plasma is either not yet new enough to be affected, or they have deliberately held back parts of Plasma (which means at some point they'll have it give in as well).

RMPR 5y ago
Using Fedora 35 here, still using i3. The trick is to modify /usr/lib/systemd/user/plasma-kwin_x11.service, here's mine. [Unit] Description=KDE Window Manager #Wants=plasma-kcminit.service PartOf=graphical-session.target [Service] ExecStart=/usr/bin/i3 BusName=org.kde.KWin Slice=app.slice Restart=on-failure The only downside is that you will need to wait a bit more for it to start.

MayeulC 5y ago

Hmm, with layer-shell, you can run some parts from other DEs under a given wayland compositor. I'm not sure what parts support the protocol, but I'm fairly sure you can run krunner, and probably the KDE status bar under sway. I think you can also run xfce's equivalents. I don't see why all of that couldn't be integrated in nice, modular packages and sets of configuration. Some say that wayland made everything more monolithic. If anything, I think it helped make everything more modular by forcing to specify the interfaces into wayland protocols. Now, of course some DE prefer using private interfaces instead of proper protocols...

onnyyonn 5y ago

You may want to have a look at Bismuth https://github.com/Bismuth-Forge/bismuth https://github.com/Bismuth-Forge/bismuth . It's the successor to Khronkite.

justemre 5y ago
I didn't used any of them before, is this any better than Kröhnkite?
rrix2 5y ago
thanks; i spent some time yesterday trying to build this from source in NixOS but didnt get it enabled. i'll keep it on my shortlist and keep working on packaging it when i have spare cycles. it looks like a nice shine-up of khronkite