flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [Discuss]Accept donation of drawing APIs
Date Mon, 18 Apr 2016 15:44:44 GMT

On 4/18/16, 6:24 AM, "Harbs" <harbs.lists@gmail.com> wrote:
>2. Assuming we accept it, what should the package naming be? I think
>there’s a strong case for leaving it as-is.

IMO, I would rename "flash" to "flex".  I'd like our FlexJS code to not
mention Flash at all, regardless of whether there is some legal/copyright
issue.  It just helps make it clear that this stuff doesn't really use
Flash, it helps us get out of the expectation that this code will somehow
perfectly replicate what Flash does, and it helps users migrating to see
what flash dependencies they have in their code.

IMO, it isn't that hard to replace flash.*.* with flex.*.*, and I've been
pondering a compile flag that automatically looks for a flex.*.* when it
sees flash.*.*.

>3. How should it be structured in the source? Should all the code go into
>a single “Flash” project? Should it be split into multiple projects
>(possibly one for each of the flash top-level packages)?

I haven't looked at the code, but if it is essentially the implementation
behind playerglobal.swc, so it would be one SWC project in


View raw message