Hi,

While we wait for @rstoenescu to issue a complete guide, here’s a starting point for all of us impatient dudes who want to port a 0.13.x app to 0.14.

1. npm update -g quasar-cli
2. quasar init 'default#beta' FOLDERNAME (will create a new folder with 0.14beta basics)
3. cd FOLDERNAME
4. npm i
5. Manually move your 0.13 code into that folder structure. Repeat step 4 once all your dependencies are set up.
6. Check the beginners intro and the beta docs, and learn about using components and tree-shaking.
7. Go ahead and apply what you learned.
8. quasar dev : check for any components still missing, adjust imports accordingly, rinse and repeat until your app starts and displays correctly.

To include icons you can now skip the respective CDNs and use quasar-extras, like this:
npm i --save quasar-extras, then use it like this.

If you have used animations in your code, take a look at this.

Since the beta is still being updated several times daily, before running to github or gitter to report a problem, please make sure you have the LATEST 0.14 version by running:
npm update quasar-framework from within your app folder (same for quasar-extras).

Hi,

Following a discussion with Razvan on Gitter, and while we wait for some good soul to build something like https://madewithfirebase.com/ but for and with Quasar, I thought I’d open this topic to build a simple list of all the live web apps and app-store available apps built with Quasar.

This would go a long way in helping with marketing for Quasar framework or in other words it would serve as a great incentive for adoption and will most probably boost support to our beloved framework.
It’s also simply a great way to showcase our community’s hard work, and will serve as a first building block for our future madewithquasar page.

Please post your apps in this topic, with links to all available builds/stores, and a short description.
Here’s a template you can use.

App name :
Description :

web :
iOS :
Android :
MacOS :
Linux :
Windows :

First release date :
Quasar version :
Full Stack description :
Comments :

If you don’t have a live app yourself (yet) but know of people who already released theirs, please ping them, like this:

/wink @luc.claustres @scottgrayson I noticed you released recently, your apps belong here too.

@rstoenescu I know you already have a list, could you please ping the guys? or share the list maybe?

Thank you all,

Can’t wait to see this list grow !

Laurent

Btw I just noticed a “chrome extension starter kit” has been on the roadmap for a while, so there’s definitely some interest in that direction.
https://github.com/quasarframework/quasar/projects/3

@oliver Btw I’m one of the guys who came back to JS dev after years of something else, and when I started diving into angular and react… I felt like I was bouncing back. The more I learned, the more confused I got. The more powerful the framework, the more restrictions it comes with… and the longer it took for a simple app to get live. Until I discovered Vue and then Quasar. Swimming with a smile on my face now. Code and logic are in harmony with the framework’s intentions, there’s ample freedom with little boilerplate, it’s easy to learn, resulting code is highly readable, docs and support are clean, clear and reactive. I can’t believe we’re still such a small community, I imagine our demographics will explode when we get to v1.0.0, because I cannot see any other obstacle to huge adoption in the JS/hybrid community.

I’ve been talking with @rstoenescu about this a few weeks ago and he agreed that we need to fix it somehow. From what I understand it will be part of the UI alignment and consistency overhaul for v0.14 final.

Personally I would advocate for no default transition, or at least an easy on/off toggle.
Changing the default header transition seems a must, as it’s visibly the worst offender (thanks for the animated gif, that really helps put us all on the same page).
Being able to select transitions at will (or use custom ones) would be great. But I’d rather have the toggle asap than wait for a full-featured solution.

It seems I had a similar conversation on gitter recently.
The gist of it was: QDialog is really a QModal with special constraints and setup, cf source code: https://github.com/quasarframework/quasar/blob/dev/src/components/dialog/Dialog.vue
Just saying…

This is just fantastic.
I hope the guys behind these apps show up here and share some more details with us.
We already have a nice starting point for a madewithquasar page !

Any of those have a quasar-driven website ?
Any web-only quasar apps you know of ?

You will get more support from both the code and the community on 0.14
It is truly great and well worth the effort.
The only reason I would maybe not do it is if the app relied on many differently configured datatables, as this seems the only component which would need some heavy polishing, and it could make the migration complex and long.
Other than that, I highly recommend 0.14, and there s plenty of help for upgraders, both in the forum (ready for you to use) and on gitter, for those times when u feel stuck.

Hi, I’m a new convert in a position similar to @ChrisB .
Awesomest of jobs on quasar @rstoenescu btw (sorry first post, a lot to say).

I’m glad to hear there will be tutorials and migration documentation soon, and I gladly support you on Patreon for your continuing hard work.

My current project is still quite simple and is already based on Vue 2 (+firebase).
I am still in a position to quickly restart from scratch with Quasar and migrate most of the current code to the quasar app manually.
I would be very willing to start this right now, but I’m in doubt.

My question is simple:

Could I safely start this rewrite based on the dev branch, which seems to be v0.14 and almost 99% ready according to the ‘0.14 features’ post ?
I don’t mind to wait a few weeks before I get tree-shaking, which seems like the only important feature not at 100% yet.
Or should I stick to the bleeding edge 13.9 ? I’m really looking forward to using the new transitions though. And I also would like to avoid dealing with breaking changes just a few weeks later. Finally, I’m a total noob to quasar, so maybe I missed something obvious.

Please advise.

I tend to agree with you on principle. We truly need a super-easy, ultra-simplistic tutorial, that would just get you started doing a single simple webpage. Something like a beginner’s tool to learning Vue and Quasar. That would really widen the audience.
Btw you only need quasar-cli to initialize the project, you can mostly forget about it later, except for quasar dev and quasar build, which are happy alternatives to npm run build whateveroptionsIcanNeverRemember

On the other side, I doubt so many people are scared off right now. Quite the contrary. Quasar is still quite niche, and it seems most people come to it after being scared off or disgusted by angular/react or whatever bloated and uselessly complex framework that did not satisfy their needs / code philosophy / UI requirements / destination platforms requirements / etc. And from what I can see, some pretty picky people are pretty happy with it.

Brilliant work, as always, thank you Razvan !

Side drawers have by default a touch directive to open/close on drag, and that interferes with any component using drag nested inside of a drawer.
Currently there seems to be no way around this (that I know of). @rstoenescu Any ideas?
The same problem disallows the use of several quasar components, as well as vue components that normally allow drag and drop, or any kind of sliding/panning behavior.
I took the liberty to create an issue on github, since you’re not the first to encounter this problem.
@tiago_startt and any other experiencing similar issues, please add your voice there too:
https://github.com/quasarframework/quasar/issues/998

I’ll try your method soon, and I will then plug my own i18next-firebase-backend instead, which I’ll opensource once all is well.
Stay tuned

@matt go ahead and post your link in there too, it might net you a few more entries : http://forum.quasar-framework.org/topic/498/quasar-live-apps/
@luc-claustres I imagine that out of respect for privacy/intellectual property, as well as practicality, Matt needs every app owner to submit details directly, instead of him fetching data left and right.

@rstoenescu While I can only applaud your wanting to get to 0.15 quickly, I feel I should chime in favor of the foldable icons-only side-menu, as it seems to be the kind of sugar-coating a lot of people are looking for these days. It is part of almost all well-made “admin-templates” nowadays and many popular frameworks include it as well. I’d say it’s worth the time, if only for “marketing” purposes… just my 2cents.

bump
@rstoenescu should we make it a github issue? is it already on your roadmap? is there some big obstacle in achieving this (either a toggle or a custom transition) ?

for anyone still not finding it (and since the link above is long dead): http://quasar-framework.org/components/flex-css.html

@cedrico2015 Yes, there is a very good reason.
Quasar 0.14.2 is now an official release and out of beta

That video is fascinating (and you can see not only vue but also quasar being developed…)
Gource is a cool tool

@rstoenescu could we have a prop for that in all animated components please?
e.g. adding no-animation to a component would do that css override (or anything else appropriate internally to forfeit the animation effect)

or maybe animation="none" if you plan on later allowing custom animations to be set through that same prop ( /wink /wink /nudge /nudge )