DioxusLabs / DioxusLabs/dioxus

Raspbery Pi cross-compilation support

Open
#4,281 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
39.1k
Forks
1.9k
Avg merge
4d 10h
Merged PRs (30d)
4

Description

Hi!
I'm planning to use dioxus for creating "native" application for Raspbery Pi 4 (latest raspbery official OS).
Currently i have a console application without any GUI interface. I am using` cross-rs` for cross-compilation and it works great (just call `cross build` instead off `cargo build`).
This is my first time trying to work with the "web-like apps", so I have a few (noob's) questions:

1) Is this even possible to run dioxus app on R-Pi in "embedded webview"? that looks like a regular GUI app (without a "address string" and other browser buttons)? Is it possible to run it fullscreen?
2) Is it possible to compile dioxus app via cross-rs?
3) Will it compile to native aarch64-unknown-linux-gnu code or wasm32-unknown-unknown?
4) I have a heavy rust and linked-with-FFI native C code that communicates with the OS and low-level busses (i2s, UART, etc...). I want to communicate between GUI and this code. how to do it? Do i need a "web server" or something like this? Do i need to "re-render" some DOM-nodes every time then value of my low-level-variable has changed?
5) As an example: Is it possible to do some "real-time volume-meter" (10 fps and 100ms max delay between audio-signal and GUI update)?
5) In general, is it a good idea to use dioxus in my case? Or it looks weird and i should better use "low-level" GUI-s like "iced"?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.