Timeline for In MVC, can/should basic data retrieval from the Model be done in the View?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2013 at 19:18 | comment | added | Reactgular | When you start to get Models used by many controllers. The need for them to be fat becomes very clear. When the View starts to contain a lot of PHP then you know your controller is to thin. When your controllers are very fat. It's difficult to get other controllers to operate the same way (for example, adding an API service). | |
| Jan 31, 2013 at 19:15 | history | edited | Reactgular | CC BY-SA 3.0 | added 1 characters in body |
| Jan 31, 2013 at 19:06 | comment | added | Adam Westbrook | Thanks Mathew. For clarification, up until now I've always decoupled the View and Model with the Controller as read and suggested. However, since starting to read up on keeping 'skinny' Controllers I've just been wondering what should/could be moved out of them, seems the thought process that lead me to this question was a step or two too far! | |
| Jan 31, 2013 at 18:57 | history | answered | Reactgular | CC BY-SA 3.0 |