@joaopaulofilho @MusicForMellons @rstoenescu
I believe that if we could get apollo working with Quasar, in what ever way necessary (and naturally as professionally as possible) we could also “spread the word” within GraphQL circles (which is growing in leaps and bounds) about Quasar and possibly get some traction with that community.
Scott
@Nicholas said in The 0.14 beta release is available!:
0.14 Beta looks fantastic! Awesome job!
Do you have any idea of a possible release date for the final version of 0.14, or a timeframe?
Razvan will be taking a well earned vacation in the next few days. He’ll be off for up to about 10 days. When he comes back 0.14 will be finalized. So, 0.14 final will be determined towards the end of July.
We feel the beta is pretty stable currently and there are no plans to make any more major changes. So, there should be no worries on anyone’s part to run with 0.14 now and to build beautiful apps with it. 
Scott
As of Quasar version 0.13.2, you can now use a Vue config setting to turn off the (annoying) production tip you see in the console, when working with Quasar in dev mode. You know, this one:
You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html
To get rid of it, all you need is:
Vue.config.productionTip = false
Happy programming!
Scott
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.
Scott
I’ve been working on the docs and I can attest to the fact that 0.14 is practically like a new Quasar. There are so many improvements. And to think Quasar was already a great piece of work. This release is going to be awesome.
Scott
Hey Jeff.
I believe the main cost is an OSX native device (i.e. MacBook or MacMini), which Razvan would need to build the app and upload it to the app store for approval.
If you are really interested in Quasar and have the money to spare, you can donate to Patreon for recurring donations or to Paypal for one time donations.
Scott
This is currently the only admin “app” built on Quasar I know of.
https://github.com/odranoelBR/vue-quasar-admin-example
https://quasar-admin.firebaseapp.com/#/
Scott
I’ll tell you what. Once I get spinner and the new observable sections out of the way, I’ll jump on layout to get it documented for you. Ok?
Scott
Good news! Version 0.14 will have more icons.
The docs are still rough, but it should give you an idea of what is coming.
https://github.com/quasarframework/quasar-framework.org/blob/dev/source/components/icons.md
Scott
It isn’t my call to make, but I currently can’t see why 0.14 won’t be released today. The reason for the delay was the unfinished Play App, and as I mentioned above, it seems 99.9% finished to me. So, I think the release is on for today. Or worst case, Razvan doesn’t wake up from what must be like a comma to him. He’s been putting in some really wicked hours to get 0.14 ready. He worked until almost 6 a.m. this morning. 
I am excited for the release too.
Scott
Out of curiosity, what else is it that tachyons has, that is missing for you in Quasar?
You mentioned these
tachyons has the small/medium/large breakpoints
tachyons has some colors that are similar but do not match up to the palette in Quasar.
Which Quasar has or offers ways to get around itself.
Breakpoints: http://beta.quasar-framework.org/components/flex-css.html#Responsive-Design
Theming your own colors: http://beta.quasar-framework.org/guide/quasar-theming.html
Scott
https://github.com/alibaba/weex/releases/tag/v0.10.0
Native apps with Vue 2.0 made possible now with Weex, Alibaba’s new development platform for iOS and Android, which is based on Vue. It is a great milestone for Vue. I would guess it will be only a matter of time to be able to use Quasar to build native apps? Maybe?
Scott
There are now also files to offer a container to develop Quasar with Docker directly in the quasarframework/quasarrepo under the dev branch.
Documentation will be coming up soon.
Scott
I spread the work as much as I can.
Suggestion: Start a “Trip to 1.0” issue on Github, and list off the to-dos that need to get done to get there, possibly with both “nice-to-haves” and “must haves”. Then contributors could know what to possibly help with.
Or, create a “contributor friendly” tag and create issues for all the to-dos and tag them also for 1.0.
What I am getting at is to make a workflow, which is as contributor friendly as possible.
Add an issue/ to-do to support Docker dev environments too. 
Edit: and if you need help doing this, I’d be glad to help with creating the issue or issues. I just need the full list.
Scott
This is a fairly good guide on how to work with Git and Github.
http://kbroman.org/github_tutorial/pages/fork.html
Scott
Not totally sure if it is relevant to your problem, but newer versions of Quasar now use the “q-” naming convention (ie. <q-layout>) for components instead of “quasar-”.
https://github.com/quasarframework/quasar/releases/tag/v0.9.1
https://github.com/quasarframework/app-template-default/blob/master/template/templates/layout.vue
Scott
I am also just learning, but I don’t believe that is a functional way to implement a component in Quasar. If at all, I believe you’d want to include the component in a page, for instance the “Index.vue” page. Import the component and then declare it as a local component within the page.
Like this for Index.vue.
<script>
var moveForce = 30
var rotateForce = 40
import Quasar, { Utils } from 'quasar'
import test from './test.vue'
export default {
data () {
return {
quasarVersion: Quasar.version,
moveX: 0,
moveY: 0,
rotateY: 0,
rotateX: 0
}
},
components: {
test: test
},
// rest of the code omitted for brevity
Then include the component in the HTML.
<test></test>
Scott