Archive for February, 2010

Improving Compiler Performance for Large Projects

  1. Exit Flash Builder or Eclipse
  2. Open your FlashBuilder.ini or eclipse.ini file
    • Mac
      1. Right click on Adobe Flash Builder 4.app or Eclipse.app, Show Package Contents
      2. Open Contents > MacOS > Adobe Flash Builder 4.ini or eclipse.ini
    • Windows
      1. Open C:\Program Files\Adobe\Adobe Flash Builder 4\FlashBuilder.ini or <path to Eclipse>\eclipse.ini
  3. Find the maximum heap size setting, e.g. “-Xmx512m”
  4. Choose a new value for Xmx
  5. Save and restart Flash Builder or Eclipse
Share on Facebook

Flash Builder 4 Advanced Tips and Tricks on Adobe TV

In case you haven’t already seen this, Scott Evans’ MAX talk “Flash Builder 4 Advanced Tips and Tricks” is up on Adobe TV.

Share on Facebook

Patch for Snow Leopard line number scrolling bug

One of the most “popular” bugs in my bug queue has been FB-23023. Essentially, if you’re using Snow Leopard with Flash Builder and your window is on a secondary monitor, the line numbers in code editors stop scrolling. That’s a pretty annoying bug for someone who just bought a shiny new Macbook and hooked up an external monitor.
Luckily, the folks at Eclipse.org were able to narrow down the issue and referenced the fix that was applied for the future 3.6 release.
And to top it off, Rick Winscot went out of his way to build a patch that’s easily applied to standalone and plugin installations of Flash Builder. Thanks, Rick!
Update: To run Flash Builder with the -clean option, do the following:
  1. Open a terminal window
  2. Right click on “Adobe Flash Builder 4.app”, show package contents
  3. Expand Contents > MacOS
  4. Drag and drop “Adobe Flash Builder 4″ to the terminal window
  5. Add ” -clean”
  6. Run
Share on Facebook

Workaround for using the latest nightly SDK 4.0 builds with Flash Builder Beta 2

The latest builds of SDK 4.0 have been updated in preparation for
including playerglobal.swc for Flash Player 10.1. Flash Builder Beta 2
can not find playerglobal.swc due to the addition of the
{targetPlayerMinorVersion} variable found in the flex-config.xml file.

When using recent nightly SDKs with Flash Builder Beta 2, please modify them as follows:

1) Rename the folder <nightly sdk location>/frameworks/libs/player/10.0 to “10″

2) Edit the file <nightly sdk location>/frameworks/flex-config.xml and remove “.{targetPlayerMinorVersion}” and save

When
you restart Flash Builder, we will now find a correct location for
playerglobal.swc, allowing for code hints and many other features to
work properly.

Update: Also make sure you’re using the correct namespace declaration. Replace xmlns:mx=”library://ns.adobe.com/flex/halo” with xmlns:mx=”library://ns.adobe.com/flex/mx“. When using the nightly builds, Beta 2 does not create MXML files with the correct namespace. Thanks.

Share on Facebook

Hi There!

Let me introduce myself. I’m Jason San Jose and I’m a Quality Engineer on the Flash Builder team. I typically focus on ActionScript and MXML editor IDE features such as code hints, refactoring and call hierarchy. I
joined the Flash Builder team in 2008 shortly after the release of Flex
Builder 3.

My goal for my shiny new blog is to highlight helpful tips and tricks in Flash Builder 4. I’ve covered a few of these tips and new features in my developer center article Developer productivity improvements in Flash Builder 4 beta 2.

Once we ship, come back here for more frequent updates on the latest Flash Builder 4 tips.

Share on Facebook