I work across different editors, in work (Professional skin) and at home(Default Skin). Often when I create an editor I want it to work (look nice) both at home and in work. Which means I have to litter my code with IsProSkin and alter the styling of elements.
I would like to suggest some quality of life changes, which will make not only my use case easier but asset store creators lives easier too!
I think it would be really useful if we could define the Pro styling similar to how we can style by Pseudo states
I understand the : operator might not be the most correct, but hopefully you get the idea.
I also really like the new @2x notation for automatically loading high DPI resources! I would like to suggest further support to @, which would automatically load the * @ * resource if the user is using the Professional editor skin.
e.g.
Thanks for your suggestions! We are aware this area of our styling solution needs some improvement. We are working on proper theming support for UIElements, which is essentially having a global StyleSheet that you work against. In the new world, you would be able to use USS variables for styles that should match the current theme. So you can just use a single USS file but instead of saying color:red;, your would put color:var(--main-background-color); or something along those lines.
For the @2x images, right now, if you use the resource() function (instead of url()) in USS you should get this functionality. But it’s something we do want to expand to url() in the future.