This is a video created by Adobe that walks you through step by step. And since Flash Builder is built on Eclipse, these instructions are 100% applicable to Flash Builder.

You can create your custom rulesets to enforce more specific best practices.

We are going to develop a large application which will be ported on web and desktop (AIR). can you suggest any good MVC framework for beginning with?

getSitesByClientID( id:int );
getUsersByClientID( id:int );

with a common event handler:

private function getResults_success( e:ResultEvent ):void {
var token:AsyncToken = e.token;
var result:XML = e.result as XML;
clearBusyCursor();

if ( token != null ) {
switch ( token.marker ) {
case UserEvent.SAVE:
dispatchEvent( new UserEvent( UserEvent.SAVE, result ) );
break;

case SiteEvent.SAVE:
dispatchEvent( new SiteEvent( SiteEvent.SAVE, result ) );
break;
}
}
}

Hmmm…

This also ties across to your MVC article. I’m trying to overlay some of those good concepts here…I have a ways to go

Thanks again.

However, I would guess what is happening is one of your components/classes are firing off an event and your metadata is no set properly or you are firing a user save event when you meant a site save event (or vica-versa).

The only time you will want to worry about a globally unique is when you are working with a global event handler or central dispatcher.

I had a recent hairball I chased for a bunch of time where I had a SiteEvent and a UserEvent that both had SAVE types. I kept getting an error thrown that a SiteEvent couldn’t be coerced to UserEvent, and nowhere could I determine that I was mixing them up in handler routines. The problem went away when I made the constants in the two classes different:

public class SiteEvent extends Event {
public static const SAVE:String = “save”;
}
public class UserEvent extends Event {
public static const SAVE:String = “save”;
}

became…

public class SiteEvent extends Event {
public static const SAVE:String = “site_save”;
}
public class UserEvent extends Event {
public static const SAVE:String = “user_save”;
}

Thanks for your thoughts.