Single Page Applications and MVC vs MVP

As it turns out, there is still no clear, a well-define architecture for building SPAs, or rich browser clients. I’ve been working on some UI recently and found this Paper by Martin Fowler that does a good job summarizing a variety of approaches to building UI: https://martinfowler.com/eaaDev/uiArchs.html.

The article references a couple of foundational publications that lead to 404s, so I found those after some digging. Definitely a must read foe those of us who want to understand MVP on the level where it can be made practical:

• MVP: Model-View-Presenter. The Taligent Programming Model for C++ and Java by Mike Potel, VP and CTO Taligent, Inc.

  A quote of gold 1: “The presenter then represents the traditional “main” or “event loop” part of the application, creating the appropriate models, selections, commands, views, and interactors, and providing the business logic that directs what happens when, like a traffic cop or orchestra conductor.”

  A quote of gold 2: “The event processing system underlying the MVP programming model is embodied in a Notification Framework, which provides for interest-based notification of events, senders and receivers of events, type checking of events, distribution of events, etc. to mediate all the interactions among the programming model abstractions.”

• TWISTING THE TRIAD. The evolution of the Dolphin Smalltalk MVP application framework. Tutorial Paper for ESUG 2000. by Andy Bower, Blair McGlashan, Object Arts Ltd.