Hi Serkan, That looks more like I would expect. I guess you should have an emulation of resourceManager which will make a lot of those errors go away. Feel free to try to build it yourself. I also see that you are using Operation and other parts of RPC. We should probably emulate that as well.
And I see that you are using some Spark components we haven’t emulated. For at least now, you might be able to map to existing MX versions via the manifest in SparkRoyale with the “lookupOnly” attribute. I won’t have much more time this weekend. Later, -Alex From: Serkan Taş <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Friday, September 28, 2018 at 11:15 PM To: "[email protected]" <[email protected]> Subject: Re: Work on Emulation Hi Alex, After updating the path definitions i got the list of errors : https://drive.google.com/open?id=16U6awiZCoiunYWgfd_SWHwbppnAImhso<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D16U6awiZCoiunYWgfd_SWHwbppnAImhso&data=02%7C01%7Caharui%40adobe.com%7Cfe4e7e254f014bc0d53e08d625d2f182%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636737985264501538&sdata=6ZSC7C6%2FzK6SQy970Fy3wpU0y2xBz1CNm7vEsu3j%2F9Q%3D&reserved=0> Thanks, Serkan 29.09.2018 03:48 tarihinde Alex Harui yazdı: Hi Serkan, Your -library-path and -js-library-path need a += (not just “=”) otherwise you reset the list of libraries on the path instead of appending to it. HTH, -Alex From: Serkan Taş <[email protected]><mailto:[email protected]> Reply-To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> Date: Friday, September 28, 2018 at 2:03 PM To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> Subject: Re: Work on Emulation Hi Alex, I replaced the namespaces to xmlns:mx="library://ns.apache.org/royale/mx" xmlns:s="library://ns.apache.org/royale/spark" compiled with options : Using Royale Compiler codebase: /home/pinara18/royale/apache-royale-0.9.4-bin-js-swf/royale-asjs/js/bin/../.. Using Royale SDK: /home/pinara18/royale/apache-royale-0.9.4-bin-js-swf/royale-asjs/js/bin/../.. MXMLJSC +royalelib=/home/pinara18/royale/apache-royale-0.9.4-bin-js-swf/royale-asjs/js/bin/../../frameworks -sdk-js-lib=/home/pinara18/royale/apache-royale-0.9.4-bin-js-swf/royale-asjs/js/bin/../../frameworks/js/Royale/generated-sources /home/pinara18/royale/pinaragroup/PinaraUI/src/com/likya/pinara/main/PinaraUI.mxml -library-path=/home/pinara18/royale/pinaragroup/PinaraUI/libs -js-library-path=/home/pinara18/royale/pinaragroup/PinaraUI/libs -source-path=/home/pinara18/royale/pinaragroup/PinaraUI/src,/home/pinara18/royale/pinaragroup/PinaraUI/locale/{locale} -services=/home/pinara18/royale/pinaragroup/Pinara-0.0.1/WEB-INF/flex/services-config.xml -locale en_US tr_TR -o .PinaraUI.swf and the result is : Loading configuration: /home/pinara18/royale/apache-royale-0.9.4-bin-js-swf/royale-asjs/frameworks/royale-config.xml /home/pinara18/royale/pinaragroup/PinaraUI/src/com/likya/pinara/main/PinaraUI.mxml(2): col: 1 Error: This tag could not be resolved to an ActionScript class. It will be ignored. <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009";<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7Cfe4e7e254f014bc0d53e08d625d2f182%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636737985264511548&sdata=XKMzeap%2FrtMK%2Bi%2BBWmdwtFzYghlPz%2FTNhJwEV8VuFis%3D&reserved=0> ^ /home/pinara18/royale/pinaragroup/PinaraUI/src/com/likya/pinara/main/PinaraUI.mxml(2): col: 1 Error: This tag could not be resolved to an ActionScript class. It will be ignored. <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009";<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7Cfe4e7e254f014bc0d53e08d625d2f182%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636737985264511548&sdata=XKMzeap%2FrtMK%2Bi%2BBWmdwtFzYghlPz%2FTNhJwEV8VuFis%3D&reserved=0> ^ 3.778434625 seconds I tried changing the application to <mx:Application> and <js:Application> got the similar errors. 27.09.2018 22:49 tarihinde Serkan Taş yazdı: Ok, I'll check it and replace.
