Colin Moock's Charges Against ActionScript 3.0
Yesterday, Colin Moock published an interesting article about nine problems he sees with ActionScript 3.0 and Flash Player 9. Most of the charges he makes are specific to the Flash CS3 authoring environment, and the general theme is that ActionScript 3.0 and its implementation in Flash CS3 makes the development process more difficult than it should be for users without significant programming backgrounds.
Colin does an excellent job of describing each charge in detail, with code examples. He also spends a lot of time discussing not only what Adobe should do in each case, but also what the Flash developer community should do. If you regularly work in the Flash CS3 environment, I highly recommend this article. There's less relevant material for Flex and FlexBuilder users, but a couple of the topics may be of interest: "2. Getting rid of loaded .swf files is hard." and "6. ActionScript 3.0's additional errors make coding cumbersome."
I'd like to encourage you to read his article and send us feedback on what you think are the most important issues he brings up in his article. Colin even links to some of Adobe's feedback mechanisms. I didn't see in his article the relative weights he attaches to the nine charges, but it would be interesting to see which charges the community would consider the highest priority.
Here's the link again in case you missed it at the top of the post:
Comments
I would say in my opinion the most important/needed of the features he charges against is:
1. the unloadMovie replacement
2. the clone object replacement
From my experience (which was extensive in AS2 and has now fully bridged over to AS3), those two issues to me are the most frustrating. They require a lot more work to get around. I don't think I've yet found a roadblock related to either of them, but I've certainly had some less than clean code solutions I've had to implement (and then cringe when I check in the code!)
Also, as I said in a comment over on that main post, I think most of the rest of what Colin is calling for seems to be more on the lines of stuff that should be in a AS Framework (similar to the JS frameworks like jQuery or Dojo) which helps fill the gaps and creates utility functions and consistency for lesser experienced designers who still need to leverage a CS3 SWF.
However, I would add (something I didn't think of last nite), perhaps what all those designers who are complaining should be reminded of is that they can still target Flash 9 with the AS engine and write their old code to their heart's content. Only if there's some specific AS3 feature would they *have* to jump the gap, and then we could have community driven frameworks that helped cushion the landing.
Posted by: Kyle Simpson | July 17, 2008 7:22 AM
I would say in my opinion the most important/needed of the features he charges against is:
1. the unloadMovie replacement
2. the clone object replacement
From my experience (which was extensive in AS2 and has now fully bridged over to AS3), those two issues to me are the most frustrating. They require a lot more work to get around. I don't think I've yet found a roadblock related to either of them, but I've certainly had some less than clean code solutions I've had to implement (and then cringe when I check in the code!)
Also, as I said in a comment over on that main post, I think most of the rest of what Colin is calling for seems to be more on the lines of stuff that should be in a AS Framework (similar to the JS frameworks like jQuery or Dojo) which helps fill the gaps and creates utility functions and consistency for lesser experienced designers who still need to leverage a CS3 SWF.
However, I would add (something I didn't think of last nite), perhaps what all those designers who are complaining should be reminded of is that they can still target Flash 9 with the AS2 engine and write their old code to their heart's content. Only if there's some specific AS3 feature would they *have* to jump the gap, and then we could have community driven frameworks that helped cushion the landing.
Posted by: Kyle Simpson | July 17, 2008 7:22 AM
I totally agree with Kyle's post above. I'm currently moving from AS2 to AS3 and those two missing elements (duplicateMovieClip and removeMovieClip) are driving me nuts as I used them both extensively in my projects and they don't have easy work-arounds. I do however also agree with the other points Colin makes, they just don't bug me as much as the other two elements.
Thanks for the great work and keep it up!
Posted by: Dave Carey | July 25, 2008 12:00 PM
The absence of an equivalent method for the duplicateMovieClip in AS-3 is a major problem. We need a simple method like:
DisplayObject.duplicate();
Posted by: Sher Ali | July 27, 2008 12:18 AM
I am a multimedia trained designer who loves using flash because I did not have to use dreamweaver. In flash I can place things were I want visually and they show up that way without code. When I want to go to a page I simply jump to a frame and display a new graphics with new animations. This is cool and smart to me and makes really nicely original designs that do not look like templates. I can not for the life of me make a site in CS3. I can not even make buttons jump to frames. I want to use the 3d papervision stuff and all the great as3.0 components on the market but I cant do simple things in the language. I am hoping flash can move to acomidate the artist designer type of person who really just want to have cool interactive experiences. I use audio programs, since I was a kid and know video software, 3D, and all the creative suite but when I am trying to make something interactive it seems like I am writing the program instead of using a program that helps me make the experience. It feels like some flash applications I buy online have so much code they mine as well as written the code for the flash application itself. i just wish web/interactive design could be as fun as making music, or art, or design or 3d. What I am saying is that I like how Collin is advocating for including designers in the flash platform and making things simple for simple people and allowing complexity for those who are smart enough to do it. Give us some visual and gui that makes simple moving around cake. Imagine a flash program that includes tons of components and pre built features for basic every day tasks. In Maya they give you hair, and cloth, and all primitive shapes and spines and all types of visiual tools for doing things. Component after component. Imagine a flash program that had a library the size of flashden for making things. I would love it if making interactive art and design was as fun as making music or designs . I kind of wish right know I did not have to work in interactive web design at this time until the software becomes more fun and easy to use so I can focus on look and experience instead of banging my head over code for days just to do something simple. I think I might take a break from interactive design for a while until sofware catches up but then again I gotta pay the bills. anyways I will learn and continue to see if I can get this developer/programming thing down because it is so dam powerful and I love the stuff these og programmers are making I just really wish I could do it but it seams so unatainable.
Posted by: jared wolf | August 2, 2008 10:35 PM