Google Git
Sign in
android / platform / frameworks / support / ab397bf8fd78414add8efe9d0dbc4ee36add4c2e
commitab397bf8fd78414add8efe9d0dbc4ee36add4c2e[log] [tgz]
authorPavel Shmakov <[email protected]>Thu May 09 14:37:59 2019 +0100
committerPavel Shmakov <[email protected]>Wed May 15 14:58:16 2019 +0100
tree1e8963395c95dac4679b90fc31a485414c1319bb
parentae53edb44c2c54552bce94f51fcff2e10bfb0f75 [diff]
Add setColorSchemeParams method for Custom Tabs.

The new method allows to specify visual parameters of Custom Tabs
for each color scheme. When Custom Tab is configured to automatically
follow system settings, it will be able to apply the correct set
of parameters while running.

The parameters are grouped into CustomTabColorSchemeParams object.
Currently there are only two: toolbar color and secondary toolbar
color, but there will be more coming.

More details:

https://docs.google.com/document/d/13m00cZlZ-d-L8prIZ4sy9sZIND1SAicz3m9FXTsxY4Y/edit#

Test: added tests to CustomTabIntentTest.

Change-Id: Ie2727d14a489cf3d2e955494bbd439b2c31ad4b1
9 files changed
tree: 1e8963395c95dac4679b90fc31a485414c1319bb
  1. .idea/
  2. activity/
  3. animation/
  4. annotations/
  5. api/
  6. appcompat/
  7. arch/
  8. asynclayoutinflater/
  9. benchmark/
  10. biometric/
  11. browser/
  12. buildSrc/
  13. camera/
  14. car/
  15. cardview/
  16. collection/
  17. compose/
  18. concurrent/
  19. content/
  20. coordinatorlayout/
  21. core/
  22. cursoradapter/
  23. customview/
  24. development/
  25. docs-fake/
  26. docs-runner/
  27. documentfile/
  28. drawerlayout/
  29. dumb-tests/
  30. dynamic-animation/
  31. emoji/
  32. enterprise/
  33. exifinterface/
  34. fragment/
  35. frameworks/
  36. gradle/
  37. graphics/
  38. gridlayout/
  39. heifwriter/
  40. interpolator/
  41. jetifier/
  42. leanback/
  43. leanback-preference/
  44. legacy/
  45. lifecycle/
  46. loader/
  47. localbroadcastmanager/
  48. media/
  49. media2/
  50. mediarouter/
  51. navigation/
  52. paging/
  53. palette/
  54. percent/
  55. persistence/
  56. preference/
  57. print/
  58. recommendation/
  59. recyclerview/
  60. remotecallback/
  61. room/
  62. samples/
  63. savedstate/
  64. scripts/
  65. security/
  66. sharetarget/
  67. slices/
  68. slidingpanelayout/
  69. swiperefreshlayout/
  70. testutils/
  71. testutils-ktx/
  72. textclassifier/
  73. transition/
  74. tv-provider/
  75. ui/
  76. versionedparcelable/
  77. viewpager/
  78. viewpager2/
  79. wear/
  80. webkit/
  81. work/
  82. .gitignore
  83. build.gradle
  84. cleanBuild.sh
  85. gradle.properties
  86. gradlew
  87. include-composite-deps.gradle
  88. include-support-library.gradle
  89. LICENSE.txt
  90. OWNERS
  91. PREUPLOAD.cfg
  92. README.md
  93. settings.gradle
  94. studiow
README.md

AOSP AndroidX Contribution Guide

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.

Follow the “Downloading the Source” guide to install and set up repo tool, but instead of running the listed repo commands to initialize the repository, run the folowing:

repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev

The first time you initialize the repository, it will ask for user name and email.

Now your repository is set to pull only what you need for building and running AndroidX libraries. Download the code (and grab a coffee while we pull down 3GB):

repo sync -j8 -c

You will use this command to sync your checkout in the future - it’s similar to git fetch

Using Android Studio

To open the project with the specific version of Android Studio recommended for developing:

cd path/to/checkout/frameworks/support/
./studiow

and accept the license agreement when prompted. Now you're ready edit, run, and test!

If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.

If you see any warnings (red underlines) run Build > Clean Project.

Builds

Full Build (Optional)

You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:

cd path/to/checkout/frameworks/support/
./gradlew createArchive

Testing modified AndroidX Libraries to in your App

You can build maven artifacts locally, and test them directly in your app:

./gradlew createArchive

And put in your project build.gradle file:

handler.maven { url '/path/to/checkout/out/support/build/support_repo/' }

Running Tests

Single Test Class or Method

  1. Open the desired test file in Android Studio.
  2. Right-click on a test class or @Test method name and select Run FooBarTest

Full Test Package

  1. In the project side panel open the desired module.
  2. Find the directory with the tests
  3. Right-click on the directory and select Run androidx.foobar

Running Sample Apps

The AndroidX repository has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.

These applications are named either <libraryname>-integration-tests-testapp, or support-\*-demos (e.g. support-4v-demos or support-leanback-demos). You can run them by clicking Run > Run ... and choosing the desired application.

Password and Contributor Agreement before making a change

Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:

Generate a HTTPS password: https://android-review.googlesource.com/new-password

Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement

Making a change

cd path/to/checkout/frameworks/support/
repo start my_branch_name .
(make needed modifications)
git commit -a
repo upload --current-branch .

If you see the following prompt, choose always:

Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?

If the upload succeeds, you'll see output like:

remote:
remote: New Changes:
remote:   https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates
remote:

To edit your change, use git commit --amend, and re-upload.

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), jcenter(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.