« On state management | Main | Flex/Flash Architectural Challenge (part 2) »
August 18, 2005
Flex/Flash Architectural Challenge
This discussion about MVC in RIAs has made it clear that different people can mean slightly different things when they talk about MVC. Once we got down to specific examples, the differences seemed to disappear.
So let's get even more specific. Suppose you were building a Flash/Flex version of Ta-da list. What would the appropriate client side architecture be? What classes would you have, with what responsibilities? If you haven't seen the app before, check it out. It's a small, convenient app made by the folks who put together Ruby on Rails.
My personal belief is that for an application of this scale, you could build it cleanly without a controller, and that the code may be simpler as a result, but I could be totally wrong. In the meantime, prove me wrong! (or better yet, prove me right!) Tell me how you would build it.
I'll offer a Macromedia T-shirt (hopefully a Flex/Zorn shirt, although we don't have any yet...) to the person who contributes the best ideas to this thread.
Full disclosure: If you feel particularly territorial about your ideas or code samples, please be warned that any insights you give may make their way into Macromedia samples / documenation / etc. In other words, please don't share anything you don't want us to share with others.
Posted by sho at August 18, 2005 12:55 PM