Would be totally cool. I didn’t try the flex sdk npm module, but it looks like it may actually be downloading the Adobe Flex SDKs. Hopefully the person who put this together has permission to distribute, and is handling the presentation of the license agreements for the Adobe bits like airglobal and playerglobal
IMO, Apache FlexJS via NPM will face similar issues because we still use playerglobal and airglobal. It would be an interesting task to see if we can make playerglobal/airglobal optional in FlexJS. I haven’t thought too much about it, your email got me thinking about it. I think we need airglobal/playerglobal to develop the FlexJS SWCs, but I think it might be true that if you are going to write cross-compilable code, the MXML and AS you write won’t need any of the APIs in airglobal/playerglobal. FB might require it, although we might be able to stick in a dummy. -Alex On 2/13/15, 12:53 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >Right now installing FlexJS requires either getting the sources and >building them, or using the Installer to install it. Another nice way >would be to add it is a npm module [1], which seems to be a popular way to >install libraries these days. So, simply running > >npm install flexjs > >should be a great way to get folks to install and try the new SDK. > >Any interest in helping build something like this? > >Note that there is already an npm module available for the flex sdk [1] >[2] > So, we might have a good starting point to add flexjs support. > >Thoughts? > >Thanks, >Om > >[1] https://www.npmjs.com/ >[2] https://www.npmjs.com/package/flex-sdk >[3] https://github.com/JamesMGreene/node-flex-sdk
