On 9/18/15, 7:26 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>
>Most of the applications produce runnable JavaScript versions. The
>DataGrid examples results in an empty screen. However not a single SWF is
>runnable.
>
>The module DataBindingExample_Flat produces this error in JavaScript mode:
>            This tag could not be resolved to an ActionScript class. It
>will be ignored.
>            <js:ViewBase xmlns:fx="http://ns.adobe.com/mxml/2009";

Is the flat.swc built after the HTML.swc?  It is supposed to be using the
“lookup” in the flat-manifest.xml to pull in components from HTML.

>
>The modules FlexJSStore_jquery and FlexJSStore produce:
>            Ambiguous reference to MouseEvent
>
>The module MobileTrader produces:
>            Implicit coercion of a value with static type Event to a
>possibly unrelated type Event.
>               <basic:TabbedViewManager id="navController" width="100%"
>height="100%" x="0" y="0" viewChanged="tabbedViewChanged(event)">

These two imply a potential issue with the default imports.  In the
standard flex-asjs flex-config.xml, there should be some “implicit-import”
tags.

>
>I did notice that you seem to be setting some compiler options in the ant
>script that I haven't seen before.
>            <arg value="-compiler.mxml.children-as-data" />
>            <arg 
>value="-compiler.binding-value-change-event=org.apache.flex.events.ValueCh
>angeEvent" />
>            <arg 
>value="-compiler.binding-value-change-event-kind=org.apache.flex.events.Va
>lueChangeEvent" />
>            <arg 
>value="-compiler.binding-value-change-event-type=valueChange" />
>
>Are these required for successfully building?

These can probably be removed.  They should be in the default
flex-config.xml for flex-asjs.  Maybe the maven build is not creating the
right flex-config.xml?

-Alex

Reply via email to