Hi Carol, On Thu, Apr 26, 2012 at 6:46 PM, Carol Frampton <cfram...@adobe.com> wrote: > ...The code in question is > > 1) playerglobal.swc to compile the majority of the Flex components > 2) airglobal.swc to compile the Flex components targeted at AIR > 3) many pieces of the AIR Integration kit which are need to do Flex mobile > development..
Ok, added that info to FLEX-53 which I just created to handle this issue. > ...I think playerglobal.swc/airglobal.swc can be looked at as Actionscript > system libraries much the same way as the java compiler has system jars. > java is considered a build tool and people can compile their code with > those jars. If that argument is correct that means one would need to get > the two swcs and put them someplace in order to build ... I agree that this looks very similar to requiring people to get a Java compiler, so it might not be a problem as long as users are made aware of the limitations. > ...and then the > remaining question is could we provide a convenience script, outside of > the build procedure, that could download the two swcs and put them into > place?... That would be ok IMO, provided the script requires active agreement from the user. > > ...I think you covered AIR Integration kit in your 4. below. We would > instruct the user to unzip the kit on top of the Flex tree. We don't use > all the pieces of the kit so we delete some of them. Again the question > would be could we provide a convenience script that either downloaded the > integration kit and unzipped it deleting the unused pieces, or just > unzipped it and deleted the unused pieces?... I think a script is ok. As this is similar to the above, we might just create a website page that explains what's going on, and point people to that when they run the convenience scripts. -Bertrand
