Android中ButterKnife框架
Android中ButterKnife框架
前言:发现一个不错的注入框架,为了偷懒,还是拿来用了,其实我不是一个喜欢偷懒的码农,但 … …
Introduction
Annotate fields with@Bind
and a view ID for Butter Knife to find and automatically cast the corresponding view in your layout.
class ExampleActivity extends Activity { @Bind(R.id.title) TextView title; @Bind(R.id.subtitle) TextView subtitle; @Bind(R.id.footer) TextView footer; @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.simple_activity); ButterKnife.bind(this); // TODO Use fields... }}
Instead of slow reflection, code is generated to perform the view look-ups. Callingbind
delegates to this generated code that you can see and debug.
The generated code for the above example is roughly equivalent to the following:
public void bind(ExampleActivity activity) { activity.subtitle = (android.widget.TextView) activity.findViewById(2130968578); activity.footer = (android.widget.TextView) activity.findViewById(2130968579); activity.title = (android.widget.TextView) activity.findViewById(2130968577);}
RESOURCE BINDING
Bind pre-defined resources with@BindBool
,@BindColor
,@BindDimen
,@BindDrawable
,@BindInt
,@BindString
, which binds anR.bool
ID (or your specified type) to its corresponding field.
class ExampleActivity extends Activity { @BindString(R.string.title) String title; @BindDrawable(R.drawable.graphic) Drawable graphic; @BindColor(R.color.red) int red; // int or ColorStateList field @BindDimen(R.dimen.spacer) Float spacer; // int (for pixel size) or float (for exact value) field // ...}
NON-ACTIVITY BINDING
You can also perform binding on arbitrary objects by supplying your own view root.
public class FancyFragment extends Fragment { @Bind(R.id.button1) Button button1; @Bind(R.id.button2) Button button2; @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View view = inflater.inflate(R.layout.fancy_fragment, container, false); ButterKnife.bind(this, view); // TODO Use fields... return view; }}
Another use is simplifying the view holder pattern inside of a list adapter.
public class MyAdapter extends BaseAdapter { @Override public View getView(int position, View view, ViewGroup parent) { ViewHolder holder; if (view != null) { holder = (ViewHolder) view.getTag(); } else { view = inflater.inflate(R.layout.whatever, parent, false); holder = new ViewHolder(view); view.setTag(holder); } holder.name.setText("John Doe"); // etc... return view; } static class ViewHolder { @Bind(R.id.title) TextView name; @Bind(R.id.job_title) TextView jobTitle; public ViewHolder(View view) { ButterKnife.bind(this, view); } }}
You can see this implementation in action in the provided sample.
Calls toButterKnife.bind
can be made anywhere you would otherwise putfindViewById
calls.
Other provided binding APIs:
- Bind arbitrary objects using an activity as the view root. If you use a pattern like MVC you can bind the controller using its activity with
ButterKnife.bind(this, activity)
. - Bind a view's children into fields using
ButterKnife.bind(this)
. If you use<merge>
tags in a layout and inflate in a custom view constructor you can call this immediately after. Alternatively, custom view types inflated from XML can use it in theonFinishInflate()
callback.
VIEW LISTS
You can group multiple views into aList
or array.
@Bind({ R.id.first_name, R.id.middle_name, R.id.last_name })List<EditText> nameViews;
Theapply
method allows you to act on all the views in a list at once.
ButterKnife.apply(nameViews, DISABLE);ButterKnife.apply(nameViews, ENABLED, false);
Action
andSetter
interfaces allow specifying simple behavior.
static final ButterKnife.Action<View> DISABLE = new ButterKnife.Action<View>() { @Override public void apply(View view, int index) { view.setEnabled(false); }};static final ButterKnife.Setter<View, Boolean> ENABLED = new ButterKnife.Setter<View, Boolean>() { @Override public void set(View view, Boolean value, int index) { view.setEnabled(value); }};
An AndroidProperty
can also be used with theapply
method.
ButterKnife.apply(nameViews, View.ALPHA, 0.0f);
LISTENER BINDING
Listeners can also automatically be configured onto methods.
@OnClick(R.id.submit)public void submit(View view) { // TODO submit data to server...}
All arguments to the listener method are optional.
@OnClick(R.id.submit)public void submit() { // TODO submit data to server...}
Define a specific type and it will automatically be cast.
@OnClick(R.id.submit)public void sayHi(Button button) { button.setText("Hello!");}
Specify multiple IDs in a single binding for common event handling.
@OnClick({ R.id.door1, R.id.door2, R.id.door3 })public void pickDoor(DoorView door) { if (door.hasPrizeBehind()) { Toast.makeText(this, "You win!", LENGTH_SHORT).show(); } else { Toast.makeText(this, "Try again", LENGTH_SHORT).show(); }}
Custom views can bind to their own listeners by not specifying an ID.
public class FancyButton extends Button { @OnClick public void onClick() { // TODO do something! }}
BINDING RESET
Fragments have a different view lifecycle than activities. When binding a fragment inonCreateView
, set the views tonull
inonDestroyView
. Butter Knife has anunbind
method to do this automatically.
public class FancyFragment extends Fragment { @Bind(R.id.button1) Button button1; @Bind(R.id.button2) Button button2; @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View view = inflater.inflate(R.layout.fancy_fragment, container, false); ButterKnife.bind(this, view); // TODO Use fields... return view; } @Override public void onDestroyView() { super.onDestroyView(); ButterKnife.unbind(this); }}
OPTIONAL BINDINGS
By default, both@Bind
and listener bindings are required. An exception will be thrown if the target view cannot be found.
To suppress this behavior and create an optional binding, add a@Nullable
annotation to the field or method.
Note: Any annotation named@Nullable
can be used for this purpose. It is encouraged to use the@Nullable
annotation from Android's "support-annotations" library, seeAndroid Tools Project.
@Nullable @Bind(R.id.might_not_be_there) TextView mightNotBeThere;@Nullable @OnClick(R.id.maybe_missing) void onMaybeMissingClicked() { // TODO ...}
MULTI-METHOD LISTENERS
Method annotations whose corresponding listener has multiple callbacks can be used to bind to any one of them. Each annotation has a default callback that it binds to. Specify an alternate using thecallback
parameter.
@OnItemSelected(R.id.list_view)void onItemSelected(int position) { // TODO ...}@OnItemSelected(value = R.id.maybe_missing, callback = NOTHING_SELECTED)void onNothingSelected() { // TODO ...}
BONUS
Also included arefindById
methods which simplify code that still has to find views on aView
,Activity
, orDialog
. It uses generics to infer the return type and automatically performs the cast.
View view = LayoutInflater.from(context).inflate(R.layout.thing, null);TextView firstName = ButterKnife.findById(view, R.id.first_name);TextView lastName = ButterKnife.findById(view, R.id.last_name);ImageView photo = ButterKnife.findById(view, R.id.photo);
Add a static import forButterKnife.findById
and enjoy even more fun.
Download
Butter Knife v7.0.1 JAR
The source code to the library and sample application as well as this website isavailable on GitHub. The Javadoc is alsoavailable to browse.
MAVEN
If you are using Maven for compilation you can declare the library as a dependency.
<dependency> <groupId>com.jakewharton</groupId> <artifactId>butterknife</artifactId> <version>7.0.1</version></dependency>
GRADLE
compile 'com.jakewharton:butterknife:7.0.1'
Be sure to suppress this lint warning in yourbuild.gradle
.
lintOptions { disable 'InvalidPackage'}
Some configurations may also require additional exclusions.
packagingOptions { exclude 'META-INF/services/javax.annotation.processing.Processor'}
IDE CONFIGURATION
Some IDEs require additional configuration in order to enable annotation processing.
- IntelliJ IDEA— If your project uses an external configuration (like a Maven
pom.xml
) then annotation processing should just work. If not, trymanual configuration. - Eclipse— Set upmanual configuration.
PROGUARD
Butter Knife generates and uses classes dynamically which means that static analysis tools like ProGuard may think they are unused. In order to prevent them from being removed, explicitly mark them to be kept. To prevent ProGuard renaming classes that use @Bind on a member field thekeepclasseswithmembernames
option is used.
-keep class butterknife.** { *; }-dontwarn butterknife.internal.**-keep class **$$ViewBinder { *; }-keepclasseswithmembernames class * { @butterknife.* <fields>;}-keepclasseswithmembernames class * { @butterknife.* <methods>;}
GitHub下载链接: https://github.com/JakeWharton/butterknife
更多相关文章
- Android常用框架混淆代码
- Android应用框架之 Application
- Android 框架学习4:一次读懂热门图片框架 Picasso 源码及流程
- 关于android中网络图片下载中oom解决开源框架Afinal的探究
- Android数据库ORMlite框架翻译系列(第一章)
- Android 安全框架 -- 总概
- Android游戏框架与常识
- 【Android】在Android上使用OrmLite数据库框架 之 使用表配置文
- Android简明开发教程九:创建应用程序框架