The catch is that emulation components expect subcomponents to extend UIComponent and Jewel components don’t. Theoretically it should be possible to mix both component sets if the Jewel components are contained in MX containers. However, I’m not sure what the styles would look like.
It may be worth it to invest some time in adding a more attractive emulation theme so you can enjoy the best of both worlds (although Jewel would still outperform emulation most likely). From: Alina Kazi<mailto:alinakazi1...@gmail.com> Sent: Tuesday, September 15, 2020 3:43 AM To: d...@royale.apache.org<mailto:d...@royale.apache.org>; users@royale.apache.org<mailto:users@royale.apache.org> Subject: Royale Emulation Components with Jewel Hi, Why Can't we use mx spark emulated components with Jewel. Output is in html and JavaScript for each case. What we need to do in sdk for that? There should be this possibility to use them simultaneously. I have worked on 2 different projects. One was pure flex to royale Emulation(porting). One is flex to jewel Development Now, I have a new project. I want it to be merger of both. So that client delivery and look n feel both could be possible 'on same' and 'in less' time. In Flex, there was no restriction of using mx with spark and vice versa. What are your thoughts? I have already shared API report for new porting project on my previous email/thread. Carlos, your reply on Jewel integration with mxRoyale and Sparkroyale. & Alex, for the possibility of Emulated components use with Jewel UI. And every one else who is involved in SDK Development. Thanks and Regards Alina Kazi
