> > >> Well Roland, I looked at the code again. I need to take it down a notch, > there are about 3 different things I am looking at. > > 1. Direct communication from an IDE to Browser over a socket. > 2. How we could use existing code, IE SWFBridge. > 3. If writing a plugin using this framework is relevant. > > When I first looked at it I was more looking at how they were > communicating with the FlashPlayer not the actual use of ActionScript to > extend Eclipse. > > They are just sending commands from a parsed ActionScript/MXML file, > creating an AST tree in Eclipse using the parser, sending that AST back to > the Player and loading it into there ActionScript AST tree that then is > used to send real commands back to Eclipse. > > This is crazy, but I actually understand what they are doing, hmm this > looks like something I would have tried if I had the time. : >
Ok, I'm kind of of following, but I'm not sure I understand what the AST represents, is that the AST of a source file? So basically you create an alternative view for an actionscript file? So, in the case of MXML, you woudl basically receieve an AST that represents the MXML file in question, and the Actionscript view is just supposed to interpret that AST and render a visual representation? Would that more or less describe what is going on? (Just trying to grasp the patterns here...)
