iris
b3d3da5dab
Interleaving textures with primitives was solving a problem that does not exist: within a layer, order is already undefined because freeing an instance swap-removes it, and layering is what layers are for. So the run batching is gone. A layer is now `LayerDraws`: a `Primitives` and a texture `InstanceList` side by side, with `updated` covering both. `Primitives` holds only primitives again -- its instance list plus the group-1 data those instances read -- and `InstanceList` is the shared push/free/apply_free the two lists have in common rather than a second copy of it. `PrimitiveHandle` names which list with `InstanceKind`, and `PrimitiveChange` carries the same, since the two index independently. The handle no longer carries a group-1 index at all: a primitive instance already records where its entry is. The renderer gives each layer a second instance buffer and draws its textures one at a time after the instanced draw, each binding its own group 2. Review fixes alongside: `GlyphAtlas::allocate` returns the `PageUpload` it reserved instead of a bare tuple; a page or image region uploads through a new `write_region`, which passes the row stride to `write_texture` rather than copying the rectangle out first. Verified by replaying taps into the `tabs` example: three images added and one deleted leaves two drawn with two live texture slots, and the masked text-edit tab still clips, with the images freed on tab switch.
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