iris-aiandClaude Opus 5
7548139861
Layout reaches one place by more than one route -- a box composed down the chain, and the same box summed from what its children asked for -- and the two land a few bits apart in floats. Where that decides something structural rather than something positional, a warm tree disagrees with a cold one: `5ed9e87` is the instance, and its margin is a patch over the representation rather than a fix to it. `Fixed<SHIFT>` is a count of `1 / 2^SHIFT`s in an `i32`. Adding and subtracting are exact, a multiply rounds once back onto the same steps, and two routes that come within half a step land on the same number -- so the comparisons downstream can ask for equality rather than for nearness. `Px = Fixed<6>` and `Rel = Fixed<24>`: a sixty-fourth of a pixel is finer than a display and still exact in `f32` up to 262,144 px, and twenty-four bits of fraction matches `f32` at a half, beats it above one where anchors sit, and leaves +/-128 of range to sum relative children in. Nothing uses it yet. The arithmetic saturates rather than wrapping, because a clamped coordinate keeps the ordering a wrapped one inverts, and the ends are what an unbounded interval will be written with. Checked: fmt, clippy, 99 tests including ten for this type -- the round trip through `f32`, halves rounding away from zero either side, saturation at both ends, and 20,000 additions landing exactly where the count says. 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