I think we have zeroed in on the point of 1a. Great! :-) I don’t understand what you mean here. I don’t understand how component styles could be assigned.
To be clear I mean something like this: <js:Application xmlns:fx="http://ns.adobe.com/mxml/2009 <http://ns.adobe.com/mxml/2009>" xmlns:js="library://ns.apache.org/royale/basic <library://ns.apache.org/royale/basic>" xmlns:j="library://ns.apache.org/royale/jewel <library://ns.apache.org/royale/jewel>"> <fx:Style> @namespace "http://www.w3.org/1999/xhtml <http://www.w3.org/1999/xhtml>"; @namespace svg "library://ns.apache.org/royale/svg <library://ns.apache.org/royale/svg>"; @namespace j "library://ns.apache.org/royale/jewel <library://ns.apache.org/royale/jewel>"; j|TextButton { padding-top:10px; } </fx:Style> </js:Application> Are you saying that this will work? If yes, please explain how. Thanks, Harbs > On May 14, 2018, at 5:26 PM, Carlos Rovira <[email protected] > <mailto:[email protected]>> wrote: > >> >> 2. Client code cannot declare default CSS in their app for all Jewel >> components of a specific type. In other words j:Button{background-color:blue} >> will not work because a Jewel Button does not have a “Button” class name. >> > > No. That would work. You can check in Jewel "sass" folder where all > components define the css that links beads and classes. > In that case we don't have anything for Button at this time, but most of > the rest have declarations like j|{Component} and beans assigned. > Then mostly all html styles are in themes in the styles that are as you > already notice "jewel {component}"
