MVC Isn’t MVC
collindonnell.com
MVC Isn’t MVC
1–10 of 165 posts
Re: MVC Isn’t MVC
#2https://en.wikipedia.org/wiki/React_(software)#Unidirectiona...
edit: better link
Re: MVC Isn’t MVC
#3If you squint a bit, the "original" MVC looks eerily similar to the one-way data flow pattern popularized by flux/redux. https://en.wikipedia.org/wiki/React_(software)#Unidirectiona... edit: better link
Re: MVC Isn’t MVC
#4If you squint a bit, the "original" MVC looks eerily similar to the one-way data flow pattern popularized by flux/redux. https://en.wikipedia.org/wiki/React_(software)#Unidirectiona... edit: better link
Re: MVC Isn’t MVC
#5Re: MVC Isn’t MVC
#6If you squint a bit, the "original" MVC looks eerily similar to the one-way data flow pattern popularized by flux/redux. https://en.wikipedia.org/wiki/React_(software)#Unidirectiona... edit: better link
- Dispatcher = Controller
- Store = Model
- View = View
And the actions are the messages sent from the user to the controller.
Re: MVC Isn’t MVC
#7If you use any SDK and or framework you do not have MVC
you instead have
framework-SuperController | MVC
Re: MVC Isn’t MVC
#8https://learn.microsoft.com/en-us/dotnet/architecture/maui/m...
Re: MVC Isn’t MVC
#9Actually, having dumb models is the surest way to completely screw up your controllers design, since you’re now left with no other places to write your business logic in. This leads to either weird trees of controller inheriting each other for the sake of reusing some data processing piece, or singletons everywhere which makes the code super hard to reason upon, not to mention harder to unit test.
My take on the model layer is : write everything that’s not strictly specific to your UI there.
Re: MVC Isn’t MVC
#10If you squint a bit, the "original" MVC looks eerily similar to the one-way data flow pattern popularized by flux/redux. https://en.wikipedia.org/wiki/React_(software)#Unidirectiona... edit: better link