For more context:
Let's be honest, I didn't catch up to 5.0 alpha and beta versions, and don't have much time to do it these days, so this decision is also easier because of that xD
tl;dr: material-ui is rebranding as "mui", which involves:
- Renaming many things, which can be a PITA for a haxe version supporting both <= 4 and >= 5
- Keeping material design as one of the possible design systems available
- (TODO: more? don't have much time for that atm)
What could be done, though, is create a separate "mui" haxe lib (by forking?), do the rebrand and updates there, and keep this library for material-ui (so <= 4)
Reactions are currently unavailable
For more context:
Let's be honest, I didn't catch up to 5.0 alpha and beta versions, and don't have much time to do it these days, so this decision is also easier because of that xD
tl;dr: material-ui is rebranding as "mui", which involves:
What could be done, though, is create a separate "mui" haxe lib (by forking?), do the rebrand and updates there, and keep this library for material-ui (so <= 4)