dagger-2

I'm trying the new dagger 2, it's my first time implementing it but I can't make it work. I think I got the concept and I understand the example here I try to copy the same structure just a bit modified for my example. Here is the AppComponent that extends the Graph where I defined the classes I want. @ApplicationScope @Component(modules = {AppModule.class, DataModule.class}) public interface EFAppComponent extends EFGraph { /** * An initializer that creates the graph from an application. */ public final static class Initializer { private Initializer() { } // No instances. public static

All the following are used with dagger 2.10 and dagger.android package. Say I have a class I'd like to inject in multiple activities. public class DemoSharedClass { Activity activity; @Inject public DemoSharedClass(Activity activity) { this.activity = activity; } } Then, using the latest Dagger APIs, my classes are defined as public class DemoActivity extends DaggerActivity { @Inject DemoSharedClass demoSharedClass; // ... } public class Demo2Activity extends DaggerActivity { @Inject DemoSharedClass demoSharedClass; // ... } Each activity has its module and subcomponent define as (exactement

Context I have two Dagger 2 modules: NetworkModule , with @Singleton scope, that provides an HTTP client; ApiModule , with a custom @UserScope scope, that uses the HTTP client to create a consumer for Github's API. Then, I create a Dagger 2 component, to provide the Retrofit client. NetworkModule.kt @Module class NetworkModule { @Provides @Singleton fun provideHttpClient(): OkHttpClient = OkHttpClient.Builder().build() } ApiModule.kt @Module(includes = [NetworkModule::class]) class ApiModule(private val user: String) { @Provides @UserScope fun provideApi(httpClient: OkHttpClient): GithubApi =

I'm trying to convert an Acticity + Fragments app to Flow + Mortar + Dagger2 I would like to save & restore screen state when jumping from screen to screen (at least backwards). What is the prefered/recommanded way to do that ? I have spent quite a lot of time looking at flow and mortar readmes and samples but couldn't figure it out (the documentation and samples are minimal and only deal with simple/static/unique data). Say, for example, you have a browser-like app that moves from Page to Page Where each Page use the same same PageView class, the same PagePresenter Class but have different

Last week, while implementing Dagger in my current Kotlin MVP project, I was testing it on oldy phone with KitKat 4.4.2 (yep, it still supports all major material features and stuff :)) due to primary phone's maintenance. So that week I was having typical issues rather than something unusual and fixed them more or less quickly by investigating provided errors. At long last, code compiled, current project version was built without issues and ran without major bugs on KitKat with UI interacting. But when I took main phone with Nougat 7.1.2 from repair center and launched app on it I stuck with

What is the difference between Dagger and Dagger 2.0, and why did Google decide to fork the existing project? Some quotes from the Dagger 2 presentation Issues of Dagger 1: Ugly generated code Runtime graph composition Inefficient graph creation Partial traceability Map-like API Dagger 2 solutions: Compile-time validation of the entire graph Easy debugging; entirely concrete call stack for provision and creation Fully traceable POJO API Performance Dagger 2 issues: Less flexible No dynamism No automated migration path from Guice 来源： https://stackoverflow.com/questions/27888580/what-is-the