OK, I got GCL to compile by disambiguating the global classes and also got Falcon to allow keywords as method names so Language.is and Language.as don’t need “_” any more and merged it all into the flex-falcon develop branch.
I pushed a bunch of commits to the core_js_to_as branch of flex-asjs that compiles Application.js from Application.as without compiler errors. The output looks reasonable to me. I commented out the reference to ViewBase in Application in order to get this to happen. The next step is to uncomment ViewBase in Application and get ViewBase and its dependencies ported from js back to as, but, if you look at the changes I made, I’m doing more fine-grained conditional compilation (per method instead of per-class) and we’ve done enough refactoring in ViewBase.js and some other classes that I think I’m going to attempt to merge from develop into core_js_to_as first before continuing. Thoughts? -Alex On 9/18/15, 10:26 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: >> Yeah, I’m just looking ahead and am in the mood to play in the compiler >> code. I figure some day we’ll have a true GCL swc, either by making >> EXTERNC more tolerant, or because a d.ts file for GCL will be converted >>to >> externs. >> >> I’m also expecting that some day as we go further into this port from JS >> back to AS, that we’ll hit some code or write some code where we need >>both >> GCL.swc and JS.swc and I would expect collisions between Event and >> EventTarget in such a case, even with the stubbed GCL.swc we currently >> have, so I’m exploring ways to deal with that. > >Fair enough, would be awesome ! > >Thanks, >Frédéric THOMAS > >> From: aha...@adobe.com >> To: dev@flex.apache.org >> Subject: Re: [FlexJS] Framework using externs (was: Setup Error) >> Date: Fri, 18 Sep 2015 17:00:51 +0000 >> >> >> >> On 9/18/15, 9:42 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: >> >> >> IMO, the externs swcs are also for developers wanting to build >>“native” >> >>JS >> >> applications without the FlexJS components, so any GCL.swc needs to >> >> support some developer using GCL and native JS. So the two swcs >>need to >> >> be compatible with each other. We could just hack up a GCL just to >>get >> >> the FlexJS JS to be written in AS but I feel like spending a day or >>two >> >> trying to see if there is a way we can be more general about it. >> > >> >Well, it would be nice if the EXTERNC could compile it all to .as but >> >IIRC, it was far to be able to do it, the reason why I didn't consider >>it >> >as another extern but only as a stub with the only purpose I described >> >before. >> >Now, if you can compile it entirely to .as, what you're saying would >>make >> >more sense to me indeed but for now, only a part of the Event API has >> >been included and for a big part, it was by hand. >> >> Yeah, I’m just looking ahead and am in the mood to play in the compiler >> code. I figure some day we’ll have a true GCL swc, either by making >> EXTERNC more tolerant, or because a d.ts file for GCL will be converted >>to >> externs. >> >> I’m also expecting that some day as we go further into this port from JS >> back to AS, that we’ll hit some code or write some code where we need >>both >> GCL.swc and JS.swc and I would expect collisions between Event and >> EventTarget in such a case, even with the stubbed GCL.swc we currently >> have, so I’m exploring ways to deal with that. >> >> -Alex >> >
