iris-aiandClaude Opus 5
d8ae9c3bdd
`redraw` asks a dirty widget at its offer, and then again in the final box its parent chose from that answer. The second ask handed that box over as if it were an offer, so `draw_inner` ran `placed_box` on it and applied the widget's own alignment to a box that had already been placed -- a second placement on every local redraw of a widget that is not near-aligned. It only showed where the widget's alignment was its own to apply: a container override makes `draw_inner` take the box as given, and `Stack`, `Pad` and `Scroll` override every child they hand a box to. It is the fix for both of the handoff's standing warm-against-cold failures. Shrinker seed 288 on `region-node` was an 8.8px inset at each end of a `Text` under a `Span(Y-)` under two `Stack`s; oracle seed 326 at depth 6 was 88px on a `Text` under two `Branch`es. Neither reduced below 11 and 43 widgets, and both are this. Checked: fmt, clippy, 80 suite tests, 17 core unit tests, the release oracle at 100 seeds, **all fifteen shrinker cases at 400 seeds of depth 5**, and **1000 seeds of depth 6** -- the last two for the first time. `tabs`, `text`, `random` and the tab replay render byte-identical at 1920x1200 against `08c9d5a`, since nothing about a cold layout changes. Generated seed 20 at depth 4 catches it and joins the ordinary set, so `cargo test` fails without this rather than only the ignored long run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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