I believe the Jewel it may be your right choice once you will be able to build your application.
The thing is that having emulation components for all your app parts you may need to at the end start to replace it one by one by Jewel or third party things. I would recognize what you are missing at first place. Once you finish basic POC for management, try to work on building whole app. I would start comment out all places which are using external libraries from your list. Than start building - if it's failing because some component is missing you need simply wrote that component. - See on the branch with emulation - there are plenty of components as an example written by Alina. Once you reach the point of building for app with commented out libraries, that would be the place where you can think about third party replacement for them. There is also a chance that you poses some more skills in the process and write some missing part on your own. Migration is a long way... That's the reality. One more thing - we are all here wanted to help, have in mind that is volunteer project, so it sometimes takes time to get the response. Only fraction of us working here for a full time with that stuff. Harbs was the one of the person who was patience with his product in case of migration and I believe it was worth. All the best! Piotr On Wed, Jul 18, 2018, 8:36 AM chembali <chemb...@hotmail.com> wrote: > I believe I have convinced the management to go with Apache Royale as part > the Deflexing effort of our Flex applications. The first project is going > to > be very important and they are going to monitor it closely. > > I want to be realistic and figure out the best approach and I need your > help > on this. I am an enterprise java developer with working knowledge of the UI > technologies. I understand the Flex programming model but don't have any > hands on experience. I tried to get an emulation component working. I > struggled. I was able to get the emulation working by cut/paste/edit with > the Royale class implementation but this may not be the best approach. > > I now realise that my developer and I don't have the necessary skillset to > get the emulation components implemented in a timely manner. This is a huge > risk. How can I mitigate this risk? Is it realistic to count on you guys to > deliver the emulation components ( not sure )? Can I go with the Apache > Royale native APIs ( Jewel, Basic, Express etc ) for the mx/spark > components > that are not emulated? > > Also the 3rd party APIs used in my application are > > AlivePDF.swc > Cairngorm.swc > CairngormEnterprise.swc > diagrammer.swc > drumbeatinsight.swc > granite.swc > kap-layouts-1.6.2.swc > MaskedTextInput.swc > multicolumnform.swc > svg-1.6.2.swc > flex-iframe-1.4.6.swc > ObjectHandles-1.0.0013.swc > > Any experience/recommendation in handling the 3rd party libraries? > I am working on the Prototype for the Management currently. But I was > thinking of trying to get the Application ( all components ) compiled using > the royale-asjs by adding stub for the missing mx/spark components. Any > other recommendations? Again thanks a bunch for your help on this. > > > > -- > Sent from: http://apache-royale-development.20373.n8.nabble.com/ >
