Android MVP - Call Method in Implementation View (Fragements or Activity)

I have implemented MVP in my new application, then I ran into a problem. I needed to call a method View

, inside View

( Activity

). This is by the definition of MVP code splitting, something is wrong.

A-priory:

The Moderator is responsible for the orchestration between the Model and the View. He basically receives events from both and acts accordingly. The leader is the only ingredient that knows others. It refers to the view and the other refers to the Model. ( source )

In the same article, it was mentioned that it View

does not respond to user interaction, it passes control Presenter

to complete the task. I also read this SOF report on dependency rules.

In my case, I am using a custom AppTheme

. AppTheme

needs to be set before calling setContent()

, what I do is create a method in the interface View

called setAppTheme()

which mine implements Activity

and there is code to apply the theme. Now the problem is that it is being called inside the application, which is calling the method call View

inside its implementation.

To summarize, which is my understanding of MVP or one of the following should be true:

• The method call is View
  
  inside Activity
  
  , because it setTheme()
  
  doesn't work after setContent()
  
  , and ours presenter.setView()
  
  is in onResume()
  
  , but does this satisfy the MVP separation of MVP?

• Don't use an interface method for setAppTheme()
  
  , instead create a private method in Activity
  
  that sets the theme. This method will have nothing to do with any MVP layer. But the question is, if the project is using the MVP pattern, is this practice valid?

Here is my MVP:

public class AboutUsMVP
{

    public interface Model
    {


        String getFbLink();
        String getTwitterLink();
        String getEmailLink();
        String getCompanyLink();

    }

    public interface Presenter
    {
        void setView( View view );

        void fbButtonClicked();

        void twitterButtonClicked();

        void emailButtonClicked();

        void imageButtonClicked();

    }

    public interface View
    {

        void showFacebookPage();
        void showTwitterPage();
        void showEmailIntent();
        void showCompanyWebsite();
        void setAppTheme();
        void setCustomActionBar();

    }

}

      

        
        
        
      

    

Please point out the errors when I missed them.

From what I know, the same case can be argued in light setActionBar()

and setOnClickListener()

, although these may require their separate position, but they are more relevant here and the new message for any of them will be duplicated.

Please note that my activity implements the View interface.

EDIT: More explanation

My View is an Activity class. This is a kind of M V P class , not for Android API View

. The point is that there is a method setAppTheme()

that is only related to the MVP view ( Activity

for Android). This call is not in the Contract ( AboutUsMVP.java

), which Google agreed to AboutUsContract.java

, this setAppTheme()

one is not in the Contract, and it cannot be, so this violates the MVP principle?

There is no alternative, one might say, to make an interface setAppTheme()

, if I do it it won't work because:

setAppTheme()

called immediately after the method super()

, unless it is useless. And the lead MVP starts working for onResume

. If the interface is made, but setAppTheme()

introduced into the MVP jurisdiction, it will have no effect.