| 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/v7/palette/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/v7/palette/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/v7/palette/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/v7/palette/Android.mk
|
| df153998b2e93117ec6fd9b799130a4fd7cc5960 |
|
04-May-2016 |
Kirill Grouchnikov <kirillg@google.com> |
Bump minSdk to 9 everywhere where it was < 9
Change-Id: Icebaa867824aa8eeda44206155670d5e390d35b3
/frameworks/support/v7/palette/Android.mk
|
| 6759b1021d8198ad1d239bb30e5a102b99624bce |
|
25-Feb-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build support libs with AAPT2
Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.
Ex:
LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4
Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.
This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.
We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.
Bug:25958912
Change-Id: I6577a91e4d428dd29fecaa86a26be43d4da8310c
/frameworks/support/v7/palette/Android.mk
|
| 57f39186667b8acef1a0ebeda585c357a751a8b3 |
|
02-Apr-2016 |
Adam Lesinski <adamlesinski@google.com> |
Revert "Build support libs with AAPT2"
This reverts commit 66b8608151c5923de3c9877bc03218d83f6b3beb.
Change-Id: I2178c0336bef8386e1f36ff3816b6dbf1e6a64d0
/frameworks/support/v7/palette/Android.mk
|
| 66b8608151c5923de3c9877bc03218d83f6b3beb |
|
25-Feb-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build support libs with AAPT2
Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.
Ex:
LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4
Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.
This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.
We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.
Bug:25958912
Change-Id: I5235b73ac68f2050d089aefc3163901ff80f2d46
/frameworks/support/v7/palette/Android.mk
|
| 4ac91fa3f14db2f25345595fb921497c11d4e5c0 |
|
31-Mar-2016 |
Adam Lesinski <adamlesinski@google.com> |
Revert "Build support libs with AAPT2"
This reverts commit 0dac8d82e2a249d7c9c42ab259389e11cac15400.
Change-Id: I830fb18162b6eea8dde9e38f9dc39b02449ec846
/frameworks/support/v7/palette/Android.mk
|
| 0dac8d82e2a249d7c9c42ab259389e11cac15400 |
|
25-Feb-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build support libs with AAPT2
Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.
Ex:
LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4
Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.
This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.
We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.
Bug:25958912
Change-Id: I71bff080ff2694aa3df1c8a67d933e2daab0f245
/frameworks/support/v7/palette/Android.mk
|
| 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/v7/palette/Android.mk
|
| f62fcdec92e2f96ec61579392ed2b593cff35b39 |
|
25-Feb-2015 |
Chris Banes <chrisbanes@google.com> |
Generate API files for the support libraries
make update-support-api
make check-support-api (run automatically on sdk builds)
BUG: 19478450
Change-Id: Idd0f12c457b7dc084a66158de452969d7afdb8dc
/frameworks/support/v7/palette/Android.mk
|
| f78a300c82748e29a3890c8f17a13726aacf33be |
|
22-Feb-2015 |
Chris Banes <chrisbanes@google.com> |
Add tests to Palette
Also changed the directory structure to enable
the tests to have their own resources.
Requires I7776f4d843aac8496240a54d0982525039b91469
Change-Id: I7bb98622995f009fc6e6c44e3a21aa88a151749a
/frameworks/support/v7/palette/Android.mk
|
| c6cdc41397bc3ad2c936069af6d448f242790513 |
|
01-Jul-2014 |
Chris Banes <chrisbanes@google.com> |
Update Palette + AsyncTaskCompat
- Added AsyncTaskCompat to v4
- Moved PaletteItem into Swatch inner class of Palette
- Removed unnecessary copying of pixel int[] data
- Use THREAD_POOL_EXECUTOR for AsyncTask
- Various other improvements
Change-Id: I06f1efefcdfa3d22578653b5f5da3d61a064b5d5
/frameworks/support/v7/palette/Android.mk
|
| 51ea7c98b34f39a2da711549a0a443c77f2c94b0 |
|
03-Jul-2014 |
Narayan Kamath <narayan@google.com> |
Revert "Update Palette + AsyncTaskCompat"
This reverts commit b14fc7c928307b6758688ed38590bf674c62a01b.
Change-Id: I57a2cee10f4084e921bc9204784c6fffce56b80b
/frameworks/support/v7/palette/Android.mk
|
| b14fc7c928307b6758688ed38590bf674c62a01b |
|
01-Jul-2014 |
Chris Banes <chrisbanes@google.com> |
Update Palette + AsyncTaskCompat
- Added AsyncTaskCompat to v4
- Moved PaletteItem into Swatch inner class of Palette
- Removed unnecessary copying of pixel int[] data
- Use THREAD_POOL_EXECUTOR for AsyncTask
- Various other improvements
Change-Id: I66ada4bd2d4cec48b87acce50fb0fd6952473c25
/frameworks/support/v7/palette/Android.mk
|
| 059178a8c7cc80848e5594a9287be91bd924831a |
|
19-May-2014 |
Chris Banes <chrisbanes@google.com> |
New Palette support library
Allows the generation of color palette from an Android
Bitmap. Items from the palette can then be used to
enhance the UI.
On my Nexus 5, a Palette instance take 10-20ms to
generate.
Change-Id: I8e16c2c9027c260a1f0ff353affa930cfa2f2c95
/frameworks/support/v7/palette/Android.mk
|