ActionScript 3.0 Design Patterns at Work Survey
A Three-Question Survey
I’m working on a new post about ActionScript 3.0 Design Patterns at work. To help get an accurate measure of what folks are doing in the ActionScript work world, I put together a simple survey. The survey is made with radio buttons and check boxes; so it only takes a minute to fill out. Click below to take the World’s Easiest Survey:
ActionScript Design Patterns at Work Survey
We thank you in advance, and when we get the post up, you’ll see the results from the survey.
Related posts:
Categories: Design Patterns at Work, Flash, Flex, Principles
Bill Sanders
Well, we actually first get a graphic design from our artists THEN try to cram MVC or other design patterns in it. Clients don’t care about architecture or user friendlyness, interface design or whatever – they want purdy graphics and flashy animasuhuns.
Hi Archont,
I suppose a lot of shops work that way. The artists go to town and then send it to developers. I’d really like to discuss building a model to provide the designers all of the freedom and creativity they need and then some kind of structure to pull everything together.
Thanks for pointing that out,
Bill
Interesting survey. I chose the “We use good practices when we can…” but only because we recently made the transition from a “Wild West” anything goes AS2 approach to a more effective “I have seen the light” AS3 with OOP architecture. It’s taken a fair amount of retraining for me and my team to make the switch, we didn’t come from a programming background. I want us to be strict about using OOP practices, but we can’t always execute for lack of experience.
Hi Alex,
I have a feeling you won’t be alone. Moreover, I’ve been finding that adopting good OOP practices and Design Patterns is not a matter of having a programming background in computer science, computer engineering, or Web development. Rather, I believe it is a decision somewhere to set up a structure so that a process includes using OOP/DP programming practices. Sometimes the developers are handed a tool that includes a DP, such as an MVC or PureMVC, and everything they do is applying the structure in the tool. Others use DPs and OOP principles for the sole reason that it saves time and money in the long run.
It sounds like what you’re doing is heading down the down exactly the right path. Bad programming habits (and I have as many as anyone) are exactly that; habits. The real trick, I’m learning, is to set up routines that make it just as easy to use good OOP and DPs as it is to crunch out Wild West (love that term!) programs held together with tape, shoestrings and baling wire.
Kindest regards,
Bill