Great idea! I’m not sure what material design has to say about it, but you should open a GitHub Feature Request Issue

@Fernando2684 Have you taken a look at https://github.com/quasarframework/quasar-play/blob/v0.14/src/components/showcase/other-components/tree.vue ? Unfortunately I haven’t spotted a Quasar app in the wild that uses tree.

@tonpereira You are right, I didn’t notice the /. The self closing syntax should work just fine. Have you tried to isolate the issue by creating a minimalistic repo to reproduce the error? And you’re using quasar 0.14 beta & vue 2.3.x right?

@a47ae Good catch. @tonpereira seems to be closing a nonexistant q-field tag instead of closing the q-input tag. Do let us know if that solves the problem @tonpereira

That’s a lot of javascript!

(missing gif from the original github issue) https://user-images.githubusercontent.com/2828767/28628251-6ec68a48-7224-11e7-8752-bc192c99f3db.gif

most people come to it after being scared off or disgusted by angular/react or whatever bloated and uselessly complex framework

That’s exactly what drove me to use Vue instead of React as I didn’t want to change my workflow for a library. I guess Quasar was just that good, and it was easy to get started due to the cli. It does seem strange how Quasar isn’t “drop in a <script src=…> tag and use” like vue is, and a codepen showing off the components would be neat, but it’s just not that difficult to install the quasar-cli and init a project to check it out. The beginner/quickstart documentation does need some love though.

@spectrolite v0.14 Quasar Apps seem to be working on Quasar Play 0.13.7 for me

@Tekki I’d think that having it on the front page of http://beta.quasar-framework.org/ would be enough ( Live DEMO [Material theme] & Live DEMO [iOS theme])

And now we wait for vue 2.4.2!