In a way this happened to meteor. Some liked the brilliant, opinionated tool as is, some pushed for breaking up the parts so they went well into a larger ecosystem. To my <opinion> the parts people won the war, and for all I know they are very happy and Meteor is doing very well in the corporate space and making more money than ever before. I was a fan of the opinionated tool - it helps reduce my js churn when someone smarter than I is making damn good choices. I left meteor during the fight, found vue and loved its magic, then found quasar and absolutely worship its magic.

I am not trying to put forward that this is a perfect analogy, but even though this is arguably a good problem to have, it is still a danger point. I think it’s the only time I’ve seen @rstoenescu loose his cool to any degree. That really should be a sign.

I’d suggest @rstoenescu and team has amazing instincts and should stick to their guts. And I hope to get out of my dev cycle so I can start making money, because truly both quasar and vue deserve a hundred times more love and support than they are getting.

Razvan,
My god, when do you sleep?

@s.molinari I easily added an existing markdown editor with live update to a project. It was reasonably easy, but would be happy to post details if anyone wants.

@mesqueeb , @kiranvasi, sorry I never noticed this request - I’ll look for it tomorrow!

also look at zeit.com’s now.
go to the correct build folder, type ‘now’ and get a free static site (or a node server site, depending on what you publish)
They will even manage your domain and swap project images at the dns level.

In a way this happened to meteor. Some liked the brilliant, opinionated tool as is, some pushed for breaking up the parts so they went well into a larger ecosystem. To my <opinion> the parts people won the war, and for all I know they are very happy and Meteor is doing very well in the corporate space and making more money than ever before. I was a fan of the opinionated tool - it helps reduce my js churn when someone smarter than I is making damn good choices. I left meteor during the fight, found vue and loved its magic, then found quasar and absolutely worship its magic.

I am not trying to put forward that this is a perfect analogy, but even though this is arguably a good problem to have, it is still a danger point. I think it’s the only time I’ve seen @rstoenescu loose his cool to any degree. That really should be a sign.

I’d suggest @rstoenescu and team has amazing instincts and should stick to their guts. And I hope to get out of my dev cycle so I can start making money, because truly both quasar and vue deserve a hundred times more love and support than they are getting.

To be specific, the problem was to use a reactive variable to compose the label and have it change.

I also gave up on computing the label for a q-collapsible, which I suspect is the same problem, and so I’d like to know what you find out.
Thanks.

Hi, I’m no cordova expert, just a long time non-web programmer, but often situations like you describe are related to timing, and although I know you are an accomplished programmer, I’ll write extra to be more helpful to others.

If you have time to play with a new blank template, out of the box functionality and the dumbest possible plugin like vibration alone, or whatever, and it doesn’t work, you could post it and rstoenescu might be able to quickly track down why. Also consider it might work for android and then not ios. Of course, as you know, if the simple version does function without your workaround, you then get to try adding each additional plugin back until you find the conflict.

Are you able to fake out a bunch of small cards and see if the behavior is what you expect? Or, is it that you have a large card which is not internally scrolling as you expect?

@RiyadhZ it seems low bandwidth and very controllable. Regex is easier on markup than any rich text. Also less mouse use. But I’m a power user mindset and your ux might indicate wysiwyg.

What does this look like when inside quasar?

https://monterail.github.io/vue-multiselect/#sub-asynchronous-select

you should be able to style things

A quick guess is that when qcards are small, they scroll just fine as entire qcards. Your card may be large enough that you need something to handle the internal scrolling, or break up the interior into cards which are small enough to scroll. I wouldn’t expect a grid inside a card; rather the contents of maybe a row.

This is a vue.js feature called dynamic components:

<template>
<div class=“app-body row”>
<template v-for="(child, index) in children">
<component :is=“child” :key=“child.name”></component>
</template>
</div>
</template>

https://forum.vuejs.org/t/any-way-to-dynamically-add-multiple-vue-components-within-a-parent-vue-component/8209

or

https://coligo.io/dynamic-components-in-vuejs/