[eluser]Aken[/eluser]
[quote author="FranckRR" date="1259356187"]Hum
Let's say. I follow your advices : I load the table in the controller and may be add_row to it ...
In my view, I use the table previously loaded in the controller.
Fine it will work
But what if I don't want to use a table any more, I need to display it in a swf. Instead of only coding a new view (which make sense because this is what I want to be changed) I must change the controller code too because I do not use the table anymore. Of course you can let the code there even if it's not used later (if you agree with that, I will stop arguing and pass mt way elsewhere)
MVC means separating logic, data and representation and not common ways or everybody does that...
If I want to represent my model in the view as a table, only the view must be aware of that ! Thus considering table in the controller already commits me about the representation.[/quote]
I think everybody's point is that it is typical, and usually recommended to load a library in the controller. However if it suits YOUR application better to load it in a view, then there is no reason why you can't. There is rarely a right or wrong when it comes to programming - technically as long as it works, life is grand. There are just opinions about what is best.