ActionScript

History

ActionScript started as an object-oriented programming language for Macromedia's Flash authoring tool, later developed by Adobe Systems as Adobe Flash. The first three versions of the Flash authoring tool provided limited interactivity features. Early Flash developers could attach a simple command, called an "action", to a button or a frame. The set of actions was basic navigation controls, with commands such as "play", "stop", "getURL", and "gotoAndPlay".

With the release of Flash 4 in 1999, this simple set of actions became a small scripting language. New capabilities introduced for Flash 4 included variables, expressions, operators, if statements, and loops. Although referred to internally as "ActionScript", the Flash 4 user manual and marketing documents continued to use the term "actions" to describe this set of commands.

Timeline by player version

• Flash Player 2: The first version with scripting support, its actions included gotoAndPlay, gotoAndStop, nextFrame and nextScene for timeline control.
• Flash Player 3: Expanded basic scripting support, it has the ability to load external SWFs (loadMovie).
• Flash Player 4: The first player with a full scripting implementation (called Actions), the scripting was a Flash-based syntax and contained support for loops, conditionals, variables, and other basic language constructs.
• Flash Player 5: Included in the first version of ActionScript, it used prototype-based programming based on ECMAScript, and allowed full procedural programming and object-oriented programming. Design based development.
• Flash Player 6 added an event-handling model, accessibility controls, and support for switch. The first version with support for the Action Message Format (AMF) and Real-Time Messaging Protocol (RTMP) allowed for on demand audio/video streaming.
• Flash Player 7: Additions to it include Cascading Style Sheets (CSS) styling for text and support for ActionScript 2.0, a programming language based on the ECMAScript 4 Netscape Proposal with class-based inheritance. However, ActionScript 2.0 can cross compile to ActionScript 1.0 bytecode, so that it can run in Flash Player 6.
• Flash Player 8 further extended ActionScript 1/ActionScript 2 by adding new class libraries with APIs for controlling bitmap data at run-time, file uploads, and live filters for blur and drop shadow.
• Flash Player 9 (initially called 8.5) added ActionScript 3.0 with the advent of a new virtual machine, called ActionScript Virtual Machine 2 (AVM2), which coexists with the previous AVM1 needed to support legacy content. Performance increases were a major objective for this release of the player, including a new just-in-time (JIT) compiler. Support for binary sockets, ECMAScript for XML (E4X) XML parsing, full-screen mode, and regular expressions were added. This is the first release of the player to be titled Adobe Flash Player.
• Flash Player 10 (initially called Astro): Added basic 3D manipulation, such as rotating on the X, Y, and Z axis, a 3D drawing API, and texture mapping. Ability to create custom filters using Adobe Pixel Bender. Several visual processing tasks are now offloaded to the GPU which gives a noticeable decrease to rendering time for each frame, resulting in higher frame rates, especially with H.264 video. There is a new sound API which allows for custom creation of audio in flash, something that has never been possible before. Furthermore, Flash Player 10 supports Peer to Peer (P2P) communication with Real Time Media Flow Protocol (RTMFP).
• Flash Player 11: The major addition in this version are the Stage3D-based advanced (graphic card accelerated) 3D capabilities for Windows Desktop, Mac Desktop, iOS, Android, and other major platforms. Significant compatibility improvements have been added for the iOS platform, and other non-desktop platforms. Other features include H.264 encoding for cameras, Native JSON support, Cubic Bézier Curves, a secure random number generator, LZMA compression for SWF files, workers to offload some code execution to other processor threads, graphics card accelerated camera feed rendering, memory intrinsics and performance analysis, and the ActionScript Compiler 2.0, as well as some other minor additions.
• Flash Player 11.2: released in March 2012, focused on adding features that are key for the gaming and video markets. Some of the features in the release include the following: Mouse-lock support. Right and middle mouse-click support. Context menu disabling. Hardware-accelerated graphics/Stage 3D support for Apple iOS and Android via Adobe AIR. Support for more hardware accelerated video cards (from January 2008) in order to expand availability of hardware-accelerated content. New Throttle event API (dispatches event when Flash Player throttles, pauses, or resumes content). Multithreaded video decoding pipeline on PCs, which improves overall performance of video on all desktop platforms. Notification of use of premium features in the debug players; content runs unrestricted in the release players.
• Flash Player 11.3: released in June 2012, focused on enabling features and functionality key for the gaming market, as well as addressing popular feature requests from developers. Some of the features in this release include the following: Keyboard input support in full-screen mode. Improved audio support for working with low-latency audio. Ability to progressively stream textures for Stage 3D content. Protected mode for Flash Player in Firefox. Frame label events. Support for compressing BitmapData to JPEG and PNG formats. Support for Mac OS X App Store application sandboxing requirements. Text streaming support for Stage 3D. Expanded information about GPU driver details. Bitmap draw with quality API (new). Release outside mouse event API. Flash Player silent update support for Mac OS. Stylus support for Android 4.0 devices (Adobe AIR). USB debugging for iOS (Adobe AIR). iOS simulator support (Adobe AIR).
• Flash Player 11.4: Released in August 2012, it focused on enabling features and functionality that are key for the gaming market, as well as addressing popular feature requests from developers. Some of the features in this release include ActionScript workers (enables concurrent ActionScript execution on separate threads), support for advanced profiling, LZMA compression support for ByteArray, support for hardware-accelerated video cards for Stage 3D expanded to 2006, improved ActionScript performance when targeting Apple iOS, performance index API to inform about performance capabilities of current environment, support for compressed textures with alpha support, support for StageVideo.attachCamera API, and support for push notifications for iOS (Adobe AIR).
• Flash Player 11.5: Released in November 2012, it focused on performance improvement and stability. Some of the features in this release include shared ByteArray support for ActionScript workers, debug stack trace in release builds of Flash Player, and various bug fixes.
• Flash Player 11.6: Released in March 2013, it focuses on performance improvements, security enhancements, and stability. Some of the features in this release include ability to query graphics vector data at runtime, full-screen permission dialog user interface improvements, ability to load SWFs at runtime when deploying as an AIR application in AOT mode on iOS, finer-grained control over supported display resolution on iOS devices when deploying as an AIR application, HiDPI support for Flash Professional, and ActionScript 3 access to fast memory operations/intrinsics.
• Flash Player 11.7: Released in June 2013, code-named "Geary", this release focuses on premium video, gaming, security, and stability. Some of the features planned for this release include Android captive runtime debugging, support for the OUYA controller, remote hosting of SWF files on iOS, and preventing backup of shared objects on iOS for better iCloud support.
• Flash Player 11.8: Adobe was planning to release this version in the early part of the second half of 2013, code-named "Harrison". This release focused on premium video, gaming, security, and stability. Some of the features in this release would have included recursive stop API on MovieClips and GamePad support on desktop browsers and Android.

Timeline by ActionScript version

2000–2004: ActionScript "1.0"

With the release of Flash 5 in September 2000, the "actions" from Flash 4 were enhanced once more and named "ActionScript" for the first time. This was the first version of ActionScript with influences from JavaScript and the ECMA-262 (Third Edition) standard, supporting the said standard's object model and many of its core data types. Local variables may be declared with the var statement, and user-defined functions with parameter passing and return values can also be created. Notably, ActionScript could now also be typed with a text editor rather than being assembled by choosing actions from drop-down lists and dialog box controls. With the next release of its authoring tool, Flash MX, and its corresponding player, Flash Player 6, the language remained essentially unchanged; there were only minor changes, such as the addition of the switch statement and the "strict equality" (===) operator, which brought it closer to being ECMA-262-compliant. Two important features of ActionScript that distinguish it from later versions are its loose type system and its reliance on prototype-based inheritance. Loose typing refers to the ability of a variable to hold any type of data. This allows for rapid script development and is particularly well-suited for small-scale scripting projects. Prototype-based inheritance is the ActionScript 1.0 mechanism for code reuse and object-oriented programming. Instead of a class keyword that defines common characteristics of a class, ActionScript 1.0 uses a special object that serves as a "prototype" for a class of objects. All common characteristics of a class are defined in the class's prototype object and every instance of that class contains a link to that prototype object.

2003–2006: ActionScript 2.0

The next major revision of the language, ActionScript 2.0, was introduced in September 2003 with the release of Flash MX 2004 and its corresponding player, Flash Player 7. In response to user demand for a language better equipped for larger and more complex applications, ActionScript 2.0 featured compile-time type checking and class-based syntax, such as the keywords class and extends. While this allowed for a more structured object-oriented programming approach, the code would still be compiled to ActionScript 1.0 bytecode, allowing it to be used on the preceding Flash Player 6 as well. In other words, the class-based inheritance syntax was a layer on top of the existing prototype-based system. With ActionScript 2.0, developers could constrain variables to a specific type by adding a type annotation so that type mismatch errors could be found at compile-time. ActionScript 2.0 also introduced class-based inheritance syntax so that developers could create classes and interfaces, much as they would in class-based languages such as Java and C++. This version conformed partially to the ECMAScript Fourth Edition draft specification.

2006–2020: ActionScript 3.0

In June 2006, ActionScript 3.0 debuted with Adobe Flex 2.0 and its corresponding player, Flash Player 9. ActionScript 3.0 was a fundamental restructuring of the language, so much so that it uses an entirely different virtual machine. Flash Player 9 contains two virtual machines, AVM1 for code written in ActionScript 1.0 and 2.0, and AVM2 for content written in ActionScript 3.0. ActionScript 3.0 added limited support for hardware acceleration (DirectX, OpenGL).

The update to the language introduced several new features:

• Compile-time and run-time type checking—type information exists at both compile-time and runtime.
• Improved performance from a class-based inheritance system separate from the prototype-based inheritance system.
• Support for packages, namespaces, and regular expressions.
• Compiles to an entirely new type of bytecode, incompatible with ActionScript 1.0 and 2.0 bytecode.
• Revised Flash Player API, organized into packages.
• Unified event handling system based on the DOM event handling standard.
• Integration of ECMAScript for XML (E4X) for purposes of XML processing.
• Direct access to the Flash runtime display list for complete control of what gets displayed at runtime.
• Completely conforming implementation of the ECMAScript fourth edition draft specification.
• Limited support for dynamic 3D objects. (X, Y, Z rotation, and texture mapping)

Flash Lite

• Flash Lite 1.0: Flash Lite is the Flash technology specifically developed for mobile phones and consumer electronics devices. Supports Flash 4 ActionScript.
• Flash Lite 1.1: Flash 4 ActionScript support and additional device APIs added.
• Flash Lite 2.0 and 2.1: Added support for Flash 7 ActionScript 2.0 and some additional fscommand2 API.
• Flash Lite 3: Added support for Flash 8 ActionScript 2.0 and also FLV video playback.
• Flash Lite 4: Added support for Flash 10 ActionScript 3.0 as a browser plugin and also hardware graphics acceleration.

AIR

Adobe AIR supports ActionScript, in addition to some extended contents, such as the Stage3D engine Adobe has developed. The number of APIs (Application programming interfaces) available to ActionScript 3.0 has also risen dramatically.

Syntax

ActionScript code is free form and thus may be created with any amount or style of whitespace that an author desires. The basic syntax is derived from ECMAScript.

ActionScript 2.0

The following code, which works in any compliant player, creates a text field at depth 0, at position (0, 0) on the screen (measured in pixels), that is 100 pixels wide and high. Then the text parameter is set to the "Hello, world" string, and it is automatically displayed in the player:

<span id="mwASE"></span><span class="nx" id="mwASI">createTextField</span><span class="p" id="mwASM">(</span><span class="s2" id="mwASQ">"greet"</span><span class="o" id="mwASU">,</span><span class="w" id="mwASY"> </span><span class="mi" id="mwASc">0</span><span class="o" id="mwASg">,</span><span class="w" id="mwASk"> </span><span class="mi" id="mwASo">0</span><span class="o" id="mwASs">,</span><span class="w" id="mwASw"> </span><span class="mi" id="mwAS0">0</span><span class="o" id="mwAS4">,</span><span class="w" id="mwAS8"> </span><span class="mi" id="mwATA">100</span><span class="o" id="mwATE">,</span><span class="w" id="mwATI"> </span><span class="mi" id="mwATM">100</span><span class="p" id="mwATQ">);</span> <span class="nx" id="mwATU">greet</span><span class="p" id="mwATY">.</span><span class="nx" id="mwATc">text</span><span class="w" id="mwATg"> </span><span class="o" id="mwATk">=</span><span class="w" id="mwATo"> </span><span class="s2" id="mwATs">"Hello, world"</span><span class="o" id="mwATw">;</span>

When writing external ActionScript 2.0 class files the above example could be written in a file named Greeter.as as following.

<span id="mwAUI"></span><span class="kd" id="mwAUM">package</span><span class="w" id="mwAUQ"> </span><span class="nx" id="mwAUU">org</span><span class="p" id="mwAUY">.</span><span class="nx" id="mwAUc">wikipedia</span><span class="p" id="mwAUg">.</span><span class="nx" id="mwAUk">example</span><span class="w" id="mwAUo"> </span><span class="p" id="mwAUs">{</span> <span class="w" id="mwAUw"> </span><span class="kd" id="mwAU0">import</span><span class="w" id="mwAU4"> </span><span class="nx" id="mwAU8">flash</span><span class="p" id="mwAVA">.</span><span class="nx" id="mwAVE">display</span><span class="p" id="mwAVI">.</span><span class="nb" id="mwAVM">MovieClip</span><span class="o" id="mwAVQ">;</span> <span class="w" id="mwAVU"> </span><span class="kd" id="mwAVY">class</span><span class="w" id="mwAVc"> </span><span class="nx" id="mwAVg">Greeter</span><span class="w" id="mwAVk"> </span><span class="kd" id="mwAVo">extends</span><span class="w" id="mwAVs"> </span><span class="nb" id="mwAVw">MovieClip</span><span class="w" id="mwAV0"> </span><span class="p" id="mwAV4">{</span> <span class="w" id="mwAV8"> </span><span class="kd" id="mwAWA">public</span><span class="w" id="mwAWE"> </span><span class="kd" id="mwAWI">function</span><span class="w" id="mwAWM"> </span><span class="nx" id="mwAWQ">Greeter</span><span class="p" id="mwAWU">()</span><span class="w" id="mwAWY"> </span><span class="p" id="mwAWc">{</span> <span class="w" id="mwAWg"> </span><span class="k" id="mwAWk">var</span><span class="w" id="mwAWo"> </span><span class="nx" id="mwAWs">txtHello</span><span class="o" id="mwAWw">:</span><span class="w" id="mwAW0"> </span><span class="nb" id="mwAW4">TextField</span><span class="w" id="mwAW8"> </span><span class="o" id="mwAXA">=</span><span class="w" id="mwAXE"> </span><span class="k" id="mwAXI">this</span><span class="p" id="mwAXM">.</span><span class="nx" id="mwAXQ">createTextField</span><span class="p" id="mwAXU">(</span><span class="s2" id="mwAXY">"txtHello"</span><span class="o" id="mwAXc">,</span><span class="w" id="mwAXg"> </span><span class="mi" id="mwAXk">0</span><span class="o" id="mwAXo">,</span><span class="w" id="mwAXs"> </span><span class="mi" id="mwAXw">0</span><span class="o" id="mwAX0">,</span><span class="w" id="mwAX4"> </span><span class="mi" id="mwAX8">0</span><span class="o" id="mwAYA">,</span><span class="w" id="mwAYE"> </span><span class="mi" id="mwAYI">100</span><span class="o" id="mwAYM">,</span><span class="w" id="mwAYQ"> </span><span class="mi" id="mwAYU">100</span><span class="p" id="mwAYY">);</span> <span class="w" id="mwAYc"> </span><span class="nx" id="mwAYg">txtHello</span><span class="p" id="mwAYk">.</span><span class="nx" id="mwAYo">text</span><span class="w" id="mwAYs"> </span><span class="o" id="mwAYw">=</span><span class="w" id="mwAY0"> </span><span class="s2" id="mwAY4">"Hello, world"</span><span class="o" id="mwAY8">;</span> <span class="w" id="mwAZA"> </span><span class="p" id="mwAZE">}</span> <span class="w" id="mwAZI"> </span><span class="p" id="mwAZM">}</span> <span class="p" id="mwAZQ">}</span>

ActionScript 3.0

ActionScript 3.0 has a similar syntax to ActionScript 2.0, but a different set of APIs for creating objects. Compare the script below to the previous ActionScript 2.0 version:

<span id="mwAZk"></span><span class="kd" id="mwAZo">var</span><span class="w" id="mwAZs"> </span><span class="n" id="mwAZw">txtHello</span><span class="p" id="mwAZ0">:</span><span class="w" id="mwAZ4"> </span><span class="kt" id="mwAZ8">TextField</span><span class="w" id="mwAaA"> </span><span class="o" id="mwAaE">=</span><span class="w" id="mwAaI"> </span><span class="k" id="mwAaM">new</span><span class="w" id="mwAaQ"> </span><span class="kt" id="mwAaU">TextField</span><span class="o" id="mwAaY">();</span> <span class="n" id="mwAac">txtHello</span><span class="o" id="mwAag">.</span><span class="na" id="mwAak">text</span><span class="w" id="mwAao"> </span><span class="o" id="mwAas">=</span><span class="w" id="mwAaw"> </span><span class="s2" id="mwAa0">"Hello World"</span><span class="o" id="mwAa4">;</span> <span class="k" id="mwAa8">this</span><span class="o" id="mwAbA">.</span><span class="na" id="mwAbE">addChild</span><span class="o" id="mwAbI">(</span><span class="n" id="mwAbM">txtHello</span><span class="o" id="mwAbQ">);</span>

Minimal ActionScript 3.0 programs may be somewhat larger and more complicated due to the increased separation of the programming language and the Flash integrated development environment (IDE).

Presume the following file to be Greeter.as:

<span id="mwAbw"></span><span class="k" id="mwAb0">package</span><span class="w" id="mwAb4"> </span><span class="nn" id="mwAb8">org.wikipedia.example</span><span class="w" id="mwAcA"> </span><span class="o" id="mwAcE">{</span> <span class="w" id="mwAcI"> </span><span class="k" id="mwAcM">import</span><span class="w" id="mwAcQ"> </span><span class="nn" id="mwAcU">flash.display.Sprite</span><span class="o" id="mwAcY">;</span> <span class="w" id="mwAcc"> </span><span class="k" id="mwAcg">import</span><span class="w" id="mwAck"> </span><span class="nn" id="mwAco">flash.text.TextField</span><span class="o" id="mwAcs">;</span> <span class="w" id="mwAcw"> </span><span class="kd" id="mwAc0">public</span><span class="w" id="mwAc4"> </span><span class="kd" id="mwAc8">class</span><span class="w" id="mwAdA"> </span><span class="n" id="mwAdE">Greeter</span><span class="w" id="mwAdI"> </span><span class="kd" id="mwAdM">extends</span><span class="w" id="mwAdQ"> </span><span class="n" id="mwAdU">Sprite</span><span class="w" id="mwAdY"> </span><span class="o" id="mwAdc">{</span> <span class="w" id="mwAdg"> </span><span class="kd" id="mwAdk">public</span><span class="w" id="mwAdo"> </span><span class="kd" id="mwAds">function </span><span class="nf" id="mwAdw">Greeter</span><span class="o" id="mwAd0">()</span> <span class="o" id="mwAd4">{</span> <span class="w" id="mwAd8"> </span><span class="kd" id="mwAeA">var</span><span class="w" id="mwAeE"> </span><span class="n" id="mwAeI">txtHello</span><span class="p" id="mwAeM">:</span><span class="w" id="mwAeQ"> </span><span class="kt" id="mwAeU">TextField</span><span class="w" id="mwAeY"> </span><span class="o" id="mwAec">=</span><span class="w" id="mwAeg"> </span><span class="k" id="mwAek">new</span><span class="w" id="mwAeo"> </span><span class="kt" id="mwAes">TextField</span><span class="o" id="mwAew">();</span> <span class="w" id="mwAe0"> </span><span class="n" id="mwAe4">txtHello</span><span class="o" id="mwAe8">.</span><span class="na" id="mwAfA">text</span><span class="w" id="mwAfE"> </span><span class="o" id="mwAfI">=</span><span class="w" id="mwAfM"> </span><span class="s2" id="mwAfQ">"Hello World"</span><span class="o" id="mwAfU">;</span> <span class="w" id="mwAfY"> </span><span class="k" id="mwAfc">this</span><span class="o" id="mwAfg">.</span><span class="na" id="mwAfk">addChild</span><span class="o" id="mwAfo">(</span><span class="n" id="mwAfs">txtHello</span><span class="o" id="mwAfw">);</span> <span class="w" id="mwAf0"> </span><span class="o" id="mwAf4">}</span> <span class="w" id="mwAf8"> </span><span class="o" id="mwAgA">}</span> <span class="o" id="mwAgE">}</span>

ActionScript 3 can also be used in MXML files when using Apache's Flex framework:

<span id="mwAgg"></span><span class="cp" id="mwAgk"><?xml version="1.0" encoding="utf-8"?></span> <span class="nt" id="mwAgo"><s:Application</span> <span class="w" id="mwAgs"> </span><span class="na" id="mwAgw">xmlns:fx=</span><span class="s" id="mwAg0">"http://ns.adobe.com/mxml/2009"</span> <span class="w" id="mwAg4"> </span><span class="na" id="mwAg8">xmlns:s=</span><span class="s" id="mwAhA">"library://ns.adobe.com/flex/mx/polysylabi"</span> <span class="w" id="mwAhE"> </span><span class="na" id="mwAhI">xmlns:mx=</span><span class="s" id="mwAhM">"library://ns.adobe.com/flex/mx"</span> <span class="w" id="mwAhQ"> </span><span class="na" id="mwAhU">layout=</span><span class="s" id="mwAhY">"vertical"</span> <span class="w" id="mwAhc"> </span><span class="na" id="mwAhg">creationComplete=</span><span class="s" id="mwAhk">"initApp()"</span><span class="nt" id="mwAho">></span> <span class="nt" id="mwAhs"><fx:Script></span> <span class="s" id="mwAhw"><![CDATA[</span> <span class="w" id="mwAh0"> </span><span class="kd" id="mwAh4">public</span><span class="w" id="mwAh8"> </span><span class="kd" id="mwAiA">function </span><span class="nf" id="mwAiE">initApp</span><span class="o" id="mwAiI">():</span><span class="w" id="mwAiM"> </span><span class="kt" id="mwAiQ">void</span><span class="w" id="mwAiU"> </span><span class="o" id="mwAiY">{</span> <span class="w" id="mwAic"> </span><span class="c1" id="mwAig">// Prints our "Hello, world!" message into title</span> <span class="w" id="mwAik"> </span><span class="n" id="mwAio">title</span><span class="o" id="mwAis">.</span><span class="na" id="mwAiw">text</span><span class="w" id="mwAi0"> </span><span class="o" id="mwAi4">=</span><span class="w" id="mwAi8"> </span><span class="s2" id="mwAjA">"Hello, World!"</span><span class="o" id="mwAjE">;</span> <span class="w" id="mwAjI"> </span><span class="o" id="mwAjM">}</span> <span class="w" id="mwAjQ"> </span><span class="s" id="mwAjU">]]></span> <span class="nt" id="mwAjY"></fx:Script></span> <span class="nt" id="mwAjc"><s:Label</span><span class="w" id="mwAjg"> </span><span class="na" id="mwAjk">id=</span><span class="s" id="mwAjo">"title"</span><span class="w" id="mwAjs"> </span><span class="na" id="mwAjw">fontSize=</span><span class="s" id="mwAj0">"54"</span><span class="w" id="mwAj4"> </span><span class="na" id="mwAj8">fontStyle=</span><span class="s" id="mwAkA">"bold"</span><span class="w" id="mwAkE"> </span><span class="nt" id="mwAkI">/></span> <span class="nt" id="mwAkM"></s:Application></span>

Data structures

Data types

ActionScript primarily consists of "fundamental" or "simple" data types that are used to create other data types. These data types are very similar to Java data types. Since ActionScript 3 was a complete rewrite of ActionScript 2, the data types and their inheritances have changed.

ActionScript 2 top level data types

• String: A list of characters such as "Hello World"
• Number: Any Numeric value
• Boolean: A simple binary storage that can only be "true" or "false".
• Object: Object is the data type all complex data types inherit from. It allows for the grouping of methods, functions, parameters, and other objects.

ActionScript 2 complex data types

There are additional "complex" data types. These are more processor and memory intensive and consist of many "simple" data types. For AS2, some of these data types are:

• MovieClip: An ActionScript creation that allows easy usage of visible objects.
• TextField: A simple dynamic or input text field. Inherits the MovieClip type.
• Button: A simple button with 4 frames (states): Up, Over, Down and Hit. Inherits the MovieClip type.
• Date: Allows access to information about a specific point in time.
• Array: Allows linear storage of data.
• XML: An XML object
• XMLNode: An XML node
• LoadVars: A Load Variables object allows for the storing and send of HTTP POST and HTTP GET variables
• Sound
• NetStream
• NetConnection
• MovieClipLoader
• EventListener

ActionScript 3 primitive (prime) data types

• Boolean: The Boolean data type has only two possible values: true and false or 1 and 0. No other values are valid.
• int: The int data type is a 32-bit integer between -2,147,483,648 and 2,147,483,647.
• Null: The Null data type contains only one value, null. This is the default value for the String data type and all classes that define complex data types, including the Object class.
• Number: The Number data type can represent integers, unsigned integers, and floating-point numbers. The Number data type uses the 64-bit double-precision format as specified by the IEEE Standard for Binary Floating-Point Arithmetic (IEEE-754). The Number type can store integers between -9,007,199,254,740,992 (-2⁵³) to 9,007,199,254,740,992 (2⁵³), and floating-point values between Number.MAX_VALUE (1.79769313486231e+308) and Number.MIN_VALUE (4.940656458412467e-324).
• String: The String data type represents a sequence of 16-bit characters. Strings are stored internally as Unicode characters, using the UTF-16 format. Previous versions of Flash used the UTF-8 format.
• uint: The uint (unsigned integer) data type is a 32-bit unsigned integer between 0 and 4,294,967,295.
• void: The void data type contains only one value, undefined. In previous versions of ActionScript, undefined was the default value for instances of the Object class. In ActionScript 3.0, the default value for Object instances is null.

ActionScript 3 some complex data types

• Array: Contains a list of data. Though ActionScript 3 is a strongly typed language, the contents of an Array may be of any type and values must be cast back to their original type after retrieval (support for typed Arrays has recently been added with the Vector class).
• Date: A date object containing the date/time digital representation.
• Error: A generic error object that allows runtime error reporting when thrown as an exception.
• flash.display:Bitmap: A non-animated bitmap display object.
• flash.display:MovieClip: Animated movie clip display object; Flash timeline is, by default, a MovieClip.
• flash.display:Shape: A non-animated vector shape object.
• flash.display:SimpleButton: A simple interactive button type supporting "up", "over", and "down" states with an arbitrary hit area.
• flash.display:Sprite: A display object container without a timeline.
• flash.media:Video: A video playback object supporting direct (progressive download) or streaming (RTMP) transports. As of Flash Player version 9.0.115.0, the H.264/MP4 high-definition video format is also supported alongside standard Flash video (FLV) content.
• flash.text:TextField: A dynamic, optionally interactive text field object.
• flash.utils:ByteArray: Contains an array of binary byte data.
• flash.utils:Dictionary: Dictionaries are a variant of Object that may contain keys of any data type (whereas Object always uses strings for its keys).
• Function: The core class for all Flash method definitions.
• Object: The Object data type is defined by the Object class. The Object class serves as the base class for all class definitions in ActionScript. Objects in their basic form can be used as associative arrays that contain key-value pairs, where keys are Strings and values may be any type.
• RegExp: A regular expression object for strings.
• Vector: A variant of array supported when publishing for Flash Player 10 or above. Vectors are typed, dense Arrays (values must be defined or null) which may be fixed-length, and are bounds-checked during retrieval. Vectors are not just more typesafe than Arrays but also perform faster.
• XML: A revised XML object based on the E4X (Standard ECMA-357); nodes and attributes are accessed differently from ActionScript 2.0 object (a legacy class named XMLDocument is provided for backwards compatibility).
• XMLList: An array-based object for various content lookups in the XML class.

Using data types

The basic syntax is:

<span id="mwAr8"></span><span class="k" id="mwAsA">var</span><span class="w" id="mwAsE"> </span><span class="nx" id="mwAsI">variableName</span><span class="o" id="mwAsM">:</span><span class="w" id="mwAsQ"> </span><span class="nx" id="mwAsU">VariableType</span><span class="w" id="mwAsY"> </span><span class="o" id="mwAsc">=</span><span class="w" id="mwAsg"> </span><span class="k" id="mwAsk">new</span><span class="w" id="mwAso"> </span><span class="nx" id="mwAss">VariableType</span><span class="p" id="mwAsw">(</span><span class="nx" id="mwAs0">param1</span><span class="o" id="mwAs4">,</span><span class="w" id="mwAs8"> </span><span class="nx" id="mwAtA">param2</span><span class="o" id="mwAtE">,</span><span class="w" id="mwAtI"> </span><span class="p" id="mwAtM">...</span><span class="o" id="mwAtQ">,</span><span class="w" id="mwAtU"> </span><span class="nx" id="mwAtY">paramN</span><span class="p" id="mwAtc">);</span>

So in order to make an empty Object:

<span id="mwAts"></span><span class="k" id="mwAtw">var</span><span class="w" id="mwAt0"> </span><span class="nx" id="mwAt4">myObject</span><span class="o" id="mwAt8">:</span><span class="w" id="mwAuA"> </span><span class="nb" id="mwAuE">Object</span><span class="w" id="mwAuI"> </span><span class="o" id="mwAuM">=</span><span class="w" id="mwAuQ"> </span><span class="k" id="mwAuU">new</span><span class="w" id="mwAuY"> </span><span class="nb" id="mwAuc">Object</span><span class="p" id="mwAug">();</span>

Or, in an informal way:

<span id="mwAuw"></span><span class="k" id="mwAu0">var</span><span class="w" id="mwAu4"> </span><span class="nx" id="mwAu8">myObject</span><span class="w" id="mwAvA"> </span><span class="o" id="mwAvE">=</span><span class="w" id="mwAvI"> </span><span class="p" id="mwAvM">{};</span>

Some types are automatically put in place:

<span id="mwAvc"></span><span class="k" id="mwAvg">var</span><span class="w" id="mwAvk"> </span><span class="nx" id="mwAvo">myString</span><span class="o" id="mwAvs">:</span><span class="w" id="mwAvw"> </span><span class="nb" id="mwAv0">String</span><span class="w" id="mwAv4"> </span><span class="o" id="mwAv8">=</span><span class="w" id="mwAwA"> </span><span class="s2" id="mwAwE">"Hello Wikipedia!"</span><span class="o" id="mwAwI">;</span><span class="w" id="mwAwM"> </span><span class="c1" id="mwAwQ">// This would automatically set the variable as a string.</span> <span class="k" id="mwAwU">var</span><span class="w" id="mwAwY"> </span><span class="nx" id="mwAwc">myNumber</span><span class="o" id="mwAwg">:</span><span class="w" id="mwAwk"> </span><span class="nb" id="mwAwo">Number</span><span class="w" id="mwAws"> </span><span class="o" id="mwAww">=</span><span class="w" id="mwAw0"> </span><span class="mi" id="mwAw4">5</span><span class="o" id="mwAw8">;</span><span class="w" id="mwAxA"> </span><span class="c1" id="mwAxE">// This would do the same for a number.</span> <span class="k" id="mwAxI">var</span><span class="w" id="mwAxM"> </span><span class="nx" id="mwAxQ">myObject</span><span class="o" id="mwAxU">:</span><span class="w" id="mwAxY"> </span><span class="nb" id="mwAxc">Object</span><span class="w" id="mwAxg"> </span><span class="o" id="mwAxk">=</span><span class="w" id="mwAxo"> </span><span class="p" id="mwAxs">{</span><span class="w" id="mwAxw"> </span><span class="nx" id="mwAx0">param1</span><span class="o" id="mwAx4">:</span><span class="w" id="mwAx8"> </span><span class="s2" id="mwAyA">"Hi!"</span><span class="o" id="mwAyE">,</span><span class="w" id="mwAyI"> </span><span class="nx" id="mwAyM">param2</span><span class="o" id="mwAyQ">:</span><span class="w" id="mwAyU"> </span><span class="mi" id="mwAyY">76</span><span class="w" id="mwAyc"> </span><span class="p" id="mwAyg">};</span><span class="w" id="mwAyk"> </span><span class="c1" id="mwAyo">// This creates an object with two variables.</span> <span class="c1" id="mwAys">// param1 is a string with the data of "Hi!",</span> <span class="c1" id="mwAyw">// and param2 is a number with the data of 76.</span> <span class="c1" id="mwAy0">// This is the syntax for automatically creating an Array.</span> <span class="k" id="mwAy4">var</span><span class="w" id="mwAy8"> </span><span class="nx" id="mwAzA">myArray</span><span class="o" id="mwAzE">:</span><span class="w" id="mwAzI"> </span><span class="nb" id="mwAzM">Array</span><span class="w" id="mwAzQ"> </span><span class="o" id="mwAzU">=</span><span class="w" id="mwAzY"> </span><span class="p" id="mwAzc">[</span><span class="mi" id="mwAzg">5</span><span class="o" id="mwAzk">,</span><span class="w" id="mwAzo"> </span><span class="s2" id="mwAzs">"Hello!"</span><span class="o" id="mwAzw">,</span><span class="w" id="mwAz0"> </span><span class="p" id="mwAz4">{</span><span class="w" id="mwAz8"> </span><span class="nx" id="mwA0A">a</span><span class="o" id="mwA0E">:</span><span class="w" id="mwA0I"> </span><span class="mi" id="mwA0M">5</span><span class="o" id="mwA0Q">,</span><span class="w" id="mwA0U"> </span><span class="nx" id="mwA0Y">b</span><span class="o" id="mwA0c">:</span><span class="w" id="mwA0g"> </span><span class="mi" id="mwA0k">7</span><span class="w" id="mwA0o"> </span><span class="p" id="mwA0s">}];</span> <span class="c1" id="mwA0w">// It creates an Array with 3 variables.</span> <span class="c1" id="mwA00">// The first (0) is a number with the value of 5,</span> <span class="c1" id="mwA04">// the second (1) is a string with the value of "Hello!",</span> <span class="c1" id="mwA08">// and the third (2) is an object with { a: 5, b: 7 }.</span>

Unlike some object-oriented languages, ActionScript makes no distinction between primitive types and reference types. In ActionScript, all variables are reference types. However, objects that belong to the primitive data types, which includes Boolean, Number, int, uint, and String, are immutable.

So if a variable of a supposedly primitive type, e.g. an integer is passed to a function, altering that variable inside the function will not alter the original variable, as a new int Object is created when inside the function. If a variable of another (not primitive) datatype, e.g. XML is passed to a function, altering that variable inside the function will alter the original variable as well, as no new XML Object is created.

Some data types can be assigned values with literals:

<span id="mwA1w"></span><span class="k" id="mwA10">var</span><span class="w" id="mwA14"> </span><span class="nx" id="mwA18">item1</span><span class="o" id="mwA2A">:</span><span class="w" id="mwA2E"> </span><span class="nb" id="mwA2I">String</span><span class="w" id="mwA2M"> </span><span class="o" id="mwA2Q">=</span><span class="w" id="mwA2U"> </span><span class="s2" id="mwA2Y">"ABC"</span><span class="o" id="mwA2c">;</span> <span class="k" id="mwA2g">var</span><span class="w" id="mwA2k"> </span><span class="nx" id="mwA2o">item2</span><span class="o" id="mwA2s">:</span><span class="w" id="mwA2w"> </span><span class="nb" id="mwA20">Boolean</span><span class="w" id="mwA24"> </span><span class="o" id="mwA28">=</span><span class="w" id="mwA3A"> </span><span class="kc" id="mwA3E">true</span><span class="o" id="mwA3I">;</span> <span class="k" id="mwA3M">var</span><span class="w" id="mwA3Q"> </span><span class="nx" id="mwA3U">item3</span><span class="o" id="mwA3Y">:</span><span class="w" id="mwA3c"> </span><span class="nb" id="mwA3g">Number</span><span class="w" id="mwA3k"> </span><span class="o" id="mwA3o">=</span><span class="w" id="mwA3s"> </span><span class="mi" id="mwA3w">12</span><span class="o" id="mwA30">;</span> <span class="k" id="mwA34">var</span><span class="w" id="mwA38"> </span><span class="nx" id="mwA4A">item4</span><span class="o" id="mwA4E">:</span><span class="w" id="mwA4I"> </span><span class="nb" id="mwA4M">Array</span><span class="w" id="mwA4Q"> </span><span class="o" id="mwA4U">=</span><span class="w" id="mwA4Y"> </span><span class="p" id="mwA4c">[</span><span class="s2" id="mwA4g">"a"</span><span class="o" id="mwA4k">,</span><span class="w" id="mwA4o"> </span><span class="s2" id="mwA4s">"b"</span><span class="o" id="mwA4w">,</span><span class="w" id="mwA40"> </span><span class="s2" id="mwA44">"c"</span><span class="p" id="mwA48">];</span> <span class="k" id="mwA5A">var</span><span class="w" id="mwA5E"> </span><span class="nx" id="mwA5I">item5</span><span class="o" id="mwA5M">:</span><span class="w" id="mwA5Q"> </span><span class="nb" id="mwA5U">Object</span><span class="w" id="mwA5Y"> </span><span class="o" id="mwA5c">=</span><span class="w" id="mwA5g"> </span><span class="p" id="mwA5k">{</span><span class="w" id="mwA5o"> </span><span class="nx" id="mwA5s">name</span><span class="o" id="mwA5w">:</span><span class="w" id="mwA50"> </span><span class="s2" id="mwA54">"Actionscript"</span><span class="o" id="mwA58">,</span><span class="w" id="mwA6A"> </span><span class="nx" id="mwA6E">version</span><span class="o" id="mwA6I">:</span><span class="w" id="mwA6M"> </span><span class="s2" id="mwA6Q">"3.0"</span><span class="w" id="mwA6U"> </span><span class="p" id="mwA6Y">};</span> <span class="k" id="mwA6c">var</span><span class="w" id="mwA6g"> </span><span class="nx" id="mwA6k">item6</span><span class="o" id="mwA6o">:</span><span class="w" id="mwA6s"> </span><span class="nb" id="mwA6w">XML</span><span class="w" id="mwA60"> </span><span class="o" id="mwA64">=</span><span class="w" id="mwA68"> </span><span class="o" id="mwA7A"><</span><span class="nx" id="mwA7E">node</span><span class="o" id="mwA7I">><</span><span class="nx" id="mwA7M">child</span><span class="w" id="mwA7Q"> </span><span class="sr" id="mwA7U">/></</span><span class="nx" id="mwA7Y">node</span><span class="o" id="mwA7c">>;</span><span class="w" id="mwA7g"> </span><span class="c1" id="mwA7k">// Note that the primitive XML is not quoted</span>

A reference in ActionScript is a pointer to an instance of a class. A reference stores the memory address of an object – operations against references will follow the value of the reference to the memory address of the object and carry out the operation on that object. All objects in ActionScript are accessed through references instead of being accessed directly.

<span id="mwA70"></span><span class="k" id="mwA74">var</span><span class="w" id="mwA78"> </span><span class="nx" id="mwA8A">item1</span><span class="o" id="mwA8E">:</span><span class="w" id="mwA8I"> </span><span class="nb" id="mwA8M">XML</span><span class="w" id="mwA8Q"> </span><span class="o" id="mwA8U">=</span><span class="w" id="mwA8Y"> </span><span class="k" id="mwA8c">new</span><span class="w" id="mwA8g"> </span><span class="nb" id="mwA8k">XML</span><span class="p" id="mwA8o">(</span><span class="s2" id="mwA8s">"<node><child /></node>"</span><span class="p" id="mwA8w">);</span> <span class="k" id="mwA80">var</span><span class="w" id="mwA84"> </span><span class="nx" id="mwA88">item2</span><span class="o" id="mwA9A">:</span><span class="w" id="mwA9E"> </span><span class="nb" id="mwA9I">XML</span><span class="w" id="mwA9M"> </span><span class="o" id="mwA9Q">=</span><span class="w" id="mwA9U"> </span><span class="nx" id="mwA9Y">item1</span><span class="o" id="mwA9c">;</span> <span class="nx" id="mwA9g">item2</span><span class="p" id="mwA9k">.</span><span class="nx" id="mwA9o">firstChild</span><span class="p" id="mwA9s">.</span><span class="nx" id="mwA9w">attributes</span><span class="p" id="mwA90">.</span><span class="nx" id="mwA94">value</span><span class="w" id="mwA98"> </span><span class="o" id="mwA-A">=</span><span class="w" id="mwA-E"> </span><span class="mi" id="mwA-I">13</span><span class="o" id="mwA-M">;</span> <span class="c1" id="mwA-Q">// item1 now equals item2 since item2 simply points to what item1 points to.</span> <span class="c1" id="mwA-U">// Both are now:</span> <span class="c1" id="mwA-Y">// <node><child value="13" /></node></span>

Only references to an object may be removed by using the "delete" keyword. Removal of actual objects and data is done by the Flash Player garbage collector which checks for any existing references in the Flash memory space. If none are found (no other reference is made to the orphaned object), it is removed from memory. For this reason, memory management in ActionScript requires careful application development planning.

<span id="mwA-o"></span><span class="k" id="mwA-s">var</span><span class="w" id="mwA-w"> </span><span class="nx" id="mwA-0">item1</span><span class="o" id="mwA-4">:</span><span class="w" id="mwA-8"> </span><span class="nb" id="mwA_A">XML</span><span class="w" id="mwA_E"> </span><span class="o" id="mwA_I">=</span><span class="w" id="mwA_M"> </span><span class="k" id="mwA_Q">new</span><span class="w" id="mwA_U"> </span><span class="nb" id="mwA_Y">XML</span><span class="p" id="mwA_c">(</span><span class="s2" id="mwA_g">"<node><child /></node>"</span><span class="p" id="mwA_k">);</span> <span class="nx" id="mwA_o">delete</span><span class="w" id="mwA_s"> </span><span class="nx" id="mwA_w">item1</span><span class="o" id="mwA_0">;</span> <span class="c1" id="mwA_4">// If no other reference to item1 is present anywhere else in the application,</span> <span class="c1" id="mwA_8">// it will be removed on the garbage collector's next pass</span>

Code protection

Like most bytecode file formats, Flash SWF files can be decompiled into their source code and assets (similarly to how Microsoft .NET files can be decompiled). Some decompilers are capable of nearly full reconstruction of the original source file, approximate to the actual code that was used during creation (although results vary on a case-by-case basis).

In opposition to the decompilers, ActionScript obfuscators have been introduced, which transform code into a form that breaks decompiler output while preserving the functionality and structure of the program. Higher-quality obfuscators implement lexical transformations such as identifier renaming, control flow transformation, and data abstraction transformation which collectively make it harder for decompilers to generate output likely to be useful to a human. Less robust obfuscators insert traps for decompilers. Such obfuscators either cause the decompiler software to crash unexpectedly or to generate unintelligible source code.