iris-ai
0e0d4af326
`draw_inner` took an answer from `try_reuse`, which checks only whether the widget itself is marked, where `retained_answer` beside it also refused one while anything the widget read a size from was dirty. A widget whose drawing happened to be reusable therefore handed back the answer it gave before that descendant changed. Nothing puts that right afterwards. The comparison that tells a reader its child's answer moved is in `redraw`, and a widget settled inside its parent's own draw never goes through it -- the placing ask redraws the subtree, the descendant's mark is cleared there, and the parent keeps a number the tree no longer agrees with. So the check is not the optimization its comment claimed; it is what makes the answer an answer, and both retained routes are answers, so it is asked once in `draw_inner` rather than by one of them. Found by the generated oracle at seed 564, depth 6, `shuffle-every-other`, while reading a child's report as a fraction of the containing widget: that reading lets a span overflow itself, which makes the two asks' boxes differ far enough for the placing one to redraw. Twenty-five rig work counters are unchanged on `cold`, `repaint`, `scroll`, `resize` and `size`; `many` makes 18 fewer reuse attempts, 17 of which already reported "dirty". Both long fuzzers green.
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