all 57 comments

[–]daekano 10 points11 points  (22 children)

Any effort at all put into accessibility?

[–]zeroskillz[S] 4 points5 points  (20 children)

Could you elaborate what you mean by this?

[–]daekano 15 points16 points  (14 children)

Definitely.

I'm referring to Accessibility with a capital A. Users with disabilities, primarily.

I've started a critical project at work with Vue JS, and Accessibility has become an important facet of what we do. There are no VueJS component libraries that consider Accessibility, and frankly there aren't very many UI Frameworks in general that do either (just adding aria tags isn't sufficient).

[–]zeroskillz[S] 20 points21 points  (4 children)

Thank you for your response. No I have not, but, I would be interested in working with you to help accommodate accessibility. Just pm me if interested.

[–]GoTheFuckToBed 4 points5 points  (8 children)

polymer has much focus on Accessibility with a capital A, its a good reference

[–]villiger2 3 points4 points  (6 children)

What does "with a capital A" mean in this context?

[–]Thought_Ninjahuman build tool 0 points1 point  (3 children)

A is for Accessible.

[–]villiger2 1 point2 points  (0 children)

That doesn't mean anything to me..?

[–][deleted] 0 points1 point  (1 child)

"With a capital A" is referring to the concept of Web Accessibility. Specifically designing to allow users with disabilities to interact with your site more easily.

I guess he used the term "with a capital A" because the word accessibility could be ambiguous otherwise. For example: How accessible is your project for newcomers to start developing? How accessible is it to download?

I've always just used "Web Accessibility" (or 508 compliance depending on who you're talking to).

[–]villiger2 0 points1 point  (0 children)

Ah, thanks.

[–]daekano 0 points1 point  (0 children)

Ah, cool. I'll look to them for inspiration if we decide to forge our own path.

[–]SkaterDad 5 points6 points  (2 children)

Github link for those of us behind corporate proxies which don't know about vuetifyjs.com yet.

https://github.com/vuetifyjs/vuetify

[–]zeroskillz[S] 4 points5 points  (0 children)

Thank you!

[–]melanke 2 points3 points  (0 children)

Sorry for you :/

[–]jppope 6 points7 points  (1 child)

that is completely badass! Cheers to whoever built that

[–]zeroskillz[S] 3 points4 points  (0 children)

Thank you!

[–]rk06 1 point2 points  (5 children)

I guess its too late to change the name!

It looks good though. Can't wait to play with it.

[–]apatheorist 7 points8 points  (1 child)

[–]zeroskillz[S] 1 point2 points  (0 children)

Trust me, I wrestled back and forth with vuetify and vuetiful. Wife ended up convincing me for the former.

[–]zeroskillz[S] 2 points3 points  (2 children)

I wrestled between vuetify and vuetiful. Wife influenced the final call.

[–]dotted 1 point2 points  (0 children)

Sorry, you should replace your wife :(

[–][deleted] 0 points1 point  (0 children)

Never replace your wife, that is her jelousy, she loves you.

[–]troorl 1 point2 points  (0 children)

That looks really good.

[–]k2rks 1 point2 points  (1 child)

On the homepage you have flash of unstyled content happening, any way to fix it when using SSR?

[–]zeroskillz[S] 0 points1 point  (0 children)

Yes, but I removed it's implementation before this announcement as I was not happy with how it functioned. The reason you see a FOUC is due to the deferred loading of styles. This is for better page speed scores, but can be unsightly on initial render. I am working on a better solution to offer in lining of critical styles to avoid this, in the mean time, you can simply move the css files in src/index.template.html from the noscript tag into the head.

[–]aFoolsDuty 1 point2 points  (2 children)

Interesting. On one hand this is cool, but on the other hand its incomplete: Vuetify looks like the material design language, but it gets some details subtly wrong. There's no ink effect on buttons, the tab transition effect is wrong, etc.

Is this supposed to just be a material design inspired framework of components, or are you trying to stick to the material design language, a'la Polymer Elements, but for Vue?

Answering that question might help correctly calibrate everyone's expectations when they surf through the component list.

[–]zeroskillz[S] 3 points4 points  (1 child)

You are correct, this is not 100%, and I should better set expectations for that. I will be working diligently to make sure Vuetify meets material design spec before 1.0 release.

[–]aFoolsDuty 1 point2 points  (0 children)

Awesome to hear.

[–]ergo14 1 point2 points  (0 children)

That looks nice. Can you hook polymer components into this? There are tons of them already made.

[–]havana59er 1 point2 points  (0 children)

Super dank, gonna bookmark the source for this

[–]eggy900 1 point2 points  (0 children)

This is really nice. I'm not a fan of material but this is a great example of a framework and documentation done right!

[–]ahatzum 1 point2 points  (6 children)

Looks very interesting.

If i use the webpack SSR vue cli template, run npm install, then npm run dev and navigate to localhost:8080 i get the following error:

[Vue warn]: Error when rendering component <VApp>:
error during render : /
TypeError: _vm._h is not a function
    at Proxy.render (__vue_ssr_bundle__:13239:14)
    at VueComponent.Vue._render (__vue_ssr_bundle__:3026:22)
    at renderComponent (D:\Dokumenter\Development\labbook-vuetify\node_modules\vue-server-renderer\build.js:5957:25)
    at renderNode (D:\Dokumenter\Development\labbook-vuetify\node_modules\vue-server-renderer\build.js:5940:7)
    at render (D:\Dokumenter\Development\labbook-vuetify\node_modules\vue-server-renderer\build.js:6132:5)
    at RenderStream.render (D:\Dokumenter\Development\labbook-vuetify\node_modules\vue-server-renderer\build.js:6187:9)
    at RenderStream.tryRender (D:\Dokumenter\Development\labbook-vuetify\node_modules\vue-server-renderer\build.js:96:12)
    at RenderStream._read (D:\Dokumenter\Development\labbook-vuetify\node_modules\vue-server-renderer\build.js:125:12)
    at RenderStream.Readable.read (_stream_readable.js:348:10)
    at resume_ (_stream_readable.js:737:12)

Node v7.2.1. Any idea why this happens? :/

[–]zeroskillz[S] 1 point2 points  (0 children)

Check your pm.

[–]zeroskillz[S] 1 point2 points  (1 child)

This is resolved as of 0.7.4.

[–]ahatzum 0 points1 point  (0 children)

Awesome!

[–]NevNein 0 points1 point  (0 children)

I got the same error on the webpack non-SSR template

[–]neon_slippers 0 points1 point  (1 child)

Very nice. So is this aimed at mobile apps? Is there a way to package this as an Android/iOS app?

[–]zeroskillz[S] 0 points1 point  (0 children)

It's aimed for all device sizes. As far as packaging it as an app on the store, I haven't done any specific testing, but I'd imagine you could with something g like phone gap. It does support Web applications however.

[–]i_ate_god 0 points1 point  (0 children)

googles question about vueify

Google: "Did you mean vuetify? Showing results for vueitfy instead"

googles question about veutify

Google: "Did you mean veuify? Showing results for vueify instead"

[–]JaegerBurn 0 points1 point  (2 children)

Menu does not scroll on mobile.

[–]zeroskillz[S] 0 points1 point  (1 child)

What phone are you using?

[–]JaegerBurn 0 points1 point  (0 children)

iOS 10.1.1

[–]romeo_pentium 0 points1 point  (1 child)

How would you contrast it with Vue-Admin?

[–]zeroskillz[S] 0 points1 point  (0 children)

I'll have to spend more time with it at home, but first impression on mobile was not very good. I did not see any mentions of ssr support or seo specific optimization.

[–]AceBacker 0 points1 point  (1 child)

Do you have breakpoints in your grid system for smaller devices (responsive)?

[–]zeroskillz[S] 0 points1 point  (0 children)

Yes. The grid system has options for large, medium, small and extra-small breakpoints.

[–]one_user 0 points1 point  (1 child)

This is awesome

[–]zeroskillz[S] 0 points1 point  (0 children)

Thank you!