Timeline for In MVC, does the view component deliver a new view to the user directly or indirectly via the controller component?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2020 at 22:46 | comment | added | Tim | @FilipMilovanović Thanks. What is a "view widget"? Is it used in sever side web MVC or client side MVC/MVP? Could you be specific about why and how "Server-side Web MVC (e.g. ASP.NET MVC & similar where controllers handle requests and views render to HTML) is not the same as client-side/desktop MVC/MVP UI pattern"? Maybe in a reply? I always upvote replies. softwareengineering.stackexchange.com/questions/403332/… | |
| Dec 1, 2019 at 12:45 | review | Close votes | |||
| Dec 16, 2019 at 3:05 | |||||
| Dec 1, 2019 at 11:08 | answer | added | Christophe | timeline score: 1 | |
| Dec 1, 2019 at 10:12 | comment | added | Filip Milovanović | The first thing to realize is that Server-side Web MVC (e.g. ASP.NET MVC & similar where controllers handle requests and views render to HTML) is not the same as client-side/desktop MVC/MVP UI pattern. In the UI pattern, generally the View component is the view (it doesn't create one). Also modern view widgets have the capability to detect user input, back when MVC was first created, widgets had no such capability (they were just pictures on the screen), so every widget had it's own MVC, where C handled the input - in modern MVC, C implements the nontrivial behavior of a larger view. | |
| Dec 1, 2019 at 7:51 | comment | added | Theraot | You may find this interesting: The Best Refactoring You've Never Heard Of. For a nugget of the difference between web and desktop: you "cannot" send a function over the network. | |
| Dec 1, 2019 at 7:39 | answer | added | Theraot | timeline score: 3 | |
| Dec 1, 2019 at 6:18 | answer | added | jleach | timeline score: 3 | |
| Dec 1, 2019 at 4:17 | history | asked | Tim | CC BY-SA 4.0 |