On 5/27/15, 12:05 PM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:

>> OK, one more thought: there may be reverse-engineering issues about
>replacing playerglobal/airglobal, but I was hoping we might find some
>Tamarin code laying around that has what we’d start with for jsglobal.swc.
>
>Hmmm, yeah I re-read the Builtin, I really thought Roland did use code
>from
>an opensource flash player impl. Actually if my memory serves me, if that
>is not what is going on here, than that was the problem with Object and
>Roland then found a workaround.

This is where, for Apache projects, it gets tricky/messy.  Tamarin code is
MPL (or xGPL) and Apache doesn’t like have source code dependencies on
those licenses.  You can have a dependency on compiled MPL code so if
there was a swc in a stable place that contained those compiled Tamarin
.as files then we’d be good to go.  Otherwise, we may need to get an
exception or get Adobe to re-license.  Not sure how hard that will be.
And just linking to Randori may be seen as a valid way to get around it
either since the Randori folks are also Flex committers.

>>>HTML.swc:
>>> Window
>>> Event
>>> UIEvent
>>> MouseEvent
>>> HTMLElement
>>> etc.
>>>
>>>
>> See for HTML lib, Roland used WebIDL parser to create it;
>>
>> https://github.com/RandoriAS/randori-libraries/tree/master/HTMLCoreLib

I couldn’t quickly find the rules around IDL and WebIDL Parser to figure
out if we can do the same.  Can you point us to links and licenses?

>>
>>
>> Question; So the code style, you said we might use the FlexJS emitter
>>but
>> I don't see how that is possible since it's not a vanilla emitter.
>>
>> It seems to me I need to know the exact code style that a vanilla
>> transpiler will create and I can make that emitter as another backend,
>>what
>> do you think?
>>
>> @Josj you have any thoughts? I am ready to start writing it. :)

I’m not clear what isn’t vanilla about the current emitter if you are
writing code against these two SWCs.  I don’t know how much Google Closure
Library code will actually get sucked in.  But it seems reasonable to at
least start with the FlexJS emitter then figure out what needs to change.

-Alex

Reply via email to