irisandClaude Opus 5
0a5eb2d984
Two majors, and the renderer is under everything else that is left to extract, so it goes before the slices that would otherwise be written twice. `image` 0.25.6 -> 0.25.10 rides along; `winit` stays on 0.30.12, since 0.31 is only a prerelease. What the API asked for: - An instance now takes the display it will present on, and GLES on Wayland needs it -- so the window the surface is made from is handed over with it. - `get_current_texture` returns a `CurrentSurfaceTexture` rather than a `Result`, which replaces an `unwrap` that would have panicked on a resize or an occluded window: reconfigure when the surface is outdated, lost or suboptimal, and skip the frame when there is nothing to draw into. - Presenting moved to the queue, after `pre_present_notify` as before. - Bind group layouts and vertex buffer layouts are sparse now, so a pipeline states `Some(layout)` per slot. Verified with the three render checks and `tests/draw_cost.rs`: identical pictures, and 33.6/167/587/2855 us per frame at 8/64/256/1024 layers against 33.3/161/588/2903 on wgpu 28. Co-Authored-By: Claude Opus 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.
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