Animations are older versions of Animators . Animators, which are introduced in version 3.0, will help to overcome some of the shortcomings that are in animations.
Animations change the visual representation of an object. This is fine if you just change the opacity, but it causes problems when translating, rotating, or scaling objects. In the old days before Animators , if you moved an object, you had to re-mock it with the new coordinates. This can be quite difficult depending on where the object is moving.
Animators, on the other hand, modify the physical properties of objects. This means that if you move the view to a new location, the touch coordinates will be displayed in the new location without any other intervention.
Personally, I no longer use animation unless I develop API 2.3 or less. Fortunately, this is becoming a problem. There are also some old classes that still use the animation APIs, especially when it comes to using xml resources, such as the android.support.v4.app.FragmentTransaction class (regular FragmentTransaction supports Animators).
As a side note, the NineOldAndroids project was designed to simulate the functionality of animators, but using animations so that you can create applications that work all the way to 1.6.
DeeV Jan 29 '15 at 17:25 2015-01-29 17:25
source share