Currently, these are the compiler arguments defined for FlexJS:
<compilerArguments passClasspath="true" passMainclass="true"
passSwcs="true" passRsls="false">
<argument>-js-output-type=FlexJS</argument>
<argument>-compiler.mxml.children-as-data=true</argument>
<argument>-compiler.binding-value-change-event=org.apache.flex.events.ValueChangeEvent</argument>
<argument>-compiler.binding-value-change-event-kind=org.apache.flex.events.ValueChangeEvent</argument>
<argument>-compiler.binding-value-change-event-type=valueChange</argument>
<argument>-target-player={playerVersion}</argument>
</compilerArguments>
There’s quite a few other arguments defined in the ant scripts (and different
ones for the different targets). I’m also not quite sure how to specify
different arguments for debug and release builds.
What’s the bare minimum needed in terms of arguments to get it to properly
compile?
On May 17, 2016, at 5:58 PM, Harbs <harbs.li...@gmail.com> wrote:
> They have a FlexJS project type, but no template. The project type seems to
> be broken though.
>
> I’m trying to fix both the type and create a template to generate a
> boilerplate project.
>
> I’m pretty close with the template, but I’m struggling with the compiler
> settings in the project type definition.
>
> On May 17, 2016, at 5:55 PM, Josh Tynjala <joshtynj...@gmail.com> wrote:
>
>> I don't think FDT officially supports FlexJS MXML yet. They only have the
>> JSC project type, which is meant to be more of a pure ActionScript kind of
>> thing.
>>
>> - Josh
>>
>> On Tue, May 17, 2016 at 7:50 AM, Harbs <harbs.li...@gmail.com> wrote:
>>
>>> I’m struggling with trying to get an MXML project set up in FDT. Has
>>> anyone managed to do so yet?
>>>
>>> Harbs
>
