Flash CS4 ACE Objectives

These days, becoming an ACE (Adobe Certified Expert) can give you a leg up in landing a job, not to mention honing your skills to a finely burnished edge.

To become an ACE you need to pass a closed-book, multiple choice test: you sit in front of a computer screen and answer the questions. The test is administered by Pearson VUE or Thomson Prometric at their testing facilities world-wide.

Pearson VUE: check for locations online at www.pearsonvue.com

Thomson Prometric: check for locations online at www.2test.com


Below the Adobe Flash CS4 ACE Objectives, all the Flash topics that will come up on the ACE test.

To prepare for the test you may be interested in taking our Flash Level 1 class and our Flash Level 2 class (Actionscript). We make sure to go over the ACE Objectives in the class, and we provide resources and sample tests after the class. The classes are described on our web site Multimedia Resource Group http://www.multigroup.com

Self-employed and unemployed people may qualify for a discount for these classes.


Flash CS4ACE Exam Objectives

1.0 Planning and designing Flash applications
1.1 Given a scenario, choose the appropriate type of image asset and explain when and
why you would use that asset type. (Image asset types include: vector, bitmap, SVG)
1.2 Given a requirement based on your audience, determine the appropriate Flash features and options used to meet the needs of your audience. (Audience requirements
include: publishing to AIR, accessibility, player version)

2.0 Creating and managing assets
2.1 Given an option in the Library panel, explain the purpose of and how to use that
option.
2.2 Given a tool, create a shape by using that tool. (Tools include: Deco, Spray Brush, Rectangle Primitive)
2.3 Given a tool, work with an existing asset by using that tool. (Tools include: Transform, 3D Rotation, Bone)
2.4 Given an asset, modify individual properties to achieve specific design requirements. (Design requirements include: advanced text controls including anti-aliasing,stroke control and styling)
2.5 Import external assets into Flash. (External assets include: XFL from InDesign or
After Effects, Photoshop files, Illustrator files, and images)
2.6 Create and manage text fields by using the Text tool.
2.7 Given an asset, convert that asset to a symbol.
2.8 Given a component, explain the purpose of or how to use that component.
2.9 Edit the skin of a component.

3.0 Creating Flash movies
3.1 Create animations by using the Timeline.
3.2 Edit animations by using the Motion Editor.
3.3 Reuse animations by using Motion Presets.
3.4 Incorporate and manage audio and video in your movie.
3.5 Apply filters and effects to Movie Clips and text.
3.6 Manage performance by utilizing bitmap techniques.
3.7 Apply inverse kinematics to objectives by using the Bone tool.

4.0 Programming with ActionScript 3.0
4.1 Given an ActionScript class, create an instance from and work with the properties of that class.
4.2 Given an object-oriented concept, explain the definition of or purpose associated
with that concept. (Object-oriented concepts include: Classes, Interfaces, Inheritance, Polymorphism, and Packages)
4.3 Create custom classes. (Options include: Extending, Subclassing)
4.4 Explain how to use the Document class.
4.5 Load content and data from external sources. (Sources include: XML, SWF, and
remote objects)

5.0 Testing, publishing, and deploying Flash movies
5.1 Recognize effective optimization considerations when testing and debugging Flash
applications.
5.2 Test an application by using the Debugger.
5.3 Given a code snippet, find the error in that code snippet.
5.4 Given a scenario, select the appropriate Publish settings to deploy a Flash movie. (Scenarios include: Web delivery and AIR)

Overview of the Debugger in Flash CS4

Using the Debugger Overview

Ok, this is not the sexiest Flash topic out there, but I've found very little on this topic when I did a search so I thought I'd make this contribution for the collective benefit of Flashinistas world-wide.

The Debugger in Flash CS4 is a window and set of related tools to help you “debug” or troubleshoot Actionscript code that is not executing properly. Typically to make full use of the Debugger you’ll need to set a breakpoint in your code that tells the Flash player to stop executing your Actionscript at the particular line in your code where the breakpoint is set. Think of it as a tool that allows you to freeze time, or at least the time during which your Actionscript code is executing.
Then using tools in the Debug Window you can very deliberately choose to execute the specific line of code in which the breakpoint is set and then observe what happens. This ability, to step through your code (among other related tools which will be described in greater detail below) line by line can be extremely useful when trying to find the fly in the ointment (or the bug in your code).

Try this simple example:

Create a new file.
Select the keyframe in frame one , open the Actions panel and add the three trace statements, one on each line:

trace(“first”);|
trace(“second ”);
trace(“third ”);

Add a breakpoint by only after before the first trace, clicking to the left of the number 1 (the line numbers that should automatically be generated as you write Actionscript code. A red circle indicating the break point should appear.

Select Debug Movie from the Debug menu to enter the debugging window.
You’ll notice a set of interrelated panels: in the upper left the Debug Console; lower left Variable Panel; The area at the top center display a line (or lines if more than one) where Actionscript was encountered in the file, below that the code for the currently selected frame or a selected external Actionscript file; and the Output panel at the bottom .
You will notice that the string “First” being evaluated from the first trace function has not yet appeared in the Output panel, the reason is the break point stopped the execution of the code just before that line was executed.

In the Debug Console panel in the upper left hand side click on the green “Continue” button which will execute all the code till another break point is encountered. . Note that the evaluation of the trace function now appears in the output panel and all three trace statements appear: “first”, “second”, “third”.

Close the Debug window by either clicking on the large red X in the Debug Console or clicking on the close button for the swf file that was generated when you first choose Debug movie.
Go back to the Flash file and execute Debug Movie again.
This time click on the Step Over button which will cause the debugger to jump to the next line of code and stop. Continue clicking on the Step Over button to step through your code line by line. If there were any variables and properties in your code you can seethem and check their values changing in the Variables panel in the lower left corner.

Note the other two buttons:
Step In will jump to any function or method reference on the current breakpoint line and then step through the code of that function or method a line at a time.
Step Out moves the debugger to the exit point of the current function or method, typically to where the function or method returns a value (if it returns a value.

Mastering the debugger just takes a little knowledge and a bit of practice, and it's on the ACE test!