Tech Blog

On Friday 29 January Adobe released a new ’stable’ version of the Flex SDK, version 4.0.0.13875. One of the nice things about it was the addition of the Flex 4 TitleWindow. Peter deHaan uses the new TitleWindow in one of his articles on his excellent blog: Constraining the movement on a Spark TitleWindow container in Flex 4

When using the new SDK we encountered quite an annoying issue. Since Flex 4 is still in beta, we use Flex Builder 3 in combination with a Flex 4 SDK. The problem was that after upgrading to the latest SDK, default flash and mx classes weren’t recognised anymore and couldn’t be imported. When added manually they gave an error.

Luckily Tim found a workaround. Go to your project’s Properties, click on Flex Build Path and  select Library path. First open up the Flex 4.0.0.13875, select the playerglobal.swc and remove it. Then click on Add SWC… and select the playerglobal.swc from the SDK (in my case /Developer/SDKs/flex_sdk_4.0.0.13875/frameworks/libs/player/10.0/playerglobal.swc).

I hope this little workaround is useful for everybody out there working with the latest Flex SDK.

PS. the workaround only seems to work for Flex/AS3 projects, but not for Library projects…

Just annouced: Adobe is going to open source Flex! Also check out these video’s on Robert Scoble’s blog.

Adobe is announcing plans to open source Flex under the Mozilla Public License (MPL). This includes not only the source to the ActionScript components from the Flex SDK, which have been available in source code form with the SDK since Flex 2 was released, but also includes the Java source code for the ActionScript and MXML compilers, the ActionScript debugger and the core ActionScript libraries from the SDK. The Flex SDK includes all of the components needed to create Flex applications that run in any browser – on Mac OS X, Windows, and Linux and on now on the desktop using “Apollo”.