You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a lot of blabbering I can contribute to the styling community that wouldn't fit very well in github issues, so I'd love to spend time in Discussions if you can enable it for this repo - or a discord.
But... for now my biggest thoughts are:
Given stylist-rs supports "runtime" styling, what do you think about the idea of making a dev tool picker that lets you select a component just like in chromium or webkit devtools and interactively change css at runtime? That way the development experience is lickity-split and one step closer to WYSIWYG! You would of course disable this picker in production once you are satisfied with the styling achieved. Or does this already exist for WASM in another form?
The text was updated successfully, but these errors were encountered:
I didn't think in implement something like this (it is not part of the Road map), the idea looks good however I would recommend to wait until css is migrated to stylist-rs then in that case you can create that module but it should be something separate from this framework, there is a branch in order to get rid of css https://github.com/dancespiele/yew_styles/tree/get-rid-of-css
I have a lot of blabbering I can contribute to the styling community that wouldn't fit very well in github issues, so I'd love to spend time in Discussions if you can enable it for this repo - or a discord.
But... for now my biggest thoughts are:
Given stylist-rs supports "runtime" styling, what do you think about the idea of making a dev tool
picker
that lets you select a component just like in chromium or webkit devtools and interactively change css at runtime? That way the development experience is lickity-split and one step closer to WYSIWYG! You would of course disable this picker in production once you are satisfied with the styling achieved. Or does this already exist for WASM in another form?The text was updated successfully, but these errors were encountered: