From 222f5347130ca6130f7c88af77ddff73a32fb2de Mon Sep 17 00:00:00 2001 From: Emil Ernerfeldt Date: Sun, 18 Oct 2020 15:42:29 +0200 Subject: [PATCH] Add links to wgpu and winit integrations --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index c534e6cf..850753c6 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,11 @@ The same code can be compiled to a native app or a web app. ### 3rd party +* [`wgpu`](https://crates.io/crates/wgpu) WebGPU API wrapper: + * [egui_wgpu_backend](https://crates.io/crates/egui_wgpu_backend) with [example code](https://github.com/hasenbanck/egui_example) + * Alternative: [egui_winit_wgpu](https://github.com/Gonkalbell/egui_winit_wgpu) (not available to crates.io) * [emigui-miniquad](https://github.com/not-fl3/emigui-miniquad): backend for [Miniquad](https://github.com/not-fl3/miniquad). [Web demo](https://not-fl3.github.io/miniquad-samples/emigui.html) and [demo source](https://github.com/not-fl3/good-web-game/blob/master/examples/emigui.rs). +* [egui_winit_platform](https://github.com/hasenbanck/egui_winit_platform) provides bindings between [winit](https://crates.io/crates/winit) and Egui. It only provides the first half of an Egui integration (IO). Painting can be done with e.g. [egui_wgpu_backend](https://crates.io/crates/egui_wgpu_backend). ### Writing your own Egui integration