I have read for three days about the Model-View-Controller (MVC) and Model-View-Presenter (MVP) patterns. And there is one question that bothers me very much. Why did software designers invent MVP, when there already was an MVC?What problems did they face, that MVC did not solve (or solved badly), but MVP can solve? Which problems is MVP intended to solve?I have read a lot of articles about the history and explanation of MVP, or about differences between MVC and MVP, but none had a clear answer to my questions.In one of the articles that I read, it was said:Now onto Model View Presenter, which was a response to the inadequacies of the MVC pattern when applied to modern component based graphical user interfaces. In modern GUI systems, GUI components themselves handle user input such as mouse movements and clicks, rather than some central controller.So, I can't understand, but can it actually be in another way, such that GUI components do not handle user input by themselves? And what exactly does handle by themselves mean?
What are the improvements of MVP over MVC?
design;design patterns;mvc;mvp