[CLOSED] Custom theme - override or SASS?

[jchau]

Currently, we change alot of the default gray styles by using css overrides. Will it be worth our effort to follow Sencha's theming guide with SASS and output our own css files? Will there be any client side performance gain by doing this?

[geoffrey.mcgill]

Creating a custom Theme using SASS is a great way to go.

In general there would be no performance gain, nor degradation with a custom Theme.

Hope this helps.

[jchau]

Creating a custom Theme using SASS is a great way to go.

In general there would be no performance gain, nor degradation with a custom Theme.

Hope this helps.

What would be the advantage of creating a custom Theme using SASS then? We are trying to see whether using SASS is worth the effort. Right now, we are getting by with CSS overrides. I was hoping that having cleaner css and less css rules will speed up the css parsing a little on the client side.

[geoffrey.mcgill]

What would be the advantage of creating a custom Theme using SASS then? We are trying to see whether using SASS is worth the effort. Right now, we are getting by with CSS overrides. I was hoping that having cleaner css and less css rules will speed up the css parsing a little on the client side.

Well, if you are changing/overriding a lot of css classes, then yes there is a theoretical benefit to creating a custom SASS Theme as the total amount of css rendered to the Page would be less. You would probably have to be overriding a fair amount to see much of a performance improvement though.

A primary benefit of a custom SASS Theme is that you create a .css file with exactly what you need, and no more. Once you figure out all the SASS properties/configs you need to change, then it's generally much easier to customize the Theme and you get a more robust .css end product.

SASS takes time to get up and running, but once you have it working, major Theme revisions generally come quickly.

Hope this helps.