I had to track down a download location for Adobe’s Flex 3 install today. It was a little hard to find so I thought I’d share this link for a Windows install:

http://download.macromedia.com/pub/flex/flex_builder/FB3_win.exe

Why it’s at a macromedia.com address I have no clue, but hope this helps someone out. This defaults to a 60 day trail and you can enter your license as well.

Adobe added a new resource to help everyone including designers, web developers, programmers, managers and architects learn Flex the way they need to. It’s called http://www.adobe.com/devnet/flex/learn/. I can’t wait to dive in and make use of this. From what I’ve seen so far, it includes real-world examples, videos, links, white papers, articles, excercises, quick starts, and documentation.

Also be sure to check out Tour De Flex. It’s an AIR application that explores Flex capabilities and resources, including the core Flex components, Adobe AIR and data integration, as well as third-party components, effects, skins, and more.

For me, the Cairngorm Flex Framework has been a bit challenging. Keeping up on different frameworks and libraries for Flex, ColdFusion, JavaScript, etc. can be a bit daunting. So every bit of help is a blessing.

Adobe has released an Eclipse Cairngorm Plugin “that augments Flex Builder to provide tooling that improves productivity when developing Cairngorm-based RIAs.”

According to Adobe, “the initial focus of the Cairngorm Plugin is on the Controller. It aims to improve productivity by removing the repetitive action of creating a new Command and associated Event and adding them to the Controller.”

It provides a new class wizard for the following Cairngorm artifacts:

For me, the Cairngorm Flex Framework has been a bit challenging. Keeping up on different frameworks and libraries for Flex, ColdFusion, JavaScript, etc. can be a bit daunting. So every bit of help is a blessing.

Adobe has released an Eclipse Cairngorm Plugin “that augments Flex Builder to provide tooling that improves productivity when developing Cairngorm-based RIAs.”

According to Adobe, “the initial focus of the Cairngorm Plugin is on the Controller. It aims to improve productivity by removing the repetitive action of creating a new Command and associated Event and adding them to the Controller.”

It provides a new class wizard for the following Cairngorm artifacts:

• Controller – creates a new Controller
• Command – creates a new Event and a new Command and adds them to the Controller.

View instructions on how to install it.

Learn how to use it by viewing the documentation.

• – creates a new Controller
• Command – creates a new Event and a new Command and adds them to the Controller.

View instructions on how to install it.

Learn how to use it by viewing the documentation.

Here’s an example I created to bind a text field with a label. This needs to be done with you are dynamically creating components inside of your app instead of using MXML. Be sure to use the if statement on the unwatch function to avoid an error for null pointing.

private var watcher:ChangeWatcher;

private function watch():void {
var SampleLabel:Label = new Label();
SampleHBox.addChild(SampleLabel);
watcher = BindingUtils.bindProperty(SampleLabel,"text", sampleText,"text");
}

private function unwatch():void {
if (watcher != null) {
watcher.unwatch();
}
}

Here’s a great tool to help with Flex debugging. Put <mx:TraceTarget /> into your code and run your app in debugging mode.

You will see valuable debugging information appear in the console area. Great for hassling with remoting like ColdFusion CFC’s.

Form more info: Adobe Flex 3 Language Reference TraceTarget

I have a Flex project that I copied in from another source to work on. I changed around some output properties and library paths via the Properties context menu for the project. The changes would hold while Flex was open, but it would never update the .actionScriptProperties file, thus when Eclipse was restarted, the changed would revert.

After doing a little bit of Googling on the issue and not finding much help I ended up making a backup copy of the folder, deleting the folder, and importing the files into the new folder via Flex Builder. This fixed the issue. Not sure what caused this, but it works now.

When removing items from an array via its index number, remember to always start from the end and work your way to the beginning. If you don’t, and are removing more than one item, the index you where looking for will no longer be the correct item because one or more have already been removed and the indexes have been reassigned to fill the gap.

Correct Example: (I am using the Cairngorm framework in this example.)

for (var j:int=grid1.selectedIndices.length-1; j>=0; j--) {
model.grid1data.removeItemAt(grid1.selectedIndices[j]);
}

Also remember, that “indices” is the plural form of “index”.