tauri-apps
example: Add GPUI example
cargo run --example gpui
- Ref https://github.com/zed-industries/zed/pull/24545 wait this PR to support run on Window.
Package Changes Through 59012f3b8dcd4703f05ff8d76d522d42ebc0135b
There are 1 changes which include wry with minor
Planned Package Versions
The following package releases are the planned based on the context of changes in this pull request.
| package | current | next |
|---|---|---|
| wry | 0.48.1 | 0.49.0 |
Add another change file through the GitHub UI by following this link.
Read about change files or the docs at github.com/jbolda/covector
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
GPUI is still in early development and I don't think we should have a dedicated example for it, not yet at least
I understand why this PR is closed but had a follow-on question: would it be possible to go the other way round and render some gpui-driven UI into a tao/wry/tauri-provided native window (something with HasWindowHandle)?
I imagine it might be useful to some Tauri apps to avoid the whole webview abstraction for some perf-sensitive UI work here and there.
In theory yes but as far as i can tell this would require changes in gpui since it currently seems to hide all the windowing internally.
In the meantime one could probably fork it so that it uses tao and then create something like https://github.com/tauri-apps/tauri-egui (i have no idea how much work that would be)
Oooh, thanks for pointing me there! tao ↔ egui seems like it could work for my use-case, but that implementation seems old. Let me try to shake off the cobwebs a little 🫡
oh yeah, that's pretty old by now and essentially unmaintained. it would be very much appreciated if someone could pick it up again (the prior maintainers don't work on tauri anymore) but it may be easier to wait until we switch back to winit (or have a fresh fork) but who knows how long that'll take. Anyway, good luck 🙏
Got a crude version working! https://github.com/clearlysid/egui-tao
Still thinking about what a good way to make a "low-overhead" (ie.. doesn't involve maintaining multiple forks) integration is.
until we switch back to winit
Are there plans for this in-place already? Given how widely adopted winit is in the rest of the Rust ecosystem, I think this will simplify a lot of things. Especially if it now supports all the things that Tauri needs, which it may not have before.
Either ways, let's tune off of this thread since we're wayy off-topic and continue on Discord/elsewhere. Cheers!