Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

NodeBB

  1. Home
  2. uncategorized
  3. Decided to try writing a Wayland compositor for fun.

Decided to try writing a Wayland compositor for fun.

Scheduled Pinned Locked Moved uncategorized
200 Posts 1 Posters 22 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • ? Guest

    Implemented basic AccessKit integration for niri based on @DataTriny's proof-of-concept. I have little experience with screen readers, and also had several questions, so I would appreciate more eyes and testing on the PR:

    https://github.com/YaLTeR/niri/pull/2273

    #niri #a11y

    ? Offline
    ? Offline
    Guest
    wrote on last edited by
    #176

    niri v25.08 is now released with a logo, xwayland-satellite integration, basic screen reader support, NVIDIA screencast flickering fix, window positions and sizes in IPC, and many other improvements!

    Read the notes here: https://github.com/YaLTeR/niri/releases/tag/v25.08

    now i need at least a month off from any release notes preparation 😴

    #niri #smithay #wayland #rust

    ? 1 Reply Last reply
    0
    • ? Guest

      niri v25.08 is now released with a logo, xwayland-satellite integration, basic screen reader support, NVIDIA screencast flickering fix, window positions and sizes in IPC, and many other improvements!

      Read the notes here: https://github.com/YaLTeR/niri/releases/tag/v25.08

      now i need at least a month off from any release notes preparation 😴

      #niri #smithay #wayland #rust

      ? Offline
      ? Offline
      Guest
      wrote on last edited by
      #177

      Screen reader announcement demo bc apparently you can't attach video and image at once

      #niri

      ? 1 Reply Last reply
      0
      • ? Guest

        Screen reader announcement demo bc apparently you can't attach video and image at once

        #niri

        ? Offline
        ? Offline
        Guest
        wrote on last edited by
        #178

        Fullscreen refactor pt. 1: track pending vs. current fullscreen state for columns, avoid vertical jump when waiting for window to commit a new buffer.

        #niri

        ? 1 Reply Last reply
        0
        • ? Guest

          Fullscreen refactor pt. 1: track pending vs. current fullscreen state for columns, avoid vertical jump when waiting for window to commit a new buffer.

          #niri

          ? Offline
          ? Offline
          Guest
          wrote on last edited by
          #179

          Fullscreen refactor pt. 2: added un/fullscreen animations. This one involved quite a lot of moving parts actually, so looking for testing.

          https://github.com/YaLTeR/niri/pull/2333

          #niri

          ? 1 Reply Last reply
          0
          • ? Guest

            Fullscreen refactor pt. 2: added un/fullscreen animations. This one involved quite a lot of moving parts actually, so looking for testing.

            https://github.com/YaLTeR/niri/pull/2333

            #niri

            ? Offline
            ? Offline
            Guest
            wrote on last edited by
            #180

            Fullscreen refactor pt. 3 turned out to be a refactor of a good chunk of core Smithay xdg-shell/layer-shell/session-lock logic, making it more correct. The fullscreen PR in niri now includes that Smithay refactor, and needs testing even more than before

            https://github.com/YaLTeR/niri/pull/2333#issuecomment-3263990200

            Specifically, the refactor makes Smithay correctly track the last acked configure for each commit, also enforces the "must ack before committing first buffer" protocol rule.

            #niri

            ? 1 Reply Last reply
            0
            • ? Guest

              Fullscreen refactor pt. 3 turned out to be a refactor of a good chunk of core Smithay xdg-shell/layer-shell/session-lock logic, making it more correct. The fullscreen PR in niri now includes that Smithay refactor, and needs testing even more than before

              https://github.com/YaLTeR/niri/pull/2333#issuecomment-3263990200

              Specifically, the refactor makes Smithay correctly track the last acked configure for each commit, also enforces the "must ack before committing first buffer" protocol rule.

              #niri

              ? Offline
              ? Offline
              Guest
              wrote on last edited by
              #181

              With the fullscreen refactors in place, I got started on the thing that I wanted to do all along: maximize.

              Niri didn't support normal Wayland maximize because it's very similar (yet slightly different) to our full-width columns—and can't be bound to our full-width state either. However, after plenty of requests, and thinking about it, I reconsidered. Henceforth, the maximize buttons and double-clicking on the titlebars will do the expected thing.

              Details in PR: https://github.com/YaLTeR/niri/pull/2376

              #niri

              ? 1 Reply Last reply
              0
              • ? Guest

                With the fullscreen refactors in place, I got started on the thing that I wanted to do all along: maximize.

                Niri didn't support normal Wayland maximize because it's very similar (yet slightly different) to our full-width columns—and can't be bound to our full-width state either. However, after plenty of requests, and thinking about it, I reconsidered. Henceforth, the maximize buttons and double-clicking on the titlebars will do the expected thing.

                Details in PR: https://github.com/YaLTeR/niri/pull/2376

                #niri

                ? Offline
                ? Offline
                Guest
                wrote on last edited by
                #182

                My Smithay refactors were merged: the big one mentioned above, plus a fix for popup stacking order (e.g. open popup, then open tooltip also from the toplevel itself), plus a fix for root popup grabs from Qt layer-shell surfaces. All of this along with fullscreen refactors and animations is now merged to niri main. (maximize is still wip)

                #niri

                ? 1 Reply Last reply
                0
                • ? Guest

                  My Smithay refactors were merged: the big one mentioned above, plus a fix for popup stacking order (e.g. open popup, then open tooltip also from the toplevel itself), plus a fix for root popup grabs from Qt layer-shell surfaces. All of this along with fullscreen refactors and animations is now merged to niri main. (maximize is still wip)

                  #niri

                  ? Offline
                  ? Offline
                  Guest
                  wrote on last edited by
                  #183

                  There's been a long-standing request to add config includes to niri. They're useful for config organization, but also for custom desktop shells to be able to change colors without having to edit the main user's config.

                  Today I finished the first step towards this: a many-days-long refactor that makes the main config part, layout, mergeable, i.e., able to be combined from multiple parts. And building on this, per-output/workspace overrides.

                  https://github.com/YaLTeR/niri/pull/2449

                  Testing wanted here!

                  #niri

                  ? 1 Reply Last reply
                  0
                  • ? Guest

                    There's been a long-standing request to add config includes to niri. They're useful for config organization, but also for custom desktop shells to be able to change colors without having to edit the main user's config.

                    Today I finished the first step towards this: a many-days-long refactor that makes the main config part, layout, mergeable, i.e., able to be combined from multiple parts. And building on this, per-output/workspace overrides.

                    https://github.com/YaLTeR/niri/pull/2449

                    Testing wanted here!

                    #niri

                    ? Offline
                    ? Offline
                    Guest
                    wrote on last edited by
                    #184

                    Our config system is declarative, rather than command-like, which means that we parse the config into a tree of data types instead of reading lines and applying them one-by-one. This design requires a lot of work to properly support includes, but in turn we get atomic and selective reloading (if output part of the config didn't change, we don't override your transient output adjustments), better error messages and no problems with things like "spawn-at-startup" that should only work once.

                    #niri

                    ? 1 Reply Last reply
                    0
                    • ? Guest

                      Our config system is declarative, rather than command-like, which means that we parse the config into a tree of data types instead of reading lines and applying them one-by-one. This design requires a lot of work to properly support includes, but in turn we get atomic and selective reloading (if output part of the config didn't change, we don't override your transient output adjustments), better error messages and no problems with things like "spawn-at-startup" that should only work once.

                      #niri

                      ? Offline
                      ? Offline
                      Guest
                      wrote on last edited by
                      #185

                      After several more days of work, I fully finished config includes. All config sections merge together, live-reloading watches all included files (even if they fail to parse), error messages work across files, documentation is written.

                      https://github.com/YaLTeR/niri/pull/2482

                      Once again, this needs testing! There must be NO breakage to existing configs, so if something breaks, I want to know about it to fix it.

                      #niri

                      ? 1 Reply Last reply
                      0
                      • ? Guest

                        After several more days of work, I fully finished config includes. All config sections merge together, live-reloading watches all included files (even if they fail to parse), error messages work across files, documentation is written.

                        https://github.com/YaLTeR/niri/pull/2482

                        Once again, this needs testing! There must be NO breakage to existing configs, so if something breaks, I want to know about it to fix it.

                        #niri

                        ? Offline
                        ? Offline
                        Guest
                        wrote on last edited by
                        #186

                        I merged config includes, along with per-output and per-workspace layout config overrides. Play around with them at your nearest niri-git package.

                        - https://yalter.github.io/niri/Configuration%3A-Include.html
                        - https://yalter.github.io/niri/Configuration%3A-Outputs.html#layout-config-overrides
                        - https://yalter.github.io/niri/Configuration%3A-Named-Workspaces.html#layout-config-overrides

                        Also merged ignore-drm-device which should let you passthrough a GPU to VMs: https://yalter.github.io/niri/Configuration%3A-Debug-Options.html#ignore-drm-device

                        #niri

                        ? 1 Reply Last reply
                        0
                        • ? Guest

                          I merged config includes, along with per-output and per-workspace layout config overrides. Play around with them at your nearest niri-git package.

                          - https://yalter.github.io/niri/Configuration%3A-Include.html
                          - https://yalter.github.io/niri/Configuration%3A-Outputs.html#layout-config-overrides
                          - https://yalter.github.io/niri/Configuration%3A-Named-Workspaces.html#layout-config-overrides

                          Also merged ignore-drm-device which should let you passthrough a GPU to VMs: https://yalter.github.io/niri/Configuration%3A-Debug-Options.html#ignore-drm-device

                          #niri

                          ? Offline
                          ? Offline
                          Guest
                          wrote on last edited by
                          #187

                          After a detour to config includes and, again, several days/weeks of work implementing all edge cases and expected behaviors, true window maximize is ready and merged to main. Tricky cases like: windows requesting fullscreen and maximize after opening; windows failing to match the full maximized size; transparent windows with the niri border behind them.

                          https://yalter.github.io/niri/Fullscreen-and-Maximize.html

                          Give it a try! Ngl I mostly switched to maximize just because I'm too lazy to reach the keyboard for Mod+F.

                          #niri

                          ? 1 Reply Last reply
                          0
                          • ? Guest

                            After a detour to config includes and, again, several days/weeks of work implementing all edge cases and expected behaviors, true window maximize is ready and merged to main. Tricky cases like: windows requesting fullscreen and maximize after opening; windows failing to match the full maximized size; transparent windows with the niri border behind them.

                            https://yalter.github.io/niri/Fullscreen-and-Maximize.html

                            Give it a try! Ngl I mostly switched to maximize just because I'm too lazy to reach the keyboard for Mod+F.

                            #niri

                            ? Offline
                            ? Offline
                            Guest
                            wrote on last edited by
                            #188

                            One cool thing I noticed about true maximize is that apps like GIMP or Inkscape or Blender, that really want all available space, maximize themselves at startup, so you don't have to window-rule them manually in your config

                            #niri

                            ? 1 Reply Last reply
                            0
                            • ? Guest

                              One cool thing I noticed about true maximize is that apps like GIMP or Inkscape or Blender, that really want all available space, maximize themselves at startup, so you don't have to window-rule them manually in your config

                              #niri

                              ? Offline
                              ? Offline
                              Guest
                              wrote on last edited by
                              #189

                              microsoft niri

                              #niri

                              ? 1 Reply Last reply
                              0
                              • ? Guest

                                microsoft niri

                                #niri

                                ? Offline
                                ? Offline
                                Guest
                                wrote on last edited by
                                #190

                                Small change on niri-git for people using the foot terminal with CSD, or other apps that constrain their sizes to a grid: niri will now match the default column width to a preset width when a window opens. So opening foot sized "proportion 0.5" and then pressing Mod+R will switch you to the next preset width, even if foot actually opened slightly smaller to match its terminal grid. Before the change, the first Mod+R would pick the same "proportion 0.5" in this case and "do nothing".

                                #niri

                                ? 1 Reply Last reply
                                0
                                • ? Guest

                                  Small change on niri-git for people using the foot terminal with CSD, or other apps that constrain their sizes to a grid: niri will now match the default column width to a preset width when a window opens. So opening foot sized "proportion 0.5" and then pressing Mod+R will switch you to the next preset width, even if foot actually opened slightly smaller to match its terminal grid. Before the change, the first Mod+R would pick the same "proportion 0.5" in this case and "do nothing".

                                  #niri

                                  ? Offline
                                  ? Offline
                                  Guest
                                  wrote on last edited by
                                  #191

                                  Also, experimenting with this interaction tweak on a branch: what if dragging tiled windows horizontally scrolled the view instead of dragging them "out"? This makes it possible to scroll the view mouse-only without going through the Overview (the zooming gets quite tiring when it's frequent), and makes it possible to scroll the view touch-only. To drag the window out of the layout, you can still drag it downward.

                                  #niri

                                  ? 1 Reply Last reply
                                  0
                                  • ? Guest

                                    Also, experimenting with this interaction tweak on a branch: what if dragging tiled windows horizontally scrolled the view instead of dragging them "out"? This makes it possible to scroll the view mouse-only without going through the Overview (the zooming gets quite tiring when it's frequent), and makes it possible to scroll the view touch-only. To drag the window out of the layout, you can still drag it downward.

                                    #niri

                                    ? Offline
                                    ? Offline
                                    Guest
                                    wrote on last edited by
                                    #192

                                    Added a small "Quick Start" to the niri docs that gets you going with niri + DMS in three commands:

                                    https://yalter.github.io/niri/Getting-Started.html#quick-start

                                    Tested the Fedora ones on a fresh VM, worked out nicely, getting me into a session with a very functional desktop shell.

                                    #niri

                                    ? 1 Reply Last reply
                                    0
                                    • ? Guest

                                      Added a small "Quick Start" to the niri docs that gets you going with niri + DMS in three commands:

                                      https://yalter.github.io/niri/Getting-Started.html#quick-start

                                      Tested the Fedora ones on a fresh VM, worked out nicely, getting me into a session with a very functional desktop shell.

                                      #niri

                                      ? Offline
                                      ? Offline
                                      Guest
                                      wrote on last edited by
                                      #193

                                      Currently in the middle of finishing up the Alt-Tab PR for niri: https://github.com/YaLTeR/niri/pull/1704

                                      Got most things working as I'd like, though still plenty of fixes and clean-ups left. Fully live window previews with block-out-from support and fading title labels.

                                      There's some interesting design differences compared to other desktops: on niri I expect it's common to have multiple terminals open, so Alt-Tab must go by windows (not by apps) and must show previews big enough to pick the right one.

                                      #niri

                                      ? 1 Reply Last reply
                                      0
                                      • ? Guest

                                        Currently in the middle of finishing up the Alt-Tab PR for niri: https://github.com/YaLTeR/niri/pull/1704

                                        Got most things working as I'd like, though still plenty of fixes and clean-ups left. Fully live window previews with block-out-from support and fading title labels.

                                        There's some interesting design differences compared to other desktops: on niri I expect it's common to have multiple terminals open, so Alt-Tab must go by windows (not by apps) and must show previews big enough to pick the right one.

                                        #niri

                                        ? Offline
                                        ? Offline
                                        Guest
                                        wrote on last edited by
                                        #194

                                        We've hit 15k stars on the niri repo!!

                                        #niri

                                        ? 1 Reply Last reply
                                        0
                                        • ? Guest

                                          We've hit 15k stars on the niri repo!!

                                          #niri

                                          ? Offline
                                          ? Offline
                                          Guest
                                          wrote last edited by
                                          #195

                                          Just merged Alt-Tab to main, shortly arriving at your nearest niri-git. Comes with plenty of ways to tweak it if you want [1], and a focus timestamp in the IPC [2] that lets shell devs make their own recent windows switchers.

                                          [1]: https://yalter.github.io/niri/Configuration%3A-Recent-Windows.html
                                          [2]: https://yalter.github.io/niri/niri_ipc/struct.Window.html#structfield.focus_timestamp

                                          #niri

                                          ? 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          Powered by NodeBB Contributors
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups