carlosrovira commented on pull request #1056: URL: https://github.com/apache/royale-asjs/pull/1056#issuecomment-762403859
Hi Rupert, each path has its pros and cons. I'll try to explain both: - Emulation path: You'll get to reuse most of your code base with little changes, so it's the fastest way to migrate. The problems are two: look and feel and themes are not done, so depending on your users that can be or not an issue. The other problem is that not all is emulated but will be more over time. Depending on your needs you can plan to help in that front, join others or contract people to help you. - Jewel: You'll need to recode, so your codebase can't be reused the same as emulation, but in my experience for my migration I could change just little things in MXML or add some beads here and there and get my app to work. But that's my case, others can be very different. The pros: Jewel has look and feel (enough to be used in mainstream scenarios) and is more suited for the future (responsiveness, themes,...). The cons: still need some things to be done. For example, there's no Tree, Multiple selection, AdvancedDataGrid,...are some of the things still undone in Jewel. HTH ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
