lewp-rs VS dioxus

Thanks for sharing and congrats, this looks pretty nice! I am looking for quite a while now for a crate like yours to integrate (and replace lewp-html) into https://github.com/emirror-de/lewp-rs

Have a look at https://github.com/emirror-de/lewp-rs if this sounds interesting.

not exactly what you are looking for, but have a look at https://github.com/emirror-de/lewp-rs

If you really plan to create one that does have a admin frontend built in, I would suggest you to choose https://github.com/emirror-de/lewp-rs for this task to not get stuck in the templating jungle later on. ;)

See CHANGELOG.md and Repository

There are currently examples in the repository, and a minimal one can be found at the docs page.

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI