Skip to content
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.

Plans for web renderer? #11

Open
nashley opened this issue Nov 21, 2021 · 3 comments
Open

Plans for web renderer? #11

nashley opened this issue Nov 21, 2021 · 3 comments

Comments

@nashley
Copy link

nashley commented Nov 21, 2021

Seeing as dodrio is now archived (and presumably unmaintained), what does the future of iced on the web look like?
Perhaps these crates are worth looking into if we don't want to maintain dodrio? Migrating to them may also improve performance, since they avoid using a VDOM.

@madmaxio
Copy link

After implemeting this, I'm also very interested in implementing optimized DOM updates similar style to Yew framework (update DOM partially instead of full page).
If someone is also interested in that work, please let me know.

@jkelleyrtp
Copy link

Dioxus is built off much of the same bones of Dodrio and supports a low-level node creation API in the same way dodrio did.

http://github.com/dioxusLabs/dioxus

Both Dodrio and Dioxus are extremely fast libraries.

@hecrj
Copy link
Member

hecrj commented Jan 9, 2022

As far as I can see, both sycamore and dominator rely on a persistent widget tree and use either a DSL or specific widget functionality to implement dynamic views without a VDOM.

These approaches are, at least for now, incompatible with iced because the Elm Architecture produces a different widget tree after every view.

Therefore, if we want to preserve the ergonomics of the current API (i.e. view logic is just Rust code), I believe a library with a VDOM will be necessary.

@hecrj hecrj transferred this issue from iced-rs/iced Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants