Putting the View back into MVC.

[eluser]Pygon[/eluser]
[quote author="dtrenz" date="1205437291"]
Are you all saying that all the controller should do is call model methods and load views, and that all data formatting or prep should be handled in the models as well as data access?
[/quote]

Absolutely not. All data formatting should be handled by the view. The model and controller
don't care AT ALL how the data is presented or what it is presented with.

[quote author="dtrenz" date="1205437291"]

EXAMPLE:

What if you are on a user profile page on a website, and a truncated version of the users bio is displayed. By clicking a "read full bio" link, you are taken to the bio page where a NON-truncated version of the bio is displayed.

In this example, would you have 2 separate model methods for retrieving the bio text? One that returned the bio, truncated by some string truncate function, and another that returned the whole bio text?

I currently have one model for retrieving the bio, and then in the controller, I truncate (or not) before sending the bio text to the view.

Which is correct MVC? Either?[/quote]

Neither -- Your model should give the view what it asks for (the bio), which the view should truncate if that is how the view wants to display it.