No More Posting New Topics!

Hi dgk. Thanks for the input and feedback. If I may ask, would you be interested in creating an RFC for your thoughts to improve Quasar in terms of Design/ Styling/ Theming for v2.0? Don’t keep yourself reduced to this situation, but go “hog wild” in imagining a new way of designing with Quasar.

This is just me, but my wish would be that components aren’t styled in any one way to begin with. But rather, they are first “styleless”. Then, there would be a “core Design” that can be added to your app (i.e. Material, Bootstrap, Tailwind, etc.). Then there would be a “Theme” choice or even set of choices that can be added. But, that is just me and my ideas. I’m not a designer. 😁

We can continue this discussion here, if you’d like. I guess bottom line is, this suggestion more than likely won’t be done. But, for v2.0, we can make designing in Quasar even better.

Scott

@a47ae said in Themeing, Stylus vs SCSS:

Only thing you currently can’t to is to use the Stylus variables in SCSS/SASS. But I guess one could find a workaround for that.

I started working on a (very hacky) workaround… gave up half way through, but maybe someone will find it useful:
https://gist.github.com/bikubi/76325574c7c8236d5f14323d52e472ab

Hi,
Sorry for late reply, I had to step aside this issue for a few days.
What you posted back on Stackoverflow solved my issue.
Many thanks for that.

stackoverflow

@rstoenescu Thanks Razvan. Using css will work fine for now.

Yes, you’re right. Lists have their own text color. Will fix this in v0.8. You can however CSS overwrite the “color” property (not through stylus variables) of lists on v0.7 until the improvement arrives in v0.8.

Sorry, in my previous post you should only comment in quasar.conf.js, the line with “roboto-font” and decomment “material-icons”