On desktop this is a full multinode, in the browser it's a multinode client.
See Releases to download pre-built binaries for your system.
todo!()todo!()Make sure you are using the latest version of stable rust by running rustup update.
cargo run --release
On Linux you need to first run:
sudo apt-get install libxcb-render0-dev libxcb-shape0-dev libxcb-xfixes0-dev libxkbcommon-dev libssl-dev
On Fedora Rawhide you need to run:
dnf install clang clang-devel clang-tools-extra libxkbcommon-devel pkg-config openssl-devel libxcb-devel gtk3-devel atk fontconfig-devel
You can compile your app to WASM and publish it as a web page.
We use Trunk to build for web target.
- Install the required target with
rustup target add wasm32-unknown-unknown. - Install Trunk with
cargo install --locked trunk. - Run
trunk serveto build and serve onhttp://127.0.0.1:8080. Trunk will rebuild automatically if you edit the project. - Open
http://127.0.0.1:8080/index.html#devin a browser. See the warning below.
assets/sw.jsscript will try to cache our app, and loads the cached version when it cannot connect to server allowing your app to work offline (like PWA). appending#devtoindex.htmlwill skip this caching, allowing us to load the latest builds during development.
- Just run
trunk build --release. - It will generate a
distdirectory as a "static html" website - Upload the
distdirectory to any of the numerous free hosting websites including GitHub Pages. - we already provide a workflow that auto-deploys our app to GitHub pages if you enable it.
To enable Github Pages, you need to go to Repository -> Settings -> Pages -> Source -> set to
gh-pagesbranch and/(root).If
gh-pagesis not available inSource, just create and push a branch calledgh-pagesand it should be available.If you renamed the
mainbranch to something else (say you re-initialized the repository withmasteras the initial branch), be sure to edit the github workflows.github/workflows/pages.ymlfile to reflect the changeon: push: branches: - <branch name>
You can test the template app at https://emilk.github.io/eframe_template/.
As of 2023, egui is in active development with frequent releases with breaking changes. eframe_template will be updated in lock-step to always use the latest version of egui.
When updating egui and eframe it is recommended you do so one version at the time, and read about the changes in the egui changelog and eframe changelog.