iris-aiandClaude Opus 5
4178dfbff9
Padding as a node, with each of the four sides its own number: a padding that is the same all round hides anything that treats one edge differently from another. Spans now hold two to four children, so a pattern of removals has something to make a pattern out of. Five ways of changing what a span holds, each a shape worth its own case rather than one shuffle: every other child out, everything but the first out, three on at once, the first out and three on, and one out of the middle with one on the end. Each is applied to every third span, and the cold tree is grown holding exactly what the warm one was left with. Three spare leaves are grown beside every span whether they end up in it or not, so a tree that leaves them out makes the same widgets in the same order as one that puts them in -- otherwise the two trees' `ids` stop lining up at the first difference and every comparison after it is against the wrong widget. Attaching one moves it, since a widget belongs to one parent; `upgrade` is for a weak handle that was never added, not a second share. The detached children are held until the comparison is over for the same reason: dropping the last share of one frees its id for the next widget to be given. Each case asserts the tree actually changed before comparing, so a shuffle that quietly did nothing fails rather than passes. All of it agrees: 49 tests, and the ignored sweep over 100 seeds and eight scenarios, 800 comparisons. 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