Very cool. I'm wondering: -Does it really need its own build or is it just part of FalconJX and FlexJS builds? -Does it really need its own installer? Currently the FLexJS install downloads and installs part of the current Flex SDK. I'm wondering if that install should set up another folder full of VF2JS stuff. The remaining "trick" is to manage flex-configs and flexlibs so that we don't get conflicting definitions. Then it isn't an overlay per-se, but rather, just another SDK.
Thoughts? -Alex On 8/1/14 5:10 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >Hi, > >An update on my VF2JS progress: > >- merged/moved the code from the various feature branches to the 'develop' >branches: > - flex-sdk: NO CHANGES were made; VF2JS will be an overlay over a >regular >SDK > - flex-asjs: added 'vf2js' directory and two examples; added two targets >to 'build-example.xml' > - flex-falcon: added a separate code path and tests for VF2JS >- deleted the published VF2JS feature branches > >Among the many (many!) ToDos are: >- write README with basic instructions and some expectation management >- add VF2JS build to 'apacheflexbuild' VM for nightly builds >- add VF2JS to Installer (allow for selection of existing Flex SDK >directory, instead of empty one) >- add launch config >- add support for more Spark and MX components and their members >- increase (cross-) compiler support for VF2JS > >EdB > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
