iris-aiandClaude Opus 5.5
487da537d3
Since 58a86fa the magnifier is a fixed layer of the overlay host beside
the handles: placed once, laid out while hidden, drawing nothing until a
handle is held, so showing it only moves it. The tree test already
expected the hidden handles that way; it now expects the magnifier too.
Co-Authored-By: Claude Opus 5.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.
view, text, overlay and task also run on Android, and jni only there: cargo run -p cargo-iris -- iris run --example view builds the APK, installs it with the
adb on PATH (on the device ANDROID_SERIAL names, when more than one is
attached) and starts it (apk instead of run only builds it). An app of your
own is a library crate depending on iris with its android feature and calling
iris::android_main!, packaged with --manifest-path or --package in place
of --example. It needs ANDROID_HOME, cargo-ndk and a JDK; cargo run -p cargo-iris -- iris help says more.
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 (+ 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