Flex could do something more like they do on iOS. They can build an
entire layout as one bitmap, but to get parts that can change or
animate, they use layer-backing. So they only create a new quad for the
parts they need to. This seems to be a better strategy on mobile than a
deep display list, where everything gets it's own BitmapData and quad.
Kevin N.
On 1/21/13 11:46 PM, Alex Harui wrote:
Did you see the thread today where someone else proposed an alternative to
Starling? Starling may not be the best way to get at stage3D/gpu. Any
emulation of the display list is likely to cost more cycles than one tuned
to the platform. Do we really need a display list at all? If not, then
don't use one.
