open source electron webview wrapper, that’s really cool.
atm I’m using the forever free and perfectly sufficient version of Fluid (a commercial product) to wrap gitter and cloud9. It’s only for MacOS, which is one more plus on the side of nativefier, which can also handle windoze…
Fluid makes it really easy, and has cool and easily activated options like url whitelists and setting various user-agents.
But for other uses, having an opensource option is great.
gmaps is quite cool, very simple, and modularized into npm. But I’m just getting started with it so take it with a grain of salt.
You can see it in action in quasar here (that’s where I’ve heard from it the first time) :
Have you tried gt-xs ?
Or maybe it’s the fact that your tabs are actually wider than the trigger-point (with some hidden content), and that interferes somehow. In this case, I guess you’ll need to wait for someone more knowledgeable than me to answer this one… Unless wrapping your q-tabs tag in a div (and putting your conditional class there) simply fixes it.
Ok, I have resolved it - to access dataLayer object you need to write:
So in index.html you include the GTM code and in analytics.js you write window.dataLayer instead of just dataLayer
The global tooltip background color can be set via the $tooltip-background Stylus variable.
Also, I think tooltips just place whatever you pass between them as slots, so you should be able to just style it yourself.
I think the 0.14 release will be the first thing to consider, and then some months with consolidation
It would be nice with an interface like the IndexedDB, but we also need some query handling and event insertion, and editable grids. What I am saying is, that this could be a potential large project in it self.
But some inspiration from things like dgrid may be worth including
When I’m building for android or ios I only need to run quasar build each time.
If you remove the cordova folder each time and run quasar wrap cordova that will generate new cordova files.
The www folder in cordova is symlinked to the dist folder of your source so, just rebuild with quasar build ios and then change into cordova folder to cordova run or cordova build
Ok, so … if we could make WebPack build the two themes as two separate css bundles, we could load these after platform detection ?
I tried to do this (separating the css file from the main bundle), as we like our customers design requests separate from the main logic, but at the moment we let the http server do the mapping of these files.