Interactive window moving, laptop lid and tablet mode switch binds, mouse and touchpad scroll speed setting in today's niri v0.1.10 release!
https://github.com/YaLTeR/niri/releases/tag/v0.1.10
Also, niri-ipc is now on crates.io, but keep in mind that it will not be Rust-semver-stable: https://crates.io/crates/niri-ipc
Added scaffolding for layer rules, along with a block-out-from rule. Now you can finally block notifications from screencasts!
Though, layer-shell surfaces don't have a "geometry" so if they have shadows or transparent padding, all of that becomes solid black, since niri has no way to know where the "actual content" of the layer surface is (that's what geometry is for windows).
Thanks to Christian Meissl's fix in Smithay, the git version of niri correctly shows nested pop-up menus in lxqt-panel. They also submitted a fix for invalid pop-up spawning to ironbar, which makes it work on Smithay compositors.
Today I merged a PR by FluxTape which adds "always empty workspace before first" to niri. At the surface this is just a simple config flag with obvious behavior, but it's actually full of edge cases! Things like which workspace to focus at startup. The code refers to workspaces by index in many places, and those all shift when you suddenly insert an empty workspace at index 0.
Took several days to catch them all even with our randomized tests, but I think it should be good now.
This morning was my niri (-adjacent) talk! 
Went really well, got many interesting questions!
They promised us video recordings in a few days, so I'll post a link when I get it. Though of course the talk is in Russian.
unusual sights
Turns out, there's a lot of details to get right when implementing a floating window space. For example, dialog windows should always show above their parent window. Otherwise, it's easy to lose them under the (usually much bigger) parent.
The WIP floating branch in niri now handles this properly, even for xdg-desktop-portal dialogs (like file chooser) as long as the app correctly parents them via xdg-foreign.
Another piece of the floating puzzle: keeping windows on screen. When you change your monitor scale or resolution, you don't want your floating windows to suddenly go unreachable behind the monitor's new borders.
Here I'm resizing a nested niri with three windows, simulating resolution changes. No matter what I do, they always remain partially visible and reachable. Even for more unusual cases like trying to resize a window into out of bounds.
In the tiling layout, niri is constantly asking windows to assume their expected size. In contrast, floating windows should be able to freely change size as they see fit.
The logic turns out to be quite tricky. On the one hand we want a window to keep its latest size, but on the other we still want to be able to resize the window, which means asking it for a different size. The window can take a second to respond, or respond with a yet another size, and nothing must break.
While trying to make this work, I realized that this is the time when I *really really* want to be able to test this stuff. So I got on a sidetrack adventure to write testing infra for running real Wayland clients inside unit tests.
I've got it working! In these tests, I'm creating a new niri instance along with test clients, all on the same test-local event loop. No global state, no threads needed.
What's really cool is that this lets me test the weirdest client-server event timings.
This morning I worked on remembering the size for floating windows when they go to the tiling layout and back.
The whole sizing code must be at the top by logic complexity in niri. I have to juggle, all at once:
- new size I haven't sent to the window yet,
- size changes I sent, but window hasn't acked yet (0, 1, or more in-flight),
- size change window acked but hasn't committed for yet,
- size change window acked and responded to with a commit (maybe with a different size entirely).
The diff is 85 lines of change and 243 lines of new tests, and I already found a few weirder edge cases that I've missed. No way I could do this well without that client-server testing setup that I posted about yesterday.
Btw I pushed the testing setup if you're curious, along with the entirety of 1215 snapshot files for a powerset of new window workspace/output target settings: https://github.com/YaLTeR/niri/commit/771ea1e81557ffe7af9cbdbec161601575b64d81
The WIP floating branch caused them to update in several commits already.
The big 1215 snapshot test powerset (actually it already grew to 1695) continues to prove its worth. Just finished a big +495 -508 cleanup of the window opening code, and verified that not a single of those 1215 window opening configurations changed its outcome. I will be sleeping well tonight
After three weeks of hard work, I am undrafting the floating window PR in niri. Please give it thorough testing and report any bugs or issues!
I spent today figuring out the remaining layer-shell keyboard focus problems, and I've got it all working! Pop-ups now render above windows, and bottom/background layers can receive on-demand focus.
Effectively, this makes the desktop icons components from @LXQt or @xfce just work on niri!
Alright, I think I got all of the important things in for the next niri release. Today I updated Smithay for the DRM compositor changes, and added a workaround for a panic when you have two monitors with exactly matching make/model/serial.
I'll give it a week of testing (if you run niri-git, please report any problems) and if all goes well, tag next Saturday.
There are a few PRs I'll try to review in time, but they're fairly self contained.
After a full day of writing release notes (god how'd it take so long 😫), niri v25.01 is out with Floating Windows and Working Layer-Shell Desktop Icons and Layer-Shell Screencast Blocking Out and so many more improvements! Yes, you read that right, we finally escaped zerover! I feel that niri is now ready to graduate from v0.1
Read here and download when your distribution package updates: https://github.com/YaLTeR/niri/releases/tag/v25.01
something odd about these windows
Looking for testing and feedback for server-side shadows: https://github.com/YaLTeR/niri/pull/990
ppl from our niri matrix playing around with the new compositor-side shadows! These screenshots are from @r4hulrosh4n and calops (no fedi)
Added shadow support for layer-shell surfaces!
Though unfortunately layer-shell has no way to signal the visual geometry, so this only looks right if the layer surface doesn't have its own margins.
https://github.com/YaLTeR/niri/wiki/Configuration:-Layer-Rules#shadow
I'm adding tabs to niri. Instead of some separate mode, they're just changing how a column is displayed. This means all your hotkeys and everything works exactly the same with tabs. Which was a wonderful UX idea by @elkowar!
I've got a draft PR going with some design and UX questions, please feel free to try it and give feedback: https://github.com/YaLTeR/niri/pull/1085
A ton of changes in the tabs PR over the past few days. Mainly various options (tabbed display by default, tab indicator position, etc.).
Just finished with a big one: you can now place the tab indicator within the column rather than "outside". This is needed for thicker tab bars, since otherwise they overlap adjacent windows.
I merged tabbed columns into niri! Now you can play around with them using your nearest niri-git package. With working animations and all
Noticed tabs can sometimes be useful for comparing windows without taking screenshots. Here for example I'm running the Adw demo from F41 vs. nightly Flathub, showing the slight color difference and apparently a 1 px layout shift.
Another cool suggestion by @elkowar: you can now match windows recorded by an active window screencast. For example, to highlight the casted window with a different color.
You can now (finally) customize the important hotkeys list: https://github.com/YaLTeR/niri/wiki/Configuration:-Key-Bindings#custom-hotkey-overlay-titles
Today in *very long* overdue features (looks like I opened the issue even before v0.1.0): moving the mouse against a monitor edge now scrolls the view during drag-and-drop.
(before this change, you had to use the keyboard for this, and yes it was very awkward)
Another neat new thing: a bind to expand column to available width. Basically, "expand to fill empty space".
But, a bit smarter: with scrollable tiling we can have windows partially off-screen. This bind ignores such windows, making it easy to position things to exactly fill the screen, even in the middle of a scrolling layout.
Today I'm releasing niri v25.02 with tabs, shadows, DnD view scrolling, and a ton of other improvements! Read the release notes at https://github.com/YaLTeR/niri/releases/tag/v25.02 and @ your distro to update the package.
[[honestly wtf how did so much stuff happen, it's been barely over a month]]
Today I merged a PR by FluxTape which adds "always empty workspace before first" to niri. At the surface this is just a simple config flag with obvious behavior, but it's actually full of edge cases! Things like which workspace to focus at startup. The code refers to workspaces by index in many places, and those all shift when you suddenly insert an empty workspace at index 0.
Took several days to catch them all even with our randomized tests, but I think it should be good now.
This morning was my niri (-adjacent) talk! Went really well, got many interesting questions!
They promised us video recordings in a few days, so I'll post a link when I get it. Though of course the talk is in Russian.
I'm thinking of switching niri to the year.month versioning. So instead of 0.1.11, the next release will be 24.12 or 25.01, and so on. Hotfix releases will use patch like 25.01.1.
Are there any issues with this versioning that I should consider? There won't be releases more frequently than monthly so that's not a problem.
Ivan Molodetskikh
TheZoq2
Julian Hofer
algernon, who woke up from a Rust plugin fever dream
sodiboo 
yyyy.m.n where n=1 at the start of each month and increments after each release. which is basically equivalent to what you were thinking of except it always specifies a patch number, even if only one release happens in a month@sodiboo hmm. Admittedly, it took me an embarrassingly long time to realize that the year.month in Ubuntu is, in fact, year.month, and four digits would clear that up a bit. I would prefer zero-padded double-digit month for the same reason.
On the other hand, spelling out the whole 2024 seems a tad redundant, and there are other projects like Helix that use double-digit year.month so it's not like there's no precedent.
YY.MM. like it's all arbitrary anyways and it doesn't really matter in the end because you do have to pick something, but personally I like four-digit year betterI would prefer zero-padded double-digit month [because it's more obviously rooted in the Georgian calendar] yeah I have no opinion in favor of or against this.2024.5.3 meant it's from the third of May (it means that's the third release in May). so maybe a different separator is worth using, to show that the third field isn't a date? I guess it's "obviously" +.> ok but what if niri lives to be 100 years old? wouldn't want another Y2.1K now would we?
The world runs on huge AI clusters. Everyone is streaming their thoughts into a neutral network and receiving the complete rendered output directly into their brains. And then there are the two weird users, one connecting to the singularity through an IRC bridge, and the other scrolling tiles on their ancient manual computer
unusual sights
Turns out, there's a lot of details to get right when implementing a floating window space. For example, dialog windows should always show above their parent window. Otherwise, it's easy to lose them under the (usually much bigger) parent.
The WIP floating branch in niri now handles this properly, even for xdg-desktop-portal dialogs (like file chooser) as long as the app correctly parents them via xdg-foreign.
Another piece of the floating puzzle: keeping windows on screen. When you change your monitor scale or resolution, you don't want your floating windows to suddenly go unreachable behind the monitor's new borders.
Here I'm resizing a nested niri with three windows, simulating resolution changes. No matter what I do, they always remain partially visible and reachable. Even for more unusual cases like trying to resize a window into out of bounds.
In the tiling layout, niri is constantly asking windows to assume their expected size. In contrast, floating windows should be able to freely change size as they see fit.
The logic turns out to be quite tricky. On the one hand we want a window to keep its latest size, but on the other we still want to be able to resize the window, which means asking it for a different size. The window can take a second to respond, or respond with a yet another size, and nothing must break.
While trying to make this work, I realized that this is the time when I *really really* want to be able to test this stuff. So I got on a sidetrack adventure to write testing infra for running real Wayland clients inside unit tests.
I've got it working! In these tests, I'm creating a new niri instance along with test clients, all on the same test-local event loop. No global state, no threads needed.
What's really cool is that this lets me test the weirdest client-server event timings.
This morning I worked on remembering the size for floating windows when they go to the tiling layout and back.
The whole sizing code must be at the top by logic complexity in niri. I have to juggle, all at once:
- new size I haven't sent to the window yet,
- size changes I sent, but window hasn't acked yet (0, 1, or more in-flight),
- size change window acked but hasn't committed for yet,
- size change window acked and responded to with a commit (maybe with a different size entirely).
The diff is 85 lines of change and 243 lines of new tests, and I already found a few weirder edge cases that I've missed. No way I could do this well without that client-server testing setup that I posted about yesterday.
Btw I pushed the testing setup if you're curious, along with the entirety of 1215 snapshot files for a powerset of new window workspace/output target settings: https://github.com/YaLTeR/niri/commit/771ea1e81557ffe7af9cbdbec161601575b64d81
The WIP floating branch caused them to update in several commits already.
The big 1215 snapshot test powerset (actually it already grew to 1695) continues to prove its worth. Just finished a big +495 -508 cleanup of the window opening code, and verified that not a single of those 1215 window opening configurations changed its outcome. I will be sleeping well tonight
After three weeks of hard work, I am undrafting the floating window PR in niri. Please give it thorough testing and report any bugs or issues!
@chfkch yeah it's a bit weird; I left a comment about it in a different test.
What I suspect is happening is that since niri sends its configures at the very end of its event loop iteration, it frequently happens that the client receives and processes the roundtrip response right before that configure.
For some reason it happens quite frequently with many threads. I'm not sure what's thread dependent, but two roundtrips should guarantee against this particular problem at least.
Tau 🏳️🌈
chfkch 
Psyhackological
armerpunkt
ralen
Eduardo Flores 
drusk
ElKowar
Paranoid
Sasaigo
huilong 
phisch
Jons Mostovojs
Alexander Sosedkin 
Sergey Bugaev