Workaround for Flash Builder & Zend installation problems (for Windows 7 64-bit edition)

Very recently, I was reviewing a tutorial for a Flex and PHP integration and ran into an issue in Flash Builder that got me stuck for a little while. I first installed Flash Builder for PHP and Zend (with phpMyAdmin) and load Zend with a sample database. I then created a Flex server (PHP) project and make a connection on my file with a PHP data service (select Data–> Connect to PHP from the menu bar). Going through the PHP service configuration wizard, I didn’t have an existing PHP class and asked Flash Builder to generate one instead. Using the login information from phpMyAdmin, I encounter the following error:

Click to enlarge

The error is currently reported as a bug:  This issue only occurs in Windows 7 64-bit edition because under the C drive, Windows contains two program file folders: “Program Files” and “Program Files (x86)”. Since Windows sets the default installation path for non-64-bit programs to be “C:\Program Files (x86)\”. Zend returns an error when it encounters the ” ( ” in the directory.

If you’re currently running into this issue, please uninstall Zend from your computer completely and follow the steps below.

  1. Install the latest version of Zend (currently version 5.5).
  2. In the installation wizard and when selecting a web server, be sure to specify your destination folder to be outside of “Program Files (x86)”. i.e. “C:\”.
  3. After installation, Flash Builder should be able to interact with Zend without any further issues.

Thiis issue has a number of variations, so please feel free to ask questions about this workaround.


Adobe Cookbooks – Recipe Request Challenge

Write some Flex code and get a chance to win a Samsung 10.1 tablet.

With the help of the user community and several Adobe employees, we have identified a list of recipe requests that we feel would be valuable contributions to the Adobe Cookbooks as well as for the larger Adobe community.  All that these requests need now are answers…and that’s where the challenge comes in!

For every recipe request below, the community member who provides the solution will receive:

  1. An Adobe Developer Connection t-shirt
  2. A chance at a Samsung 10.1 tablet

Adobe Cookbook recipes are snippets of code that are shared by community members to assist fellow developers in overcoming specific development issues; example here.  If a developer cannot locate a recipe to solve their issue they may submit a recipe request, where they outline the issue they are having in the hopes that someone else in the community may have a code snippet to share.  When a recipe request gets answered, it gets published as a regular recipe, same as the example linked above.

See this page for more information: Adobe Cookbooks – Recipe Request Challenge


Stephen Gilson
Flex Doc Team

What’s not to like?

About 8 months ago, we added a pair of radio buttons to all the Flex 4.5 doc and ActionScript language reference pages that asks you is the content was helpful:

What we were hoping for was a large amount of data, good or bad, that would tell us where weaknesses and strengths exist in the documentation. This would give us much more insight into the efficacy of individual pages, or into groups of pages. It would also help us decide where to put our resources when updating the documentation. Unfortunately, the number of ratings has been extremely low. Like lower than many banner ad click through rates. Like lower than my Angry Birds score kind-of-low.

So, why aren’t you rating the pages?

Are you too busy as a developer to rate the page?
Maybe you’ve got a lot on your mind when you end up at a Flex doc page, and don’t want to distract from your thought process, especially if you’re copying/pasting a code example or trying to grok something.

Are you worried about privacy?
There is absolutely no way for us to track your rating or any comments you add with that rating. It is completely anonymous.

Is the location of the rating “widget” inconvenient?
The widget currently appears at the top of the page. But Flex doc pages tend to be long and dense with material, so maybe you see it and then just forget about it. We’ve thought about moving the widget to the bottom of the page, or adding it multiple times to the pages, but we don’t want to get in your way, either.

Do you think we ignore this data?
We don’t. We look at it very closely, and even read the comments.

We’d love to get your feedback (here, and, of course, on the help pages)!

-Matthew J. Horn
Flex doc team

Add Chrome Search Extension for the ActionScript® 3.0 API Reference (ASDoc)

Use the ActionScript® 3.0 Reference as the API reference for many Adobe products, including Flash Player, AIR, Flex, and LiveCycle. To improve searching of the reference in Chrome, install the “ActionScript 3.0 Search” extension:

ActionScript 3.0 Search


Stephen Gilson
Flex Doc Team

Context-sensitive language reference Help in Flash Builder

Context-sensitive language reference Help is not really a new feature in Flash Builder. However, we figured that several people were not aware of the ways in which you can access the ActionScript language reference and ASDoc content from within Flash Builder.

So, this post describes the ways in which you can quickly access the ActionScript API reference and the ASDoc content while writing code.

Display the ActionScript Language Reference in a swift keystroke

The Adobe ActionScript Language Reference is integrated into the MXML and ActionScript editors and lets you quickly view the reference Help for an MXML tag or property, a class, or a Flex framework element.

  1. In the MXML or ActionScript editor, select a Flex framework element (a word in your code) by highlighting or placing the mouse pointer in the word.
  2. To open the relevant ActionScript Language Reference topic directly in the Help viewer, press Shift+F2.
ActionScript Language Reference


Display ASDoc content in code hints, as a tool tip, and in the ASDoc view

Flash Builder displays ASDoc content in code hints, as a tool tip while hovering over a code element, and in the ASDoc view.

  1. Begin entering a line of code that contains either an MXML or ActionScript class. You can also hover over the class. As you type, ASDoc content for the class displays next to the code hints, as follows:

    ASDoc Code Hints

    ASDoc Code Hints

  2. If you hover over a class, just the ASDoc reference summary appears. To display the content in a separate, scrollable window, press F2.The ASDoc content is displayed as follows:
    ASDoc Content

    ASDoc Content

    When you finish reading the documentation, click outside the ASDoc window to close it.

  3. To display the complete ASDoc content in a dockable ASDoc view in Flash Builder, select Window > Show View > Other, and select ASDoc.A quicker way of displaying the ASDoc view is to press Ctrl+3, type asdoc, and select Views, as follows:
    ASDoc view

    ASDoc view

    Note: This feature supports user-generated ASDoc documentation. That is, you can document your custom components by adding ASDoc comments to the code that implements the components. The ASDoc comments are then available as code hints in the MXML and ActionScript editors.
    For more information on creating ASDoc comments for your source files, see ASDoc.

New Features Added to Adobe ActionScript API Reference (ASDoc)

Use the ActionScript® 3.0 Reference for the Adobe® Flash® Platform as the API reference for many Adobe products, including Flash Player, AIR, and Flex. The new release of the ActionScript Reference ( contains several new features:

  • Support for a quick search added to the Packages and Classes lists.The quick search lets you filter the content of the Packages and Classes lists as you type. This feature is not supported on IE 7 and IE 8.
  • When displaying all classes in the Classes list, selecting a class name in the list continues to display all classes.In the previous release, selecting a class name in the Classes list while displaying all classes changed the Classes list to display only the classes in the package of the selected class.
  • Added a Home link to the top of all pages.The Home link lets you navigate back to the index.html page from anywhere in the reference.
  • Fixes for issues associated with localization and translation.


Stephen Gilson
Flex Doc Team

Tips for creating mobile applications

Adobe evangelist Mike Jones posted some advice for creating mobile applications with the mobile workflow in Flash Builder 4.5. These are a great collection of tips that come from someone who has hands-on experience developing real-world applications.

My 10 Tips When Developing For Multiple Devices

I suggest you check them out before you start your next project!

-Matthew J. Horn
Flex doc team

Handle hardware keyboard events in a Flex mobile application

In a mobile application built in Flex, you can detect when the user presses a hardware key on a mobile device. For example, on an Android device you can detect when the user presses the Home button, Back button, or Menu button.

To detect when the user presses a hardware key, create an event handlers for the KEY_UP or KEY_DOWN event. Typically, you attach the event handlers to the application object as defined by the Application, ViewNavigatorApplication, or TabbedViewNavigatorApplication containers.

The Stage object defines the drawing area of a Flex application. Each application has one Stage object. Therefore, an application container is actually a child container of the Stage object.

The Stage.focus property specifies the component that currently has keyboard focus, or contains null if no component has focus. The component with keyboard focus is the one that receives event notification when the user interacts with the keyboard. Therefore, if Stage.focus is set to the application object, the application object’s event handlers are invoked.

On a mobile device, your application can be interrupted by another application. For example, the mobile device can receive a phone call while your application is running, or the user can switch to a different application.  When the user switches back to your application, the Stage.focus property is set to null. Therefore, event handlers assigned to the application object do not respond to the keyboard.

Because the Stage.focus property can be null on a mobile application, listen for keyboard events on the Stage object itself to guarantee that your application recognizes the event. The following example assigns keyboard event handlers to the Stage object:

<?xml version="1.0" encoding="utf-8"?>
<s:ViewNavigatorApplication xmlns:fx=""
    xmlns:s="library://" firstView="views.View1"


            // Add the hardware key event handlers to the stage.
            protected function appCompleteHandler(event:FlexEvent):void {
                stage.addEventListener("keyDown", handleButtons, false,1);
                stage.addEventListener("keyUp", handleButtons, false, 1);

            // Event handler to handle hardware keyboard keys.
            protected function handleButtons(event:KeyboardEvent):void
                if (event.keyCode == Keyboard.HOME) {
                    // Handle Home button.
                else if (event.keyCode == Keyboard.BACK) {
                    // Hanlde back button.


Stephen Gilson
Flex Doc Team

A great resource for Flex, Flash Builder, and Flash Platform content

Hi all,
Last Summer, Brian Rinaldi joined our group as Web Community Manager for the Flash Platform. This covers a lot of ground, but Brian has done a great job, and one of his biggest contributions is a weekly list of blog posts and other news related to the Flash Platform. So if you haven’t already, visit and read through his “Cool stuff…” posts.

He posts pretty much every week, so I recommend you bookmark this URL and visit it often!

Flex 4.5 Example Source Code

Below is a link to a ZIP file that contains all the source code and assets for the Flex 4.5 examples that are used in the core documentation. This includes the *.mxml and *.as files, as well as the stylesheets, images, videos, audio files, and other assets that they use. This ZIP file also includes the mobile examples. It does not include the compiled SWF files for these examples, but it should be useful to you if you like to search for and look at source code for the Flex 4.5 examples.

The ZIP file is organized roughly by topic. For example, the Spark DataGrid examples are in the code\dpcontrols\sparkdpcontrols\ directory of the ZIP file. The mobile skinning examples are in code\mobile_skins.

flex45_using_examples_source (30MB)