The document introduces the Model-View-Presenter (MVP) pattern, which is a derivation of MVC that aims to address issues like spaghetti code, lack of reusability, difficulty of maintenance and testing in GUI applications. It discusses the advantages of MVP in promoting separation of concerns and testability. The document also covers the passive view and supervising presenter implementations of MVP, as well as frameworks that support MVP in various programming languages.

1. Introduction To
MVP
PRESENTED IN TABRIZ SOFTWARE OPEN TALKS
SAEED SHARGI GHAZANI
@saeed_shargi

2. Problem

3. Solution’s
• Ugly
• Spaghetti Code
• Not Reusable
• Not Maintenance
• Not SRP
• Not Testable

4. Solution’s
• Bad
• Spaghetti Code
• Not Reusable
• Hard Maintenance
• Not SRP
• Not Testable

5. Solution’s
Forms and Controls
Model View Controller
VisualWorks Application Model
Model-View-Presenter (MVP)
Humble View
Martin Fowler

6. MVP
A GUI Design Pattern (Architecture)
Derivation of MVC
Early in 1990s at Taligent
Popularized in a paper by Taligent CTO Mike Potel
In 1997,Andy Bower and Blair McGlashan adapted it in Smalltalk UI
In 2006,Microsoft incorporating it for UI programming in .NET Framework

7. MVP

8. MVP

9. Advantages
SRP
Unit Test
Easier Maintain
Easily Interchangeable Views
Reusable

10. Disadvantages
Complexity
A little Trouble
Maybe not for simple and small applications

11. Implementation
Passive View
Supervising Presenter (Controller)

12. Passive View

13. Supervising Presenter

14. Implementation Frameworks
.NET
MVC# Framewok
Winforms MVP
Claymore
…
PHP
Nette Framework
Java
Swing
JFace
GWT
Google Web Toolkit
…

15. MVC

16. MVVM

17. MVC vs MVP

18. MVVM vs MVP

19. MVC vs MVVM vs MVP

20. Example Code In GitHub