So in trying to get the JewelExample to work, I think I understand what Carlos is trying to do with the Jewel Theme. I'm going to attempt to clear up some confusion and propose a plan. Note that below I am not using actual file names for brevity and clarity.
A Theme in Royale is the same as it was in Flex. It can be a SWC with code and assets (and some CSS), or just a simple CSS file. You can specify more than one theme to the compiler. The themes/JewelTheme is not set up properly right now. It has both a red.css and blue.css file that are being included in the JewelTheme.swc. The compiler has been taught to include all css in a SWC in the final output. Really, in the themes folder there should be a JewelBlue folder with just a jewel-blue.css file in it and a JewelRed folder with just a jewel-red.css file in it and a JewelTheme folder with only shared assets. In Ant, command-line, or IDEs, the user would specify both JewelTheme.swc and either jewel-blue.css or jewel-red.css as themes. For Maven, it is not clear how to make a simple css file be a Maven artifact so for other CSS-only themes, so we still build a SWC with only the .css file in it. See the basic.css in themes. IMO, that’s the Royale way for choosing your "primary" color of the theme at compile-time. I think there may be customers who already know this and will expect it to work. I don't see the need to develop some other way like additional compiler options and substitutions. If someone like Carlos wants to use SASS to generate the jewel-red.css and jewel-blue.css, I guess that's ok as long as that isn't part of the build such that every developer and patcher needs to install SASS. We can call the "final" css files that are committed to the repo the source, IMO. Thoughts? -Alex
