iris
a08f61a80c
Three defects, two of them invisible to every case I had run. An image alone in a layer failed validation. The texture pipeline never bound group 1, and every earlier case happened to have a rect in the same layer, which left one bound from the primitive draw -- so the bug was hidden by the tests passing. A `min_binding_size: None` binding takes its minimum from the first pipeline built against that bind group layout, so one shared group 1 layout held every primitive to the largest. Rect and glyph coexisted only because glyph is the bigger of the two; the texture slots, at four bytes, did not. Each primitive now gets its own layout with its entry size stated, which is also why `PrimitiveRegistry` records the stride. Because the pipeline layouts now differ per primitive, a pipeline change drops the bound groups, so group 2 moves after `set_pipeline`. An empty list still built a bind group over a buffer too small for one entry, which the stated minimum would now reject. It gets no bind group, and nothing draws it. Also from the read-through: `UiRenderNode` kept a `Device` beside the one `update` is handed, `PrimitiveRegistry::default` registered inside an `assert_eq!`, and `mask_idx` was an unqualified integer varying where `idx` beside it was `flat`.
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