So I am voting for FalconJX, even if it relies on Falcon, but that isn't 
released?
Hope we're not sort of talking of different things ... let me try to clarify 
what I understood:

Falcon is used as a new compiler replacement to the old Flex compiler, so I 
could use this instead of the old compiler in the FDK without any important 
changes. The code for this compiler is in (let's simplify it: a jar falcon.jar).

FalconJX is an addition to Falcon, that allows HTML output. You can use this to 
build normal SWF applications and JavaScript ones, by providing parameters. 
However if building SWF, I assume this will simply use the Falcon compiler and 
have that generate the output. Only if I select JavaScript will the actual 
FalconJX code do it's magic.

Am I correct this far?

So we are discussing of releasing FalconJX 0.5 without having released Falcon 
0.5? I don't quite get it :-(

Chris

________________________________________
Von: Alex Harui <aha...@adobe.com>
Gesendet: Mittwoch, 14. Oktober 2015 16:46
An: dev@flex.apache.org
Betreff: Re: Falcon, FalconJX, FlexJS

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

Reply via email to