Oh, then you are doing something wrong :D
Never, never change code in the source folder of an installed dependency (this will even not longer be possible in Quasar 0.14 because too much people misused the src).
Quasar already defines a convenient place to overwrite variables.
Add the variables under src/themes/app.variables.styl like described here
@a47ae First of all: LOL, I think I would too.
About Stripping Roboto, imho it would be a shame to cripple the looks of the UI, and the objective was reducing requests to the server, not optimizing bandwidth usage or app total size.
I thought that would be a problem only if you’re overriding existing quasar classes. In your example you are not (my-card-style is not in quasar).
Are you really encountering this problem with this example, or are you over-simplifying your issue for the forum ?
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.
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.
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