RDX

Rhai markDown egui eXtensions (RDX)

Rust Developer eXperience (RDX)

Real gooD eXperiment

• 🦀 Pure Rust (no JavaScript)
• 🥇 All Platforms (Web, Desktop)
• 🦕 Extensible - Bring your own eXtensions, or run other's privately
• 🦺 Safe - FULL STACK code safely in a WebAssembly
• 🚀 Fast - WebAssembly is fast, and Rhai is Fast
• 🎨 Beautiful - eGUI is beautiful, and Rhai is simple
• 📦 Bundled - Everything you need in one package
• 🌐 Web - Deploy to the web with Trunk
• 📱 Mobile - Coming soon

Why?

Because we need a way to encapsulate full stack apps into WebAssembly, so they can be run in a trustless way.

What is RDX?

RDX is a combination of:

1. Rhai (for control flow logic) and
2. html subset (for User Interface).

In RDX, the html gets parsed then rendered into egui user interface components.

Using HTML gives RDX authors access to great crates such as html for type safety, and render for composable html components.

For example, It looks something like this:

// call the system function `render` on the template with the ctx from scope

// rhai script controls the flow of logic on what to show

if !is_def_var("count") || count == "0" {

    // the render function returns a string of RDX
    // render is provided by the rhai scope by default
    render(ctx, `



            <button data-on-click="increment()">Increment</button>
            <button data-on-click="decrement()">Decrement</button>
            <label>Click to Start counting!</label>



    `)

} else {

    // alternate RDX if count is not 0 
    // the {{count}} is a variable stored in rhai scope
    render(ctx, `



            <button data-on-click="increment()">Increment</button>
            <button data-on-click="decrement()">Decrement</button>
            <label>Count is: {{count}}</label>



    `)

}

The increment() and decrement() functions are provided by WebAssembly exported functions. These functions emit a count variable that is stored in the Rhai scope, then displayed back in the gui.

Bundle RDX scripts into WebAssembly then run them as eframe components, natively or in the browser.

eframe template experiment to see if I can parse an RDX format into eframe.

The goal is for this to be the simplest way to get started writing a eGUI app in Rust.

You can compile your app natively or for the web, and share it using Github Pages.

Getting started

Build a component in either pure Rhai or Rhai + Rust compiled to WASM.

1. Get an eframe environment set up using eframe_template so you can test your app while you develop.
2. Develop a Wasm Component using cargo-component. Create it using cargo component new --lib <your_plugin_name>. I like to add a rustfmt.toml file with ignore = ["src/bindings.rs"] becaus the generated bindings fail the format tests.

Testing locally

Make sure you have just installed and are using the latest version of stable rust by running rustup update.

just run

Dependencies

On Linux you may 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

Web Locally

You can compile your app to WASM and publish it as a web page.

We use Trunk to build for web target. 1. Install the required target with rustup target add wasm32-unknown-unknown. 2. Install Trunk with cargo install --locked trunk. 3. Run trunk serve to build and serve on http://127.0.0.1:8080. Trunk will rebuild automatically if you edit the project. 4. Open http://127.0.0.1:8080/index.html#dev in a browser. See the warning below.

assets/sw.js script 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 #dev to index.html will skip this caching, allowing us to load the latest builds during development.

Web Deploy

1. Just run trunk build --release.
2. It will generate a dist directory as a "static html" website
3. Upload the dist directory to any of the numerous free hosting websites including GitHub Pages.
4. 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-pages branch and / (root).

   If gh-pages is not available in Source, just create and push a branch called gh-pages and it should be available.

   If you renamed the main branch to something else (say you re-initialized the repository with master as the initial branch), be sure to edit the github workflows .github/workflows/pages.yml file to reflect the change yml on: push: branches: - <branch name>

You can test the template app at https://emilk.github.io/eframe_template/.

Updating egui

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.