[DO NOT MERGE] Editor GUI: Experiments with Yew #2101
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevin-legion
force-pushed
the
editor-experiments-with-yew
branch
from
afdb5ea to
527c8f7
Compare
kevin-legion
force-pushed
the
editor-experiments-with-yew
branch
from
527c8f7 to
f462f2b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Experimenting with https://yew.rs/
So far the experience is rather smooth, though some questions start arising when dealing with mutable states for instance.
I could implement a basic resource tree and some auth to make it work.
There is also a Sycamore feature (not on par with the yew version) to compare the two frameworks (must be changed in the
Cargo.tomlfile manually if the app is ran using Trunk).