No More Posting New Topics!

jeffatpf

@pepe-pipo My two cents - we’re solidly on the Vue/Quasar train. The components are world-class, the build tools are great, and the support (we’re a Patreon contributor) is truly excellent. But, don’t let a single guy on a chat board somewhere convince you around decisions concerning your tech stack. Take a day and write the same application in Ionic and Vue/Quasar. A very simple way to feel/decide what is best for you with minimal investment and maximum return.

jeffatpf

Thanks! It really works out great being a Patreon of this project!

jeffatpf

@Jason
(1) ‘npm install --save-dev prerender-spa-plugin’
(2) add 'let path = require(‘path’); to the top of quasar.conf.js - the prerender plugin needs to know where the build is.
(3) add…

let spaPath = path.join(__dirname, ‘dist/’ + ctx.modeName + ‘-’ + ctx.themeName);
cfg.plugins.push(
new PrerenderSpaPlugin(spaPath, [’/’])
);

… to the build.extendWebpack(cfg) section of quasar.conf.js.

jeffatpf

Setting an HTML message within Notify and Dialog is a missed feature - lost with the removal of Alert in 0.15 and it’s HTML support. It would be great to get it back.

jeffatpf

@patryckx Do you need to support IE 11 with your application and Apex Charts? Apex Charts no longer supports IE 11 without the addition of a few polyfills. I’m in the process of figuring out how to add these polyfills within the quasar environment/webpack, as we still do need to support IE11.

The change itself - https://github.com/apexcharts/apexcharts.js/releases?after=v3.13.1
The fix to the change - https://github.com/apexcharts/apexcharts.js#using-it-with-ie11

jeffatpf

I figured this one out after inspecting the cfg object. I needed to push the plugin onto cfg.plugins (not cfg.module.plugins).

jeffatpf

window.Stripe

jeffatpf

(1) add this to the <head> section of index.template.html

<link href="https://fonts.googleapis.com/css?family=PT+Sans:400,700" rel="stylesheet">

(3) and add this class to app.styl

*:not(i)
{
font-family: ‘PT Sans’, sans-serif;
}

There are many other ways to do this but this approach works great for me.

jeffatpf

I used the HTML property within Alert to bold the important part of the message, ala “Do you really want to delete <b>whatever</b>?”

jeffatpf

@benoitranque - could enabling/disabling this become an option?

jeffatpf

A ‘read-only’ q-input has a dashed border. I’d like the border to be solid black. Any help changing the styling would be greatly appreciated.
The real purpose of this is that we are using a q-input with q-date and we want the date selected by q-date and displayed within the q-input, without the ability to change it (read only) within the q-input. But, the readonly attribute on q-input is really only an attempt to get the behavior we’d like. It would be better if there were some way to popup q-date when a user clicks on the input (when it gets focus). Any ideas?

jeffatpf

@ahmadx87, I add:

$form-autofill = #000000

to my quasar.variables.styl and this does the trick.

jeffatpf

@yusufkandemir Strange, I use NVM and the latest “stable” version shows as 10.17.0. Updated to 10.20.1 and all is good. Thank you.

jeffatpf

@rstoenescu I’m having issues installing the latest @quasar/app

node --version ->
10.16.3

This is the latest stable version of node.

quasar upgrade ->
@quasar/app: 1.7.1 → 1.8.10
quasar upgrade -I ->
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
error move-file@2.0.0: The engine “node” is incompatible with this module. Expected version “>=10.17”. Got “10.16.3”
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Quasar CLI · ️ Command “yarn” failed with exit code: 1

Removed node_modules floder
yarn install -> same error as above
removed yarn.lock
yarn install -> similar error as above with more @quasar/app related warnings

yarn install v1.16.0
info No lockfile found.
[1/5] Validating package.json…
[2/5] Resolving packages…
warning @quasar/cli > metalsmith > gray-matter > coffee-script@1.12.7: CoffeeScript on NPM has moved to “coffeescript” (no hyphen)
warning @quasar/app > webpack-dev-server > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning @quasar/app > webpack-dev-server > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning @quasar/app > node-sass > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning @quasar/app > node-sass > node-gyp > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning @quasar/app > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning @quasar/app > @quasar/babel-preset-app > @babel/runtime-corejs2 > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning @quasar/app > fork-ts-checker-webpack-plugin > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning @quasar/app > fork-ts-checker-webpack-plugin > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning @quasar/app > stylus > css-parse > css > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning @quasar/app > @quasar/babel-preset-app > babel-plugin-transform-imports > babel-types > babel-runtime > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
[3/5] Fetching packages…
error move-file@2.0.0: The engine “node” is incompatible with this module. Expected version “>=10.17”. Got “10.16.3”
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Please advise, thanks.

jeffatpf

@bamboechop exactly

jeffatpf

It’s absolutely required for our application - many enterprise users here in the US are on IE11.

jeffatpf

@patryckx Do you need to support IE 11 with your application and Apex Charts? Apex Charts no longer supports IE 11 without the addition of a few polyfills. I’m in the process of figuring out how to add these polyfills within the quasar environment/webpack, as we still do need to support IE11.

The change itself - https://github.com/apexcharts/apexcharts.js/releases?after=v3.13.1
The fix to the change - https://github.com/apexcharts/apexcharts.js#using-it-with-ie11

jeffatpf

I’ve used the loglevel module with the corresponding Quasar boot file (loglevel.js):

// https://github.com/pimterry/loglevel
import loglevel from ‘loglevel’;

const isDevelopment = process.env.NODE_ENV === ‘dev’;
loglevel.setLevel(isDevelopment ? ‘debug’ : ‘error’, false);

window.console = loglevel;

jeffatpf

I have a q-tree question, given this codepen:

https://codepen.io/jeffbcole/pen/bGNXVNa?editable=true&editors=101

I need ‘leaf’ tick strategy behavior, with the following…

(0) When the user selects the node “0” with no other nodes selected I need the “ticked” array to contain all node id’s, including 0, 1, 2, 3. It currently only contains the id’s of the innermost children [‘1.1’, ‘1.2’, ‘2.1’, ‘2.2’, ‘3.1’, ‘3.2’]

(1) When the user selects the node “2” (with no other nodes selected) I need the “ticked” array to contain [‘0’, ‘2’, ‘2.1’, ‘2.2’] - i.e. any node in the hierarchy above the selected node. As written the “ticked” array only contains [‘2.1’, ‘2.2’].

(2) When the user selects the node “2.1” (with no other nodes selected) I need the “ticked” array to contain [‘0’, ‘2’, ‘2.1’] - i.e. any node in the hierarchy above the selected node. As written the “ticked” array only contains [‘2.1’].

(3) I’d like the tree to be fully expanded with no ability to expand/collapse any node.

I’m using q-tree in my application as a way to set hierarchal permissions.

Any help on the above is greatly appreciated.

Jeff.

jeffatpf

Im interested in why the installed versions of ESLiint and related are a bit behind the latest.

@vue/eslint-config-standard 4.0.0 4.0.0 5.1.0 devDependencies https://github.com/vuejs/eslint-config-standard#readme
eslint 5.16.0 5.16.0 6.8.0 devDependencies https://eslint.org
eslint-loader 2.1.2 2.1.2 3.0.3 devDependencies https://github.com/webpack-contrib/eslint-loader
eslint-plugin-node 9.2.0 9.2.0 11.0.0 devDependencies https://github.com/mysticatea/eslint-plugin-node#readme
eslint-plugin-vue 5.2.3 5.2.3 6.1.2 devDependencies https://eslint.vuejs.org

No More Posting New Topics!

jeffatpf

@jeffatpf

Best posts made by jeffatpf

Latest posts made by jeffatpf