Lizhi has put together some impressive classes to implement the Flash drawing 
APIs for FlexJS using Canvas.[1]

Lizhi has offered to donate the code[2] and I believe has just filed an ICLA.

The question now remains whether we want to include the code. I personally see 
a lot of value in the code as it offers a lot of functionality users are used 
to out of the box using the same APIs.

I do have some questions about accepting the code:
1. Whether to keep the packages as they are. Currently, they use the flash.* 
packages to match the ones in playerglobal. One the one hand, this makes a lot 
of sense in terms of migrating code because everything stays exactly the same. 
On the other hand, the package names are misleading as it’s not “Flash” 
packages. The alternate would be to wrap things in apache flex packages, but 
that would add a lot of work in terms of conditional compilation and 
redirection. I also don’t know if there are legal issues with using the “flash” 
package. I can’t imagine what they might be, but INOL…

2. How should these files be organized in FlexJS? This might be related to the 
package names, but might not. I assume this is not “core”. Should it all go 
into a single project, or should it be split up into multiple projects?

Harbs

[1]https://github.com/matrix3d/spriteflexjs
[2]http://mail-archives.apache.org/mod_mbox/flex-dev/201604.mbox/browser

Reply via email to