Ted Patrick - Demos & MAX @ Adobe Systems
Note: This is the personal blog of Ted Patrick. The opinions and statements voiced here are my own.
Flex Best Practices - Slides and Code
DIGG IT!
8
Comments
Published
Friday, November 09, 2007
at
12:25 AM
.
I gave a presentation on Flex Best Practices at FOTB 2007 and MAX 2007 Japan. The presentation is fairly high level as providing Best Practices guidance is so very precarious. I provided a warning before giving this presentation which I will repeat here:"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 3 years. In many ways my recommendations should not come as a surprise as these are tenets of classical software development."
SLIDES: PDF, SWF, PPT
FILES: FXP3 (ZIP FX3 Project - With Flex Builder 3 Beta 2, simply import this project.)
Cheers,
Ted :)
8 Responses to “Flex Best Practices - Slides and Code”
Post a CommentWhere to find me:
Ted on Twitter - @AdobeTed
Ted on Adobe Groups
Ted on LinkedIn
Ted on Facebook
Ted at Adobe
Latest
- Flex Builder 2 Price Change Active
- Adobe MAX 2007 Japan - The Arrival
- Flex Bootcamp - "Flex in 30 minutes"
- Adobe MAX Europe - Saturday Setup
- Adobe MAX Europe - SOLD OUT!!!
- Adobe MAX Europe - 18 Registrations to SOLD OUT
- Flex Family Expansion - Linux Alpha, "Thermo", "El...
- Adobe MAX Europe - 110 Registrations to go...
- MAX Europe hits 1013 Registrations
- Bono or Fake Bono
Lists
Links
Jobs
Flex JobsArchives
- May 2003
- June 2003
- July 2003
- August 2003
- September 2003
- October 2003
- November 2003
- December 2003
- January 2004
- February 2004
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
- July 2009
- August 2009
- September 2009
- October 2009
- November 2009
Hey Ted,
Great slides! Simple and to the point ;-). I understood where and why you were coming from with each, except for one: Be Careful with Bindings. Could you explain this topic a little more? Does bindings introduce complexity into a Flex app, does it decrease performance, etc?
Thanks!
funny.... I've the same reaction as Dan.
And I've the same ideas about binding, because I prefer the PuveMVC framework than Cairngorm.
I think that you have more controls with PureMVC and without binding
Dan, Laurent,
Ted said in his session that databindings are a bit of a performance hog as they essentially auto-wire up listeners and events to everything. If you create your own events you have much better control and are much more effecient. I'm sure Ted can explain it better but just wanted to prove I was listening :P
Ted, thanks for the great presentation.
OK, Ted. I'll bite. When is this FxD2 - Flex Deep Dive 2008 going to occur, where is it going to occur.
The link goes to the Adobe MAX site, so what's the deal?
Bindings are not bad. On larger projects they can add up over time. This mention was very specific to using many of them in a project. A binding creates an anonymous function and subscribes in may places listening for changes. Should you do this alot and have lots of views, this will become a performance issue.
On larger projects I recommend subscribing directly and using getter/setters.
Bindings are great in the small but in the large they can become a problem. This was not framework specific.
Ted :)
Flex + Diving = FXD2. It is a trip in 2008, either Bonaire or Grand Cayman. Fun Fun!
Ted :)
Another point about bindings. I use them often, and I suppose that one more negative is that they aren't compile time type safe. I'm referring to BindingUtils.as which allows you to bind to a property that declare as a String argument. When another developer changes the name of that variable, you don't realize that your bindings aren't firing till the application doesn't work.
Hi Ted-
I'm thinking of moving to Mac with Flex 3. Is there an upgrade path for that?