Andy Wardley wrote:
What the MVC-for-the-web crowd are really trying to achieve is a clear
separation of concerns. Put your database code in one place, your
application code in another, your presentation code in a third place.
That definitely is what I've always meant by MVC. I haven't found a better fit for describing that to people. If I just say "separation of concerns" people stare blankly and want a more concrete pattern to follow. I could say something like "command classes + data objects + templates", but it doesn't have the same ring or historical proof behind it.
Of course some people use MVC to abstract different types of inputs as well (web browser vs. cell phone vs. cron job), but that's not common.
Is there a better way to describe this sort of thing without the baggage of arguing about what a controller is, etc.?
- Perrin
_______________________________________________
templates mailing list
[EMAIL PROTECTED]
http://lists.ourshack.com/mailman/listinfo/templates
