Android Dagger 2 with MVP











up vote
0
down vote

favorite












Using Dagger 2 for the first time with MVP.



I am stuck at a very simple implementation.



my presenter module takes View Interface in constructor along with context and data manager,I am confused in how to send activity context to the constructor for the view interface..
Any help will be highly appreciated..



Here is my code for App class:



public class App extends Application {


private static App app;

public SampleComponent getSc() {
return sc;
}

private SampleComponent sc;

public static App getApp() {
return app;
}

@Override
public void onCreate() {
super.onCreate();

app = this;
sc = DaggerSampleComponent.builder()
//.sampleModule(new SampleModule())
.presenterModule(new PresenterModule(new MainActivity(), getApplicationContext(), new ModelManager()))
.build();

}
}


Code for Presenter Module :



@Module
public class PresenterModule {
ShowCountContract.view v;
ModelManager mm;
Context c;
public PresenterModule(MainActivity m, Context c,
ModelManager mm) {
this.c = c;
this.mm = mm;
this.v = m;
}

@Singleton
@Provides
PresenterClass getPresentationClass() {


return new PresenterClass(mm, v);
}

}









share|improve this question


























    up vote
    0
    down vote

    favorite












    Using Dagger 2 for the first time with MVP.



    I am stuck at a very simple implementation.



    my presenter module takes View Interface in constructor along with context and data manager,I am confused in how to send activity context to the constructor for the view interface..
    Any help will be highly appreciated..



    Here is my code for App class:



    public class App extends Application {


    private static App app;

    public SampleComponent getSc() {
    return sc;
    }

    private SampleComponent sc;

    public static App getApp() {
    return app;
    }

    @Override
    public void onCreate() {
    super.onCreate();

    app = this;
    sc = DaggerSampleComponent.builder()
    //.sampleModule(new SampleModule())
    .presenterModule(new PresenterModule(new MainActivity(), getApplicationContext(), new ModelManager()))
    .build();

    }
    }


    Code for Presenter Module :



    @Module
    public class PresenterModule {
    ShowCountContract.view v;
    ModelManager mm;
    Context c;
    public PresenterModule(MainActivity m, Context c,
    ModelManager mm) {
    this.c = c;
    this.mm = mm;
    this.v = m;
    }

    @Singleton
    @Provides
    PresenterClass getPresentationClass() {


    return new PresenterClass(mm, v);
    }

    }









    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Using Dagger 2 for the first time with MVP.



      I am stuck at a very simple implementation.



      my presenter module takes View Interface in constructor along with context and data manager,I am confused in how to send activity context to the constructor for the view interface..
      Any help will be highly appreciated..



      Here is my code for App class:



      public class App extends Application {


      private static App app;

      public SampleComponent getSc() {
      return sc;
      }

      private SampleComponent sc;

      public static App getApp() {
      return app;
      }

      @Override
      public void onCreate() {
      super.onCreate();

      app = this;
      sc = DaggerSampleComponent.builder()
      //.sampleModule(new SampleModule())
      .presenterModule(new PresenterModule(new MainActivity(), getApplicationContext(), new ModelManager()))
      .build();

      }
      }


      Code for Presenter Module :



      @Module
      public class PresenterModule {
      ShowCountContract.view v;
      ModelManager mm;
      Context c;
      public PresenterModule(MainActivity m, Context c,
      ModelManager mm) {
      this.c = c;
      this.mm = mm;
      this.v = m;
      }

      @Singleton
      @Provides
      PresenterClass getPresentationClass() {


      return new PresenterClass(mm, v);
      }

      }









      share|improve this question













      Using Dagger 2 for the first time with MVP.



      I am stuck at a very simple implementation.



      my presenter module takes View Interface in constructor along with context and data manager,I am confused in how to send activity context to the constructor for the view interface..
      Any help will be highly appreciated..



      Here is my code for App class:



      public class App extends Application {


      private static App app;

      public SampleComponent getSc() {
      return sc;
      }

      private SampleComponent sc;

      public static App getApp() {
      return app;
      }

      @Override
      public void onCreate() {
      super.onCreate();

      app = this;
      sc = DaggerSampleComponent.builder()
      //.sampleModule(new SampleModule())
      .presenterModule(new PresenterModule(new MainActivity(), getApplicationContext(), new ModelManager()))
      .build();

      }
      }


      Code for Presenter Module :



      @Module
      public class PresenterModule {
      ShowCountContract.view v;
      ModelManager mm;
      Context c;
      public PresenterModule(MainActivity m, Context c,
      ModelManager mm) {
      this.c = c;
      this.mm = mm;
      this.v = m;
      }

      @Singleton
      @Provides
      PresenterClass getPresentationClass() {


      return new PresenterClass(mm, v);
      }

      }






      android dagger-2 mvp






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 9 at 18:53









      TahirRaza

      11




      11
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          To handle the Android context the best approach is to create an Application Component with an Application Module. This module should be responsible to provide objects that are common in the entire application, as the Context. And based on that component you can create subcomponents for each feature/activity/etc.



          @Module
          public class ApplicationModule {

          private final Application application;

          public ApplicationModule(Application application) {
          this.application = application;
          }

          @Provides
          Context provideContext() {
          return application;
          }

          }


          If you choose to work with just one component (what I do not recommend), your code for DaggerComponent creation will look like this:



          DaggerSampleComponent.builder()
          .applicationModule(new ApplicationModule(this))
          .otherModule(new OtherModule())
          .build();


          Or you can use Component.Builder



          As the Activity instance is created by the Android Framework, we cannot pass the View interface as a constructor parameter. The common way is to create such a method as attachView(ViewInterface) in your Presenter to be able to set an internal property.



          Another thing you should change is to remove the Presenter's constructor from App and let the OtherModule be responsible for that:



          @Module
          public class OtherModule {
          @Singleton
          @Provides
          PresenterClass getPresentationClass(Context ctx) {
          return new PresenterClass(ctx, new ModelManager());
          }
          }


          I recommend you to check this article where it goes deeper on Dagger explanation and even shows another Dagger's version that is directly thought to the Android environment.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53231751%2fandroid-dagger-2-with-mvp%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            To handle the Android context the best approach is to create an Application Component with an Application Module. This module should be responsible to provide objects that are common in the entire application, as the Context. And based on that component you can create subcomponents for each feature/activity/etc.



            @Module
            public class ApplicationModule {

            private final Application application;

            public ApplicationModule(Application application) {
            this.application = application;
            }

            @Provides
            Context provideContext() {
            return application;
            }

            }


            If you choose to work with just one component (what I do not recommend), your code for DaggerComponent creation will look like this:



            DaggerSampleComponent.builder()
            .applicationModule(new ApplicationModule(this))
            .otherModule(new OtherModule())
            .build();


            Or you can use Component.Builder



            As the Activity instance is created by the Android Framework, we cannot pass the View interface as a constructor parameter. The common way is to create such a method as attachView(ViewInterface) in your Presenter to be able to set an internal property.



            Another thing you should change is to remove the Presenter's constructor from App and let the OtherModule be responsible for that:



            @Module
            public class OtherModule {
            @Singleton
            @Provides
            PresenterClass getPresentationClass(Context ctx) {
            return new PresenterClass(ctx, new ModelManager());
            }
            }


            I recommend you to check this article where it goes deeper on Dagger explanation and even shows another Dagger's version that is directly thought to the Android environment.






            share|improve this answer

























              up vote
              0
              down vote













              To handle the Android context the best approach is to create an Application Component with an Application Module. This module should be responsible to provide objects that are common in the entire application, as the Context. And based on that component you can create subcomponents for each feature/activity/etc.



              @Module
              public class ApplicationModule {

              private final Application application;

              public ApplicationModule(Application application) {
              this.application = application;
              }

              @Provides
              Context provideContext() {
              return application;
              }

              }


              If you choose to work with just one component (what I do not recommend), your code for DaggerComponent creation will look like this:



              DaggerSampleComponent.builder()
              .applicationModule(new ApplicationModule(this))
              .otherModule(new OtherModule())
              .build();


              Or you can use Component.Builder



              As the Activity instance is created by the Android Framework, we cannot pass the View interface as a constructor parameter. The common way is to create such a method as attachView(ViewInterface) in your Presenter to be able to set an internal property.



              Another thing you should change is to remove the Presenter's constructor from App and let the OtherModule be responsible for that:



              @Module
              public class OtherModule {
              @Singleton
              @Provides
              PresenterClass getPresentationClass(Context ctx) {
              return new PresenterClass(ctx, new ModelManager());
              }
              }


              I recommend you to check this article where it goes deeper on Dagger explanation and even shows another Dagger's version that is directly thought to the Android environment.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                To handle the Android context the best approach is to create an Application Component with an Application Module. This module should be responsible to provide objects that are common in the entire application, as the Context. And based on that component you can create subcomponents for each feature/activity/etc.



                @Module
                public class ApplicationModule {

                private final Application application;

                public ApplicationModule(Application application) {
                this.application = application;
                }

                @Provides
                Context provideContext() {
                return application;
                }

                }


                If you choose to work with just one component (what I do not recommend), your code for DaggerComponent creation will look like this:



                DaggerSampleComponent.builder()
                .applicationModule(new ApplicationModule(this))
                .otherModule(new OtherModule())
                .build();


                Or you can use Component.Builder



                As the Activity instance is created by the Android Framework, we cannot pass the View interface as a constructor parameter. The common way is to create such a method as attachView(ViewInterface) in your Presenter to be able to set an internal property.



                Another thing you should change is to remove the Presenter's constructor from App and let the OtherModule be responsible for that:



                @Module
                public class OtherModule {
                @Singleton
                @Provides
                PresenterClass getPresentationClass(Context ctx) {
                return new PresenterClass(ctx, new ModelManager());
                }
                }


                I recommend you to check this article where it goes deeper on Dagger explanation and even shows another Dagger's version that is directly thought to the Android environment.






                share|improve this answer












                To handle the Android context the best approach is to create an Application Component with an Application Module. This module should be responsible to provide objects that are common in the entire application, as the Context. And based on that component you can create subcomponents for each feature/activity/etc.



                @Module
                public class ApplicationModule {

                private final Application application;

                public ApplicationModule(Application application) {
                this.application = application;
                }

                @Provides
                Context provideContext() {
                return application;
                }

                }


                If you choose to work with just one component (what I do not recommend), your code for DaggerComponent creation will look like this:



                DaggerSampleComponent.builder()
                .applicationModule(new ApplicationModule(this))
                .otherModule(new OtherModule())
                .build();


                Or you can use Component.Builder



                As the Activity instance is created by the Android Framework, we cannot pass the View interface as a constructor parameter. The common way is to create such a method as attachView(ViewInterface) in your Presenter to be able to set an internal property.



                Another thing you should change is to remove the Presenter's constructor from App and let the OtherModule be responsible for that:



                @Module
                public class OtherModule {
                @Singleton
                @Provides
                PresenterClass getPresentationClass(Context ctx) {
                return new PresenterClass(ctx, new ModelManager());
                }
                }


                I recommend you to check this article where it goes deeper on Dagger explanation and even shows another Dagger's version that is directly thought to the Android environment.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 16 at 13:42









                haroldolivieri

                17812




                17812






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53231751%2fandroid-dagger-2-with-mvp%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Guess what letter conforming each word

                    Port of Spain

                    Run scheduled task as local user group (not BUILTIN)