Your Presenter should not be Context dependent in the first place. If your presenter needs SharedPreferences you should pass them in the constructor. If your presenter needs a Repository, again, put that in the constructor. I highly suggest watching Google clean code talks since they do a really good job explaining why you should use … Read more
Microsoft’s Application Architecture Guide describes MVC and MVP, and explores the differences between the two. http://www.codeplex.com/AppArch This MSDN article describes MVVM and it’s evolution. http://msdn.microsoft.com/en-us/magazine/dd419663.aspx
Don’t you need to pass the argument? Your event signature is EventHandler, which is (object sender, EventArgs e). this.mockView.Raise(mock => mock.MyEvent += null, new EventArgs()); I’ve never used the overload you’ve specified here… it doesn’t seem correct, though.
It has been some time since you asked this question but I thought it would be useful to provide an answer anyway. I would strongly suggest that the presenter should have no concept of the Android Context (or any other Android classes). By completely separating your Presenter code from the Android system code you are … Read more
Besides the already mentioned great reads (Fowler & Miller) and to reply to your point on differences among controller/ presenter/ … from the developer’s point of view: Controller in MVC: Controller is the actual component that gets called as a result of user interaction. Developer does not have to write code to delegate calls to … Read more
Model View Presenter and Model View Controller both try to solve the same “seperation of concerns” problem. The primary difference you’ll find is that Model View Controller (MVC) is often implemented with some coupling between the view and some model of some sort – thereby a given view is specifically purposed to provide a visualization … Read more
At the time of writing (2016), many projects are written using bad version of MVC pattern. Where an Activity/Fragment/Controller has too many line of codes. This issue is commonly called God Activity. MVP is gaining popularity to solve this issue by decoupling class to a Model, View, and Presenter. But MVP itself isn’t enough, we … Read more
This is my humble take on MVP and your specific issues. First, anything that a user can interact with, or just be shown, is a view. The laws, behavior and characteristics of such a view is described by an interface. That interface can be implemented using a WinForms UI, a console UI, a web UI … Read more
Some basic differences can be written in short: MVC: Traditional MVC is where there is a Model: Acts as the model for data View : Deals with the view to the user which can be the UI Controller: Controls the interaction between Model and View, where view calls the controller to update model. View can … Read more
Model-View-Presenter In MVP, the Presenter contains the UI business logic for the View. All invocations from the View delegate directly to the Presenter. The Presenter is also decoupled directly from the View and talks to it through an interface. This is to allow mocking of the View in a unit test. One common attribute of … Read more