See containerized layouts: https://quasar.dev/layout/layout#Containerized-QLayout
Best posts made by JaredThirsk
-
RE: how can I nest q-layouts?
-
RE: $ quasar dev not working
I ran into a similar problem.
Tried ‘quasar build’, and it spit out some compile errors at me, though not in the usual way – it was post-processed vue template.
Latest posts made by JaredThirsk
-
RE: Deploy Quasar Application in IIS
Is it possible to host under a subfolder? Such as https://example.com/myapp
-
RE: Nested <q-layout>
One idea I am trying: using portal-vue (https://portal-vue.linusb.org/) in the header and footer to add additional sub-headers and sub-footers.
-
RE: how can I nest q-layouts?
See containerized layouts: https://quasar.dev/layout/layout#Containerized-QLayout
-
[Found workaround. Bug?] IE11 missing polyfills for q-layout?
I am trying to get q-layout working in IE11 UMD but I get a bunch of errors unless I put this code in my page. Is this a bug in Quasar’s IE11 support?:
// IE11 polyfill //NodeList.prototype.remove = HTMLCollection.prototype.remove = if (!HTMLDivElement.prototype.remove) { HTMLDivElement.prototype.remove = function () { for (var i = this.length - 1; i >= 0; i--) { if (this[i] && this[i].parentElement) { this[i].parentElement.removeChild(this[i]); } } } } if (!HTMLDivElement.prototype.closest) { HTMLDivElement.prototype.closest = function (s) { var el = this; do { if (el.matches(s)) return el; el = el.parentElement || el.parentNode; } while (el !== null && el.nodeType === 1); return null; }; } if (!HTMLDivElement.prototype.matches) { HTMLDivElement.prototype.matches = HTMLDivElement.prototype.msMatchesSelector || HTMLDivElement.prototype.webkitMatchesSelector; } if (!HTMLBodyElement.prototype.matches) { HTMLBodyElement.prototype.matches = HTMLBodyElement.prototype.msMatchesSelector || HTMLBodyElement.prototype.webkitMatchesSelector; } if (!HTMLHtmlElement.prototype.matches) { HTMLHtmlElement.prototype.matches = HTMLHtmlElement.prototype.msMatchesSelector || HTMLHtmlElement.prototype.webkitMatchesSelector; }
-
RE: $ quasar dev not working
I ran into a similar problem.
Tried ‘quasar build’, and it spit out some compile errors at me, though not in the usual way – it was post-processed vue template.
-
RE: Native dependencies in electron wrapper
I am trying to get quasar working with edge-js (for .NET interop) (https://github.com/agracio/electron-edge-js)
I managed to make some progress in loading the native .node file by doing this in the top of my quasar.conf.js file:
// Configuration for your app module.exports = function (ctx) { return { module: { rules: [ { test: /\.node$/, use: 'node-loader' } ] },
I think I did a
yarn add node-loader
Then in my index.vue, I do this:
import edge from 'node-loader!../../node_modules/electron-edge-js/lib/native/win32/x64/8.9.3/edge_nativeclr.node'
It loads in
quasar dev -m electron
, but not build – still need to sort out paths. Not sure if this even makes sense yet.