iris-ai
a92c6acdbf
The queue was already deepest-first, but a widget that could not settle where it was called `redraw` on its parent from inside itself. That drew a shallow widget while dirty widgets deeper in other subtrees were still pending, and a parent drawing over a subtree that has not settled reads answers about to move: the one that settles does so inside the parent's draw, where its mark comes off and nothing compares what it now answers. Seed 564 was exactly that, and it is the second time this shape has been found. So a widget that cannot settle defers instead. It marks its parent, stays marked itself, and waits in `deferred` until the walk down the depths reaches the parent -- which cannot be before everything deeper has settled, because the walk always takes the deepest widget that is not waiting. The category stops being something to check for. (Bryan, 2026-09-17.) `dirty_size_under` stays in `draw_inner` for now: `update` draws the root for a resize before `redraw_updates` runs at all, so the ordering does not cover that entry. Green on the suite, the shrinker at 400 seeds of depth 5, the oracle at 1000 seeds of depth 6, and 2000 seeds at depth 4 over all fifteen cases. Drawn widgets, widget draws and primitive writes are unchanged on every rig phase; `many` pays 51 queue pops for 27 and 1059 depth reads for 410, which is the deferring and nothing else.
iris
My experimental attempt at a rust ui library (also my first ui library).
It's currently designed around using retained data structures (widgets), rather than diffing generated trees from data like xilem or iced. This is an experiment and I'm not sure if it's a good idea or not.
Examples are in examples, eg. cargo run --example tabs.
Goals, in general order:
- does what I want it to (text, images, video, animations)
- very easy to use ignoring ergonomic ref counting
- reasonably fast / efficient (a lot faster than electron, save battery life, try to beat iced and xilem)
dev details
not targeting web rn cause wanna use actual nice gpu features & entire point of this is to make desktop apps / not need a web browser
general ideas trynna use rn / experiment with:
- retained mode
- specifically designed around wgpu so there's no translation
- postfix functions for most things to prevent unreadable indentation (going very well)
- events can be done directly where you draw the widgets
- almost no macros in user code & actual LSP typechecking (variadic generics if you can hear me please save us)
- relative anchor + absolute offset coord system (+ "rest" / leftover during widget layout)
- single threaded ui & pass context around to make non async usage straightforward (pretty unsure about this)
- widgets store outside of the actual rendering so they can be moved around and swapped easily (unsure about this but seems to work good for now)
under heavy initial development so not gonna try to explain status, maybe check TODO for that; sizable chance it gets a rewrite once I know everything I need and what seems to work best
it's called iris because it's the structure around what you actually want to display and colorful