iris-aiandClaude Opus 5
c596bf12c6
`SetSize` drew its child in whatever box it had been given and then reported its declared length, so the child answered about a box it was never going to have -- and the answer on the *other* axis was taken under that. A wrapping text under `SetSize(x: 76px)` was measured in the whole 640 available, reported one line, and the parent sized itself to one line. The text was then drawn again at 76 and reported two, but by then its box was settled and nothing revisited it. A repaint put it right, which is why the first frame and the second disagreed. So the layout was not a function of the state, and "cold" was not a fixed point -- which means the warm-against-cold oracle has been measuring against a tree that had not settled, and some of what it reported as a retained-layout defect was the cold side being wrong. Nothing about retained state is involved in this: it reproduces in six widgets on a first frame. The declared length is what the child gets, so that is where it is measured. `apply_rest` carries `rel` and `rest` through unchanged, and a `px` length composes as an offset, so the child's box does not move again when this widget's own box shrinks to what it declared. `tests/unsettled.rs` passes, and the generated sweep now passes at depth 5 where it failed. Depth 6 and 7 still fail; there is more than one of these. 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