About Flash Lite technology

Macromedia Flash Lite from Adobe is a version of Adobe Flash Player designed for mobile devices. It balances Flash features and capabilities with the processing power and configurations of today's mass market mobile devices. There are currently two versions of Flash Lite 1: Flash Lite 1.0 and Flash Lite 1.1, collectively known as Flash Lite 1.x. Flash Lite 1.x consists of the following features:

The core rendering engine The rendering engine handles all vector and bitmap rendering.

ActionScript interpreter Flash Lite supports the version of the ActionScript language used in Macromedia® Flash® Player 4 from Adobe, including many mobile-specific commands, such as getting time and date information from the device. This hybrid of Flash Player 4 ActionScript and commands with properties specific to Flash Lite is collectively called Flash Lite 1.x ActionScript.

For more information about Flash Lite 1.x ActionScript, see Flash Lite 1.x ActionScript Language Reference and Learning Flash Lite 1.x ActionScript.

Text and fonts Flash Lite supports static, dynamic, and input text fields. You can use fonts that are available on the device or embed font data in your published SWF file. For more information about using text and fonts in Flash Lite, see Working with Text and Fonts in Developing Flash Lite 1.x Applications.

Sound Flash Lite 1.0 and Flash Lite 1.1 both support device audio formats (such as MIDI or MFi). Flash Lite 1.1 also supports standard Flash audio. For more information about working with sound in Flash Lite, see Working with Sound in Developing Flash Lite 1.x Applications.

Network connectivity Flash Lite 1.1 supports the ability to load external data and SWF files, as well as commands and properties for getting connectivity and HTTP request status information.

Device and platform integration Flash Lite provides access to several system features and commands, such as the ability to initiate phone calls and short message service (SMS) messages, get platform capability information, and get user input using the device's standard input dialog box.

View comments on LiveDocs