Comments on: Top 10 Mistakes when building Flex Applications http://gorillajawn.com/wordpress/2008/04/16/top-10-mistakes-when-building-flex-applications/ Enterprise Software Consultant Mon, 15 Mar 2010 20:02:48 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Amanda Johnson http://gorillajawn.com/wordpress/2008/04/16/top-10-mistakes-when-building-flex-applications/comment-page-1/#comment-14894 Amanda Johnson Wed, 30 Apr 2008 16:25:16 +0000 http://ectropic.com/wordpress/?p=30#comment-14894 Nice articles, Jon! Would you be interested in speaking on this topic at an upcoming meeting of the (Denver-based) Rocky Mountain Adobe Users group? I think discussing misconceptions, mistakes, and fallacies in Flex development would be of interest to our group. If you're interested, please let me know and I'll give you more details. Nice articles, Jon! Would you be interested in speaking on this topic at an upcoming meeting of the (Denver-based) Rocky Mountain Adobe Users group? I think discussing misconceptions, mistakes, and fallacies in Flex development would be of interest to our group.

If you’re interested, please let me know and I’ll give you more details.

]]> By: Harry B. Garland http://gorillajawn.com/wordpress/2008/04/16/top-10-mistakes-when-building-flex-applications/comment-page-1/#comment-13362 Harry B. Garland Thu, 17 Apr 2008 18:23:33 +0000 http://ectropic.com/wordpress/?p=30#comment-13362 The most common mistake that I've seen is not taking full advantage of mxml. New Flex developers tend to reinvent the wheel a lot by programming something that Flex already has a built-in solution for. For example, they are unaware of how to use states and transitions, or they are unaware of all the things you can do with data binding. So they write a lot of ActionScript with tightly coupled views instead of writing small amounts of Actionscript and using mxml for all that it can model. The most common mistake that I’ve seen is not taking full advantage of mxml. New Flex developers tend to reinvent the wheel a lot by programming something that Flex already has a built-in solution for. For example, they are unaware of how to use states and transitions, or they are unaware of all the things you can do with data binding. So they write a lot of ActionScript with tightly coupled views instead of writing small amounts of Actionscript and using mxml for all that it can model.

]]>