Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vuetify - Material Component Framework for VueJS 2

vuetifyjs.com

Post reply on HN
Print view View original

11–20 of 39 posts

Re: Vuetify - Material Component Framework for VueJS 2

#11

Post by zeroskillz »

samcheng wrote: post #2

This 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.

It has to do with lazily loading assets, but not actually having the critical styles inlined. It's something that I had before launch, but ultimately did not like how it was done so I removed it. It's also not a product of the framework, just where I choose to load assets in the docs for pagespeed. They can easily be moved into the head and all of that is resolved.

Re: Vuetify - Material Component Framework for VueJS 2

#12

Post by zeroskillz »

simooooo wrote: post #3

Looks 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.

Completely agree, it is one of the most important things I'm working on right now, fleshing out each components API with additional functionality.

Re: Vuetify - Material Component Framework for VueJS 2

#13

Post by zeroskillz »

desireco42 wrote: post #4

While 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?

Simply for semantics, as they are done with functional components. As far as layouts, you do not have to use them, they are just an added feature to help the prototyping and build phase.

Re: Vuetify - Material Component Framework for VueJS 2

#14

Post by zeroskillz »

samcheng wrote: post #10
bpicolo wrote: post #7

Earlier quoted context omitted.

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!

That is correct. It can just be a pain to do intuitively as all sites are different. Vuetify Documentation runs off of the vuetify webpack-ssr vue cli template which I recently removed that functionality.

Re: Vuetify - Material Component Framework for VueJS 2

#16

Post by tzury »

simooooo wrote: post #3

Looks 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.

thanks for bringing semantic-ui. heaven't heard of it till now, and love what I see very much!

Re: Vuetify - Material Component Framework for VueJS 2

#17

Post by [deleted] »

pasta wrote: post #6

I 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 s…

[deleted]

Re: Vuetify - Material Component Framework for VueJS 2

#18

Post by Kiro »

pasta wrote: post #6

I 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 s…

> Why would someone choose ligatures over CSS classes?

That's a really good question because I presume they did it for a reason. Why else go through the hassle?

Re: Vuetify - Material Component Framework for VueJS 2

#19

Post by Kiro »

desireco42 wrote: post #4

While 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?

If you don't want to make many modifications I prefer having it like this, with each component being completely self-contained with no global CSS dependencies.
Post reply on HN