| commit | d4144e400de1e2492b2a91513dc90fc5938199d1 | [log] [tgz] |
|---|---|---|
| author | Ankit <[email protected]> | Tue Dec 12 17:54:04 2023 +0000 |
| committer | Ankit <[email protected]> | Tue Jan 02 11:18:20 2024 +0000 |
| tree | fe6dc5ae13d0819f5a9bd6c6a28f767f6cae7125 | |
| parent | 7a24f4b653437faeec714b7d7f8c2eee006156ae [diff] |
Update ColorScheme to be Immutable Based on the recommendation from API council, making the ColorScheme immutable. This makes it more preformant on the general usage of the scheme faster while making the individual color updates slower which is uncommon. Related CL: https://android-review.googlesource.com/c/platform/frameworks/support/+/2733678 Also added a ColorSchemeBenchmark to measure the overall change in timings and allocations for such changes. Here are the numbers extracted from running the benchmark with and without the change. Before the change * Timing: ~2.8 ms (Avg of two runs) * Allocations: 1467 allocations After the change * Timing: ~2.6ms (Avg of two runs) * Allocations: 1299 allocations Based on the above results, we imporved nearly by 0.2 ms for the initialization of the ColorScheme object and also reduced the overall allocations that were being made for it. Bug: 300090055 Relnote: """ ColorScheme is now Immutable, making individual color updates less efficient, but making more common usage of colors more efficient. The reasoning behind this change is that the majority of apps wouldn't have updating individual colors as a main use case. This is still possible but it will recompose more than before, in turn we significantly decrease the amount of state subscriptions through all of material code and will impact initialization and runtime cost of more standard use cases. """ Test: Existing tests Change-Id: Ibc2d6d36f4bdd817c06f686cd1e3c210c2544b82
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
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
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(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.
