为iOS视网膜显示屏优化Flash空气的编程技巧?-ProgrammingtipstooptimizeFlashAIRforiOSretinadisplays?

6  

Flex 4.6 supports MultiDPIBitmapSource which would provide a way to supply bitmap optimized for different screen density. You may read an in-depth discussion over this link.

Flex 4.6支持MultiDPIBitmapSource，它可以为不同屏幕密度优化的位图提供一种方法。您可以阅读关于这个链接的深入讨论。

In general, if your bitmaps are used as icon, logo display, where animation or transformation are limited to moving, panning and clipping, and your bitmap it is not scaled, you would achieve optimal display result and descent performance. Vector assets' performance is less predictable compared to bitmap for this usage.

一般来说，如果你的位图被用作图标、标志显示，其中动画或转换仅限于移动、平移和剪切，而你的位图没有缩放，你将获得最佳显示结果和下降性能。与使用位图相比，向量资产的性能更难预测。

However, bitmaps are not silver bullets to all solutions. They would adversely impact performance as soon as you involve any rotation, distortion or scaling (zoom in and out), this is because the system would have to do a lot more calculation to relocate every pixels, which is a lot more involved compared to vectors.

然而，位图并不是万能的解决方案。一旦涉及到旋转、失真或缩放(放大或缩小)，它们就会对性能产生负面影响，这是因为系统需要做更多的计算来重新定位每个像素，这比矢量要复杂得多。

Stage3D is also worth looking into, but if you are usage is primarily 2D, wisely choose between MultiDPIBitmapSource and vector graphics could be a much simpler solution.

Stage3D也值得研究，但如果您使用的主要是2D，那么明智地选择MultiDPIBitmapSource和vector graphics可能是更简单的解决方案。

7  

In general, you want to avoid using bitmap graphics as much as possible. If you are using only vector and fonts, these can scale up without issue. The trick to avoid killing the CPU is to use cacheAsBitmap whenever feasible, e.g., when the object does not change often. Then you gain the resolution advantage of vector grx, and after the initial rendering gain the speed of bitmap grx.

一般来说，您希望尽可能避免使用位图图形。如果你只使用矢量和字体，它们可以毫无问题地扩展。避免破坏CPU的技巧是在可行的情况下使用cacheAsBitmap，例如，当对象不经常更改时。然后获得矢量grx的分辨率优势，初始渲染后获得位图grx的速度。

Another tool to start looking into is using the Stage3D. This layer sits behind the Air program, and acts as a robust backdrop. The real advantage is that it uses the GPU, instead of the CPU, which means you have two processors kicking out the grx. If you develop or use coherent foreground and background systems, this can boost your grx performance. One tool that seems nearly ready is Starling 2D. This should help shortcut a lot of the difficult areas for Stage3D. I have yet to use Stage3D, so a lot of this is speculative. I will edit my answer when more experienced.

开始研究的另一个工具是使用Stage3D。这一层位于空气计划的后面，作为一个坚实的背景。真正的优势是它使用GPU，而不是CPU，这意味着有两个处理器将grx踢出。如果您开发或使用连贯的前景和背景系统，这可以提高您的grx性能。一个似乎已经准备就绪的工具是Starling 2D。这将帮助你在舞台3d的许多困难领域找到捷径。我还没有使用舞台3d，所以很多都是推测性的。我将编辑我的答案当更有经验。

Edit

@TianzhenLin's response has some pretty good tips. It reminded me that CacheAsBitmapMatrix should be used for objects that are going to be rotated, scaled, etc., but not changed structurally.

@TianzhenLin的回应有一些相当不错的技巧。它提醒我CacheAsBitmapMatrix应该用于对象，这些对象将会被旋转、缩放等等，但是不会在结构上发生改变。