> It is interesting to try and fit our approach into the MVC+template > pattern
Just to clarify, it's not MVC+template; it's just MVC. The templates are one way of implementing views. You could mix and match this where appropriate, so that your Excel view is a perl module with a set of formatting guidelines stored in a sort of style sheet, while your HTML view is simply a template executed by a templating module. > I see the Controller as also responsible for deciding what to do with > the results of rendering the DOM in Excel or HTML formats - Views > don't decide how their results should be distributed. This is typically something you would put into the controller, since the view shouldn't have to worry about details like HTTP headers. - Perrin
