I think I mostly agree with your point. We want to make styling easy as possible. My point was that we have lots of work to do, and sometimes we have to "settle" for providing the same way of doing things as folks would do if they didn't use Royale. So, if you didn't use Royale, chose some CSS theme like Bootstrap or MaterialDesignLite and wanted to change something, what would you have to do? I'm not quite sure what that is, but I think you may need to know that CSS rules the theme designers used in order to override them. I'm not sure you can "un-set" a style defined in a CSS theme or not.
Now if you have a better idea and can implement it or get a volunteer to implement it, great. But for now, I'm going to be happy if the CSS our users can define can override styles in the SWCs. My 2 cents, -Alex On 1/8/18, 11:19 AM, "Olaf Krueger" <[email protected]> wrote: >Hmm, I am not sure if we're misunderstood... > >I don't want to say that we should go the Flex way or that we need >something >like skinning. >I just would like to say that from my point of view it is important to >provide a possibility to overwrite CSS styles in that way, that no >default >styles remain in the HTML. > >As long as we target HTML I think the easiest way is to just apply >HTML/CSS3 >styles to change the look and feel of components/elements. > >However, maybe I get something wrong... I'll continue for now with >exploring >those things... > >Thanks, >Olaf > > > > > >-- >Sent from: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy >ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7 >Cb7df7d8be61147e0303908d556ccb423%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7 >C0%7C636510359552480505&sdata=15HOLwMdIXqtQDzOyzRNf6fZCbiTTx%2BcgX3NRY%2Bz >Xtc%3D&reserved=0
