Right now, you can play with FlexJS by getting a FlexJSOverlay.zip and following a set of instructions. The reason it is called FlexJSOVERLAY is because it overlays a hacked up copy of framework.swc on top of the framework.swc in a working Flex SDK.
Framework.swc is used by MXMLC when it compiles your code as you type. Classes in framework.swc are not use in Falcon compiles your code. I think I've now identified the set of classes that MXMLC was counting on, and built "shim" classes for them in FlexJSUI.swc, so that we no longer need to overlay framework.swc. The latest FlexJSOverlay.zip I just posted no longer does the overlay and doesn't have a framework.swc at all, MXMLC finds the shim classes in FlexJSUI.swc. That said, FlexJSUI.swc now contains around two dozen shim classes. I now want to separate them into their own MXMLCClasses.swc. This will require some re-organization of classes in frameworks/as. I want to make sure everyone is mostly checked in before I go and do this. No longer having to hack framework.swc has one other big benefit. It simplifies the steps to packaging so it now starts to make sense to manage the packaging as part of an Ant script, so once I get the SWCs refactored I'm going to create an Ant script that makes the FlexJSOverlay.zip. I'll probably keep the name for now until after we get a true installer ready. So, let me know if it is safe to do this refactoring. -Alex
