I think SourceMaps for MXML were working in some simple cases in 0.8.0 but there was a bug that Josh fixed that we were going to release in a 0.8.1. Given we're creating a new project, we'll probably call it Royale 0.9.0 and get it out shortly after we get everything else in the project up and running. I'm currently playing around with different ways to package Royale so we don't have to use the Installer.
Regarding debugging in FlashBuilder, the original vision for FlexJS development workflow was that you would build both a SWF and JS version and debug your SWF version in FlashBuilder. Debugging using Flash has some significant advantages as the Flash runtime will: -not allow some kinds of type mismatches -verify that modules conform to interfaces -not allow unexpected access of protected and private members -not allow method reassignment -catch all kinds of assignments to missing properties And more. Debugging the SWF version should save you significant time. The goal was to make the UI widgets look the same, but at minimum, we want the widgets to take the same space on the screen and the layouts to place things in pretty much the same place so that you can test your code in Flash. Then, once you have that working, you can try the JS version and in theory, once we fixed enough bugs in the JS version, there should be little or no need to debug JS in the browser. That's not true right now, we've got plenty of bugs to fix where the JS runs differently than the SWF version, but that's the basic theory. IOW, you want to test your code in a more rigid environment (Flash) before trusting that it will run in the less rigid environment (JS in the browser). I still believe that debugging in Flash will pay off in catching errors sooner, especially for bigger more complex apps. My 2 cents, -Alex On 9/26/17, 8:32 AM, "Idylog - Nicolas Granon" <ngra...@idylog.com> wrote: >Hi Piotr, > >Thank you for this information. >Following your reply, I have read Josh Tynjala's papers and, as I >understand it, it is possible to use source maps for debugging with FB >but it works only with pure as3 source code, not mxml code. Furthermore, >the actions are a bit convoluted (you have to load the map from the >browser debug tools, go back to the IDE...many extra steps and not very >convenient). > >It seems that the work Josh has made for tight integration between VSCode >and FlexJS is amazing. > >I will (try to) go that way. VSCode is a good editor, and I don't mind >using it for our FlexJS projects (we will keep Eclipse for Java and >Coldfusion). >Moreover, we are also evaluating ReactJS as a replacement for SWF apps, >and use VSCode as an editor. > >Many thanks again > >Nicolas Granon >
