Cool, don't worry about it. I just finished up some other work and I am back into the compiler refactoring.
Funny thing dawned on my last night. I have dyslexia so sometimes I think about things backwards. I was thinking about what you said about you and Peter wanting this new project path to work out. And I was like, why does this matter, why can't they just use the FlexJS emitter to create their JavaScript. Then as I was finishing up some commits last night, the light bulb went on. HAHA They need the DOM! So, the I realized how important it is to just use the FlexJS emitter and break it apart and configure it to death. Example, don't emit goog doc comments, etc. Plus, we are going to need some special metadata for these DOM type and Library SWCs, like we did in Randori. We need to know if a class is exportable and allow for name, package transformations. There are a couple other things from porting frameworks that suck, one is like jquery that has 4 different versions of a method, we can't use strict argument checks with that unless we call the methods like; - show1(arg1) - show2(arg1, arg2) Roland did this in the JQuery lib that he created with his doc parser. It's kind of weird because you are changing the API but then you get strict parameter types. Anyway, I am on the road to get the FlexJS emitter working for extensibility and configuration. I understand everything 100% more now. Mike On Sun, May 31, 2015 at 10:02 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 5/31/15, 3:28 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: > > >Alex, you had said you might be able to push a project you use to test the > >framework with. > > > >I know you are busy but, it would be cool to look through it and mess with > >it. > > > >I'm trying to manage my development time between this project and my other > >things, so now that I have gotten back into the compiler, things make > >sense. :) I can see the start and end finally. > > I was all set to push it, then I tested on my people.a.o account and > realized there were a bunch of cross-domain issues (I had been running off > of file:// until then). So I put it down to work on FDB so I can focus on > re-packaging FlexJS and have a better chance of it working in IJ. > > Besides this one app, before checking in I also try to run up to four > examples in the flex-asjs/examples folder. The ones that work the best > are DataBindingTest, FlexJSStore, ChartExample and DataGridExample. Each > has some layout issues. FlexJS is the most complex as it will run state > transitions as you to from Home to Products view. > > -Alex > >
