iris-aiandClaude Opus 5
e166e005dc
Asked of the `tabs` render: does a gap come out the same number of pixels wherever it appears? For a length in pixels it does, and structurally rather than by luck -- `Len::within` adds a part's own pixels rather than scaling them, and both ends of a gap carry the same fraction, so the multiply that rounds is the same on each and cancels. The test buries a row of five under three containers that are each a fraction of their parent, so nothing reaches the window without being composed and rounded, and checks every gap and every declared width at five box widths. Swept over 2,100 widths when it was written and exact at every one. For a share it does not, and the second test pins by how much rather than pretending otherwise: one or two steps between children that asked for the same fraction, 0.001 to 0.002 px. A position is the quantity that gets rounded so the row fills exactly and no two children leave a seam, and that is what costs it. Exact composition would shrink the spread, not remove it: five equal lengths cannot fill a row whose step count is not a multiple of five. Checked: fmt, clippy, 83 suite tests, 17 core unit tests. 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