> Hey man, that's what happens to everyone. Don't sweat it. Seriously, > design patterns are sort of your "road map". It's not important > EXACTLY how you get there, and if it's easier for you to walk around > something, then walk around something, don't force yourself to walk > OVER something just because the map says that's the direction you need > to go in.
Jeff, this is really a great analogy and I agree to a certain extent but... >In other words, just start off doing what makes sense to > YOU. What makes YOU comfortable. I have to disagree here. This is only OK if you are 100% sure you're the only person who'll ever work on a project. I guess it's cool to mess around with MVC implementations on your personal projects as an exercise - to get a feel for it. I've been involved in various commercial projects lately where we've used various types of "home-cooked" MVC frameworks and experience tells me that if you want your project to be maintainable, stay away from the "do-what-you-like" type of MVC implementations. True, there's no right or wrong way when applying MVC. But I'll have to agree with Mike about using something like ARP or Cairngorm. Both of these are well-documented with full UML diagrams. This way, if you get stuck you have a community to go to for help. Sorry, I didn't mean to start an MVC war or anything like that - I'll leave that to the SmallTalk and Java gurus who have been at it since early nineties ;-) Just my 2 pence. Cheers, /Johan _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
