No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. A3an
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 18
    • Best 3
    • Groups 0

    A3an

    @A3an

    5
    Reputation
    539
    Profile views
    18
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location South Africa

    A3an Follow

    Best posts made by A3an

    • RE: How to install an advance preview of Quasar Framework version 0.15?

      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 😀

      posted in Framework
      A3an
      A3an
    • RE: [Solved] How does the new 'Notify' component work in v0.15?

      @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 🙂

      posted in Help
      A3an
      A3an
    • [Solved] How does the new 'Notify' component work in v0.15?

      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!

      posted in Help
      A3an
      A3an

    Latest posts made by A3an

    • RE: [Solved] How does the new 'Notify' component work in v0.15?

      @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 🙂

      posted in Help
      A3an
      A3an
    • RE: How to add a button in the q-data-table header?

      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!

      posted in Help
      A3an
      A3an
    • RE: Starter Kit to 0.15 version?

      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.

      posted in Starter Kits
      A3an
      A3an
    • RE: [Solved] How does the new 'Notify' component work in v0.15?

      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?

      posted in Help
      A3an
      A3an
    • [Solved] How does the new 'Notify' component work in v0.15?

      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!

      posted in Help
      A3an
      A3an
    • RE: How to install an advance preview of Quasar Framework version 0.15?

      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 😀

      posted in Framework
      A3an
      A3an
    • RE: How to install an advance preview of Quasar Framework version 0.15?

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

      posted in Framework
      A3an
      A3an
    • RE: Disabled Input fields are not actually disabled

      duh! Facepalm. Thanks Benoit!

      posted in Framework
      A3an
      A3an
    • Disabled Input fields are not actually disabled

      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?

      0_1513080126971_45a5a0fd-22d5-40c0-9683-8e47e5619599-image.png

      posted in Framework
      A3an
      A3an
    • RE: Is it possible to add other Quasar components like a QPopOver to a QTree node?

      @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.

      posted in Framework
      A3an
      A3an