New thread:
On 5/27/15, 9:52 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: >Well, when I said "teach" I just meant getting into the code. Really, I >know the base part of the compiler and the walker/visitor framework well >;-), so getting FalconJX to use an HTML.swc would be exactly what I am >looking for to do. > >This is where you can keep doing what you are good at and I can work on >what I am good at(code rendering). > >Can I ask you to start another thread and outline what you see needs to be >done to accomplish what is in your mind dealing with FalconJX and the >HTML.swc? If you can just brainstorm, then I can ask you questions to fill >in the gaps that I am not seeing. > As I see it, FalconJX should just be able to grab some SWCs and cross-compile some AS based on definitions in the SWCs. Right now we feed it playerglobal/airglobal and FlexJS swcs with UIBase widgets, but in theory, as Josh suggests we should be able to replace those SWCs with just: jsglobal.swc: Object Number String <what else>? HTML.swc: Window Event UIEvent MouseEvent HTMLElement etc. Then folks should be able to test drive FalconJX by running some AS through it to get any JS they normally use in their web apps, and we should be able to stop writing any JS at all. All files in flex-asjs that are currently .JS files should be able to be written in AS and cross-compiled with only those two SWCs. I can tell you that it would probably have saved us much time if we had this already. It is painful doing .JS code simply in the writing of ‘this.’ and ‘prototype’. Anyway, that’s as far as I’ve thought on this subject. As you said in another thread this is where we’d have to prove there are no hard-coded dependencies in Falcon/FalconJX on playerglobal/airglobal. OK, one more thought: there may be reverse-engineering issues about replacing playerglobal/airglobal, but I was hoping we might find some Tamarin code laying around that has what we’d start with for jsglobal.swc. -Alex
