Adobe Designer and Developer Lounge
a place where designers and developers can get to know one another
Making the Jump to AS 3.0
In AS 3.0, it is not easy to find a child MovieClip by reference if it did not appear on the first frame. So the cleanest way is probably to attach a base class to the button or interactive element in the library linkage.
This is nothing new, folks did this in AS 2, as well. For some things, having the class associated with a library clip makes a lot of sense, but I also look at that from an application design point of view with some trepidation. I suspect a centralized event dispatcher is ideal when you have all these little pieces of MovieClips and their code floating around in a project. I'd be interested to hear if/how other people have used an event dispatcher this way and how did they go about it.
Growing pains wise, the 'yuck' thing for me with AS 3 are some of the error messages that my browser chugged up for me. Normally I love error messages, but some were so odd or vague, it took hours to chase down the culprit. In one case, it turned out that a series of clips I was showing in sequence had not all been published in AS 3. So as I loaded the swfs and displayed them, one or two triggered an odd debugger message about my loader. I knew there was no code in any of the items so it was very confusing.
This is nothing new, folks did this in AS 2, as well. For some things, having the class associated with a library clip makes a lot of sense, but I also look at that from an application design point of view with some trepidation. I suspect a centralized event dispatcher is ideal when you have all these little pieces of MovieClips and their code floating around in a project. I'd be interested to hear if/how other people have used an event dispatcher this way and how did they go about it.
Growing pains wise, the 'yuck' thing for me with AS 3 are some of the error messages that my browser chugged up for me. Normally I love error messages, but some were so odd or vague, it took hours to chase down the culprit. In one case, it turned out that a series of clips I was showing in sequence had not all been published in AS 3. So as I loaded the swfs and displayed them, one or two triggered an odd debugger message about my loader. I knew there was no code in any of the items so it was very confusing.
About
© 2009 Created by Brad Tollefson on Ning. Create Your Own Social Network
