Useful tip, you could also do something like this:

// generate nav links as a list of q-items <q-list> <q-item v-for="(item,id) in items" :key="id" exact tag="a" v-bind="item"> <q-item-section> <q-item-label> {{ item.label }} </q-item-label> </q-item-section> </q-item> </q-list>

And bind all attributes to the item. Binding unused attributes like label usually isn’t a problem, if you wanted could also do:

// the data data () { return { items: [ { label: 'One', attrs: { to: '/one' } }, { label: 'Two', attrs: { to: '/two' } }, { label: 'Bing', attrs: { href: 'http://bing.com', target: '_blank' } } ] }}

And v-bind="item.attrs"

@metalsadman thanks for the feedback

Sorry for the late answer.

@irexqudiet said in Example of combining Laravel 7 and Quasar superpowers in separate repos:

Status Code: 419 unknown status why did i get this error when i try logging in

It’s usually due to misconfiguration of these variables in your .env file: SANCTUM_STATEFUL_DOMAINS and SESSION_DOMAIN

Check out the note here.

Hello Guys, I have updated the Quasar Echarts demo app with Echarts v5.You can access it using the following URL.

Github - https://github.com/pratik227/quasar-echarts

Demo - https://quasar-echarts-v5.netlify.app/

QuasarEchartV5.png

New examples added!

Captura de Tela 2021-01-08 às 11.22.56.png

Captura de Tela 2021-01-08 às 11.23.02.png

Very cool

Good work .

And for visual people, here’s a before / after of webpack analyze:

webpack

Thanks!!!

Nice one! Hope it will fit my new website!
I am pro at digital gaming, so I created a website which is dedicated to my hobby ^^

Hi @gs86,

I never worked on server side pagination and filter with QTable. I have tried to implement in QGrid but no luck yet.

Thanks

@ArkIv That’s good.

dotenv not working my quasar. so I mixed your method + qenv.

.quasar.env.json

{ "development": { "ENV_TYPE": "Running Development", "ENV_DEV": "Development", "API_URL": "https://dev.some.com" }, "production": { "ENV_TYPE": "Running Production", "ENV_PROD": "Production", "API_URL": "https://some.com" }, "test": { "ENV_TYPE": "Running Test", "ENV_Test": "Test" }, "stage": { "ENV_TYPE": "Running Stage", "ENV_STAGE": "Stage", "API_URL": "https://stg.some.com" } }

quasar.conf.json

const configEnv = require('./.quasar.env.json') module.exports = configure(function (ctx) { return { ...... env: { // for settting proxy address with ctx.dev, ctx.prod IS_STAGE: false, }, }, devServer: { proxy: { // proxy all requests starting with /api to specific url '/api': { target: ctx.prod ? configEnv["production"].API_URL : process.env.IS_STAGE ? configEnv["stage"].API_URL : configEnv["development"].API_URL, changeOrigin: true, pathRewrite: { '^/api': '' } },

@dobbel https://en.wikipedia.org/wiki/Lotka–Volterra_equations

@aislan said in Web workers - how to use in Quasar:

Right now I’m just struggling with Quasar to place my worker files in another place not in statics folder.
I would like to put them next my actions folder, etc.

with the method described on top, you can put them anywhere - as long as they have an extension .worker.js. The webpack will do his job and properly inline/bundle your code.

And related to workerize-loader, how could we test them with Jest, for example ?

Don’t know 😞 carefully??? This should be asked to the author/users group, probably.

@jmriyaz84 said in Quasar Framework + Speech API:

https://developer.mozilla.org/pt-BR/docs/Web/API/SpeechRecognition#Browser_compatibility

Well, for browsers I don’t think there is a solution. Unless you force iphone users to use chrome for this.

You have the alternative of generating hybrid apps with corva and using the TTS plugin:

https://www.npmjs.com/package/cordova-plugin-tts

@dobbel said in Using FFmpeg WASM in Quasar:

@qyloxe
Not wanting to hijack you thread, but I found this plugin to wrap .asm files for use in vue:

feel free to hijack or byejack 🙂

Could that be interesting approach to integrate/use .asm in Vue?

Sure. The ffmpeg is interesting because it is highly useful in some applications. The general WASM imho is rather hard to find a purpose at least in my line of work.

Anyway - you asked about general solution - from the user point of view, then yes, this is specialized project, BUT from a developer point of view, the whole ffmpeg integration as a project a developer environment on github could be useful in other wasm projects. BUT on the other hand, the new WASM projects are started with rust or nim with llvm backend probably, so I don’t really know if it could/would be useful in real world applications.

So, ffmpeg in the browser could be VERY useful. From what I’ve seen it is an early project BUT there’s active development.

Hello, I’m driving crazy trying to adapt colorschemes I found in Dashblocks.
https://slanatech.github.io/dashblocks-template/#/
It’s very powerfull and made for complex graphs. I’d like something more simple to parameter a dashboard like yours.
I’m trying to use the store for this and hope to make conditional colors for displays, but I’m still learning Vue…