Mike, What are you planning to do with your Friday work? Assuming I get time to work on my MXMLClassDirectiveProcessor today or tomorrow, I think I want to teach it to spit out the goog code, but then I need the AS output to also do the same. Maybe I'll just try make the changes for the AS output myself in the current Reducer/Emitter classes?
You might want to feed an MXML file into Falcon and watch it hit the MXMLClassDirectiveProcessor APIs. All I"m going to do is override each of those APIs and instead of sticking ABC code in the instruction lists, stick in single instructions that are a string of JS. That's my understanding of how JSEmitter works today. On 12/10/12 1:05 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote: > > Quoting Alex Harui <aha...@adobe.com>: > >> >> >> >> On 12/9/12 11:28 PM, "Frank Wienberg" <fr...@jangaroo.net> wrote: >> >>> Mike, this is really great news! Wow! I'd really like to get my hands on >>> that code of yours! >> I'd like to see it too. FWIW, I think I have successfully found a way to >> get FalconJS to call my MXMLClassDirectiveProcessor so I think I can now >> start generating JS from MXML. > > Like I told Frank, I will get the code up ASAP. FalconJS is just "to > deep" for me Alex. I don't feel comfortable investing a huge amount of > time hacking something I don't understand. > > I for some reason this new design pattern doesn't work out, I will > force myself to learn FalconJS's internals. I spent 8 hours on Friday > trying to mangle code around and I found myself hacking a couple > things like super because the implementation of the BURM and other > renderings were so complex. Yes I was stepping through the code and > saw exactly what it was doing. :) > > On a side note, I would love to see your implementation of the > MXMLClassDirectiveProcessor. I would like to see if I can make a > traversal just like I have done here with as AST. > > Mike > > >>> What else do you need? Would it make sense if I helped coding stuff? >> Frank, if you plan to contribute code, I think it would be a good idea to >> file a CCLA from your employer and an ICLA for yourself. Even though >> Jangaroo is OS and AL, it is still important that contributions are >> voluntary and ok'd by your employer. And significant contributions of >> existing code may need a software grant. >> >> http://www.apache.org/licenses/cla-corporate.txt >> http://www.apache.org/licenses/icla.txt >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
