Hi all, One major pain point of developing custom themes is the fact that you can only specify 1 stylesheet as the user agent stylesheet. I develop custom themes to be used by application developers that are somewhat popular but this has been problematic for quite some time. Others, like Alessadro Parisi have also voiced their interest in having this (he developed MaterialFX also a quite popular theme).
Any complex custom theme will at some point hit this issue. In my case JMetro / Transit have lots of CSS rules and 2 different styles (light and dark) making it very cumbersome (and not desirable or even feasible) to fit into 1 single stylesheet. What ends up happening in my case and probably others (90% of themes I know of use scene stylesheets rather than user agent stylesheet for the reasons mentioned) is that often users give up and just copy the stylesheet to their own app and tweak it. This is not ideal for various reasons, among them are: - Updates I do to my library will be hard to get through since they just copied the css code and tweaked it. They'll need to copy again and tweak again which most will probably not do. - Copyright and attribution. This breaks copyright, ideally they would use the library rather than copy the code into their app. - Themes are not just CSS and sometimes contain other things like custom skins, controls, etc.. Copy and Pasting is not ideal. (side note: Themes being composed of scene stylesheets means all styles set in code by the developer will be overridden by these stylesheets. Also these stylesheets will "compete" with stylesheets created by the developer in which case only the rules with the greatest specificity will win. This is a major hassle for app developers using these themes and why they sometimes prefer to just copy and tweak the stylesheets) I wonder, is this on the near future plans? This seems like it could be a quick win (?), i.e. instead of accepting just 1 stylesheet to be the user agent stylesheet, being able to accept multiple. This would also be one quick first step towards supporting the concept of Themes (there's already an issue that's meant to support it) or even if not supporting the concept of Themes would make a huge difference for custom Theme development. Thanks! -- Pedro Duque Vieira - https://www.pixelduke.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Sem vírus.www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
