Would I even need to fork it? I mentioned to Josh that I use MXML and Feathers extensively for these audio apps I am about to release on Android which means I have a high stake in the tech at the moment.
That tinkerer side of me feels I could do something about this but I am at a loss of what I need to do to get the ball rolling. If I could get this project to work, this would be huge for the project since the Falcon compiler could actually start to be used in production. It also means I would have a monetary reason to be able to contribute to the development and learning deeper of the compiler. Alex, I need some advice man. :) Where would I even begin? Below is what I posted on Josh's Feathers SDK issue, just me talking to myself. Mike " I'm putting this here just so if anybody else reads it and wants to chime in. Background; I have worked extensively with the Falcon compiler mainly in creating/writing the FalconJX compiler FlexJS uses to cross compile AS/MXML to JS. The problem I see is that I wrote a traversing framework that was a visitor and walker implementation which was an abstraction outside of the actual AST Falcon produces when it parses AS3. The actual MXML compiler uses JBurg and is completely outside of my knowledge base. I don't off the top of my head know of any hooks to extend MXML generation or even how to start. I do understand "what" the original compiler does as far as setting up AS to be compiled again so the theory is there for me but I am totally lacking in the vision from start to end of what I need to do to get Falcon to produce different byte code since there is no code generation pass. Anyway, I think this could be HUGE for Starling and Feathers if it could be done since then we could add a whole bunch of specific things that could enhance the dynamic nature of constructing a Starling/Feathers mobile/desktop app."
