Hi T-San, There is no single perfect migration strategy for Royale. You will have to choose a path.
One way to think about migration is that there is your starting point, some amount of work, and an ending point. Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components. If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice. A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components. If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice. A couple of folks that I know of are trying to use the Emulation set. The goal of the emulation set is to minimize the amount of changes to your MXML and AS. A fair amount of Tour De Flex has been migrated using the Emulation components. There is still work to be done, but there were very few changes to the MXML and AS. All of the changes are in the emulation components. To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance. Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change. If you choose one of the other options and change your code, then only you benefit from that change. I wish I could convince more of the other Royale committers to help with the emulation components. As the clock marches towards 2020, folks will have less and less time to move. If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself. In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain. So, think about it, and pick one of the three strategies and let us know what choice you make. And feel free to ask more questions. HTH, -Alex On 2/21/19, 4:46 AM, "T-san" <[email protected]> wrote: Carlos, Thanks for your advice and work. Let me clarify several things. 1. Do I need to convert mx coding to Jewel? 2. If so, is there any useful information on how to do that? 3. Is there user guide available for Jewel? Or I have to read the Jewel source to study? And if you have a time, would you make your sample code complete for build? I'd also need to know how to build it since at this moment I do not know how to create pom.xml. T-san -- Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&reserved=0
