6 ms·
Anything Material is utter crap, Vuetify is not the exception. Minimal CSS frameworks like Picnic CSS are the only way to go. You do not need components and CSS
by lowry 8y ago
Anything Material is utter crap, Vuetify is not the exception. Minimal CSS frameworks like Picnic CSS are the only way to go. You do not need components and CSS classes to have a decent design. Quite to the contrary.
- Tade0 8y ago> Minimal CSS frameworks like Picnic CSS are the only way to go. They are not if you need the components do something aside from looking a specific way. For the project I'm in I need a: -Range slider -Date picker -Autocomplete select -Data table with pagination Obviously none of the "minimal CSS frameworks" have any of those because it's impossible.
- nogridbag 8y agoDid you consider using individual components instead of adopting an entire component framework? Interestingly, I just picked a random Vuetify component from your list, Autocomplete, and the demo is broken in Chrome (cannot type or click trigger - only keyboard down arrow works): https://vuetifyjs.com/en/components/autocompletes https://vuetifyjs.com/en/components/autocompletes
- Tade0 8y ago> Did you consider using individual components instead of adopting an entire component framework? Yes and it's a headache. Mostly because they have separate docs and CSS. The other day I had to change the appearance of all the labels - with a single framework I could just add a simple, single selector(because Vuetify as opposed to Angular Material uses BEM) and be done with it. I may have to use an individual component for uploading since it hasn't landed in Vuetify yet: https://github.com/vuetifyjs/vuetify/issues/238 https://github.com/vuetifyjs/vuetify/issues/238 > (cannot type or click trigger - only keyboard down arrow works): Control question: did you click the icon on the left or on the right?
- nogridbag 8y ago> Control question: did you click the icon on the left or on the right? This is the first time I've ever been stumped by a simple read-only field. I think my confusion was due to the floating label animation on focus which I would expect only if the field was editable. You typically don't encounter read-only fields in mobile apps but they're common place in enterprise desktop apps. Regardless, there is a bug since clicking the down arrow on the keyboard still allows me to select a state even though the field is read-only.