iris-aiandClaude Opus 5
b165164e59
A span reporting `Len::default()` whenever a child had a share threw away how many shares it was holding, so each level of nesting re-divided a share rather than dividing the same space. One span of a rect beside a span of three gave 1/2 and 1/6 each, where the same four rects directly in one span get a quarter. A span that sizes from its children does not resolve `rest`, it passes the weight up; resolution belongs at the nearest ancestor with a length, and since the output became a box there is always one. The placement loop already divides by `len.rest / total.rest`, so it consumes carried weights unchanged -- only what the span reported was wrong. The uneven nesting is the case that fails without this; the even one passes either way and is here as the statement of intent. Decided by the owner, 2026-09-14. 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