7b59d3ae599949c7c6b4c5806b4dda7f41147690 |
|
13-Jun-2016 |
Alan Viverette <alanv@google.com> |
Remove old API check artifacts, invoke gradle from old make target Fixes paths in build.gradle so they are relative to the project root, rather than the current directory. Bug: 28124434 Change-Id: Ieeae97cd789a6addf3282f2c43cd754ca8e84c57
/frameworks/support/graphics/drawable/Android.mk
|
3c141cd9c1cfecd9352b82d9dae4d9601fabd4e6 |
|
11-Jun-2016 |
Yigit Boyar <yboyar@google.com> |
Revert "Remove old API check artifacts, invoke gradle from old make target" This reverts commit 009647bbfa5efef608d6a660fc8ba191d876b1ed. Change-Id: I59deae2a7180f58bc0c770f7b3f70962c8d2f73f
/frameworks/support/graphics/drawable/Android.mk
|
009647bbfa5efef608d6a660fc8ba191d876b1ed |
|
09-Jun-2016 |
Alan Viverette <alanv@google.com> |
Remove old API check artifacts, invoke gradle from old make target Fixes paths in build.gradle so they are relative to the project root, rather than the current directory. Bug: 28124434 Change-Id: I8cde9db47d60ec1220d35fce5ef6fd2c6e97b1f8
/frameworks/support/graphics/drawable/Android.mk
|
55fc3f2df63118f3d4daea6df5b5eb531dcf194f |
|
12-May-2016 |
Kirill Grouchnikov <kirillg@google.com> |
Internal cleanup * Make more targeted dependencies where we can * Remove build targets for folders that are no longer there Change-Id: I3477e7d2b06e6095badfed18f4977d26757ba3ea
/frameworks/support/graphics/drawable/Android.mk
|
c5e344c7edd7ad47c85bdf2aa9e987aa0e333e90 |
|
25-Feb-2016 |
Neil Fuller <nfuller@google.com> |
Pin support libraries to Java 1.7 so they can be used with dx am: e1cd5a1f80 am: d8d2289aef * commit 'd8d2289aefdb5b7d9878ac37613495889fb5c3fe': Pin support libraries to Java 1.7 so they can be used with dx
|
e1cd5a1f80010eece43cb4608505fd39f4832c00 |
|
25-Feb-2016 |
Neil Fuller <nfuller@google.com> |
Pin support libraries to Java 1.7 so they can be used with dx The .jar artifacts must contain v51 class files to prevent them being rejected by dx. Bug: 26753820 Bug: 27353172 Bug: 27338966 Change-Id: I03a881a86bb6e3fcaa4ccb33e6c0615157ee363f
/frameworks/support/graphics/drawable/Android.mk
|
4a6f901cf69381fb43ca3e087f75f4354acd5d6d |
|
12-Feb-2016 |
Narayan Kamath <narayan@google.com> |
drawable: Fix api-check rule. am: a1be71b3d5 am: 3c3153fe9b * commit '3c3153fe9bb1c31449da297d3ed559dd3aa7f802': drawable: Fix api-check rule.
|
a1be71b3d588b717c0af2da84353c8a2404e7474 |
|
12-Feb-2016 |
Narayan Kamath <narayan@google.com> |
drawable: Fix api-check rule. Include sources for the packages we're being asked to generate stubs for. Change-Id: I55a6c52448f7cee212fd10ff2b20cab2a5440cbe
/frameworks/support/graphics/drawable/Android.mk
|
e02f970b1da3c1853891ab5dafbd478e0a3834a8 |
|
12-Feb-2016 |
Tenghui Zhu <ztenghui@google.com> |
Merge "Fix mystery method arraycopy not found issue for VDC DO NOT MERGE" into mnc-ub-dev
|
d6b323993b900899f3c4204e14b27e168dcf2954 |
|
10-Feb-2016 |
Chris Banes <chrisbanes@google.com> |
Add API generation to VDC + AVDC BUG: 27128213 Change-Id: I307a22b1b7c1a1b3f8390d3642c21ac9ad643dc1
/frameworks/support/graphics/drawable/Android.mk
|
13ea98c1e78cddd0edfb4ecd002fc56868a2b979 |
|
04-Feb-2016 |
Teng-Hui Zhu <ztenghui@google.com> |
Fix mystery method arraycopy not found issue for VDC DO NOT MERGE b/26959365 Change-Id: Id16f185543521e8f9989de37cc7b02c6f2196188
/frameworks/support/graphics/drawable/Android.mk
|
c12dc3d83c1ef7be0f4d4fd7a5a1dbce68138820 |
|
22-Jan-2016 |
Chris Banes <chrisbanes@google.com> |
Update support lib to use correct current SDK DO NOT MERGE BUG: 26714403 Change-Id: I2153dbda365f4552a14df1f432239bddfbbbef00
/frameworks/support/graphics/drawable/Android.mk
|
e4beadba70aecabbd7f6677943ab7c0b94809b8a |
|
10-Nov-2015 |
Chris Banes <chrisbanes@google.com> |
AppCompat + VectorDrawableCompat AppCompat now depends on VectorDrawableCompat and makes use of it for certain drawables (radio button, checkmark, back, etc). We make use of the few extension points in the Drawable loading system to make this possible. Most drawable loading happens in Resources.loadDrawable() which can't be overriden. On API 19 and below though, most DrawableContainers load their child drawables through Resources.getDrawable(), which we can hook into. This means that a <vector> resource file can be loaded as long as it is wrapped in a seperate DrawableContainer (Inset, StateList, etc). For the times that wrapping the drawable isn't an option, we now also have a app:srcCompat attribution on ImageView and ImageButton. AppCompat statically compiles in VDC into the Make build artifacts. This is to aid migration. Gradle is unaffected. Change-Id: If2ab63e561354fe290e5df47e7560533725175fc
/frameworks/support/graphics/drawable/Android.mk
|
1f8664abb6cdd6962d58433e06dd9cc7ea856782 |
|
12-Dec-2015 |
Teng-Hui Zhu <ztenghui@google.com> |
Setup new lib name for Android.mk file, update the scaling computation b/22564270 Change-Id: I89f8d6d19d0dd074175d0d10490bb65bd04d6bb0
/frameworks/support/graphics/drawable/Android.mk
|
2c3c8bff4c669316cdc2db24b72d9ac3f9b33725 |
|
05-Dec-2015 |
Teng-Hui Zhu <ztenghui@google.com> |
Add Gradle support and tests in VDC and AVDC Fix some bugs which are fixed in MNC and ported here too. b/22564270 Change-Id: I9e5b195134d6ce759d9cc74f6072f6f105b0ce2f
/frameworks/support/graphics/drawable/Android.mk
|
c0a76bda6919fe6d713d6ff1ff102b408ace0946 |
|
02-Dec-2015 |
Teng-Hui Zhu <ztenghui@google.com> |
Remove unnecessary resource file attrs.xml Change-Id: Ia690a0ca0907b0684bd949d00b4be0f0e81fd393
/frameworks/support/graphics/drawable/Android.mk
|
ee43f2be553d068b570afc1ec03703cf17be70cc |
|
01-Dec-2015 |
Teng-Hui Zhu <ztenghui@google.com> |
Fix local mk build Change-Id: I4a8f5f7c8e255d47f95c54d5f129a67a7890bc56
/frameworks/support/graphics/drawable/Android.mk
|
d85f3e0b931d3e127242a375e0d00c4696bba912 |
|
10-Nov-2015 |
Teng-Hui Zhu <ztenghui@google.com> |
Use android namespace in (Animated)VectorDrawableCompat. To workaround the possible resource id confliction issue, check the attribute existence before TypedArray get its value. A little perfomance cost on inflation time here, but that is the only way to protect us from the id confliction. Add some more manual tests, covering references too. https://b.corp.google.com/issues/22564270 Change-Id: Iee5f559372c553ed1d936404f86c7195ca657a1c
/frameworks/support/graphics/drawable/Android.mk
|
4fcaa70c2362e58a3fb30d140f0a0eeda8e35b44 |
|
04-Mar-2015 |
ztenghui <ztenghui@google.com> |
Add the support lib for VD and AVD By using auto namespace, we have all the functionality we want for support lib of VD and AVD. All the java files in the support lib are based upon the framework ones, with slight modification. The test cases are also from framework test, with namespace changed. Note that the animator part are still using android namespace since they are supported in v11. TODO: 1 integrate the AAPT support to use android namespace. 2 find the best way to integrate the framework VD AVD for L+. b/19200714 Change-Id: I10a80a89d26237ea780368e19929d83cd7678fff
/frameworks/support/graphics/drawable/Android.mk
|