On 10/14/15, 1:01 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi, > > >I was just a bit confused about the the discuss thread ... I thought >FalconJX is built up on top of Falcon and is sort of a strap-on adapter >to output JavaScript ... so it seems I must have mis-understood this. As >it seems to be possible to release FalconJX without releasing Falcon > > >@Alex ... could you please elaborate a little on the differences of >Falcon and FalconJX? Cause this would have an effect on my maven-bundling >and Flexmojos integration efforts. > There is code and then there is packaging. Your are correct that FalconJX is built on top of Falcon. Falcon produces SWFs, and FalconJX produces HTML/JS/CSS. But the artifacts named apache-flex-falconjx bundle both the Falcon and FalconJX code since those artifacts target FlexJS which uses both compilers to produce both SWF and HTML/JS/CSS versions of your app. The build script currently also products a set of artifacts named apache-flex-falcon which is just the Falcon code, but I have not done any testing of the apache-flex-falcon packages and don’t plan to put them up for vote or release. I am keeping the build script that way in case someday we do produce a Falcon-only package for the current Flex SDK. HTH, -Alex
