Sean is a highly sought after Flex developer and consultant with extensive ActionScript programming experience, including more than five years developing for the Flash platform and over a decade of experience designing and developing desktop and web based applications. Business owner, technical author, blogger and Adobe Flex/AIR enthusiast, Sean is an Adobe Flex Developer Community Champion and the creator of the ActionScript Cheatsheets. Sean has posted 2 posts at DZone. View Full User Profile

Flex best practices – Part 1: Setting up your Flex project

03.11.2009
| 43569 views |
  • submit to reddit

Where to go from here

For more information on using and applying best practices for your Flex development process be sure to see the second part of this article, which will be published on DZone in the coming weeks.


Disclaimer

Here is a quote that you should keep in mind while you are going through the material presented in this article. I think this quote is pretty applicable:

"Every project targeting Flex is different, and thus best practices vary depending on the team involved and the project at hand. I have seen all manner of project practices that work for small teams but fail for larger teams and vice versa. This is my take on Flex best practices from having looked at many projects over the past three years. In many ways, my recommendations should not come as a surprise, as these are tenets of classical software development." - Ted Patrick

Attributions

Thank you very much to the following people for their input and review of this article. It would not exist without their help: Hong Qiu, Dolores Joya, Eric Feminella, Jeffry Houser, Jesse Warden, Shannon Hicks, and Chris Griffith.

Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.

AttachmentSize
adobe_fx_download_button_100x30.jpg1.49 KB
Published at DZone with permission of its author, Sean Moore.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)