iris-ai
38b3a81053
`size_hint` resolves a child's hint against the asking widget's frame and pins that frame, so a later draw cannot reuse a resolution made against a different one. It asked the *resolved* hint whether it still had a fraction, which is false whenever the frame is itself pixels -- a slot of a row, or the box a stack's sizing child decided -- and the pin was dropped there. Ask the declared hint, which is what made this draw depend on the frame, and what `ruled` in `render_state` already asks for a rule. No generated tree distinguishes the two: the fuzzer grows no `rel` rules, and a frame that changes almost always changes a box the other pins catch. Kept for the reason the `frame_len` pin beside it is kept -- "these two invalidations always coincide" is an assumption nothing states.
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