In previous version there was an asset script which could be used to load a given theme and access its properties. It was theme.js stored in assets/general/services/media-tool/theme.js
In 3.0 it's gone. I used that service in some of my extensions as a dependency. I understand that it was removed intentionally and I should rewrite my extensions?
Can you please advice how can I write generic custom extensions which use color palettes defined in themes? Native extensions adjust to used theme so I believe there must be easy way to adapt this mechanism in custom extension.
I am also in search of a good way to write styles that override the default ones. I do realize with a sheet you can make a widget that would use js to inject a <link /> in the <head /> BUT this causes FOUC (Flash of unstyled content - Wikipedia, the free encyclopedia), very bad for UX. I really wish there was a way to include a custom css file in the <head /> BEFORE any js is loaded.
I find the lack of this functionality a major bummer as we really desire our Qlik iframe embeds to look as part of the application and not something duck tapped onto it.
If anyone has any tricks on using CSS to override default sheet styles I would be very grateful.