irisandClaude Fable 5.1
3b80a88f3b
Threads DisplayMetrics.density (read once in new_peer, via the Context android-view already hands the JNI entry point) through AndroidUiState as content_scale, and divides by it everywhere a raw device-pixel number used to reach layout unscaled: AndroidRenderer::size()/resize()/new() now report logical (physical / density) dimensions to UiRenderNode and to UiRenderState's own root-layout size, and on_touch_event divides the incoming MotionEvent coordinates the same way, so touch and layout agree on units again. This is the fix for RUST.md's P0 box, "text is far too small" -- a font_size: 16.0 was 16 raw device pixels on a ~3x-density phone, identical to the desktop fix in the previous commit. Installs Device::on_uncaptured_error on the Android device (wgpu's default handler is an unconditional panic outside UiRenderNode::new's own error scopes) into a new iris_core::WgpuErrorLog, and adds AndroidRenderer::diagnostics_report() combining adapter identity, font resolution, atlas view count and the error log into one string for a future Diagnostics screen. render() now logs a one-line diagnostic (masks/moves resized, atlas pages grown, image bind-group creates, wgpu error count) for the first 10 frames after each surface_changed -- the window RUST.md's P0 box says the glyph-wipe-on-first-touch happens in. Adds AndroidAppState::on_insets_changed(rsc, LogicalInsets), called from render() exactly when AndroidUiState::insets() changes (once at startup for the status bar, again on rotation/IME) -- nothing previously read insets().top at all, which is why RUST.md's P0 box found the bench screen's top buttons sitting under the status bar. Co-Authored-By: Claude Fable 5.1 <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