Quoting Gordon Smith <gosm...@adobe.com>:
The possibility of transcoding ABC -> JS (rather than AS -> JS, MXML -> JS, CSS -> JS, and .properties -> JS) has come up on another thread. I should mention that this approach is the one that the architect of the Falcon compiler (Chris Brichford, who recently left Adobe) recommended for getting to JS. Bernd Paradies, who did FalconJS, was on another team and decided to run with AS -> JS.
You say he decided to fun with AS -> JS, this is because he used a implementation of a tree walker that is still traversing the AST correct?
What makes that code REALLY confusing is although you say he is using AS, there is a huge amount of ABC opcode in that code he wrote.
SO I will say to anybody, in the current state of the FalconJS compiler, you NEED to know opcdes to be able to fix anything.
This is hwy I kinda got bummed out, I don't know that stuff so it's like walking in the dark but knowing your standing on the ground at least.
Knowing the cookie jar is right in front of you but has a lock on it... :)
One advantage of ABC -> JS is that it solves the problem of having a 3rd party SWC that you don't have source code for but want to transcode to JS.
Couldn't we write an intermediary SWC parsing tool that could create classes with native stubs (by parsing the ABC in the SWF), like Frank has done, then feed those into the parse session?
One disadvantage is that you have to have a good understanding of the ABC format and its opcodes.
I would say this is a major disadvantage in this open source environment.
- Gordon
-- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
