irisandClaude Opus 5
01a9b8633d
Nothing seeds the registry any more, so a kind's id is decided by the first draw and no order within a layer can be relied on even by accident. A ui that draws no images now pays for no image pipeline, and a layer's list vector only reaches the highest kind that layer draws. The atlas and the sampler are still bound for every draw, but are declared by the two shaders that read them rather than by the prelude, which is now only what every primitive uses. `TexturePrimitive` gets a `From<&TextureHandle>`; `Painter::texture_at` stays because the share of the handle is what keeps the slot from being freed while it is drawn, which a `Pod` primitive cannot hold. Checked on the headless rig that the layers carry the ordering rather than the ids: with a bare text drawn first, so glyph registers before rect, a stacked label still draws over its background. Also re-ran an image alone in a layer, now the only primitive a ui registers, and a four-layer atlas. 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