-
-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI kit #1483
Comments
Should this have a "custom" name like taffy and freya, or just something like "dioxus-kit"? I prefer the "custom" route, unless this is going to be a core part of Dioxus, but I don't see it that way. |
So far, anything that can be used outside of Dioxus has a custom name:
Forms could be progressively enhanced using server functions |
"Kit" might not be ideal, but my issue with "UI" is that it's too ambiguous and "components" is perhaps too specific. This won't contain just components. |
I'm on the fence about one of the potential features I mentioned, that being custom types for commonly used HTML/CSS types. I think this would be a very nice feature, but I'm wondering if it shouldn't be in If this UI library has an enum like |
This would be awesome to incorporate with #1443 to create a global settings page! |
https://github.com/matthunz/dioxus-material is a component library for dioxus based on material UI |
This is being implemented in https://github.com/DioxusLabs/components |
Specific Demand
A components and utilities kit for Dioxus. Some specific feature ideas:
href
being a string, it would be aLink
, which would be constructed with aparse_str_to_link!()
macro. This would enable compile-time validation of values for literals. Another example might be CSS units. So,"10px"
turns intoAbsoluteUnit::PX(10)
. This way we could implement operators and other goodies.Implement Suggestion
I think for styling, we could use Bulma. It's purely-CSS, simple, extendable with Sass, and looks good.
The text was updated successfully, but these errors were encountered: