Android基于Facebook Rebound的动画效果框架Backboard demo (非常炫酷)

一个基于Facebook Rebound的动效框架Backboard，封装了一些API，便于开发者更方便的把View与Motion结合起来，一些效果很棒 ：https://github.com/tumblr/Backboard Demo ：https://github.com/tumblr/Backboard/releases

使用说明：

Usage

更新build.gradle 

1 2 3 4

dependencies {     compile  'com.facebook.rebound:rebound:0.3.8'     compile  'com.tumblr.backboard:backboard:+' }

开始

Backboard是一个基于rebound 的框架，它管理spring的使用，简化了最常用的用例：

• Actions, such as MotionEvents, are mapped to Springs via Imitators.

• Springs are mapped to Views and view properties via Performers.

In addition, an Actor wraps the above objects and provides a simple interface for mapping touch motion to a view's position - dragging.

Performers

一个Performer获取Spring当前的值并把它设置为view的一个属性值。

1 2 3

Spring bounce = SpringSystem.create().createSpring(); Performer xMotion =  new  Performer(view, View.TRANSLATION_X); bounce.addListener(xMotion);

对那些想节约屏幕空间的人来说，可以使用 流式接口 ：

1	Spring bounce = SpringSystem.create().createSpring().addListener( new  Performer(view, View.TRANSLATION_X));

Imitators

An Imitator constantly perturbs the Spring it is attached to. This perturbation can originate a variety of sources:

1. A MotionEvent, where the Spring can change based on the action (ACTION_DOWN,ACTION_UP), or imitate a property (x, y, etc.). These are called EventImitators.

2. Another Spring, which leads to results similar to springs being chained together. These are called SpringImitators.

Imitating Touch

An EventImitator primarily operates with OnTouchListeners. The simplest example is aToggleImitator, which toggles between two different values depending on the touch state:

1	view.setOnTouchListener( new  ToggleImitator(spring, 0, 1));

when the user touches the view, a value of 1 is set on the spring, and when the user releases, a value of 0 is set.

Imitating Motion

A MotionImitator is a special type of EventImitator that maps x and y movement to a spring. This is done with MotionProperty enums, which specifies which methods to call in a MotionEventobject. For example, MotionProperty.X.getValue(MotionEvent) calls event.getX(). It also specifies the view property to animate - MotionEvent.X.getViewProperty() corresponds toView.TRANSLATION_X. This is useful for the Actor builder later on. In addition, tracking and following strategies allow for customization of how the event value is mapped to the spring.

Tracking Strategies

Two tracking strategies are available to configure how an imitator tracks its imitatee.

• TRACK_ABSOLUTE maps the imitatee value directly to the spring.

• TRACK_DELTA maps the change in the imitatee value (relative to the initial touch) to the spring.

Follow Strategies

Two follow strategies are available to configure how the spring is updated.

• FOLLOW_EXACT maps the imitatee value directly to the current and end value of the spring.

• FOLLOW_SPRING maps the imitatee value to the end value of the spring (which allows the spring to overshoot the current position)

Imitating Springs

A SpringImitator is also a SpringListener. When the Spring it is imitating updates, it updates the end value of the Spring it is controlling. Usage is simple:

1 2 3 4 5 6 7

SpringSystem springSystem = SpringSystem.create();   Spring leader = springSystem.createSpring(); Spring follower = springSystem.createSpring();   SpringImitator follow =  new  SpringImitator(follower); leader.addListener(follow);

Actors

Even though backboard reduces a significant amount of boilerplate code, the Actor class further simplifes view motion by connecting each component together. It also manages aView.onTouchListener() (a MotionListener), which it attaches to the View automatically (this can be disabled). Here is how to create one:

1 2 3

Actor actor =  new  Actor.Builder(SpringSystem.create(), view)    .addTranslateMotion(MotionProperty.X)    .build();

in two dimensions:

1 2 3 4

Actor actor =  new  Actor.Builder(SpringSystem.create(), view)    .addTranslateMotion(MotionProperty.X)    .addTranslateMotion(MotionProperty.Y)    .build();

Two calls to addTranslateMotion(MotionProperty) are needed because each axis is independent of the other. The builder will create an OnTouchListener and attach it to the View, as well as aSpring with the default settings. A Performer is also created and attached to the Spring. When there is a touch event, it is passed to the MotionImitator, which perturbs the spring, which moves the view.

It is also possible to supply your own SpringSystem, Spring, MotionImitator and Performer, and the builder will properly connect them. The first example above can also be expressed as:

1 2 3 4 5 6 7

SpringSystem springSystem = SpringSystem.create(); Spring spring = springSystem.createSpring();   Actor verbose =  new  Actor.Builder(springSystem, view)   .addMotion(spring,  new  MotionImitator(spring, MotionProperty.X),                       new  Performer(view, View.TRANSLATION_X)   .build();

The View can be also left out of the constructor of the Performer and the Spring out of theMotionImitator (using the default SpringConfig), since the builder will connect them.

1 2 3 4 5

Actor walk =  new  Actor.Builder(SpringSystem.create(), walker)    .addMotion(      new  MotionImitator(MotionProperty.X),      new  Performer(View.TRANSLATION_X))    .build();

which can be further simplified to

1	Actor run =  new  Actor.Builder(SpringSystem.create(), runner).addMotion(MotionProperty.X, View.TRANSLATION_X).build();

and for more sugar, the previous case:

1	Actor bolt =  new  Actor.Builder(SpringSystem.create(), bolter).addTranslateMotion(MotionProperty.X).build();

Actor Options

• requestDisallowTouchEvent() causes the Actor to callViewParent.requestDisallowTouchEvent(true) which is helpful when the view is inside aListView or another view that captures touch events.

• dontAttachMotionListener() tells the builder to not attach the MotionListener to the View, which is useful when you want to attach your own OnTouchListener to the view.

Dependencies

• rebound