How to split the controller / model workload

[eluser]Dave Stewart[/eluser]
I think maybe the solution might be to abstract my data, and instead have the column formatting data be a property of the model, that gets generated at the same time as the query result.

This way, the controller can grab this data and pass it to a function in the view, which can then act upon it accordingly.

The controller could also make decisions about the "html options" part I was discussing as well, and that way I don't need to muddy the model with data it should not be concerned about.