commit | c5f36c050e6ec86e8a504031b3cd7602a11f4d9e | [log] [tgz] |
---|---|---|
author | Doris Liu <tianliu@google.com> | Tue Nov 14 18:28:39 2023 -0800 |
committer | Doris Liu <tianliu@google.com> | Wed Apr 03 19:54:51 2024 -0700 |
tree | e6a9a72918b6f68991c159d1650958448b44053f | |
parent | 91bc21ab760bef37b10cbacd513d6ac7217d2336 [diff] |
Introduce Shared Element Transition Supported: - Shared content key match, bounds animation - Derived "visible" state based on AnimatedVisibilityScope - Rendering in overlay during transition by default - All animations are added to a (child) transition of AnimatedVisiblityScope (if provided) for future seeking - Bounds animations can be customized via BoundsTransform - Distinct mental model for different use cases: sharedElement vs. sharedBounds - Error case handling: - When there are > 1 targetBounds Providers, use the last added provider for bounds - When there are 0 targetBounds provider, no bounds animation, to fail fast. - zIndex customization is now supported in overlay - Clip to shape or clip based on other shared elements' bounds - Skip to lookahead layout for layouts that prefers no reflow - renderInOverlay modifier to render non-shared content in overlay to preserve z-order relative to shared elements/bounds RelNote: " New experimentals shared element and shared bounds features await your usage and feedback. These new APIs enable tagging layouts as shared across layout tree using the provided modifiers, producing smoothly changing bounds when one set of shared content exits and the other set enters. " Test: New tests added Change-Id: Icb0b953f1eaff80a582b1edd3f21f9f8031cf8b0
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.