Personal tools

Views

Flash Builder 4:Release Notes

From Adobe Labs

Table of contents
1 Overview

1.1 What's New

2 Comparison of MX and Spark Components
3 System requirements
4 Installation Instructions

4.1 Installing Flash Builder 4 Beta 2

4.1.1 Installing Flash Builder stand-alone
4.1.2 Installing Flash Builder plug-in

4.2 Installing Flex SDK 4 Beta 2

4.2.1 Uninstall Current Flash Player
4.2.2 To install the Flex SDK:

4.3 Install and Configure Flex and AIR Automated Testing

4.3.1 Use run-time automated testing (recommended) for Flex Applications
4.3.2 Compile your applications with static automation support for Flex Applications
4.3.3 Compile your applications with static automation support for AIR Applications
4.3.4 Flex 4 Plug-in for HP QuickTest Professional

4.3.4.1 Installing the Plug-in
4.3.4.2 Using the Plug-in

4.4 Uninstalling

4.4.1 Uninstalling Flash Builder
4.4.2 Uninstalling Flash Player

5 Documentation
6 Compatibility Issues
7 Known Issues

7.1 Top Issues
7.2 Flex SDK Issues
7.3 Flash Builder Issues

Overview

Welcome to the Adobe® Flash Builder™ 4 Beta 2 release!

Adobe® Flash Builder™ 4 was formerly known as the Gumbo release.

Please note: Beta 2 is an early preview of the Flash Builder 4 release. The goal of this release is to give the community an opportunity to provide feedback on the feature design and to help identify bugs and missing capabilities.

Not all of the planned features have been fully implemented, but the product is solid and nearing release quality. While we encourage you to try out the beta you should expect to find some bugs; be sure to save and back up your work often.

Please review the Known Issues list prior to using the beta.

Flash Builder 4 is Adobe's professional Flex IDE built on Eclipse. It can run either as a standalone tool or as a plug-in to an existing Eclipse installation. Flex SDK includes the Flex framework (also known as the Flex class library), Flex command-line compilers, Adobe Integrated Runtime (AIR) framework, Adobe AIR command-line compilers, the Flex debugger, the ASDoc utility, and the debugger version of Flash Player. Use the Flex SDK to develop, compile, and deploy Flex applications that connect to XML and SOAP web services with no additional charges or server licensing required. This release also includes Data Visualization features.

Warning: Do not install Flash Builder 4 Beta 2 on top of an existing installation of Flex Builder 3 or Flash Builder 4. In particular, do not install the plug-in version of Flash Builder 4 Beta 2 into an Eclipse installation that is already running the plug-in version of Flex Builder or Flash Builder.

What's New

Read What's new in Flash Builder 4 beta and What's new in the Flex 4 SDK beta to become acquainted with all the new features in these releases.

In addition, here are some quick highlights:

Flex SDK

New functionality in Flex 4

Highlight of changes from Flex 4 Beta 1 to Flex 4 Beta 2

Flash Builder

New for Beta 2

New for Flash Builder 4

Comparison of MX and Spark Components

Controls:

MX Spark
mx.controls.AdvancedDataGrid none
mx.controls.Alert none
mx.controls.Button spark.components.Button
mx.controls.CheckBox spark.components.CheckBox
mx.controls.ColorPicker none
mx.controls.ComboBox spark.components.DropDownList (w/o editability)
mx.controls.DataGrid none
mx.controls.DateChooser none
mx.controls.DateField none
mx.controls.HorizontalList spark.components.List (w/ HorizontalLayout)
mx.controls.HSlider spark.components.HSlider
mx.controls.Image spark.primitives.BitmapImage
mx.controls.Label spark.components.Label
mx.controls.LinkButton spark.components.Button (w/ custom skin)
mx.controls.List spark.components.List
mx.controls.Menu none
mx.controls.NumericStepper spark.components.Spinner (no TextInput control)
spark.components.NumericStepper
mx.controls.OLAPDataGrid none
mx.controls.PopUpButton use spark.components.PopUpAnchor
mx.controls.PopUpMenuButton use spark.components.PopUpAnchor
mx.controls.ProgressBar none
mx.controls.RadioButton spark.components.RadioButton
mx.controls.RadioButtonGroup spark.components.RadioButtonGroup
mx.controls.RichTextEditor build own component
mx.controls.SWFLoader none
mx.controls.Text spark.components.Label
mx.controls.TextArea spark.components.TextArea
mx.controls.TextInput spark.components.TextInput
mx.controls.TileList spark.components.List (w/ TileLayout)
mx.controls.Tree none
mx.controls.VideoDisplay spark.components.VideoPlayer
mx.controls.VSlider spark.components.VSlider

Additional Spark controls

Layouts/Containers:

MX Spark
mx.core.Application spark.components.Application
mx.containers.ApplicationControlBar spark.components.ControlBarContent
mx.containers.Canvas spark.components.Group
spark.components.DataGroup
spark.components.SkinnableContainer
spark.components.SkinnableDataContainer
spark.components.Border
mx.containers.ControlBar spark.components.ControlBarContent
mx.containers.Form none
mx.containers.FormHeading spark.component.FormHeading
mx.containers.Grid write custom layout
mx.containers.HBox spark.components.HGroup
mx.containers.HDividedBox use MX with Spark containers
mx.controls.HRule spark.primitives.Line
mx.modules.ModuleLoader none
mx.containers.Panel spark.components.Panel
mx.controls.Spacer none
mx.containers.Tile spark.components.Group (w/ TileLayout)
mx.containers.TitleWindow none
mx.containers.VBox spark.components.VGroup
mx.containers.VDividedBox use MX with Spark containers
mx.controls.VRule spark.primitives.Line
mx.core.Window spark.components.Window
mx.core.WindowedApplication spark.components.WindowedApplication

Additional Spark Layouts/Containers:

Navigators

MX Spark
mx.containers.Accordion use MX with Spark containers
mx.controls.ButtonBar spark.components.ButtonBar
mx.controls.LinkBar spark.components.ButtonBar (w/ custom skin)
mx.controls.MenuBar none
mx.controls.TabBar spark.components.ButtonBar (w/customSkin)
mx.containers.TabNavigator custom Spark TabBar with MX ViewStack
mx.controls.ToggleButtonBar spark.components.ButtonBar (w/ custom skin)
mx.containers.ViewStack use MX with Spark containers

Charts

MX Spark
mx.charts.AreaChart none
mx.charts.BarChart none
mx.charts.BubbleChart none
mx.charts.CandlestickChart none
mx.charts.ColumnChart none
mx.charts.HLOCChart none
mx.charts.Legend none
mx.charts.LineChart none
mx.charts.PieChart none
mx.charts.PlotChart none

System requirements

Please see the system requirements information on the Flex 4 SDK and Flash Builder pages on Adobe Labs.

Installation Instructions

Installing Flash Builder 4 Beta 2

This release contains the following versions of Flash Builder:

Note: You can run Flex Builder 3 and Flash Builder 4 Beta 2 on the same system. You do not have to uninstall Flex Builder 3.

Warning: Do not install Flash Builder 4 Beta 2 on top of an existing installation of Flex Builder or Flash Builder 4. In particular, do not install the plug-in version of Flash Builder 4 Beta 2 into an Eclipse installation that is already running the plug-in version of Flex Builder Flash Builder 4. Additionally, workspaces should not be shared between installations.

Note: The Flash Builder 4 Beta allows the selection of installation in English, French, German, Japanese, Simplified Chinese and Russian. We are still in the process of translating non-English versions, so some strings may appear in English. For this reason, we ask that you do not file linguistic bugs related to translation quality or missing translations at this time; however, we do look forward to hearing about your experience running Flash Builder on localized OSs.

Installing Flash Builder stand-alone

To install Flash Builder on Windows:

The default location of the installation directory for Flash Builder stand-alone is C:\Program Files\Adobe\Flash Builder Beta.

  1. Prior to installing, remove any previous versions of Flash Builder 4 (Gumbo).
  2. Download Flash Builder Win Stand Alone Installer (flashbuilder4_b2_win_100509.exe) from the Adobe Labs site.
  3. Exit all running applications.
  4. Open or double-click the installer executable file.
  5. Accept the license agreement and follow the prompts.
  6. Review the Release Notes.
  7. Start Flash Builder.

To install Flash Builder on Mac OS X:

  1. Prior to installing, remove any previous versions of Flash Builder 4 (Gumbo).
  2. Download Flash Builder Mac Stand Alone installer (flashbuilder4_b2_mac_100509.dmg) from the Adobe Labs site.
  3. Exit all running applications.
  4. Open or double-click the installer DMG file. The installer image will be mounted.
  5. Open or double-click the installer app to begin the Flash Builder installation process.
  6. Accept the license agreement and follow the prompts.
  7. Follow the prompts to complete the installation.
  8. To start Flash Builder, locate and double-click the executable file in the \Applications\Adobe Flash Builder Beta 2.
  9. Review the Release Notes.

Installing Flash Builder plug-in

Note: Flash Builder is only supported on Eclipse 3.4.

Warning: Do not install Flash Builder 4 Beta 2 on top of an existing installation of Flex Builder or Flash Builder 4. In particular, do not install the plug-in version of Flash Builder 4 Beta 2 into an Eclipse installation that is already running the plug-in version of Flex Builder Flash Builder 4. Additionally, workspaces should not be shared between installations.

To install the Flash Builder Eclipse plug-in on Windows:

  1. Prior to installing, remove any prerelease versions of Flash Builder 4 (Gumbo).
  2. Download Flash Builder Win Plug-in installer (flashbuilder4_b2_plugin_win_100509.exe) from the Adobe Labs site.
  3. Exit all running applications.
  4. Open or double-click the installer executable file. Accept the license agreement and follow the prompts.
  5. Review the Release Notes.
  6. Start Eclipse using its shortcut in the Start Menu.

Note: You must create a new workspace before beginning. Select File > Switch Workspace from the menu bar and enter a new folder name. If the folder doesn't exist, Eclipse creates it.

To install the Flash Builder Eclipse plug-in on Mac OS X:

  1. Prior to installing, remove any prerelease versions of Flash Builder 4.
  2. Download Flash Builder Mac Plug-in installer (flashbuilder4_b2_plugin_mac_100509.dmg) from the Adobe Labs site.
  3. Exit all running applications.
  4. Open or double-click the installer DMG file. The installer image will be mounted.
  5. Open or double-click the installer app to begin the Flash Builder installation process.
  6. Accept the license agreement and follow the prompts.
  7. Review the Release Notes.
  8. Start Eclipse.

Note: You must create a new workspace before beginning. Select File > Switch Workspace from the menu bar and enter a new folder name. If the folder doesn't exist, Eclipse creates it.

Installing Flex SDK 4 Beta 2

You can install the Flex SDK separately. The Flex SDK install, which is delivered as a ZIP file, contains the Flex framework, Adobe AIR framework, and command-line tools, such as the mxmlc command-line utility, Adobe AIR command-line utility, the ASDoc utility, the Flex command-line debugger, and the debugger version of the Flash Player.

Uninstall Current Flash Player

Prior to installing the Flex SDK, it is recommended that you also uninstall your current Flash Player and upgrade to the version provided in the SDK.

Windows—Internet Explorer

Due to security features in the Adobe Flash Player ActiveX Control, you must first remove all existing installations of Flash Player from your Windows system before installing prerelease versions of the Flash Player ActiveX Control:

  1. Download the Uninstaller.
  2. Open the Windows Command Prompt ( Run > cmd ).
  3. Navigate to the directory where the uninstaller was downloaded.
  4. Run "uninstall_flash_player.exe /clean".

Windows—Plugin-based browsers

Run the appropriate uninstaller available from this Technote.

Macintosh

Run the appropriate uninstaller available from this Technote.

Linux

Manual removal (for users who installed the plug-in via Install script):

RPM removal:

To install the Flex SDK:

Download the Flex 4 SDK from either Adobe Labs Downloads or the Adobe Flex SDK Open Source Site.

  1. Create a directory to contain the Flex SDK.
  2. Extract the Flex SDK ZIP file to this directory. The Flex SDK contains the following directories:
    • ant - Contains Flex Ant Tasks.
    • asdoc - Contains helper files for the ASDoc tool that creates HTML documentation from your MXML and ActionScript source code.
    • bin - Contains the mxmlc, compc, asdoc, and fdb utilities. The bin directory also contains the jvm.config file, which specifies Java settings that you can modify, if necessary.
    • frameworks - Contains compiled framework classes, configuration files, and framework source code.
    • lib - Contains JAR files used by the utilities.
    • runtimes - Contains installers for the Adobe AIR runtime inside the air folder and installers for debug versions of Flash Player 10 inside the player folder .
    • samples - Contains sample applications.
    • templates - Contains HTML templates for Flash Player detection and browser integration and inside the air folder, a sample Adobe AIR application.xml file.
  3. Review the Release Notes.
  4. Ensure that Java SDK is installed on the computer and that the java_home/bin directory is defined in the system path. JDK 1.4, 1.5, or 1.6 is required. For 1.4, JDK 1.4.2_06 or later is required.
  5. Install the appropriate Flash Player from the install_root/runtimes/player/10/platform directory.
  6. (Optional) When the Flash Player installation finishes, restart your computer to ensure that the updated Flash Player browser plug-in is enabled.

Install and Configure Flex and AIR Automated Testing

To use Flex or AIR Automated Testing, you must install Flash Builder 4 Professional. You cannot use Flex Automated Testing with only the Flex 4 SDK. If you do not have a Flex Builder 3 Professional license, your test scripts are limited to 30 actions. If you exceed 30 actions in a test without the Professional license, you will receive a warning that your license is not present.

Flex and AIR Automated Testing SWC files are installed by default with Flash Builder 4. The automation swcs corresponding to Flex 4 SDK can be found in the /frameworks/libs/automation directory while as the automation swcs for Flex 3.4 SDK will be found in the Framework/libs directory. You can begin using Flex Automated Testing and build your own custom agents without any further installation.

NOTE: The automation libraries are now under the framework/libs/automation directory. In Flex4, you must add this location to the library path or include these libraries using the –include-libraries compiler option.

Use run-time automated testing (recommended) for Flex Applications

  1. Open a command prompt.
  2. Navigate to the flash_builder_root/sdks/4.0.0/templates/automation-runtimeloading-files directory.
  3. Execute the build.bat file. This compiles the runtimeloading.mxml file into a SWF file.
  4. Copy the runtimeloading.swf and RunTimeLoading.html file to your web server. Copy the Flex application that you want to test to this server as well (the application need not be compiled with automation libraries).
  5. Request the RunTimeLoading.html file and pass your Flex application as the automationswfurl query string parameter; for example: 
http://localhost/RunTimeLoading.html?automationswfurl=MyApp.swf

Please note that run-time loading is not supported for AIR applications

Compile your applications with static automation support for Flex Applications

  1. Start Flash Builder.
  2. Create a new Flex Project.
  3. Select your new Flex project in the Navigator.
  4. Select Project > Properties > Flex Compiler.
  5. In the "Additional compiler arguments" field, enter the following, replacing flash_builder_root with your install directory : -include-libraries "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation_agent.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\qtp.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation_dmv.swc". Users interested in trying the new automation of spark components feature will also need to include "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation_spark.swc “
  6. Click the OK button to save your changes and OK to close the project Properties dialog box.
  7. Compile your Flex application.

Examples and documentation for using custom agents can be found at Custom Agents

Spark Components made automation ready for Beta 2

Automation of these Spark Components is currently supported only for Flex Applications.

Compile your applications with static automation support for AIR Applications

  1. Start Flash Builder.
  2. Create a new AIR (desktop) Project.
  3. Select your new AIR project in the Navigator.
  4. Select Project > Properties > Flex Compiler.
  5. In the "Additional compiler arguments" field, enter the following, replacing flash_builder_root with your install directory : -include-libraries "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation_agent.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\qtp_air.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation_dmv.swc" "flash_builder_root\sdks\4.0.0\frameworks\libs\automation\automation_air.swc"
  6. Click the OK button to save your changes and OK to close the project Properties dialog box.
  7. Compile your AIR application.

Flex 4 Plug-in for HP QuickTest Professional

To use Flex and AIR Automated Testing with the Flex 4 Plug-in for HP QuickTest Professional (formerly Mercury QuickTest Pro), you must perform additional steps. The rest of this section describes how to install and use the Flex 4 Plug-in for HP QuickTest Professional

Requirements for Using the QTP Plug-in

To test applications with Flex Automated Testing and the QTP agent, you must install the following:

Installing the Plug-in

This section describes the steps necessary for a QC testing professional to configure QTP to work with Flex applications. You must install QTP and the plug-in.

To install QTP

  1. Install Flash Player 9 ActiveX control (9.0.28.0 ) or newer for Microsoft Internet Explorer. This is currently the only supported browser/player.
  2. If you are using Mercury QTP on Microsoft Windows Vista you need to turn off the User Account Control (UAC) feature. Instructions to turn off UAC are available here
  3. Restart your computer.

To install the Flex 4 Plug-in for Mercury QuickTest Pro

  1. Download the Adobe Flex 4 Plug-in for HP QuickTest Pro zip file and unzip it on the machine where you want to install the plug-in.
  2. Double Click on the Install_QTP_Plugin.bat.
  3. Restart your machine.

The plug-in installer will include the following in the installation directory:

Using the Plug-in

You can download a demo zip. It contains a Flash movie that describes the basics of using the plug-in.Be sure to enable audio on your computer.

  1. Start QTP again after installing the plug-in. The Add-in Manager lists the Flex and AIR plug-in.
  2. Select the Flex plug-in in the Add-in Manager if you want to automate Flex applications or select the AIR Plug-in in the Add-in Manager if you want to automate AIR applications.
  3. Select New > Test and click the Record button.

NOTE: Flex application testing with QTP currently supports only Microsoft Internet Explorer with the ActiveX Flash Player. For more information on these tasks and using QTP to test Flex applications, see Testing with QTP. For information on the operations and properties of Flex objects in QTP, see QTP Object Type Information.

Samples for Automated Testing Sample custom agents are available at Custom Automation Agents. An application ready for testing with QTP can be found at Flexstore AT. This sample can be used to test if the QTP plugin installation was successful. An example for automating custom components can be found at Automating Custom Component.

Uninstalling

Uninstalling Flash Builder

Uninstalling Flash Builder Beta 2 on Windows:

  1. Select Start > Settings > Control Panel.
  2. Select Add or Remove Programs.
  3. Click the Adobe Flash Builder version to uninstall (Adobe Flash Builder Beta 2, Adobe Flash Builder Plug-in Beta 2).
  4. Click the Uninstall button in the uninstaller dialog box.
  5. Click Done.

Uninstalling Flash Builder Beta on Mac OS X:

  1. Go to the flash_builder_root/Uninstall Adobe Flash Builder Beta 2 folder.
  2. Double-click "Uninstall Adobe Flash Builder Beta 2".
  3. Click the Uninstall button in the uninstaller dialog box.
  4. Click Done.

Uninstalling Flash Builder Plug-in Beta on Windows:

  1. Select Start > Settings > Control Panel.
  2. Select Add or Remove Programs.
  3. Click the Adobe Flash Builder version to uninstall (Adobe Flash Builder Beta 2, Adobe Flash Builder Plug-in Beta 2).
  4. Click the Uninstall button in the uninstaller dialog box.
  5. Click Done.

Uninstalling Flash Builder Plug-in Beta on Mac OS X:

  1. Go to the flash_builder_root/Uninstall Adobe Flash Builder Plug in Beta 2 folder.
  2. Double-click "Uninstall Adobe Flash Builder Plug-in Beta 2".
  3. Click the Uninstall button in the uninstaller dialog box.
  4. Click Done.

Uninstalling Flash Player

Windows—Internet Explorer

  1. Download the Uninstaller
  2. Open the Windows Command Prompt ( Run > cmd ).
  3. Navigate to the directory where the uninstaller was downloaded.
  4. Run "Uninstall Adobe Flash Player.exe /clean."

Windows-Plugin or Macintosh

If you wish to uninstall the Windows—Plugin-based browsers or the Macintosh Flash Players included with beta 2, refer to the following this Technote.

Documentation

Documentation is available withing the Flash Builder help system or help.adobe.com. It includes:


Note the following:

Compatibility Issues

Flash Builder

Flex SDK

Known Issues

Here are product-specific lists of known issues in the Flex 4 and Flash Builder Public beta. Flex 4 and Flash Builder use a public bug system (https://bugs.adobe.com/flex) and most bugs in these lists contain a link to more detail in this bug system. You can also use the public bug system to post bugs you find in the beta 2 release.

When using the public bug system, you should start by clicking on the Bug Standards / Community Process link to learn more about the bug system (be sure to check the section at the bottom). Then go back, register for your account and you should be able to view and define bugs.

Top Issues

Workaround After installing on 10.6.1, run the mini-installer found at Flash Builder installation folder/install.support/builder-common-mul/Setup.app

Flex SDK Issues

Please see the full list of open issues in our public bug database

The issues below are included in the bug lists mentioned above, but we have pulled them out separately for visibility's sake.

Accessibility

Compiler

DeepLinking

Embedded Fonts

Effects / Transitions

FXG

The FXG 2.0 implementation is still under development and as a result, some functionality is limited or missing. Specifically, the Beta 2 implementation of FXG contains about half of the FXG 2.0 dictated functionality (in both the runtime implementation as well as the static compilation). Work that is in includes the name changes to the TextGraphic element (now called RichText), addition of the resizeMode functionality to FXG-based bitmap fills and elements, the 'auto' blendMode functionality, etc. Work that did not make it into the Beta 2 build includes the new AIM blendModes, new AIM luminosity mask type, and some additional renames to certain elements. This work is in various state of completion in the SDK trunk for both the runtime implementation as well as the static compilation library. Since most of the larger changes are not in the Beta 2 build, and the Beta 2 functionality is functionality that existed in MXML Graphics since Beta 1, the quality is relatively stable. Bugs do continue to come in with regards to static compilation (FXGUtils), and they are getting fixed in trunk. As such, users may see rendering differences when chosing to opt in for static compilation, but that was deemed acceptable by Catalyst since static compilation was not deemed a Beta 2 requirement.

Halo Components

IME Support

Spark: Application

Spark: Button

Spark ButtonBar support for Halo Viewstack

Spark: ControlBar in Spark Panels and Application

Spark: DropDownList

Spark: Label

Spark: List There is limited support for paged data in Spark Lists. This feature is still under development and as a result some functionality is limited and has not yet undergone extensive testing.


Spark: SkinnableContainer

Spark: Text

TextFlows can't be shared and this scenario requires the first TextFlow in the list be shared since it is also used for by virtual layout code for measurement. Workaround: use RichEditableText instead of RichText 

 import flashx.textLayout.elements.TextFlow;

and add this to the List : 

 typicalItem="{(TextFlow(data[0]).deepCopy())}"



Spark: VideoPlayer


Styles

Themes 

headerBackgroundSkin: ClassReference("mx.skins.halo.DataGridHeaderBackgroundSkin");

Flash Builder Issues

Please see the full list of open issues in our public bug database

Installation

Workaround
  1. If you’re using your own copy of Eclipse, enable Classic Update in Eclipse Preferences > General > Capabilities > Classic Update.
  2. The copy of Eclipse bundled with FB4 Plug-in doesn’t include the Classic Update option in Preferences, so it needs to be enabled:
    1. In the default workspace (/yourUserName/Documents/Adobe Flash Builder Plug-in Beta 2/), locate the following file: /.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.workbench.prefs
    2. At the end of that file, add the following line: UIActivities.org.eclipse.equinox.p2.ui.sdk.classicUpdate=true
  3. Add FB4 as a product extension, using these steps:
    1. Invoke Help > Software Updates... > Manage Configuration
    2. Add an extension folder, pointed to the FB4 Plug-in subfolder named eclipse.
To install the Carbon version, go to Eclipse downloads, click the Eclipse 3.5 link, then scroll down the page to locate the Mac OS X Carbon installer.

Licensing

Workaround After installing on 10.6.1, run the mini-installer found at Flash Builder installation folder/install.support/builder-common-mul/Setup.app

Debug / Run

Workaround
Design View Design View – CSS
CSS Design View is no longer available for Flex SDK 4 projects.
Code editing and Refactoring DCD : General DCD : LCDS DCD : Form Generation DCD: CF Sample Generation: DCD: PHP Sample Generation: DCD: PHP Introspector DCD: DataGrid Column Configuration DCD: Configure Return Type DCD: UI Authoring Debugger Flex Unit IDE Compatibility
The recommended workaround is to install the Flash Builder plug-in into the All-In-One Eclipse PDT + Zend Debugger Plug-in (http://www.zend.com/en/community/pdt). An alternate workaround is to rename Zend Studio's “dropins” folder to “links” and restart Zend.

Miscellaneous issues

Network Monitor

Package Explorer

Profiler

Project

Skinning

Flex Automation

Retrieved from "http://labs.macromedia.com/wiki/index.php/Flash_Builder_4:Release_Notes"