Timeline for In MVC, can/should basic data retrieval from the Model be done in the View?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2013 at 12:06 | comment | added | Adam Westbrook | Thank you for the link, I knew I wasn't mad in thinking this! This is essentially what I'd been going off before I took the idea a bit too far, as long as the Model isn't dependant on anything what does it matter how/where it is accessed? I haven't decided what approach I'm going to take on my next development yet, but this definitely helps. | |
| Feb 2, 2013 at 17:54 | comment | added | Erik Eidt | Right, and the other thing that adds confusion is client-server, which the original SmallTalk MVC did not really account for. In client-server (e.g. with javascript) there are presentation-oriented models, views, and controllers on the client, and domain-oriented views and controllers on the server, though the server also does some presentation-oriented processing adding confusion. Also, sometimes we want a domain views to have some persistence, which means the view parameters form their own model, that is not necessarily part of the domain model. | |
| Feb 2, 2013 at 11:43 | history | answered | alnafie | CC BY-SA 3.0 |