I would caution against complicating MXRoyale to try to mix component sets. Royale component sets are not required to interoperate.
MXRoyale tries to override most positioning/sizing/layout CSS and use absolute positioning everywhere because Flex emulation of things like percentWidth are not CSS compliant. Having to be compatible with another component set's CSS sounds like a painful debugging challenge. If you want to try it, I'd recommend a new SWC that subclasses or forks MXRoyale to see how far you can get. MXRoyale did support, in theory, custom themes, and Spark supported Skinning. SparkRoyale is using skins in Spark Containers. Work could be done to support skins in the other Spark controls. In summary, folks who want to do the work to get a modern UI should just migrate to Jewel. If you want to upgrade the look of MXRoyale and/or Spark, we should try to emulate the customizing that was available in Flex. My 2 cents, -Alex On 6/18/20, 8:53 AM, "Yishay Weiss" <[email protected]> wrote: I wonder if UIComponent in MXRoyale could optionally add an ICSSClassInjector bead for each component which takes care of the typenames and ClassSelectorList. Maybe then we can use Jewel (or other theme) css. Just a thought. From: Carlos Rovira<mailto:[email protected]> Sent: Thursday, June 18, 2020 12:13 PM To: Apache Royale Development<mailto:[email protected]> Subject: Re: [Discussion] MXRoyale Theming Hi Yishay, modern look and feel requires CSS and some HTML structure to make possible some visual things. That was the main task when doing Jewel, take Basic components and make it generate the additional HTML structure and sync with a set of CSS rules. Before doing it, I did MDL set (that could be something similar to Spectrum). I decide to abandon that path since it implies the set dictates what can be done and what done. IOW. If you want to make a Flex MX Accordion, you must count with something similar in that set. That use to be not the case in many cases. So for that reason the only path I saw possible was to create our own code and themes, so we can change look and feel on the HTML structure we provide, instead of adapt to external UI sets that could not have the components we need or the functionality we want in the components we share. I think the best option could be to make MXRoyale components generate HTML structures like Jewel. Then you could use jewel themes or even create a MXRoyale theme based on master JewelTheme just my 2... El jue., 18 jun. 2020 a las 9:38, Yishay Weiss (<[email protected]>) escribió: > Hi Guys, > > The work put into MXRoyale so far means it’s probably the path of least > resistance when porting a Flex app. What are the challenges in applying a > modern looking html theme such as Jewel or Spectrum on an MXRoyale app. > > Any thoughts welcome, > Yishay > -- Carlos Rovira https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C680270df992c4b9ea04808d8139fc549%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637280924217045583&sdata=VOJMusTPuPzrmecyMGonWRvDBLcOiAaMxj%2BrIuoqmBw%3D&reserved=0
