Quasar Framework

rstoenescu

No. You could build a similar store with a JS object that you import where you need it, but I don’t recommend it unless you really know how Vue works.
Don’t be scared of Vuex though.

rstoenescu

Only vertical is currently supported with QScrollArea.

rstoenescu

Use Vuex. Read Vuex docs first, then head to Quasar docs: https://quasar-framework.org/guide/app-vuex-store.html

Also additional read:

Make sure you understand how Vue Router works before diving in.

rstoenescu

Usually Cordova plugins inject their object to the global window scope. I see no imports required in this plugin’s docs. So just install it then use window.CameraPreview. Or contact the plugin owner for more info.

rstoenescu

@Hawkeye64 Have you upgraded eslint & co to newer versions? They can be upgraded to at least one major version – which introduces breaking changes. As ESlint & co. are project specific and NOT part of Quasar CLI, if you upgrade them it’s your duty to make the necessary changes to your .eslintrc.js too – whatever the new version with breaking changes requires.

rstoenescu

Just open that link in vue docs and see the DOM node count rising up.

rstoenescu

Like I showed you earlier, it should be reported to Vue with the simple example (that I copy-pasted) from their docs.

rstoenescu

quasar.conf runs in a Node environment, so don’t use “import” because there’s nothing transpiling ES6 to ES5.
So:

const fs = require('fs')

rstoenescu

Without a shadow of a doubt it’s not QTooltip and it’s not Quasar.

It’s either Vue or something else (like how browser schedules for GC). I also did a quick test on https://vuejs.org/v2/guide/transitions.html#Custom-Transition-Classes --> check the example on this section, and hit “Toggle Render” a few times. DOM node count rises up. This is with very simple code:

<div id="example-3">
  <button @click="show = !show">
    Toggle render
  </button>
  <transition
    name="custom-classes-transition"
    enter-active-class="animated tada"
    leave-active-class="animated bounceOutRight"
  >
    <p v-if="show">hello</p>
  </transition>
</div>

new Vue({
  el: '#example-3',
  data: {
    show: true
  }
})

This should be reported to Vue team.

rstoenescu

Ok, now it’s more clear to me what you’re reporting. Will investigate. Might be related to how Vue handles the memory. Will see.

rstoenescu

Dev is handled by webpack-dev-server, so you can fill quasar.conf > devServer > https with these options: https://webpack.js.org/configuration/dev-server/#devserver-https

rstoenescu

@rconstantine For v0.15+, quasar.conf > devServer > https: true

rstoenescu

https://jsfiddle.net/rstoenescu/metz5kx3/

rstoenescu

Quasar IS in in performance/optimisation/efficiency mode. But it depends on the usage. If you render 1 million components then any framework would start to cope hard with this.
This is NOT an issue. The QTooltip (and QPopover, and QModal) are kept in memory and added to DOM only when they are displayed as long as the components are being rendered by Vue. The Garbage Collector works when their parent component gets destroyed (which makes sense). This is the required behaviour because tooltips, popovers and modals need to be dynamically added at the end of <body> so they get displayed on top of any other page content – and not in the same place as their parent components (which would raise another issue of inheriting CSS props from it too).

rstoenescu

@ssuess iOS has just started on really working on their PWA features support. So it might not work as expected yet. Desktop browsers (regardless of OS) and Android on the other hand have a pretty solid PWA support.

rstoenescu

Is it a Quasar v0.15+ project, or you’ve “quasar init”-it with pre-v0.15?

rstoenescu

@mbrandeis who would use q-no-ssr to not render an H1 tag on the server? :))
Should it should use an example with H2 instead? Leaving jokes aside, isn’t the documentation supposed to offer the concept of QNoSsr? Who cares what the QNoSsr example nodes contain? The concept matters.

Small tip: you can use process.env.CLIENT to avoid the unnecessary negation on process.env.SERVER.

rstoenescu

v0.14 is very old. Are you able to upgrade to a newer version?

rstoenescu

Make use of src-pwa/register-service-worker.js… You got the “updated” method there.

rstoenescu

It’s because of style="height: 60vh;".

Posts made by rstoenescu