Ivan MolodetskikhImplemented the thing where you can toggle the mouse pointer on the screenshot after the fact (by pressing P). Gonna add a help panel here soon to remind you of this.
Much better
key repeat + scrollable tiling = fun
One of the niri users has contributed a gradient interpolation color space setting! Now you can do pretty gradient borders in srgb-linear, oklab and oklch (in all four hue directions).
I made a COPR for git builds of niri: https://copr.fedorainfracloud.org/coprs/yalter/niri-git
Apparently this is a thing you can do; relatively easily, even. It's fully automatic, triggers on a webhook from GitHub.
Thanks Michael (my4ng) from our Matrix channel for showing me the relevant docs and doing the initial work!
also in an act of severe procrastination i decided to try drawing a diagram of the redraw state machine: https://github.com/YaLTeR/niri/wiki/Redraw-Loop
Spent a better part of today, but I've got dmabuf modifier negotiation fully working in my pipewire screencasting code in niri! This happens to finally fix screencasting on NVIDIA GPUs. Still haven't got any GStreamer pipeline working though, maybe needs a pipewire update.
Apparently, my AMD selects a BGRA format modifier that has two planes. Some out of band info I suppose. And on Intel a preferred BGRA modifier has three entire planes!
My Wayland compositor, niri, turns one today! 
Here's v0.1.8 with bind key repeat, screenshot UI pointer toggle, gradient color spaces, wlr screencopy v3 and output management, and lots of other improvements: https://github.com/YaLTeR/niri/releases/tag/v0.1.8
omg, my friend drew a birthday nirik 
i recorded a demo video for the focus-follows-mouse section to showcase it lol
Several days and a lot of hair pulling later, I *think* I got resize transactions working?? Maybe? Hopefully?
Resize transactions is when all windows that must resize together, resize together, with no mismatching frames in between. For example, all windows in a column must add up to the full screen height.
This requires correct configure acks on the client (looking at you, Blender) and very careful state update delaying and resize throttling on the compositor side.
narrator: there was still one case where it didn't work due to a bug
okay, surely this time it definitely works for all correctly written clients
Here's one mainly for people who disable animations: window closing now runs in a transaction with the other windows resizing. This means, no background flicker.
There's been another logo discussion in the niri Matrix room with some quite interesting concepts emerging. Here's one by Endg4me_ with edits by bluelinden and myself, and inspiration from a concept by ElKowar.
What do you think?
I'm working on an "event stream" IPC for niri where you get notified about events as they happen. For example, "workspace switched" or "keyboard layout changed".
To give it a good test, I actually started implementing native niri support in Waybar. You can give it a try too: https://github.com/YaLTeR/niri/pull/453#issuecomment-2317110904
I finished the initial event stream IPC implementation for niri. My Waybar fork implements a decent amount of the modules niri/workspaces, niri/window, niri/language. Please give that a try, also anyone who makes IPC scripts or bars please give a try to the event stream IPC itself so we can find any design flaws before merging.
The PR you will need: https://github.com/YaLTeR/niri/pull/453#issuecomment-2321730996
Waybar fork is linked from there.
The other day, Christian Meissl finished updating and publishing the libdisplay-info bindings [1]. This is quite exciting because, unlike edid-rs, it can parse the manufacturer/model/serial from pretty much any monitor.
So, today I spend a few hours integrating the manufacturer/model/serial monitor addressing all throughout niri: config, IPC, niri msg, screencast output selector. You should now be able to write/use "SomeCompany CoolMonitor 1234" everywhere!
Set up CI rustdoc publishing for niri-ipc: https://yalter.github.io/niri/niri_ipc/
This has the entirety of the niri IPC documented, including the new event stream events.
After the Waybar maintainer speedran merging my niri modules and releasing, I would feel bad delaying any longer, so here's niri 0.1.9 :)
Event stream IPC for bars, better window resizing, properly named outputs, on-demand VRR, out-of-the-box fix for NVIDIA flickering, and other improvements!
wtf did I Just Make
Over the past 2 weeks I've been slowly but surely working on the interactive move niri PR [1] by @pajn. It's already got me to fix quite a bit of tech debt in the layout code, which is cool.
The PR is still rough around the edges, but mostly works, and I switched to running the branch on my own systems to give it thorough testing.
(also no, this is not the Floating Layer yet, though it's a good step towards that)
Attaching a video of what it looks like rn
Made interactive move work on touch (and resize too while I was at it), didn't need that many changes actually
Added a bit of rubberbanding before the window is "dragged out" of the layout. Should help avoid unintended layout changes.
Along with a few more fixes I did, I think interactive move should be good to merge? It's not 100% perfect and jank free, but I'm fairly sure I got all the important things done. Will give it some more testing.
Suddenly, @drakulix showcasing the Cosmic session running on, among other compositors, niri! On the big screen at the Ubuntu Summit 😄
somehow this touch moving under stationary pointer works better than i expected
(yes trying to do a precise left click with an elbow was difficult)
By the way! I'll be giving a talk at RustCon in Moscow on December, 6! 
Wherein I will briefly describe what a Wayland compositor is, and then show several testing and profiling workflows that I've been using to keep niri stable, robust and performant.
(The invitation to submit a talk was completely unexpected, guess niri found its way into the right eyes. 😅)
There will be a recording, though in Russian.
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.
Somehow, a small change for tests escalated into trying to completely refactor how animation timing works in niri. And right now I find myself at the exact opposite of this picture. Unfortunately, time has not stopped and is causing problems
Like three complete refactors later, I think it's... working? For real this time? No weird issue is gonna sneak up that undermines the whole design?
Nothing seems to have caught on fire after one more day of personal testing and one more day in main. So here's a technical page I wrote about the the new niri animation timing design and its motivations: https://github.com/YaLTeR/niri/wiki/Animation-Timing
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.
>did a +4,657 −4,237 refactor in the layout code
>while testing, already found two uncaught regressions introduced in previous niri releases, and no issues with the refactor
>while testing, already found two uncaught regressions introduced in previous niri releases, and no issues with the refactor
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
i was finishing writing these to celeste reach for the summit ost lol
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
Why would you even want tabs in niri? Occasionally it's quite useful. For example, when streaming programming, I increase the font size, so I can no longer fit editor + terminal on the screen at once. Scrolling back and forth gets annoying, and tabs feel just right for this.
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.
Psyhackological
φ@YaLTeR hii kinda unrelated but do u know of anyone who made a script for a dmenu window picker in niri ? i wanna make one but i wont if theres one already floating around haha , i just couldnt find it
@fiore yeah ppl did make, search in Discussions. I don't have link handy
Areskul@YaLTeR only thing I can see is a man using the right vcs.
David Runge@YaLTeR well deserved! 👍
Sai (సాయి)@YaLTeR an useful project deserves it :)
scientiac@YaLTeR Love the way it looks!
VBB♈️@YaLTeR hi Ivan, can I install niri on fedora in some default configuration with recommended plugins, ready to use? I would like to test it on the same pc I have gnome installed, but don't want to configure it.
@VBB hey, you can use my COPR: https://copr.fedorainfracloud.org/coprs/yalter/niri
That'll give you a few utilities like fuzzel (app launcher) and swaylock (screen locker), but no bar and no xwayland-satellite. So you'll still need to do some configuring for a comfortable session (though, everything else will work out of the box, including portals, etc.).
There are some COPRs for xwayland-satellite, haven't tried them: https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=xwayland-satellite
Lucie / minute
Ryan Brue@YaLTeR Do the shadows provide the same shape regardless of the window's shape? i.e. more or less roundness in the corners
@ryanabx they use the same thing as border and focus ring, which is unfortunately simply a window rule for geometry corner radius. If you don't window rule it, it will assume that the window has square corners. And if you do set a corner radius with the window rule, the shadow will also use the correct corner radius.
A Wayland protocol for toplevels to tell what their CSD corner radius is would be real nice here
@YaLTeR yep, on the cosmic side we've had the same want!
David 
@YaLTeR Where did you get that background? I love it!
@dperson good question. Last year I went through some wallpapers subreddits, must've been from there somewhere
holly, 
huilong 
ElKowar@YaLTeR Hell yea, congrats!!
I feel like celebrating leaving zeroVer, when your solution is just fully moving to calver, is... funky lmao
@elkowar for this one I definitely waited to change the version until I felt that it was ready to leave v0.1. Maybe if not for calver I would've called this a v1.0
@YaLTeR looks amazingly smooth! Great job!
LXQt-Project@YaLTeR Works really fine, we will ship updated config.kdl with some floating rules when it's released.
@YaLTeR so glad you exist with your compositor and expertise!
@tbernard I remember you asking if it will work for the window dragging to target the mosaic tiling layout when the window is close enough to a tiling position, and to remain free-floating otherwise.
I tried this in niri at first, but quickly realized it's annoying. When you drag a tiled window, you likely want to put it back to tiling, and vice versa.
I came up with a gesture instead: while dragging a window, you can right click to change whether it "targets" tiling vs. free-floating.
Tobias Bernard@YaLTeR I'd have to try it, but yeah how to make the tiling/floating switch explicit in a nice way is a bit of an open research question.
I think it needs to be more obvious than a mystery gesture, but you're right that it shouldn't be in the way either. One idea we had at some point was a literal drop area labelled "move to floating", but no idea if that's viable...
@YaLTeR what is that image viewer you're using? GNOME's?
@YaLTeR I recently searched for best Wayland image viewers as Nomacs couldn't open my Wayland session and I found this, maybe it will interest you as it is written in Rust: https://github.com/woelper/oculante
But will try Gnome's too.
But will try Gnome's too.
armerpunkt@YaLTeR In order to test this, I have to build the floating branch, right?
@YaLTeR I take it that it’s not supposed to remember where a window was in the tiling layout. Like if I have two windows open, toggle the left to floating (using keyboard shortcut), then toggle it back to tiled, it moves to be on the right. I guess keeping track of that when the tiling could change in the background would be a nightmare. But other than that little nitpick, it’s working great so far 👍
@armerpunkt yeah, you got the main problem with remembering the tiling position right. That said, the tiling focus works the same as when opening/closing windows in this case, so for instance opening a new window (even in the middle) then immediately toggling it to floating and back should put it where it was.
ralen@YaLTeR so now you can finally fix the bug of resizing the window past the bottom of a screen?
@ralen guess i can clamp it now yeah
Val Packett 🧉@YaLTeR mmmmm actually would be really cool if dialogs could (optionally) "stick" to their parents (like basically treat their position as relative to parent's center)
@valpackett we can do that for modal dialogs. It's more work though, not as simple
chfkch 
@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.