Hi Takeshita-san, As the others explained, the example isn’t set up for Maven. It is a “fewest changes” migration from Flex and Flex didn’t support Maven so the folder structure of the sources is not conducive to Maven and I don’t want to spend the time making those kinds of changes.
Why do you want to build it yourself? You can grab all of the output files from here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/ If you are just looking to do some testing, there is an example in this comment: https://github.com/apache/royale-asjs/issues/391#issuecomment-463181901 HTH, -Alex From: Takeshita Shoichiro <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Sunday, February 24, 2019 at 2:29 AM To: "[email protected]" <[email protected]> Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread) Alex, I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail. (no result) Under the following directory, I ran mvn clean install. \royale-asjs\royale-asjs\examples\mxroyale Did I use the wrong procedure? Appreciate your advice. Best regards, S. Takeshita On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[email protected]<mailto:[email protected]>> wrote: First, lower your expectations 😉 Then, make a copy of your code. And read this: https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.github.io%2Froyale-docs%2Fcreate-an-application%2Fmigrate-an-existing-app%2Fmigrate-from-flex.html&data=02%7C01%7Caharui%40adobe.com%7C8d5cba5372d7412f141408d69a42e960%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636866009536024185&sdata=aI4nV%2BsLNqDwJboZdVsxeUSy70W0afVDWprebWy%2BiVQ%3D&reserved=0> Good luck. I’m about to stop work for today as I am on the road in the middle of the US. I’ll be back on the west coast of the US in about 24 hours. Thanks, -Alex From: Takeshita Shoichiro <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, February 22, 2019 at 10:22 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread) Alex, got it. Cool. I would like to try conversion of our mxml using this emulation approach. To do that, how I can? Appreciate your help. Thank you, S. Takeshita On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[email protected]<mailto:[email protected]>> wrote: Hi, Takeshita-san, For these examples, I also think the Royale version loads faster. It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it. The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years. To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one. It should show an AdvancedDataGrid with a GroupingCollection. HTH, -Alex From: Takeshita Shoichiro <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, February 22, 2019 at 10:04 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread) Alex, thanks for the link information. I understand Flash version takes more time for loading SWF than new Apache Royale. Is my observation correct? It seems what I'm looking for is the Advanced Data Grid. It seems not implemented in Royale yet. But anyway, the progress seems to be great. T-san On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[email protected]<mailto:[email protected]>> wrote: Hi, The examples using emulation components are in examples/mxroyale. The most sophisticated example is a migration of a subset of Tour De Flex. It is still a work in progress. The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FTourDeFlexMigration%2FlastSuccessfulBuild%2Fartifact%2Fexamples%2Fmxroyale%2Ftourdeflexmodules%2Fbin%2Fjs-debug%2Findex.html&data=02%7C01%7Caharui%40adobe.com%7C8d5cba5372d7412f141408d69a42e960%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636866009536024185&sdata=CAbPHQig1AQ0LvYEn3PWDEYax4iV%2FXNLxHKX2hQN6zk%3D&reserved=0> The Flex version it is based on is here: http://flex.apache.org/tourdeflex/index.html<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflex.apache.org%2Ftourdeflex%2Findex.html&data=02%7C01%7Caharui%40adobe.com%7C8d5cba5372d7412f141408d69a42e960%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636866009536034190&sdata=5V2TzEOF2mvnnzw5Flr7naTyFrUSdAdl3KomJ2LubYc%3D&reserved=0> The repos do not contain any serious example of migrating Flex to Basic The focus of Basic was more about code size and performance than ease of migration. We did migrate the FlexStore example. It is in examples/royale/RoyaleStore. The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fflex-examples%2Ftree%2Fdevelop%2FFlexStore&data=02%7C01%7Caharui%40adobe.com%7C8d5cba5372d7412f141408d69a42e960%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636866009536044195&sdata=tfAFYkNF%2BjaWk4IGRIp4Vm%2BU4QsPByt5BQ8aPj0NDHY%3D&reserved=0> There aren’t any examples running on a server at the moment. Still, Harbs ported his app to Basic and he can tell you more about it. -Alex From: Takeshita Shoichiro <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, February 22, 2019 at 5:01 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread) Alex, Thanks a lot for providing me a set of choices to go. I need some time to decide after doing some benchmark. I'm interested in modern UI that may make users happy. And also need to think about minimizing the migration effort to save time and money. Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation? Best rega On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[email protected]<mailto:[email protected]>> wrote: 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]<mailto:[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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C8d5cba5372d7412f141408d69a42e960%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636866009536044195&sdata=r1qjxHmt7JX2dCIwG%2Br1%2B5vmseFblmDnwWfQH5YJ%2FEo%3D&reserved=0> -- Shoichiro Takeshita 武下 祥一郎 -- Shoichiro Takeshita 武下 祥一郎 -- Shoichiro Takeshita 武下 祥一郎 -- Shoichiro Takeshita 武下 祥一郎
