Posts made by walfin

To everyone who celebrates

All the best to Quasar for 2020! Everyone here wants you to succeed.

What about glossy only for buttons?

Don’t know, haven’t tried before. I think for that you may have to manually obfuscate the service worker js file since it is a separate file. Or maybe there’s some other rule you can add to webpack for that.

Use npm install --save-dev webpack-obfuscator.

Here’s a sample from my quasar.conf.js:

let JavaScriptObfuscator=require('webpack-obfuscator');
...
build:{
...
extendWebpack(cfg,{isServer,isClient}){
if(!ctx.dev&&!ctx.debug){
cfg.plugins.push(new JavaScriptObfuscator({
debugProtection: true,
debugProtectionInterval: true,
rotateStringArray: true,
renameGlobals: true,
stringArrayEncoding: 'rc4',
stringArrayThreshold: 1
}));
...
}
...
}

Don’t they serve different purposes? Vuex is for storing state, while a global event bus is for raising events.

I have found a temporary workaround. My solution is to build with quasar build -m android --debug and add devtool:!ctx.dev&&!ctx.debug?’’:‘eval-source-map’ under build in quasar.conf.js and also to disable my use of webpack-obfuscator if !ctx.dev&&!ctx.debug. Thereafter I run cordova run android from src-cordova.

However, a special flag for this use case would still be nice.

I received some feedback about my app on this forum that glossy appearance is dated.

Why is glossy appearance good or bad in your opinion?

Is there any alternative apart from glossy and solid colours?

I use auth0 (https://auth0.com).

It works with Safari (after some workarounds).

@eyedean said in multiple entry points?:

PS. The solution I am going to go with, for now, is similar to your #2. I am going to have my Nginx do reverse proxy anything like mydomain.com/login to mydomain.com/index.html?from=/login, then in my router, at the first rendering time, I’ll try to parse that from query parameter and make an internal programmatic navigation to that page.

Why not just use html5 history mode in vue-router? That should be good enough to hot-link directly to the login page.

No you don’t. The import is in the component vue file and not the boot file. That’s how I got it working for mine.

OK, I have lodged this as an issue on GitHub.

@PeterQF wow that’s a strange error. Sure it didn’t come from somewhere else, like a Vue template? I don’t think there would be any < in your code otherwise.

But it seems doable, just a bit confusing especially on how to integrate this with quasar & quasar CLI: https://medium.com/js-dojo/advanced-server-side-rendering-with-laravel-vue-multi-page-app-486b706e654

I’m asking this because all my backends are PHP. I don’t think I have the access rights to install node.js or to modify my apache config to forward the requests to node.js.

@PeterQF Put import {gmapApi} from ‘vue2-google-maps’; at the start of your script, computed:{google:gmapApi} in your component, then use this.google instead of google.

How do I issue a feature request?

Is glossy really that bad? I thought flat solid colours were dull.

Wow nice! If only there was a way to save it as a quasar template.

Next step: a full WYSIWYG GUI editor for Quasar!

Has anybody managed to run a Quasar SSR+PWA killer combo app using PHP V8js? (With or without Laravel, preferably without)

Asking as I intend to move from an SPA to SSR+PWA and my backend server only supports PHP.

@PeterQF Do you mean this?

http://xkjyeah.github.io/vue-google-maps/index-app.html#/02LatLngBounds