iris-aiandClaude Opus 5
e5a3e640d4
Six widgets from 905, and it fails in 0.06s: everything inside a declared 189x176 box is the same size whatever the output is, so a resize may not reach any of it, and the text still comes out 3.92px narrower warm than cold. `tests/trace_unsettled.rs` says why, and it is not what it looked like. A span measures a content-sized child in the space remaining, is told 167.41, and then offers that back as the child's box -- so the text is re-broken at exactly its own longest line, which is a knife edge: warm lands on four lines and 163.49, cold stays on three and 167.41. Measuring an answer against itself is unstable precisely at the fixed point. `Painter::settle` -- move the child's slot, keep the drawing, never measure again -- is the shape of the fix and does not work yet. In a span it breaks five cases, because a container child may have laid its own children out as fractions of the box it drew in, so moving it into a shorter one shrinks them; reporting a length in pixels does not mean the drawing is positioned in pixels. In `Aligned` alone it breaks two. Recorded rather than kept: the condition wants to be something a widget declares, near `OnResize`, rather than something its caller infers. 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