> We shouldn’t. Make sure you are using the latest from flex-falcon repo.
My bad, thanks.
> I don’t remember why we have sprite.js. Maybe Erik does. I’d rather
> remove it if we can.
Yep, @Erik, any hint ?
Still remain the start function def, should it be moved to an interface or
removed too ?
Frédéric THOMAS
----------------------------------------
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FlexJS] Framework using externs (was: Setup Error)
> Date: Sat, 8 Aug 2015 16:27:53 +0000
>
>
>
> On 8/8/15, 8:46 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
>
>>I thought I could have used the framework as a test for what I'm about to
>>implement in the compiler to make IJ compiling externs/as3 based projects
>>with 1 build conf.
>>Apparently I was wrong but I will try to implement it first anyway.
>>
>>For the framework migration, I just had a look and indeed I will have a
>>lot of questions, the 2 first ones:
>>
>>1- If I'm not wrong, sprite.js can't have an AS counterpart, this one
>>needs to stay JS only but it includes a "start" method definition, not
>>having this methos in the AS part, I won't be able to use it, should this
>>definition be moved to an interface in asjs and be shared by both sides ?
>
> I don’t remember why we have sprite.js. Maybe Erik does. I’d rather
> remove it if we can.
>
>>
>>2- Classes and Interfaces are written this way in JS:
>>
>>org.apache.flex.core.IStrand.prototype.FLEXJS_CLASS_INFO ={ names: [{
>>name: 'IStrand', qName: 'org.apache.flex.core.IStrand' }] };
>>
>>But if I cross compile IStrand.as, I get:
>>
>>org_apache_flex_core_IStrand.prototype.FLEXJS_CLASS_INFO = { names: [{
>>name: 'IStrand', qName: 'org_apache_flex_core_IStrand'}] };
>>
>>Why we still have the underscores ?
>
> We shouldn’t. Make sure you are using the latest from flex-falcon repo.
>
> -Alex
>
