Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Difference between Dagger and ButterKnife Android

Can anyone point out the difference between Dagger and Butterknife? I know that Butterknife is a view injection library and Dagger is a dependency injection library. But the documentation online seems a bit overhead for me. According to Butterknife documentation, you can do non-activity injections as well, which is what Dagger does? Or did I misunderstand something?

like image 878
user2511882 Avatar asked Dec 29 '13 01:12

user2511882


2 Answers

ButterKnife is targeted to inject views only. Non-activity injection just means that you can provide your own view root to inject views from (like with manually inflated views, etc.). Dagger is a bit more complicated. It can inject anything you want as long as you specified Module - class which satisfies those dependencies (alternatively you can use constructor injection).

As a bottom line - I would say ButterKnife helps you to avoid all that boilerplate code for creating views (aka (TextView)findViewById(R.id.some_text_view);. Nothing more. Under the hood it still does all that boring code. So it is not really an injection..

Also it worth mentioning that Jake Wharton is one of the developers for both those cool libs :)

Here is some useful links:

Dagger sample project on GitHub

Dagger presentation on Devoxx (Jake Wharton)

Dagger hangout with Dagger devs

Don't have much of useful ButterKnife links. It really simple and straight forward though, so hopefully you don't need any

like image 80
Pavel Dudka Avatar answered Sep 22 '22 16:09

Pavel Dudka


Here is a link to the Buterknife documentation. It's very straightforward. However, what the documentation doesn't say but the design of Butter Knife implies is that you can also use Butter Knife in custom views. Just replace "this" with "context" or "getContext" so you determine the scope.

Link: http://jakewharton.github.io/butterknife/

I combine Butter Knife, parcelable and easyAdapter for list views in my project. Reason is less boilerplate and with parcelable faster and cleaner parceling. So if you have a lot of ListViews, I recommend this approach.

Links:

https://github.com/johncarl81/parceler

https://github.com/ribot/easy-adapter

like image 35
greenspand Avatar answered Sep 21 '22 16:09

greenspand