What's New In Version 2 Components - MACROMEDIA FLASH MX 2004-USING COMPONENTS Use Manual

Version 2 components are included in the Components panel as compiled clip (SWC) symbols. A
compiled clip is a component movie clip whose code has been compiled. Compiled clips cannot
be edited, but you can change their parameters in the Property inspector and Component
inspector, just as you would with any component. For more information, see
clips and SWC files" on page
Version 2 components are written in ActionScript 2.0. Each component is a class and each class is
in an ActionScript package. For example, a radio button component is an instance of the
RadioButton class whose package name is mx.controls. For more information about packages, see
"Using packages" in Using ActionScript in Flash.
Most UI components built with version 2 of the Macromedia Component Architecture are
subclasses of the UIObject and UIComponent classes and inherit all properties, methods, and
events from those classes. Many components are also subclasses of other components. The
inheritance path of each component is indicated in its entry in
Dictionary," on page
Note: The class hierarchy is also available as a GIF file (v2_Flash_component_arch.gif) in the
Examples folder.
All components also use the same event model, CSS-based styles, and built-in themes and
skinning mechanisms. For more information on styles and skinning, see
Components," on page
with Components," on page
For a detailed explanation of the version 2 component architecture, see
Components," on page

What's new in version 2 components

This section outlines the differences between version 1 and version 2 components from the
perspective of a developer using components to build Flash applications. For detailed information
about the differences between the version 1 and version 2 architectures for building components,
see Chapter 7, "Creating Components," on page
The Component inspector
Macromedia Flash and Macromedia Dreamweaver. (See
on page 47.)
The listener event model
Component Events," on page
inspector, as there was in Flash MX; you must write ActionScript code to handle events.
Skin properties
a check box) at runtime. (See
CSS-based styles
styles to customize component color and text" on page
following syntax:
Themes
allow you to drag a new look from the library onto a set of components. (See
themes" on page
16 Chapter 1: About Components
17.
91.
67. For more information on event handling, see
43.
915.
allows you to change component parameters while authoring in
allows listeners to handle events. (See
55.) There isn't a
let you load individual skins (for example, up and down arrows or the check for
"About skinning components" on page
allow you to create a consistent look and feel across applications. (See
componentInstance.setStyle("styleName", value)
77.)
Chapter 6, "Components
915.
"Setting component parameters"
Chapter 4, "Handling
parameter in the Property
clickHandler
80.)
67.) To set a component style, use the
"About compiled
Chapter 5, "Customizing
Chapter 3, "Working
Chapter 7, "Creating
"Using
.
"About