@TarasNovak It’s mainly just waiting for content at the moment. I’ve only got like 4 sites / apps to put in it, and I can’t really do a lot with that.

FYI, check out this thread to have your site featured on the upcoming ‘Made With Quasar’ site: http://forum.quasar-framework.org/topic/957/made-with-quasar

@spectrolite Thanks, I will post there shortly. You are correct that I do need the form to be filled out as it grants the necessary consent for the data to be published in this format.
@luc-claustres I have received your entry and it will be part of the initial data set when the site goes live.

Hi all,

I am working on a ‘Made With Quasar’ site and could use some community contributions on existing projects. If you have a project that you would like to submit to be featured on this site then please fill out this short form with the details of the project: https://goo.gl/forms/KclyF6l251FYLa7n1

Thanks,
–Matt

Edit by Razvan: Also please submit a PR to https://github.com/quasarframework/quasar-awesome with your website/app/Quasar tutorial/video etc. Thank you!

Thanks for this amazing addition, this is going to be really helpful for my next project.

Done a long while ago but it’s great to see Quasar really take off. As Vue itself has just over 60k, that would imply that one in every 20 Vue developers has used (is at least aware of) Quasar. That is a pretty impressive statistic.

Great job @rstoenescu, it looks amazing

@rstoenescu Do you have any update on roughly how long it will be until the 0.14 update is published? I’m not trying to rush you - I don’t care if you say it will be a couple of months, I’m just wondering about what the current timeline is.

I haven’t tried doing this myself but I can’t immediately think of a reason that this would not work. I would suggest giving it a try and let me know if there are any errors with it.

@rstoenescu Sorry to jump onto an existing thread, but am I correct in assuming that importing at the local or global level will not affect the size of the build with Webpack tree-shaking?

@benoitranque As you say, make the router redirect /myroute to /myroute/tab1 and your problem should be solved.
Just make sure that your tabs are only looking for the /myroute/tab1 and /myroute/tab2 paths, with none corresponding to the route /myroute path and you should be fine.

Yes, it is the route that would have the default selection, with the tabs being linked directly to the route.

I think that we all agree that you deserve more than just a couple of days to relax - take care of yourself!

@spectrolite Give me a couple of weeks

No problem, glad that it worked out

Thanks, I use webstorm and had just accepted that I would have to make do with it throwing errors. This is very helpful!

See this page of the docs: http://quasar-framework.org/guide/handling-back-button.html

I imagine that this will be part of v0.15 or even wait until v1 as v0.14 is basically just bug fixes and will be released imminently.

Definitely something that I would like to see in a future version, though.

In case you guys haven’t been following the Gitter chat (https://gitter.im/quasarframework/Lobby), @rstoenescu said “beta version will come today 100%, just be patient. lots of last minute details. sorry for the delay” a couple of hours ago.

It’s so close!

Any second now?