| | h2. Bitmap and vector graphics on mobile devices |
| |  | ?{info:title=Add your own tips} |
| | |
| | |
 | | Sign into this wiki (or register) and edit this page directly or click Add Comment. The controls are at the bottom of the page. {info} |
| | | {info:title=Add your own tips} |
| | Sign?into this wiki (or register) then use Edit to insert your tip or click Add Comment at the bottom of the page. |
| | {info}\\ |
| | \\ |
| | \\ |
| | |
| | \\ |
| | |
| | (/)* Avoid outlines* |
| | * Avoid using outlines on vector shapes. Outlines have an inner and outer edge (fills have only one) and are twice the work to render.Corners are simpler to render than curves. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashBitmapOutlines\|display=default} |
| | \\ |
| | |
| | (/)* Use flat edges* |
| | * When possible, use flat edges, especially with very small vector shapes.Optimization is especially helpful with small vector shapes such as icons. Complex icons may lose their details upon rendering, and the work of rendering the details is wasted. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashEdges\|display=default} |
| | \\ |
| | |
| | (/)* Import bitmap graphics at the correct size * |
| | * Don't import large graphics and scale them down in Flash, because this wastes file size and run-time memory. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashAnimationImport\|display=default} |
| | \\ |
| | |
| | (/)* Avoide scaling or rotating bitmaps* |
| | * The Flash Lite player does not support bitmap smoothing. If a bitmap is scaled or rotated, it will have a chunky appearance. If it is necessary to scale or rotate a graphic, consider using a vector graphic instead. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashBitmapOutlines1\|display=default} |
| | \\ |
| | |
| | (/)* Avoid animating text* |
| | * Text is essentially just a very complex vector shape. Of course, text is often critical, so it can rarely be avoided entirely. When text is needed, avoid animating it or placing it over an animation. Consider using text as a bitmap. For multiline dynamic and input text, the line break of the text string is not cached. Flash breaks lines at run time and recalculates the breaks every time the text field needs to be redrawn. Static text fields are not problematic, because the line breaking is precalculated at compile time. For dynamic content, using dynamic text fields is unavoidable, but when possible, consider using static text fields instead. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashBitmapAnimText\|display=default} |
| | \\ |
| | |
| | (/)* Avoid using transparency* |
| | * Minimize the use of transparency in PNG files; Flash must calculate redraws even for the transparent portions of the bitmap. For example, with a transparent PNG file that represents a foreground element, don't export the transparent PNG at the full size of the screen. Instead, export it at the actual size of the foreground element. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashBitmapTrans\|display=default} |
| | \\ |
| | |
| | (/)* Group bitmap layers* |
| | * Try to group bitmap layers together and vector layers together. Flash needs to implement different renderers for bitmap and vector content, and switching between renderers takes time. |
| | |
| | *Author:* Adobe |
| | |
| | {rate:title=Rate this tip\|theme=dynamic\|key=AdobeFlashBitmapLayers\|display=default} |
| | \\ |
| | \\ |
| | \\ |
| | |
