In main.js after
Vue.use(Quasar) // Install Quasar Framework
That is where I’d put it.
We have a PR for a feathers API wrapper. https://github.com/quasarframework/quasar-wrapper-feathersjs-api
And the maker of that did a tutorial too. https://github.com/claustres/quasar-templates/tree/feathers-api
Do let us know, how the rest goes (haha, pun not intended). I’d be very interested in how you get Quasar running with Nuxt.
BTW, I am working on a GraphQL API for Quasar. The start is also made with a simple wrapper. https://github.com/quasarframework/quasar-wrapper-graphql-api
And a demo app is also in the works, similar to the Feathers demo. All of this is WIP, so take it with a grain of salt.
Yeah, the sliding mechanism can be either horizontal or vertical. With a slider like functionality though, you are stuck to swiping one day at a time. Whereas, with the iOS selection wheel, you can “spin it”, which makes selection a better UX for date selection.
Razvan is off for this week. As he suggested, it would be really cool, if you could put your finding together in a docs page. Even just some text here in this thread would be super, if you aren’t up for making a docs PR. It would be hugely appreciated.
Quasar is a front-end framework. What you are looking for or rather where you should be looking is within the API or backend, which Quasar currently doesn’t have. There are two API wrappers in the works. One for a REST API based on FeathersJS and another for a GraphQL API based on Apollo. They should get you a lot closer to what you are looking for.
Razvan is off for a week.
Someone else mentioned making an iOS-like selection for dates. I think that is what you are heading for too. This would require a new component or even set of components (one for day, month and year). The slider could be the start.
Quasar is a framework for building SPAs. It isn’t an application in and of itself, but rather a good couple of steps above Vue, built for the purpose of rapid application development. It sort of goes the steps you would have to take to get Vue to where you’d need it for a full blown SPA, by integrating things like vue-router, a CSS framework (ie Stylus) and building up a large set of standardized components, among many other things.
Currently Quasar is built only to be used by itself. So, if you want to build a front or backend UI, you can only use Quasar on its own. If you are using Laravel with Quasar, then Laravel can only serve as a REST API.
I hope that makes sense.
I can recommend this book: https://www.amazon.com/Learning-Vue-js-2-Olga-Filipova-ebook/dp/B01JLBMCAY
I was under the impression Flow was like TypeScript, just with the added benefit of having a better type inference and also no transpiling (aka “blazing fast”). This article makes a pretty good sell of it all.
@LaurentPayot - yeah. I am not really begging here at all to get any type system going. In fact, I am more like you in my thinking. To me a type system is a crutch for the “not-so-careful” or “not-so-experienced” or those afraid of JS’s dynamic capabilities and them being so odd compared to stricter typed languages. Type checking can, however, contribute to what many say is a better developer experience. I personally haven’t used TS or Flow enough to say “yup. That is correct.” And, good design, programming and testing can offer a nice developer experience too.
I didn’t mean to make this a “static/ dynamic typing” war, but let’s look at those static typing advantages.
Better design - being forced to think about the types of values in your software up front can push you towards cleaner, more logical solutions. (I say can - it’s still possible to design really bad code…)
Better compile time checking - static typing can enable more errors to be caught at compile time. This is a huge advantage, and is arguably the best thing about statically typed languages overall.
Auto-completion - static typing can also give more information to the IDE so that auto-completion of code or documentation lookup is more effective.
Discourages hacks - you have to keep type discipline in your code, which is likely to be an advantage for long term maintainability.
Type inference - in some languages (e.g. Scala) this can get you many of the conciseness benefits of dynamic languages will still maintaining type discipline.
Looks like your connection to Quasar Framework was lost, please wait while we try to reconnect.