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

21–30 of 39 posts

Re: Vuetify - Material Component Framework for VueJS 2

#21

Post by johndoe4589 »

Could actually see a "flash of unstyled content" on my desktop PC. No biggie, but that makes me think about just how overkill I want to go with VueJS. (edit: wondering also if they precompiled those templates with vue-loader?)

I'm super excited about VueJS, and start using it on my site. But when I see a component for a button, you know, just a regular styled link... I wonder if there is really a purpose to that? How do you strike the right balance of what should be a component, and what can be handled as plain html with perhaps some backend helpers to output in view templates?

Also just as a general criticism I think it's not welcoming for a Vue component framework to have such a strong opiniated design built in. It would be much nicer to have the theme something relatively easy to change. It may be don't get me wrong... but my first impression is "Can I even use this? Without changing tons of style rules?".

For this I think the relatively simple design of Bootstrap is a strength. Give me the same components with a barebones design, with cheap flat buttons with some rounded corners for "pzaz" and then I feel much more confident about bringing that into an existing project. Even if I started a site today, I don't want to use Material design.

Re: Vuetify - Material Component Framework for VueJS 2

#22

Post by colordrops »

johndoe4589 wrote: post #21

Could actually see a "flash of unstyled content" on my desktop PC. No biggie, but that makes me think about just how overkill I want to go with VueJS. (edit: wondering also if they precompiled those templates with vue-loader?) I'm super excited about VueJS, and start using it on my site. But when I see a component for a button , you know, just a regular styled link... I wonder if there is really a purpose to that? Ho…

> But when I see a component for a button, you know, just a regular styled link... I wonder if there is really a purpose to that?

Why shouldn't there be a component for a button? Buttons can have endless styles and animations. They have a myriad of behaviors. For instance, there are differences in how they could respond to touches versus mouse clicks. They have a standard interface. With a component, you could keep them consistent across an application and share them across applications.

Re: Vuetify - Material Component Framework for VueJS 2

#23

Post by onurozkan »

baobrain wrote: post #8
retube wrote: post #5

what'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.

completely agree.

https://angular.io/docs/ts/latest/ is the best material implementation i believe.

Re: Vuetify - Material Component Framework for VueJS 2

#26

Post by kukx »

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…

Could you provide a screenshot of the problem you encounter?

Re: Vuetify - Material Component Framework for VueJS 2

#27

Post by spankalee »

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.

The advanced functionality is left out because it's very difficult, and quite a waste of valuable developer time, to reimplement essentially the same widget set over and over and over again for each framework.

That's just one reason why it saddens me to see so many proprietary frameworks out there with more all the time, especially ones that are so close to being compatible with Web Components. If Vue just used and produced Web Components, it could use a common Material Design component set. The investment in fewer component sets by more people would result in much higher quality and free up developers to work on higher-level things.

Re: Vuetify - Material Component Framework for VueJS 2

#28

Post by haffla »

Hmm I thought I could use this and add a few Material elements to my project here and there. But only including the CSS completely changes the styling of everything on my page (buttons, inputs, etc..). I mean not even Bootstrap changes the appearance of until you add 'btn' class.

Re: Vuetify - Material Component Framework for VueJS 2

#29

Post by mrgoldenbrown »

What would be helpful is a comparison to all the other Vue Material frameworks that already exist. (see github.com/vuejs/awesome-vue for example) ie, why should I switch? Why did this project get created from scratch instead of adding on to the existing ones?

Re: Vuetify - Material Component Framework for VueJS 2

#30

Post by subpixel »

retube wrote: post #5

what's the big deal with "material"? Looks ugly as sin. I just don't get it.

"I just don't get it" sums up my thoughts on a lot of Material Design. Here's an example from just this morning, where I wanted to sign up for Netlify News: https://www.netlify.com/news/

There's a form near the bottom of page, but it's very, very easy to miss because it implements Material Design-inspired input fields. And thought this is a DIY implementation, the 'official' version is highly similar: https://material.angularjs.org/latest/demo/input

For me, no animation or clever UX in the world is worth actually hiding the input a user is looking to use.

Post reply on HN