Great news Alex! That's promising! :) Maybe that effort could end having real usable components that works in a high percentage...Once the components are working I think more people could eventually help to work in that front to bring the rest of components API. Maybe no 100% in the end, but could be a 80-90% aproximate to flex and API components
thanks! 2018-03-22 22:37 GMT+01:00 Alex Harui <[email protected]>: > Hi Folks, > > I am pleased to report that we have reached milestone #2 today. The > Button test in the flex-sdk checkintests passes in Royale without > modification on both platforms. It isn't perfect, but it proves that the > emulation components can work and minimize impact on migrating code. The > checkintest uses states and containers so we have shown that we can > emulate that Flex functionality in Royale. > > Peter and I, and hopefully Alina and one of her co-workers will continue > to build emulation components and try to get them to work in checkintests > and in Alina's app. It would be great if other folks could pitch in and > help as well. > > Thanks, > -Alex > > On 3/8/18, 7:37 PM, "Alex Harui" <[email protected]> wrote: > > >Hi Folks, > > > >As you hopefully know, we've started on creating new Royale component sets > >that more closely match the APIs used in Flex. These components will not > >be 100% backward compatible with Flex, but should go a long way towards > >minimizing the number of changes required to your code. > > > >I am pleased to report that we reached a first milestone today. We started > >with a simple 3-line Flex Hello World: > > > ><mx:Application > >xmlns:fx="https://na01.safelinks.protection.outlook. > com/?url=http%3A%2F%2F > >ns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com > %7C417e853c2a3 > >34c98c7f008d5856f12e5%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365616 > >34466593649&sdata=Hq6Oqu6yv8Bnc%2FwV7dWSTNGwofnUeuf32% > 2F56xsqQcoo%3D&reser > >ved=0" > > xmlns:s="library://ns.adobe.com/flex/spark" > > xmlns:mx="library://ns.adobe.com/flex/mx"> > > <mx:Label text="Hello World" /> > ></mx:Application> > > > > > >This compiles in Flex and produces your generic HelloWorld.swf. Then we > >renamed the mx namespace to point to the MXRoyale emulation components as > >shown below: > > > ><mx:Application > >xmlns:fx="https://na01.safelinks.protection.outlook. > com/?url=http%3A%2F%2F > >ns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com > %7C417e853c2a3 > >34c98c7f008d5856f12e5%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365616 > >34466593649&sdata=Hq6Oqu6yv8Bnc%2FwV7dWSTNGwofnUeuf32% > 2F56xsqQcoo%3D&reser > >ved=0" > > xmlns:s="library://ns.adobe.com/flex/spark" > > xmlns:mx="library://ns.apache.org/royale/mx"> > > <mx:Label text="Hello World" /> > ></mx:Application> > > > >We compiled this app with the Royale compiler and it produced a working JS > >Hello World. The placement of the text wasn’t exactly the same. That is > >still work in progress. But I think it shows the potential of reducing > >the migration effort (but it will not be zero). > > > > > >It would help greatly to have more folks helping to build out the > >emulation components. We are still smoothing out the process, but we have > >tried to document the process in the wiki [1]. If every committer were to > >add even one API a day, it would greatly speed up how soon we can provide > >this set to migrating users. > > > >Thanks, > >-Alex > > > >[1] > >https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fgithub.co > >m%2Fapache%2Froyale-asjs%2Fwiki%2FEmulation-Components& > data=02%7C01%7Cahar > >ui%40adobe.com%7C417e853c2a334c98c7f008d5856f > 12e5%7Cfa7b1b5a7b34438794aed2 > >c178decee1%7C0%7C0%7C636561634466593649&sdata= > etSIlHBrFra3P3Dt0JZb67BLR8O5 > >cO3HevWv4hloSWA%3D&reserved=0 > > > > > > > > -- Carlos Rovira http://about.me/carlosrovira
