i3
krohnkite
Our great sponsors
i3 | krohnkite | |
---|---|---|
200 | 89 | |
9,053 | 1,584 | |
1.7% | - | |
7.6 | 0.0 | |
1 day ago | 9 months ago | |
C | TypeScript | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
https://github.com/i3/i3/issues/4353
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
krohnkite
-
kde tilling features needs some attention
That's exactly what happens. Bismuth was a fork of Krohnkite. If someone needs Bismuth enough, they will pick it up, fork it or whatever.
- Why KDE Plasma was chosen as the default desktop environment for Asahi Linux
-
Manjaro / KDE ā hard to dislike
I wonder if this PR would help you.
-
KDE VS GNOME
No idea what exactly that shell does but in KDE krohnkite https://github.com/esjeon/krohnkite was pretty popular until it was somehow superseeded by bismuth https://github.com/Bismuth-Forge/bismuth (which forked krohnkite or was inspired by or whatever) and now with Plasma 5.27 there's initial work on a native tiling window manager including a whole new API for people to build upon, and which can be accessed with Meta+T.
-
Is there a way to install Kwin - Bismuth on my steam deck in a way that doesn't make my head hurt?
You can use Kronkite just fine. Bismuth is a fork of it, and their feature-sets are practically the same.
- I made outlines for KDE Breeze window decoration
- Iām done with pop
-
KDE/Plasma Nordish
Kwin tiling script - Krohnkite
-
Are there options for dynamic window tiling in a traditional desktop environment?
Do you know how that differs from https://github.com/esjeon/krohnkite it seems like that is another tiling extension.
-
What does your workflow look like on Linux?
I love virtual desktops and Krohnkite; it works infinitely better than windows.
What are some alternatives?
sway - i3-compatible Wayland compositor
bismuth - KDE Plasma add-on, that tiles your windows automatically and lets you manage them via keyboard, similarly to i3, Sway or dwm.
awesome - awesome window manager
kwin-tiling - Tiling script for kwin
bspwm - A tiling window manager based on binary space partitioning
bismuth - KWin tiling extension, that gets you down to bismuth. Wayland Support included! š [Moved to: https://github.com/Bismuth-Forge/bismuth]
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
Grid-Tiling-Kwin - A kwin script that automatically tiles windows
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
Lightly - A modern style for qt applications.
tmux - tmux source code
i3-gaps - i3-gaps ā i3 with more features (forked from https://github.com/i3/i3)