| d82c8ac4db7091d2e976af4c89a1734465d20cd2 |
|
26-Aug-2013 |
Chet Haase <chet@google.com> |
Transition API changes from API council recommendations
Issue #10460684 KLP API Review: android.view.transition and android.animation
Issue #10570740 Transitions: inflate transition targets from xml
Change-Id: I7a3f6d3aece2fcafc5efd555d033f79e86635c98
/frameworks/base/tests/TransitionTests/src/com/android/transitiontests/ScenesTestAutoTransition.java
|
| 797b7559d6d8d5dc7c1903f345162751a57560f6 |
|
18-Apr-2013 |
Chet Haase <chet@google.com> |
Fix build due to transition test errors
erroneous inclusion of R file for test files is causing build breakage
on the server. Remove the offending lines.
Change-Id: I1948facc1b5e3f8b7415e0e6c4290b53a54f12af
/frameworks/base/tests/TransitionTests/src/com/android/transitiontests/ScenesTestAutoTransition.java
|
| faebd8f0795b7d275fb4e503533c8c0c4a9acc21 |
|
18-May-2012 |
Chet Haase <chet@google.com> |
First draft of Scenes & Transitions feature
This checkin has preliminary API (in flux, definitely changes still
to be made) and implementation for a new "Scenes & Transitions" feature.
The current implementation allows you to define different Scenes
(via layout resource IDs or callbacks) and Transitions to be used when
changing to those scenes. By default, scene changes will use AutoTransition,
which generally does the right thing.
There are no overview docs or tutorials yet. The best way to learn how things
work is to see the code for the various tests in
frameworks/base/tests/TransitionTests.
Expect the API to change. Expect the implementation to change (mostly to add
more functionality). Expect bugs, but tell me if things do not work
as expected.
Change-Id: Ib025a9f565678b225afa4759325cf6d496cc7215
/frameworks/base/tests/TransitionTests/src/com/android/transitiontests/ScenesTestAutoTransition.java
|