I have not tried to alleviate the playerglobal/airglobal dependency for FalconJX. In FlexJS there is a SWF compile that I’m currently encouraging folks to use to at least mock test their code. The idea is that the Flash runtime with its verifier will find more problems early. And the SWF version is your backup to deploy to old browsers. The SWF compile will almost certainly require playerglobal/airglobal
The cross-compile shouldn’t require Flash classes, but probably does want to have the primitive types like Object, Number, String. I’m not sure we’re allowed to fake up our own SWC of those types or not. We’d have to dig through licenses to be sure. It might be considered reverse-engineering. Regardless, the situation today is that the cross-compiler runs a fair amount of the SWF compiler code in order to resolve states and data binding. I have not tried to move that code to the block walker/emitters and have no plans to do that right now. Volunteers are welcome to take that on, but for me there are bigger fish to fry. So right now, I think you will need playerglobal/airglobal, and once we figure out what we can do about the primitive types, if there is an option to not use playerglobal/airglobal, some volunteers can try to figure out how to do that. -Alex On 5/9/15, 4:49 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: >I did a lot of work with the Falcon compiler, as far as understanding it's >code base. It would seem to me, in the core Falcon code which FalconJx >uses >for it's model, playerglobal is a dependency in the compiler and Object is >treated very special. > >I spent a lot of time trying to figure out a way to get around this when I >was writing FalconJx. I just couldn't do anything since Falcon seems >hardwired with a weird declaration of Object. > >Although I may have missed something stupid. > >Mike > >On Sat, May 9, 2015 at 7:46 AM, Michael Schmalle ><teotigraphix...@gmail.com> >wrote: > >> My point was, hacking meant "testing" alternatives. We found there is no >> alternative, if Alex has an answer it would be news to me. :) >> >> Mike >> >> On Sat, May 9, 2015 at 7:43 AM, Christofer Dutz >><christofer.d...@c-ware.de >> > wrote: >> >>> Well I don't want to do any hacking as we are in the position to change >>> things, that are not working. So I guess a hack around this isn't a >>>good >>> idea. Hopefully Alex will be able to shed some light on this. >>> >>> Chris >>> >>> ________________________________________ >>> Von: Michael Schmalle <teotigraphix...@gmail.com> >>> Gesendet: Samstag, 9. Mai 2015 13:17 >>> An: dev@flex.apache.org >>> Betreff: Re: [FlexJS] Does the FlexJS compiler need the playerglobal? >>> >>> When doing the Randori compiler 2 years ago, we ran into this same >>>issue. >>> It seems you cannot escape the fact playerglobal must be compiled. >>> >>> It was kind of weird having to use it in a non flash based framework. >>>We >>> tried a bunch of hacks to simulate Object, but it never worked. >>> >>> Mike >>> >>> On Sat, May 9, 2015 at 6:08 AM, Christofer Dutz < >>> christofer.d...@c-ware.de> >>> wrote: >>> >>> > Hi, >>> > >>> > >>> > I am continuing my work on Flexmojos FlexJS support and am doing the >>> > fine-tuning. >>> > >>> > One of the things I was currently working on, is making Flexmojos not >>> > enforce the presence of a global artifact if the compiler is set to >>> FlexJS. >>> > After finishing my work on this I noticed, that FlexJS won't compile >>>if >>> the >>> > playerglobal is missing. >>> > >>> > >>> > I am then getting this: >>> > >>> > >>> > [INFO] --- flexmojos-maven-plugin:7.1.0-SNAPSHOT:compile-swf >>> > (default-compile-swf) @ flexjs-hello-world --- >>> > [INFO] Flexmojos 7.1.0-SNAPSHOT >>> > [INFO] GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file >>> > [WARNING] No themes are explicitly defined in the <theme> section or >>>in >>> > any scope="theme" dependencies. Flexmojos is now attempting to figure >>> out >>> > which themes to include. (to avoid this warning you should explicitly >>> state >>> > your theme dependencies) >>> > Missing builtin type Object >>> > >>> > Unable to build SWF >>> > >>> >>>/Users/christoferdutz/Projects/Apache/Flex/flex-utilities/maven-flex-plu >>>gin/examples/flexjs/flexjs-hello-world/target/flexjs-hello-world-1.0.0-S >>>NAPSHOT >>> > >>> > [INFO] >>> > >>>------------------------------------------------------------------------ >>> > [INFO] BUILD FAILURE >>> > [INFO] >>> > >>>------------------------------------------------------------------------ >>> > [INFO] Total time: 2.910s >>> > [INFO] Finished at: Sat May 09 12:07:36 CEST 2015 >>> > [INFO] Final Memory: 16M/316M >>> > [INFO] >>> > >>>------------------------------------------------------------------------ >>> > [ERROR] Failed to execute goal >>> > net.flexmojos.oss:flexmojos-maven-plugin:7.1.0-SNAPSHOT:compile-swf >>> > (default-compile-swf) on project flexjs-hello-world: Execution >>> > default-compile-swf of goal >>> > net.flexmojos.oss:flexmojos-maven-plugin:7.1.0-SNAPSHOT:compile-swf >>> failed: >>> > Output file doesn't exist and no error was thrown by the compiler! -> >>> [Help >>> > 1] >>> > [ERROR] >>> > [ERROR] To see the full stack trace of the errors, re-run Maven with >>>the >>> > -e switch. >>> > [ERROR] Re-run Maven using the -X switch to enable full debug >>>logging. >>> > [ERROR] >>> > [ERROR] For more information about the errors and possible solutions, >>> > please read the following articles: >>> > [ERROR] [Help 1] >>> > >>> >>>http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionExceptio >>>n >>> > >>> > Process finished with exit code 1 >>> > >>> > ?Any ideas? >>> > >>> > Chris >>> > >>> > >>> >> >>
