To use root propriety the class that you are working on most extend a DisplayObject (Sprite,MovieCLip,etc…) because you have to add the class to the parent class. And note, you can’t use the root propriety in the constructor method, because the addChild haven’t been process yet! Well let’s stop writing and see some code:

Main.as

In the Main class I’m declaring a variable named myValue which I did the proper sets and get. I am declaring two classes, in one of them I will set the value at the Main class and in the other I will get that value back. I’m also creating a movieClip just for test purposes.

ExampleClass.as

In ExampleClass I’m setting myValue that is propriety of the Main class with some text and I’m tracing the movieClip that I create in the Main Class.

AnotherClass.as

In AnotherClass I’m tracing the myValue propriety. So the result should be:
[object MovieClip]
This value is inside the Main Class

So it works ok, you only have to be carefull not refer root inside the constructor method, have the certain that you already addChild the class when you are referring to root and that the class extends a display object. If you do that, you can too have access to stage propriety, let’s check the next example:

ExampleClass.as

The result should be or stage width.

Another way to access to main proprieties, methods, etc… is with static members. In the next example I’m declaring a static property in the main class and setting and trace the value of it in the example class.

Main.as

ExampleClass.as

The result should be “Hello Word!”, if you didn’t know this, read some books about object oriented programming and static members.

Another way to do the same thing is to pass the instance of main class as an argument to the other classes.

Main.as

Example.as

There are still another ways to access to the Main class code. I don’t know which techniques are more correct, I usually use them all depending in what I need. I hope I help someone.

Lately I've working on three big projects that would require the usage of a framework, and not wanting to extend my own framework, that consists mostly of accumulated libraries over time, I decided to give the most prominent ones a go.

So I started by checking out what was on the market, I found as-hive, pureMVC, Cairngorm and Mate ( there are a few more but somehow I didn't feel they were mature enough to be used.

Now for a little background on this quest for the framework, and few of my personal opinions on the whole framework business.
The point of a framework is to aid you in the making of your application/website, this can be the handling of repetitive tasks for you, providing a strict way of coding and thus giving you a common ground of understanding with your peers. Also it's meant to enable you to code more efficiently, make your code more readable and produce a scalable product that you can, even at a later date, modify without breaking everything.
What they are NOT meant to do is to force a coding style that makes feel restricted, uncomfortable with and most important they shouldn't be extra work. It feels pretty pointless to have to code 3 times as more to have the same functionality, some of you might immediately argue "but what about scalability?" well sometimes that's not everything, in the real work time matters.

Ok, now that we got that out of the way let's move on to the frameworks.
The project that required me to start first was a PV3D website that heavily relies on dynamic content. So I checked out pureMVC and as-hive and quickly decided to go with pureMVC.
So then I went on to the forums and examples pages and tried to read all that mattered to me, plus I found nice diagrams that help you out alot in the beginning.
As I delved more into the project I realized that some extending and heavy integration of PV3D and pureMVC would be required in order to make things easy for me, plus the project relies on the URL to know where it is and react accordingly, this was easy enough, simple and clear.

So my opinion on pureMVC is that it's the perfect framework for AS3 projects because it's easily extensible, highly functional, doesn't force you to adopt a specific style but still requires you to have rules and standards.

The next project is an AIR Application that will mimic some of the functionality of Powerpoint so I immediately thought of Cairngorm, but then I heard about Mate (pronounced mah-tey) and it seemed like the perfect solution.

So having already started development with Cairngorm when I heard about Mate, it felt like a risk to change, but nevertheless a risk worthwhile taking should Mate be more practical and provide me with a faster environment in which to code.
Well Mate does look great on paper ( and I printed the architecture) but somehow it feels like it still hasn't achieved critical mass to be used, now don't get me wrong it's a great framework and I'm sure that with some extra work I'd be in love with it, but at the moment I just didn't have the time to try and figure out somethings on my own and the forums don't have that many topics, plus the examples are far too simple. So I'm sticking with Cairgnorm for the time being.
Cairgorm is a must know for any Flex developer, it's the official framework which means that plenty of clients will feel more comfortable with ,or even ask for it.

That said I started using Cairngorm and eventually grew to like it, I liked the ViewModelLocator and the self dispatching event model, and it did eventually make my work easier.

And to finalize I'll go into no frameworks at all because sometimes a framework is just an overkill, some might say that it's always the best solution, but not always. Sometimes we just need to develop a small application/website and using a framework is actually extra work than just making it the fastest way possible and if it needs updates after they should be easy enough, if they aren't, well you can always refactor it into a framework based app. This works well for me because of years of accumulated libraries that provide me with most of the common tasks i need, many of them published here on DIF.

So that's enough and if you read all the way here congratulations, and please leave me your thoughts.

• Use ASDoc block comments (Ctrl+Shift+D in Flex Builder).
• Write in English.
• Use a $Id$ svn/cvs keyword so everyone knows directly who did the last change on the file.
• If importing to COM, write an example of usage.
• Favor the use of getters and setters instead of public vars/const.
• In the source code use the following order to keep things organized: