Putting the View back into MVC.

[eluser]wiredesignz[/eluser]
The strange thing to me is that most CI example code suggests collecting your model resultset in an array and passing this to your view. Not only does this place more demand on memory, but breaks the basic MVC principle of seperation of concerns.

It seems more fuctional to fully prepare the data for display while its still in the Model and then pass only a reference to the Model into the View.

The View remains independent of the Model, the reference can be changed at any time by pointing to a different Model as needed, and the View processing is simplified.

EDIT:
On a second reading I can say quite categorically, Pygon and xwero have the MVC design pattern correct, Controllers are not supposed to gather data or manage business logic.

Each component must be reusable, the Model goes with its data source and doesnt care about the Controller or the View, the View needs a data source, but it doesnt depend on one exact Model, any Model providing the correct data could be used. The Controller should not depend on either the View or the Model.