mvp

The classical strongly typed MVP pattern looks like this in Scala: trait IView { } trait Presenter[View <: IView] { // or have it as an abstract type member val view : View } case class View1(...) extends IView { ... } case object Presenter1 extends Presenter[View1] { val view = View1(...) } Now, I wonder if there is any nice way to improve on it which I am missing... Nice thing about MVP pattern is that it makes your UI code unit testable. I'd suggest you to avoid instantiating view in presenter and pass it to constructor. That will allow you to just mock out the View and unit test the

I want to pass the Model data into another activity using Parceler through Bundle intent. My problem is how could I pass the data from Presenter into the View layer to display in another activity using MVP architecture in android? This is certainly possible. Presuming that your Activity implements your View interface you'd have a method in the interface like: void startNextActivity(MyData data); Then in the Activity: @Override void startNextActivity(MyData data) { // create bundle // send intent } And in Presenter: view().startNextActivity(myData); However I don't recommend that you do this I

Recently I took over an android project which is built on top of MVP. While simple screens are quite straight forward and easy to read and maintain, the more complex parts of the app are not. Multiple inheritance levels have caused me days of switching between classes, trying to find out how the information flow is actually working. Here one example of the more problematic hierarchies: Since we use MVP, naturally there is another presenter class and another view class for each of the classes in the diagram. So I did some research and found this article: Composition vs Inheritance in MVP and it

I am using MVP pattern to build a small test android app. I have two fragments Fragment B (I am using for sliding drawer) and Fragment A (main fragment). Both fragments have their own presenters. when I click on sliding draw it should send message or invoke a method in Fragment A to update view. I want to ask , how both fragments presenter can talk under MVP. I know other solutions but I want to do it through MVP pattern. Please suggest some options that MVP pattern follows to deal such scenarios. First of all, in MVP approaches, presenter and view have 1 to 1 relation to each other. If you

I'm currently developing an android app using MVP Pattern. When I try to develop an Activity, I should use a ListView. So I'm using Adapter for ListView. But I heard Adapter is similar to Presenter on MVP Pattern. I think if Apdater is smiliar to Presenter, then I should make Presenter for updating ListView instead of Adapter. When this situation, how to develop ListView? Just use Adapter and keep using MVP Pattern? Thanks for your reading. Yes, the Adapter should be the P component in an MVP pattern. In fact ListViews are pretty much written as MVP- the getView() function needs to set all the

I just read this article and it did confuse me a lot. Secondly, this model allows us to minimize our use of GWTTestCase, which relies on the presence of a browser, and, for the bulk of our code, write lightweight (and fast) JRE tests (which don't require a browser). [1] Is this the whole benefit, I have from following this design pattern? It seems to make the code more complex... Do you use this pattern? topchef I have to disagree, MVP makes code way less complex, especially in case of GWT. If you plan on medium to large size GWT project then MVP architecture is your primary option. I suggest