Thursday, July 17th, 2008
Colin Moock has been creating some buzz in the Flash community with his article on the charges against ActionScript 3.0:
- The removal of on()/onClipEvent() from Flash CS3 makes creating simple interactivity hard.
- Getting rid of loaded .swf files is hard.
- Casting DisplayObject.parent makes controlling parent movie clips hard.
- The removal of getURL() makes linking hard.
- The removal of loadMovie() makes loading .swf files and images hard.
- ActionScript 3.0’s additional errors make coding cumbersome.
- Referring to library symbols dynamically is unintuitive.
- Adding custom functionality to manually created text fields, to all movie clips, or to all buttons is cumbersome.
- The removal of duplicateMovieClip() makes cloning a MovieClip instance (really) hard.
Despite all the talk of GPU blitting, pixel shading, and ligatures, a non-negligible percentage of the Flash community is rightfully asking: is Adobe still committed to the simple, agile authoring practices on which Flash was founded? It’s a rational enough concern. After all, Flash built its success on “ease of use.” Some 11 years ago, the tagline on the Flash 2 box read: “The Easiest Way to Create Fast Web Multimedia.” Originally, Flash was purpose-built for people who wanted to make things move without years of animation training, or who wanted to create interactivity and programmatic behavior without a degree in computer science. A decade of loyalty later, those same peopleâ€”call them the “everyday Flashers”â€”are now wondering how, or even if, they fit into Adobe’s new platform strategy.
Although the general concern over Flash’s ease of use is natural, much of it is based on fear, not facts.
I am sure Adobe is watching. For one, Francis Cheng posted about it too, and asked for input.
Posted by Dion Almaer at 1:18 am