chore: Initialize scaffolding for dioxus cross platform

Author: thehanriver

src/app/.gitignore

@@ -0,0 +1,7 @@
+# Generated by Cargo
+# will have compiled files and executables
+/target
+.DS_Store
+
+# These are backup files generated by rustfmt
+**/*.rs.bk

src/app/Cargo.toml

@@ -0,0 +1,16 @@
+[workspace]
+resolver = "2"
+members = [
+    "ui",
+    "web",
+    "desktop",
+    "mobile",
+    "api",
+]
+
+[workspace.dependencies]
+dioxus = { version = "0.6.0" }
+
+# workspace
+ui = { path = "ui" }
+api = { path = "api" }

src/app/README.md

@@ -0,0 +1,72 @@
+# Development
+
+Your new workspace contains a member crate for each of the web, desktop and mobile platforms, a `ui` crate for shared components and a `api` crate for shared backend logic:
+
+```
+your_project/
+├─ web/
+│  ├─ ... # Web specific UI/logic
+├─ desktop/
+│  ├─ ... # Desktop specific UI/logic
+├─ mobile/
+│  ├─ ... # Mobile specific UI/logic
+├─ api/
+│  ├─ ... # All shared server logic
+├─ ui/
+│  ├─ ... # Component shared between multiple platforms
+```
+
+## Platform crates
+
+Each platform crate contains the entry point for the platform, and any assets, components and dependencies that are specific to that platform. For example, the desktop crate in the workspace looks something like this:
+
+```
+desktop/ # The desktop crate contains all platform specific UI, logic and dependencies for the desktop app
+├─ assets/ # Assets used by the desktop app - Any platform specific assets should go in this folder
+├─ src/
+│  ├─ main.rs # The entrypoint for the desktop app. It also defines the routes for the desktop platform
+│  ├─ views/ # The views each route will render in the desktop version of the app
+│  │  ├─ mod.rs # Defines the module for the views route and re-exports the components for each route
+│  │  ├─ blog.rs # The component that will render at the /blog/:id route
+│  │  ├─ home.rs # The component that will render at the / route
+├─ Cargo.toml # The desktop crate's Cargo.toml - This should include all desktop specific dependencies
+```
+
+When you start developing with the workspace setup each of the platform crates will look almost identical. The UI starts out exactly the same on all platforms. However, as you continue developing your application, this setup makes it easy to let the views for each platform change independently.
+
+## Shared UI crate
+
+The workspace contains a `ui` crate with components that are shared between multiple platforms. You should put any UI elements you want to use in multiple platforms in this crate. You can also put some shared client side logic in this crate, but be careful to not pull in platform specific dependencies. The `ui` crate starts out something like this:
+
+```
+ui/
+├─ src/
+│  ├─ lib.rs # The entrypoint for the ui crate
+│  ├─ hero.rs # The Hero component that will be used in every platform
+│  ├─ echo.rs # The shared echo component that communicates with the server
+│  ├─ navbar.rs # The Navbar component that will be used in the layout of every platform's router
+```
+
+## Shared backend logic
+
+The workspace contains a `api` crate with shared backend logic. This crate defines all of the shared server functions for all platforms. Server functions are async functions that expose a public API on the server. They can be called like a normal async function from the client. When you run `dx serve`, all of the server functions will be collected in the server build and hosted on a public API for the client to call. The `api` crate starts out something like this:
+
+```
+api/
+├─ src/
+│  ├─ lib.rs # Exports a server function that echos the input string
+```
+
+### Serving Your App
+
+Navigate to the platform crate of your choice:
+```bash
+cd web
+```
+
+and serve:
+
+```bash
+dx serve
+```
+

src/app/api/Cargo.toml

@@ -0,0 +1,7 @@
+[package]
+name = "api"
+version = "0.1.0"
+edition = "2021"
+
+[dependencies]
+dioxus = { workspace = true, features = ["fullstack"] }

src/app/api/README.md

@@ -0,0 +1,13 @@
+# API
+
+This crate contains all shared fullstack server functions. This is a great place to place any server-only logic you would like to expose in multiple platforms like a method that accesses your database or a method that sends an email.
+
+This crate will be built twice:
+1. Once for the server build with the `dioxus/server` feature enabled
+2. Once for the client build with the client feature disabled
+
+During the server build, the server functions will be collected and hosted on a public API for the client to call. During the client build, the server functions will be compiled into the client build.
+
+## Dependencies
+
+Most server dependencies (like sqlx and tokio) will not compile on client platforms like WASM. To avoid building server dependencies on the client, you should add platform specific dependencies under the `server` feature in the [Cargo.toml](../Cargo.toml) file. More details about managing server only dependencies can be found in the [Dioxus guide](https://dioxuslabs.com/learn/0.6/guides/fullstack/managing_dependencies#adding-server-only-dependencies).

src/app/api/src/lib.rs

@@ -0,0 +1,8 @@
+//! This crate contains all shared fullstack server functions.
+use dioxus::prelude::*;
+
+/// Echo the user input on the server.
+#[server(Echo)]
+pub async fn echo(input: String) -> Result<String, ServerFnError> {
+    Ok(input)
+}

src/app/clippy.toml

@@ -0,0 +1,8 @@
+await-holding-invalid-types = [
+  "generational_box::GenerationalRef",
+  { path = "generational_box::GenerationalRef", reason = "Reads should not be held over an await point. This will cause any writes to fail while the await is pending since the read borrow is still active." },
+  "generational_box::GenerationalRefMut",
+  { path = "generational_box::GenerationalRefMut", reason = "Write should not be held over an await point. This will cause any reads or writes to fail while the await is pending since the write borrow is still active." },
+  "dioxus_signals::Write",
+  { path = "dioxus_signals::Write", reason = "Write should not be held over an await point. This will cause any reads or writes to fail while the await is pending since the write borrow is still active." },
+]

src/app/desktop/Cargo.toml

@@ -0,0 +1,13 @@
+[package]
+name = "desktop"
+version = "0.1.0"
+edition = "2021"
+
+[dependencies]
+dioxus = { workspace = true, features = ["router"] }
+ui = { workspace = true }
+
+[features]
+default = []
+desktop = ["dioxus/desktop"]
+server = ["dioxus/server"]

src/app/desktop/README.md

@@ -0,0 +1,30 @@
+# Development
+
+The desktop crate defines the entrypoint for the desktop app along with any assets, components and dependencies that are specific to desktop builds. The desktop crate starts out something like this:
+
+```
+desktop/
+├─ assets/ # Assets used by the desktop app - Any platform specific assets should go in this folder
+├─ src/
+│  ├─ main.rs # The entrypoint for the desktop app.It also defines the routes for the desktop platform
+│  ├─ views/ # The views each route will render in the desktop version of the app
+│  │  ├─ mod.rs # Defines the module for the views route and re-exports the components for each route
+│  │  ├─ blog.rs # The component that will render at the /blog/:id route
+│  │  ├─ home.rs # The component that will render at the / route
+├─ Cargo.toml # The desktop crate's Cargo.toml - This should include all desktop specific dependencies
+```
+
+## Dependencies
+Since you have fullstack enabled, the desktop crate will be built two times:
+1. Once for the server build with the `server` feature enabled
+2. Once for the client build with the `desktop` feature enabled
+
+You should make all desktop specific dependencies optional and only enabled in the `desktop` feature. This will ensure that the server builds don't pull in desktop specific dependencies which cuts down on build times significantly.
+
+### Serving Your Desktop App
+
+You can start your desktop app with the following command:
+
+```bash
+dx serve
+```

src/app/desktop/assets/blog.css

@@ -0,0 +1,8 @@
+#blog {
+  margin-top: 50px;
+}
+
+#blog a {
+  color: #ffffff;
+  margin-top: 50px;
+}