iris-ai
429a4f1330
StrongWidget has no Clone on purpose, so the RefCounter in it never counted anything: the count stayed at zero, RefCounter::drop always answered true, and StrongWidget::refs had no caller -- while every widget made paid a heap allocation for an Arc<AtomicU32> and every one created or dropped paid two atomic read-modify-writes. The handle is the id, the sender and the type now, and Drop sends. It is 32 bytes rather than 40, and 40 rather than 48 for a dyn one. RefCounter stays for TextureHandle, which does clone -- several widgets showing one picture share its slot -- and is trimmed to what that needs: quiet_clone and refs had no callers at all, and new was Default spelt out. Bryan asked for this in #19 rather than in the review of the code written before the gate, where the fourteenth sweep had left it.
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