Different frameworks have different tweaks to the conventions. It's usually best to have a specific framework in mind when working on this.
Eg. We do things differently in RubyonRails to RobotLegs. I've worked with Django in the past as well. It has hard blockers to keep logic getting into the views which occasionally make things incredibly difficult, whereas Rails doesn't force you as much. Django also calls controllers views and views templates, in case you're confused when reading their doco. The best thing is to go with a framework that has the developer culture and features that you like and then work with their way of doing things. It's particularly important to follow framework conventions as it makes upgrades much easier. On 26 February 2012 02:05, John McCormack <j...@easypeasy.co.uk> wrote: > I have really appreciated this thread too. > > The basic ideas of MVC seem straight forward enough, but the problems > arise in implementing it. > > Disagreements about the roles inside MVC can really help us understand it. > So if anyone has a specific example in which they struggled to determine > the responsibilities of the roles, then it would be good to hear about it. > > John > > > ______________________________**_________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.**com <Flashcoders@chattyfig.figleaf.com> > http://chattyfig.figleaf.com/**mailman/listinfo/flashcoders<http://chattyfig.figleaf.com/mailman/listinfo/flashcoders> > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
