rksaran

Apache Flex Blog

Saran — Mon, 16 Jan 2012 05:33:47 +0000

http://blogs.apache.org/flex/

Top 10 Performance Tips for 2012

Saran — Tue, 10 Jan 2012 04:17:51 +0000

Use native code instead of AS3Generally, it’s better to let Flash Player’s native code do the heavy lifting rather than using AS3. The reason for this is that the VM that AS3 code runs in necessarily has some overhead to it compared to the functions you can call in the Flash Player API (everything in the flash.* packages). One exception to this rule is when the API does something you want to avoid such as allocate memory.
Eliminate allocations to reduce GCIn addition to the allocations that you expect—such as those that you trigger by using the new operator—there are tons of hidden allocations such as String objects from concatenation, objects the Flash Player creates such as Events. These allocations are slow and collecting them when you’re done with them is even slower, so try to get rid of them.
Reuse objects to reduce GCWhen you’re done with objects, Flash Player’s garbage collector will reclaim their memory for reuse later. Unfortunately, this process is very slow and it’s hard to control when it will happen. Instead of making new objects, consider reusing existing ones. One technique that can help with this is called free lists.
Don’t use anything dynamicThat includes dynamic functions (e.g. anonymous functions and functions declared as local variables), objects such as Object and MovieClip, the [] operator for accessing fields, and untyped (*) variables. All of these are much slower than their static equivalents such as regular methods, non-dynamic classes, the dot operator, and typed variables.
Offload to the GPUThese days in Flash you have the ability to use video cards’ GPUs in addition to the main CPU. Using a combination of these is the key to high performance with 3D graphics (Stage3D) and high-definition video (StageVideo).
Reduce function callsFunction calls are, very unfortunately, quite slow in AS3. This includes getters and setters, which occur all the time (e.g. Array.length). Try caching the results of functions instead of calling them more than once, especially with getters. In extreme cases, manually inline the body of functions into one larger function.
Use speciality functions and classes rather than general purpose onesSprite uses less memory than MovieClip, Shape uses less memory than Sprite, and BitmapData.copyPixels is faster than BitmapData.draw.
Use fewer static accessesAccessing static variables, constants, and functions is slower than accessing their non-static counterparts. Consider using non-static alternatives or caching those static accesses as either non-static variables/constants or local variables/constants.
Prefer local variables to fieldsReading and writing class and object variables (a.k.a. fields, member variables) is much slower than accessing local variables. Cache field accesses as local variables when you use them a lot.
Eliminate pointless codeIt’s common to see variables initialized to their default value, which slows down the creation of objects and the execution time of functions. Get rid of this code that does nothing as a matter of good habit and the performance advantages will add up across your entire app.

Adobe Flex now Apache Flex

Saran — Mon, 09 Jan 2012 08:46:20 +0000

Adobe planed to donate Flex to Apache foundation and now Flex is officially accepted by Apache Software Foundation(ASF).

For more info on this – http://wiki.apache.org/incubator/FlexProposal

Flash Player Adminm Guide

Saran — Thu, 29 Dec 2011 11:42:31 +0000

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flash/articles/flash_player_admin_guide/flash_player_11_1_admin_guide.pdf

Flex 3.x Examples source code

Saran — Tue, 08 Nov 2011 07:17:12 +0000

http://blogs.adobe.com/flexdoc/2011/11/flex-3-x-examples-source-code.html

What’s new in Flash Player 11 ?

Saran — Fri, 04 Nov 2011 04:09:36 +0000

Native 64-bit support (Flash Player desktop): Take advantage of native support for 64-bit operating systems and 64-bit web browsers on Linux, Mac OS, and Windows.
Stage 3D accelerated graphics rendering: Stage 3D (formerly called “Molehill”) is a new architecture for hardware-accelerated graphics rendering developed by Adobe. Stage 3D provides a set of low-level APIs that enable advanced 2D/3D rendering capabilities across screens and devices (desktop, mobile, and TV). It gives 2D and 3D app and framework developers access to high-performance GPU hardware acceleration, enabling the creation of new classes of rich, interactive experiences. (This release includes Flash Player and Adobe AIR desktop support; AIR for Android and iOS support will be enabled in a future prerelease build.)
Adobe Flash Access content protection support for mobile: Flash Access content protection support is now available on mobile devices.
H.264/AVC software encoding for cameras (desktop): Stream high-quailty video from your computer’s camera with higher compression efficiency and industry-wide support, enabling both immersive real-time communications (e.g., video chat and video conferencing) and live video broadcasts.
Native JSON (JavaScript Object Notation) support: ActionScript developers can now take advantage of high-performance native parsing and generation of JSON-formatted data. Developers can integrate existing data seamlessly into their projects.
G.711 audio compression for telephony: Support interoperability with legacy phone systems via the Flash Media Gateway (FMG) and other third-party clients (through the open RTMP protocol) without the need for transcoding.
Garbage collection advice: Provide smoother, more responsive user experiences by allowing developers to provide hints (through System.pauseForGCIfCollectionImminent) to optimize garbage collection scheduling.
Cubic Bézier curves: With the Graphics.cubicCurveTo drawing API, developers can easily create complex cubic Bézier curves without requiring custom ActionScript code.
Secure random number generator: Developers can now take advantage of cryptographically secure random number generation to build more secure algorithms and protocols.
Protected HTTP Dynamic Streaming (HDS) and Flash Access enhancements: Protected HTTP Dynamic Streaming (HDS) provides protection for streaming video across screens while eliminating the deployment complexity of a license server. New Flash Access content protection features include key rotation support, V3 license chaining, domain support, and enhanced output protection and device filtering.
TLS secure sockets support (new for Flash Player): Enable secure communications for client/server applications.
Socket progress events: Improve management of data transfer using the Socket class by providing a new property to determine the number of bytes remaining in the write buffer and a new event for when data is being sent to the network layer. The new APIs (Socket.bytesPending, Event.OutputProgressEvent) allow applications to easily track progress and provide responsive feedback.
Native text input UI (mobile): Mobile apps can now take advantage of the native text input controls on mobile platforms, including platform-specific user interaction behaviors such as magnification and text selection. Native text controls are available on iOS, Android, and BlackBerry Tablet OS.
JPEG-XR support: Flash Player and AIR now include support for the JPEG-XR advanced image compression standard (ISO/IEC 29199-2). The computationally lightweight JPEG-XR format provides more efficient compression than JPEG, enables both lossy and lossless compression support, and adds support for alpha channel transparency.
Enhanced high-resolution bitmap support: BitmapData objects are no longer limited to a maximum resolution of 16 megapixels (16,777,215 pixels) and maximum bitmap width/height is no longer limited to 8,191 pixels, enabling the development of apps that utilize very large bitmaps.
High-efficiency SWF compression support: Developers can now take advantage of LZMA compression for their SWF files. LZMA compression can reduce SWF size by up to 40 percent, enabling users to benefit from richer experiences with shorter download times and reduced bandwidth consumption. Use Tinic Uro’s LZMA compression tool or a custom utility to compress your SWFs.
DisplayObjectContainer.removeChildren and MovieClip.isPlaying: DisplayObjectContainer now implements a removeChildren API, allowing developers to remove all of a container’s children quickly using a single API.
Sound.loadCompressedDataFromByteArray and Sound.loadPCMFromByteArray: Developers can now inject compressed or raw PCM sound data into a Sound object to play sounds.
Asynchronous bitmap decoding: Improve application responsiveness and deliver smoother animation by decoding images on initial load instead of on demand. Images are cached as needed.

Fundamentals of ActionScript 3:0 — Instructor and Student Guides now available

Saran — Tue, 25 Oct 2011 04:53:07 +0000

Fundamentals of ActionScript 3:0 — Instructor and Student Guides now available — http://wp.me/p1sDoC-2F

Secure Data Persistence with AIR3

Saran — Wed, 19 Oct 2011 05:14:13 +0000

http://blogs.adobe.com/cantrell/archives/2011/10/secure-data-persistence-with-air-3.html

Customizing Flex applicationDPI for a multiple screen size application

Saran — Tue, 18 Oct 2011 05:51:01 +0000

http://renaun.com/blog/2011/10/customizing-flex-applicationdpi-for-a-multiple-screen-size-application/

Creation of an iPhone App with Flash and without a Mac (for all Windows lovers)

Saran — Mon, 03 Oct 2011 07:03:37 +0000

http://www.emanueleferonato.com/2011/09/22/creation-of-an-iphone-app-with-flash-and-without-a-mac-for-all-windows-lovers/