Crates.io | dioxus |
lib.rs | dioxus |
version | 0.6.0-alpha.4 |
source | src |
created_at | 2021-01-20 17:05:08.008973 |
updated_at | 2024-11-01 23:35:41.614625 |
description | Portable, performant, and ergonomic framework for building cross-platform user interfaces in Rust |
homepage | https://dioxuslabs.com/learn/0.5/ |
repository | https://github.com/DioxusLabs/dioxus/ |
max_upload_size | |
id | 344480 |
size | 36,939 |
A concurrent, functional, virtual DOM for Rust
This overview provides a brief introduction to Dioxus. For a more in-depth guide, make sure to check out:
Dioxus makes it easy to quickly build complex user interfaces with Rust. Any Dioxus app can run in the web browser, as a desktop app, as a mobile app, or anywhere else provided you build the right renderer.
Dioxus is heavily inspired by React, supporting many of the same concepts:
If you know React, then you know Dioxus.
Dioxus is substantially more performant than many of the other Rust UI libraries (Yew/Percy) and is significantly more performant than React—roughly competitive with InfernoJS.
Remember: Dioxus is a library for declaring interactive user interfaces—it is not a dedicated renderer. Most 1st party renderers for Dioxus currently only support web technologies.
All Dioxus apps are built by composing functions that start with a capital letter and return an Element
.
To launch an app, we use the launch
method and use features in Cargo.toml
to specify which renderer we want to use. In the launch function, we pass the app's root Component
.
use dioxus::prelude::*;
fn main() {
dioxus::launch(App);
}
// The #[component] attribute streamlines component creation.
// It's not required, but highly recommended. It will lint incorrect component definitions and help you create props structs.
#[component]
fn App() -> Element {
rsx! { "hello world!" }
}
You can use the rsx!
macro to create elements with a jsx-like syntax.
Any element in rsx!
can have attributes, listeners, and children. For
consistency, we force all attributes and listeners to be listed before
children.
# use dioxus::prelude::*;
let value = "123";
rsx! {
div {
class: "my-class {value}", // <--- attribute
onclick: move |_| println!("clicked!"), // <--- listener
h1 { "hello world" } // <--- child
}
};
The rsx!
macro accepts attributes in "struct form". Any rust expression contained within curly braces that implements IntoDynNode
will be parsed as a child. We make two exceptions: both for
loops and if
statements are parsed where their body is parsed as a rsx nodes.
# use dioxus::prelude::*;
rsx! {
div {
for _ in 0..10 {
span { "hello world" }
}
}
};
Putting everything together, we can write a simple component that renders a list of elements:
# use dioxus::prelude::*;
#[component]
fn App() -> Element {
let name = "dave";
rsx! {
h1 { "Hello, {name}!" }
div { class: "my-class", id: "my-id",
for i in 0..5 {
div { "FizzBuzz: {i}" }
}
}
}
}
We can compose these function components to build a complex app. Each new component we design must take some Properties. For components with no explicit properties, we can omit the type altogether.
In Dioxus, all properties are memorized by default with Clone and PartialEq. For props you can't clone, simply wrap the fields in a ReadOnlySignal
and Dioxus will handle converting types for you.
# use dioxus::prelude::*;
# #[component] fn Header(title: String, color: String) -> Element { todo!() }
#[component]
fn App() -> Element {
rsx! {
Header {
title: "My App",
color: "red",
}
}
}
The #[component]
macro will help us automatically create a props struct for our component:
# use dioxus::prelude::*;
// The component macro turns the arguments for our function into named fields we can pass in to the component in rsx
#[component]
fn Header(title: String, color: String) -> Element {
rsx! {
div {
background_color: "{color}",
h1 { "{title}" }
}
}
}
You can read more about props in the reference.
While components are reusable forms of UI elements, hooks are reusable forms
of logic. Hooks provide a way of retrieving state from Dioxus' internal Scope
and using
it to render UI elements.
By convention, all hooks are functions that should start with use_
. We can
use hooks to define the state and modify it from within listeners.
# use dioxus::prelude::*;
#[component]
fn App() -> Element {
// The use signal hook runs once when the component is created and then returns the current value every run after the first
let name = use_signal(|| "world");
rsx! { "hello {name}!" }
}
Hooks are sensitive to how they are used. To use hooks, you must abide by the "rules of hooks":
In a sense, hooks let us add a field of state to our component without declaring an explicit state struct. However, this means we need to "load" the struct in the right order. If that order is wrong, then the hook will pick the wrong state and panic.
Dioxus includes many built-in hooks that you can use in your components. If those hooks don't fit your use case, you can also extend Dioxus with custom hooks.
Using components, rsx, and hooks, we can build a simple app.
use dioxus::prelude::*;
fn main() {
dioxus::launch(App);
}
#[component]
fn App() -> Element {
let mut count = use_signal(|| 0);
rsx! {
div { "Count: {count}" }
button { onclick: move |_| count += 1, "Increment" }
button { onclick: move |_| count -= 1, "Decrement" }
}
}
This overview doesn't cover everything. Make sure to check out the tutorial and reference on the official website for more details.
Beyond this overview, Dioxus supports:
Build cool things ✌️