Vuetify - Material Component Framework for VueJS 2
vuetifyjs.com
Vuetify - Material Component Framework for VueJS 2
1–10 of 39 posts
Re: Vuetify - Material Component Framework for VueJS 2
#2This page had an ugly flicker as the page loaded, with the unstyled left-side navigation displayed before the CSS rules were loaded.
It's not a huge deal, and honestly I have built some sites like that as well, but when you're pitching front-end frameworks, stuff like that matters. I don't want anyone to think that that kind of flicker is inherent to Vue.
Re: Vuetify - Material Component Framework for VueJS 2
#3Looks cool, unfortunately like many of these UI frameworks, the more advanced functionality has been left out so far. Compared to http://semantic-ui.com/modules/dropdown.html which has searching and filtering etc.
Hard to move to anything this unless it's the most basic of applications.
Re: Vuetify - Material Component Framework for VueJS 2
#4While this is useful to have, I would argue that layout should be left to css frameworks (material css in this case) and components only used for functional parts of the app.
No one is forcing us to make everything a component. What would be a benefit of having a footer or header a component for example?
Re: Vuetify - Material Component Framework for VueJS 2
#5what's the big deal with "material"? Looks ugly as sin. I just don't get it.
Re: Vuetify - Material Component Framework for VueJS 2
#6I disabled the use of custom fonts and have to say that the material style of Google makes websites unreadable. Just like this framework does.
This is because the span inside an icon has a huge font size. And they use ligatures for characters (so I'm seeing the huge ligatures).
Why would someone choose ligatures over CSS classes?
Edit: I was thinking about problems with screen readers and so on. A CSS class is just styling, but what Google uses is content.
Re: Vuetify - Material Component Framework for VueJS 2
#7This page had an ugly flicker as the page loaded, with the unstyled left-side navigation displayed before the CSS rules were loaded. It's not a huge deal, and honestly I have built some sites like that as well, but when you're pitching front-end frameworks, stuff like that matters. I don't want anyone to think that that kind of flicker is inherent to Vue.
What's the recommended way to resolve that these days? Render your primary CSS bundle in head?
Re: Vuetify - Material Component Framework for VueJS 2
#8what's the big deal with "material"? Looks ugly as sin. I just don't get it.
Personally, I like material design, as do many others.
If done right, it makes the interface feel fluid and alive rather than just click and appear.
Whether or not you like that is personal preference.
Re: Vuetify - Material Component Framework for VueJS 2
#9what's the big deal with "material"? Looks ugly as sin. I just don't get it.
I don't think it looks ugly, but I'm also not overly enamoured of it. But it's free, available, coherent and familiar to users.
Re: Vuetify - Material Component Framework for VueJS 2
#10This page had an ugly flicker as the page loaded, with the unstyled left-side navigation displayed before the CSS rules were loaded. It's not a huge deal, and honestly I have built some sites like that as well, but when you're pitching front-end frameworks, stuff like that matters. I don't want anyone to think that that kind of flicker is inherent to Vue.
What's the recommended way to resolve that these days? Render your primary CSS bundle in head?
I believe best practice is to sort out which of your CSS is needed to render above-the-fold content, separate that out into a smaller file, and serve that higher in the page or even inline it. The rest of the CSS can be served at the bottom, with the JavaScript.
If anyone has a better plan, I'm all ears!