I think the reason for the overlay is that by this we are tricking the FlashBuilder to use Falcon instead of the old compiler. It should be possible to have Falcon separate from the normal compiler. It's just that FlashBuilder will probably not be albe to use it that way. Probably IntelliJ would support this withn a few hours, Flexmojos within a few weeks and FlashBuilder never ;-)
You shouldn't implement this in the develop branch but create a feature-branch instead that forks off the develop branch. This way your changes are available to anyone interested and as soon as the feature is finished, you merge it back to develop. Chris ________________________________________ Von: Erik de Bruin <e...@ixsoftware.nl> Gesendet: Mittwoch, 2. Juli 2014 09:33 An: dev@flex.apache.org Betreff: New Flex to JS project Hi, I'm working on creating a way to publish vanilla Flex SDK projects to JavaScript on latest gen browsers. This project consists of several sub projects, and I'm wondering what is the best way forward with regard to contributing them: 1) two new namespaces and accompanying projects in the main Flex SDK: vf2js_mx and vf2js_s. These namespaces will contain shim objects for (you guessed it) MX and Spark components. 2) two new code paths in FalconJX: one for AS and one for MXML 3) a new JavaScript library for the components and shims for AS classes 4) a testing framework for the JS components, loosely based on Marmotinni Questions: A - I would very much like to work in the 'develop' branches of the projects involved, but especially on the part of '1)' I'm not sure if I did it right. All tests I can think of seem to pass, but maybe someone has the time to do a code review on a branch that I can publish? B - In order for this to work, FalconJX needs to be part of the regular SDK distribution. Folks who did this on the FlexJS overlay: what does it take to make FalconJX part of the SDK? That's it, for now :-) Thanks, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
