You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building skin system for my site engine, and on now technologies it is difficult to achieve.
I think this is common case for many projects, to apply customs skins.
What is skin?
Some aditional css styles above Qausar CSS.
To build custom skin I need
Some command to compile my stylus skin file. It may be extension.
I dont know the extensions syntax but it can be something like this quasar compile-skin my-skin.styl
And this command produce css code in one file => my-skin.css
I need to apply my-skin.css to the site, so Quasar Api need to have function to apply
import {applySkin} from "quasar"
applySkin("MySkin", "/somedir/my-skin.css"); // 1 parameter is skin name, it needed to remove skin by name.
Skin compiler.
My thoughts.
I am building skin system for my site engine, and on now technologies it is difficult to achieve.
I think this is common case for many projects, to apply customs skins.
What is skin?
Some aditional css styles above Qausar CSS.
To build custom skin I need
I dont know the extensions syntax but it can be something like this
quasar compile-skin my-skin.styl
And this command produce css code in one file =>
my-skin.css
my-skin.css
to the site, so Quasar Api need to have function to applyremoveSkin("MySkin")
It needed to skin different components separetly if I want.
This is my vision of how skins have to work.
The text was updated successfully, but these errors were encountered: