To be clear: if after installing, quasar dev does not work for you, try npm run dev. Also, after installing, you can do npm run build, and copy the new dist folder to your node_modules\quasar-framework folder, (don’t forget to copy the package.json, icons and i8n folders as well). This will allow you to use it in an existing project.

[Edit: it is best to create a Simlink from your node_modules/quasar-framework folder to the dist folder of your cloned v0.15. This way, you can get the latest changes from Github, and then simply rebuild v.015. The magic of simlinks!]

Be prepared for updating your existing Vue files to use the new/updated components. Make a backup of your project first

@rstoenescu solved this for me!

If you are using the v0.15 starter kit ( https://github.com/quasarframework/quasar-starter-kit ), then do it like this:

-> “add it in quasar.conf > framework > plugins: [ ‘Notify’, …]”

If you are not using the starter kit, then:

-> “Then in main.js, import { Notify } from ‘quasar’… then look for Vue.use(Quasar, {plugins: {Notify, …”

Just putting it out there

Hi, does anyone know how the new Notify component works? I have tried several approaches, but none work for me.
I have tried the following (following some comments in Gitter on 2 Dec)

Notify('My Error Message')  // -> TypeError: Object(...) is not a function
Notify({ message: 'My Error Message' }) // -> TypeError: Object(...) is not a function
this.$q.notify('My Error Message') // -> TypeError: this.$q.notify is not a function
Notify.create('My Message') // -> TypeError: cannot read property 'add' of undefined

Please help!

@rstoenescu solved this for me!

If you are using the v0.15 starter kit ( https://github.com/quasarframework/quasar-starter-kit ), then do it like this:

-> “add it in quasar.conf > framework > plugins: [ ‘Notify’, …]”

If you are not using the starter kit, then:

-> “Then in main.js, import { Notify } from ‘quasar’… then look for Vue.use(Quasar, {plugins: {Notify, …”

Just putting it out there

You will be able to do this easily in v0.15 QTable (i’ve tested it) It should be out shortly. No, sorry, I don’t have a fixed date on that. But it will be soon!

Here is the v0.15 starter kit… it’s VERY nice! https://github.com/quasarframework/quasar-starter-kit.

Note, it suggests that you install the latest vue-cli and quasar-cli. If quasar dev stops working after this, just run npm run dev instead.

I also notice in the source for src/plugins/notify.js, the create function is as follows:

var notify = {
  create: function create (opts) {
    return this.__vm.add(opts)
  },

but there is another install ({ $q, Vue }) function included below that as well, which implies that the component needs to be installed.

I have also tried adding a `<q-notification></q-notification> to my template as well.

Can anyone comment on this?

Hi, does anyone know how the new Notify component works? I have tried several approaches, but none work for me.
I have tried the following (following some comments in Gitter on 2 Dec)

Notify('My Error Message')  // -> TypeError: Object(...) is not a function
Notify({ message: 'My Error Message' }) // -> TypeError: Object(...) is not a function
this.$q.notify('My Error Message') // -> TypeError: this.$q.notify is not a function
Notify.create('My Message') // -> TypeError: cannot read property 'add' of undefined

Please help!

To be clear: if after installing, quasar dev does not work for you, try npm run dev. Also, after installing, you can do npm run build, and copy the new dist folder to your node_modules\quasar-framework folder, (don’t forget to copy the package.json, icons and i8n folders as well). This will allow you to use it in an existing project.

[Edit: it is best to create a Simlink from your node_modules/quasar-framework folder to the dist folder of your cloned v0.15. This way, you can get the latest changes from Github, and then simply rebuild v.015. The magic of simlinks!]

Be prepared for updating your existing Vue files to use the new/updated components. Make a backup of your project first

FYI, for some of us, running quasar dev after install doesn’t work. You can run npm run dev instead.

duh! Facepalm. Thanks Benoit!

I have a bunch of Input fields in a Modal form, all with v-bind:class="{ disabled: true }". They “appear” to be disabled, but you can still, click, edit text and values etc.

I’m using 0.14.7. Is anyone else getting this problem? Here are some samples:

          <!-- IS FOR SALE -->
          <q-checkbox 
            v-model="record.is_for_sale" 
            label="For Sale?"
            v-bind:class="{ disabled: isForSaleDisabled }"
          />

          <!-- IS GIVEAWAY -->
          <q-checkbox 
            v-model="record.is_giveaway" 
            label="This is a Give Away"
            v-bind:class="{ disabled: isGiveAwayDisabled }"
          />

and a screenclip shows that they are greyed out… but I can still edit in all the controls. Is this a known bug, or am I just being an idiot again?

@benoitranque Yes, I just tried that. Same result. Sorry, It took a while, we had a power failure here due to lightning and hail. Is there any way to get some sort of error message? I could work from that.