On 11/7/13 7:49 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> was last built by MXMLC and not Falcon (or was built by Falcon without >>the >> -compiler.mxml.children-as-data flag). Every once in a while, FB will >> suddenly re-build the SWF when you launch it. Not sure why. Om says it >> happens every time for him. For me, I just run the external tool again >> and it goes away. > >I figured as much, but the thing is, like Om, I haven't been able to >run it at all :-( Yeah. Will have to figure this out some day. The workflow shouldn't require special launch configs if we can avoid it. >Since next on my list is an attempt to get the class structure on the >JS side to match that on the AS side, it's not high priority for me, >but it would be nice to have to occasionally run a test on both side >of the aisle. I'd like to make sure we're on the same page on this. Now that you've provided interfaces on the JS side I can see that we should use them more, but I don't think the set of superclasses and interfaces need to match exactly. For example, we don't need a Sprite superclass in JS just because there is one under the covers on the AS side. IMO, the only thing that needs to match is the "API Surface", the set of public APIs. Your thoughts? -Alex
