Sounds interesting. Is there any way to get more information on what kinds of changes are going to be made? More comments in-line.
On 7/2/14 12:33 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >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. Just wondering after seeing all the branch/merge discussion: are you sure you can't auto-generate the shims via a custom back-end for FalconJX? It could suck in your JS files as well if that helps to compute the shim. Then you may not need to branch/merge at all and just be a separate swc project or two (or three). > >2) two new code paths in FalconJX: one for AS and one for MXML If the changes going in here are not going to interfere with FlexJS, I don't see why you need to branch now. FlexJS is in alpha, so having other alpha/prototype code in its release shouldn't be a killer. > >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? I'm not quite sure what this means. Why can't it be an overlay? If Chris is right and you want FB integration such that building the FB project runs FalconJX, that part is in the flex-oem-compiler project. You should be able to follow what I did in git history and get an idea of what you need to change, but there is one possible gotcha: FB runs in Java 6 and I believe GCC required Java 7. I'm not sure if there is a way to have FB's Java 6 call into GCC without recompiling GCC to Java 6 (which is an option I think). HTH, -Alex
