We use AIR and AS3 for the Installer that installs binary packages for IDEs.
For a source package, which can’t have any binaries, we need to start from somewhere, and require AIR can be a hassle especially for Linux folks which we still want to support. So Ant works on all 3 platforms (Win, Mac, Linux) so it is our current choice. -Alex On 10/22/15, 5:30 PM, "jude" <flexcapaci...@gmail.com> wrote: >Off topic but related question: Why aren't we using AS3 and AIR extended >profile to check for env variables and download and setup of FlexJS, etc? > >I've issues with ant and it doesn't always seem like a faster approach >after using it for so long. Then again, AIR didn't have extendedDesktop >until relatively recently. FYI extendedDesktop let's you call commands >(command line) from your AIR app. So we could run command line tools from >our Flex app and check for environment variables, download and more. Plus >everyone on this list knows AS3 while ant is a mystery. > >The only advantage to ANT is that it's somewhat cross platform (Win/Mac) >and has a some builtin API's. > >I even have a native process effect that can help you run native >processes, >https://github.com/monkeypunch3/flexcapacitor/blob/master/MainLibrary/src/ >com/flexcapacitor/effects/nativeProcess/RunProcess.as. > > >If someone had a list of the processes we're using to setup FlexJS we >could >set up a Sequence or Parallel set of effects inside an AIR app to get the >same behavior and events. > >My point is that it seems like we are asking a lot to get people to try >and >use FlexJS. A simple UI should be doing this (why not the Flex >installer?). >I can try and help with writing the effects if someone is willing to tell >me what they need. > > >On Thu, Oct 22, 2015 at 12:45 AM, Harbs <harbs.li...@gmail.com> wrote: > >> Thanks for finding that! >> >> It now appears to build fine. The build works even without that extra >>arg >> value. >> >> OK. Next task is to try and target the developer build of FlexJS and see >> if I can put together an app using that. >> >> On Oct 22, 2015, at 4:27 AM, Alex Harui <aha...@adobe.com> wrote: >> >> > Well, I think I was able to reproduce your problem. Falcon is looking >> for >> > env.properties in a different place and doesn’t use the arg value >>passéd >> > in. >> > >> > I pushed a change to Falcon to fix that. So pull changes to >>flex-falcon >> > before trying again and run “ant all”. You may need to add the >> > >> > <arg value="+env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}” >> > >> > >> > to other build.xml files although the build now passes for me with >>what I >> > think your set up is. >> > >> > -Alex >> > >> > On 10/21/15, 1:44 PM, "Harbs" <harbs.li...@gmail.com> wrote: >> > >> >> OK. I’m calling it a night. >> >> >> >> Hopefully, I’ll have more success with this tomorrow. >> >> >> >> Harbs >> >> >> >> On Oct 21, 2015, at 11:41 PM, Alex Harui <aha...@adobe.com> wrote: >> >> >> >>> >> >>> >> >>> On 10/21/15, 1:37 PM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> >> >>>> No joy. >> >>>> >> >>>> I made this change in that file: >> >>>> <compc fork="true" >> >>>> output="${FLEXJS_HOME}/frameworks/libs/Core.swc"> >> >>>> <jvmarg line="${compc.jvm.args}"/> >> >>>> <load-config filename="compile-config.xml" /> >> >>>> <arg >>value="+env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}" >> >>>> /> >> >>>> <arg >>value="+playerglobal.version=${playerglobal.version}" /> >> >>>> <arg value="+env.AIR_HOME=${env.AIR_HOME}" /> >> >>>> </compc> >> >>>> >> >>>> >> >>>> I’m really confused about where that is defined. The only place I >>see >> >>>> it >> >>>> would be in flex-asjs/installer.xml: >> >>> >> >>> I think they are magic tokens in the compiler code. I will try to >> >>> re-create your scenario. >> >>> >> >>> -Alex >> >>> >> >> >> > >> >>
