Help

• Y

  How to speed up page change ?
  • yamland  

  6
  1
  Votes
  6
  Posts
  116
  Views

  Y

  Hi, @metalsadman Thank your reply!! Sorry to confuse you because my first post describe is wrong. I used q-router-tab outside of keep-alive. So footer works well. Problem is very slow page change at first time page change from page A to Page B. Second time page change is enough fast thanks to keep-alive. So, I searching the way to pre-rendering other router page on client side. But I can’t find the way yet. ( For example, when you see user’s page, I want to do pre-rendering time-line page in background on client side, like after <keep-alive> . ) But this is not quasar specific problem? So better to ask at stack overflow ?
• A

  Download pdf in the mobile version of the application
  • aiai  

  2
  0
  Votes
  2
  Posts
  17
  Views

  L

  I believe you should ask this on JSPDF help platform
• 

  How to run a Quasar 0.17 project after system migration to 1.0?
  • marcelo  

  3
  2
  Votes
  3
  Posts
  142
  Views

  O

  I am facing the same problem with npm running 0.17.x app with quasar v1.0.0-rc.4 on linux. Is there a solution with npm? I would not like to switch to yarn
• F

  Axios - sending json to php page
  • FraserMcT  

  9
  0
  Votes
  9
  Posts
  53
  Views

  F

  @metalsadman - thank you very much! I have to admit my stupidity - I have been making my life difficult by saving the variable as a file to view the contents - not realising that I could echo as a response. I also thought that by having quotes in the json that it made it invalid, but it didn’t. Thank you for your patience and for your help.
• H

  Running nodejs inside electron app
  • haohmaru  

  1
  0
  Votes
  1
  Posts
  15
  Views

  No one has replied

• J

  TreeShaking using webpack
  • jetsmart  

  5
  0
  Votes
  5
  Posts
  43
  Views

  

  I would think that import {default as Quasar} from 'quasar' would bring in exactly everything. Why not be specific, import {QBtn} from 'quasar'?
• F

  Unexpected return to the line with suffix on q-input
  • Florentin  

  1
  0
  Votes
  1
  Posts
  11
  Views

  No one has replied

• S

  QDateTime not loading correctly
  • Sheejavarghese6  

  6
  0
  Votes
  6
  Posts
  31
  Views

  J

  @Sheejavarghese6 Frankly, you need to put in the time and go thru the upgrade guide in very focused detail. It works, we just finished a fairly painless conversion of a large project to V1 and the guide was great. I would recommend creating a new v1 project and migrating your code over piece-wise.
• T

  QTree selection and ticking id to create dynamic components
  • Todo Digital  

  6
  0
  Votes
  6
  Posts
  55
  Views

  T

  @s-molinari thank you again for our time. Thought of that, about query the object with the key and return the desired data. It is just that I thought I was missing something from the QTree component, but now that I see your code and tested myself, works great. This really gives QTree a huge potencial. Regards, Jaime
• A

  $root.$emit on Q-menu not possible
  • anhln8x  

  3
  0
  Votes
  3
  Posts
  21
  Views

  A

  @lucasfernog thanks
• V

  This topic is deleted!
  • vonSansberg  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• C

  [Solved]Impossible set global variable on quasar 0.15
  • cklinx  

  15
  0
  Votes
  15
  Posts
  3322
  Views

  

  It’s not BS. Having general global variables is an anti-pattern and not “something so simple”. Vuex is, however, a global store for data and offers reactivity to boot, and thus since it is a viable, accepted and “built-in” pattern to Vue, it is the solution to “global data” for your app. Scott
• J

  Emoji appear black and white in Firefox.
  firefox emoji • • JazzOne  

  2
  0
  Votes
  2
  Posts
  109
  Views

  M

  Having the same issue in V1
• J

  Expansion Item: Prevent Unnecessary Re-Render
  • Julia  

  7
  0
  Votes
  7
  Posts
  40
  Views

  L

  LOL i have no idea why that happened
• N

  module.exports drama and how to access webpack-chain config.output in quasar.conf.js?
  • nejlyn  

  9
  0
  Votes
  9
  Posts
  1222
  Views

  N

  With the upgrade to quasar v1 I thought I’d post my new babel config file here, in case it might be of help to anyone searching the interwebs. “modules” is now deprecated in babel configuration. But, instructions are given here: https://babeljs.io/docs/en/babel-plugin-transform-modules-commonjs So my new babel.config.js is now: module.exports = { presets: [ ‘@quasar/babel-preset-app’, { ‘plugins’: [’@babel/plugin-transform-modules-commonjs’] } ] } Cheers
• C

  Unable to migrate to v1
  • Cochonours  

  5
  0
  Votes
  5
  Posts
  36
  Views

  C

  That’s what I followed…
• V

  Uploader with Axios
  • valasek  

  3
  0
  Votes
  3
  Posts
  66
  Views

  M

  @valasek make use of the upload-factory. edit. so it’s removed now and it’s called factory prop in v1, the new one doesn’t pass the updateProgress function tho :(.
• J

  Disable entire form (Quasar Beta v1)
  form prop • • jriemer  

  5
  0
  Votes
  5
  Posts
  47
  Views

  M

  @jriemer welp, you could use inner loading component https://quasar.dev/vue-components/inner-loading#Introduction to disable a part of your form. example https://codepen.io/metalsadman/pen/QRoKoz. you could use a spinner or just choose not to show one, by giving it a size prop of 0px.
• M

  This topic is deleted!
  • mKomo  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• B

  q-select error
  • bszubiak  

  1
  0
  Votes
  1
  Posts
  22
  Views

  No one has replied