iris-aiandClaude Opus 5
394d5149a5
`Branch` picks which of two subtrees to draw by comparing a measured pixel length with a threshold. That is exactly what the oracle wants -- it is how a widget believing a measurement a cold start would not have given it becomes a different tree -- and exactly what a rig measuring cost must not have: the fixture's shape moves with the thing being measured. It has been moving. Seed 1 at depth 8 draws 88 widgets and writes 2,298 primitives a frame at `5ed9e87`, and 115 and 8,209 at `bd6de71` -- three and a half times the work -- so the handoff's "fixed point cost 3x" compared two different workloads and is withdrawn. Measured on one tree instead, with `Edits::fixed_branches`, `5ed9e87` is 1,761M instructions and ~699M cycles against this head's 2,093M and ~819M, while drawing 100 widgets against 97 and writing 4,272 primitives against 3,951. Fixed point costs something like a fifth to a quarter, not three times. The oracle keeps measured branches: `fixed_branches` is false by default and only the rig sets it. A branch consumes its randomness either way, so both grow the same ids. **Check the work counters before comparing two commits' times.** The rig prints drawn widgets, widget draws and primitive writes for this reason; an undrawn `leftover` child still moves them, which no flag can remove. Checked: fmt, clippy, 105 tests, the 100-seed generated oracle. 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