How to split the controller / model workload

[eluser]Dave Stewart[/eluser]
Thanks for your input.

I agree that perhaps the view would be the best place for the JS and HTML. However, I do like the idea of having one class that keeps EVERYTHING to do with a report in one place, rather than splitting it up all over the place.

For example, for each table that gets generated from the model data, I need to send appropriate column formatting data to the HTML view, to be post-processed by JavaScript. It seems logical to me to include all this data within one class, so for example one class / model per report stores:

- SQL query
- table formatting
- Related reports / next options

More views are very welcome, thanks.

Dave