mirror of https://github.com/emilk/egui.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
follower
95ff7ec000
|
3 years ago | |
|---|---|---|
| .. | ||
| src | 3 years ago | |
| CHANGELOG.md | 3 years ago | |
| Cargo.toml | 3 years ago | |
| README.md | 3 years ago | |
README.md
egui_web
This crates allows you to compile GUI code written with egui to WASM to run on a web page.
Run the web demo to try it now.
Check out eframe_template for an example of how to set it up.
Downsides with using egui on the web
egui_web uses WebGL (via glow) and WASM, and almost nothing else from the web tech stack. This has some benefits, but also produces some challenges and serious downsides.
- Rendering: Getting pixel-perfect rendering right on the web is very difficult.
- Search: you cannot search an egui web page like you would a normal web page.
- Bringing up an on-screen keyboard on mobile: there is no JS function to do this, so
egui_webfakes it by adding some invisible DOM elements. It doesn't always work. - Mobile text editing is not as good as for a normal web app.
- Accessibility: There is an experimental screen reader for
egui_web, but it has to be enabled explicitly. There is no JS function to ask "Does the user want a screen reader?" (and there should probably not be such a function, due to user tracking/integrity concerns). - No integration with browser settings for colors and fonts.
- On Linux and Mac, Firefox will copy the WebGL render target from GPU, to CPU and then back again (https://bugzilla.mozilla.org/show_bug.cgi?id=1010527#c0), slowing down egui.
In many ways, egui_web is trying to make the browser do something it wasn't designed to do (though there are many things browser vendors could do to improve how well libraries like egui work).
The suggested use for egui_web are for web apps where performance and responsiveness are more important than accessibility and mobile text editing.