iris
7b318e3271
`write_texture` differed from `write` by one argument, which is what the generic parameter was already for, so textures register as a primitive with a `TexturePrimitive` holding the slot. `write_texture`, `InstanceKind` and the layer's separate texture list are gone; `DrawLayers` is back to `write` and `free`, with the kind carried in `PrimitiveInst` as it carries everything else. What differs between a texture and a rect is only what it samples, so that is what registration says: `PrimitiveTexture::Atlas` binds the shared atlas once for the layer, `PerInstance` binds the texture its own data names and draws one instance at a time. One loop over a layer's lists, one match on that. `Pod` is back to being a supertrait of `Primitive` rather than the bound itself. The guarantee is that a `PrimitiveKind<P>` is only minted by `register::<P>` and `write` takes the kind and the value together, so a primitive always has a list of its own to go in and the write does not check anything: a list takes its stride from the type it was made for instead of inferring it from the first write and asserting on the rest. Also from reviewing this: a layer's lists and their buffers are created only when that layer draws that primitive, so a primitive nobody uses no longer costs two buffers in every layer -- which matters more now the set is open-ended. `ListBuffers::update` takes the two things it uses rather than the whole pipeline. Verified again over all five cases: an image alone in a layer, three images added and one deleted, the masked text-edit tab, the text-layout tab and the default tab.
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