Hi,

>From Crosswalk 7,  the embedding API for Android supports the animatible 
>XWalkView by use of TextureView as the target compositing surface, which is 
>one of major differences from the upstream implementation and its variants, it 
>addresses the limitations of SurfaceView which cannot be animated, transformed 
>and overlayed, but with much memory consumption.

I found some embedding API users may always ask the question about when to use 
animitable XWalkView and what is the difference. So I put down the comparison 
between SurfaceView and TextureView on 
https://crosswalk-project.org/#wiki/Android-SurfaceView-vs-TextureView for your 
reference.

Thanks...Hongbo
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to