| commit | e9095137fe875403ec911f6469b996658250322a | [log] [tgz] |
|---|---|---|
| author | Leland Richardson <lelandr@google.com> | Fri May 27 00:28:02 2022 +0100 |
| committer | Leland Richardson <lelandr@google.com> | Wed Aug 10 22:17:27 2022 -0700 |
| tree | 2f62bbb1ce12cb474fb5d7996b613e9662c8c708 | |
| parent | 5fe17d04b4e3159e0fb58ad26b4171145fff9e9b [diff] |
Introduce Modifier.Node APIs, refactor Modifier/Wrapper/Entity strategy Bug: 239955664 Test: Added tests, and also most existing tests exercise this code Relnote:“”” The layer which handles Modifier/Modifier.Element instances and coordinates their behavior on LayoutNodes has been majorly refactored. As it stands this was a refactor which did not affect the public API of any of the many modifiers in Compose, and can be viewed as an implementation-only change. Despite that, this is an important change for various reasons. Change Summary === The added experimental Modifier.Node APIs provide an abstraction that allows for state to be maintained on an instance that will be retained with the lifecycle of the layout node, and will be allocated per-layout-node and per-usage of the corresponding Modifier.Element that produced it. Broadly speaking, this abstraction provides an alternative mechanism to produce stateful modifiers without relying on the mechanics of the Modifier.composed API. Risk === This change is strictly binary compatible with prior releases, and is intended to be backwards compatible in terms of observable behavior as much as practical and reasonable. That said, there are few subsystems of compose this refactor did not touch, and *it is likely that behavior has changed in ways that were not covered by our tests and have not yet been found and fixed*. Please upgrade to this release with caution. If you believe this has broken something for you, please let us know. Experimental APIs === Various experimental APIs have been added, all relating to the new concept of a “Modifier Node”. Modifier.Node’s are created as a result of fun modifierElementOf(…): Modifier abstract class ModifierNodeElement abstract class Modifier.Node abstract class DelegatingNode interface LayoutModifierNode interface DrawModifierNode interface SemanticsNode interface PointerInputNode interface ModifierLocalNode interface ParentDataModifierNode interface LayoutAwareModifierNode interface GlobalPositionAwareModifierNode interface IntermediateLayoutModifierNode “”” Change-Id: Ie4313071d4d9ebc82b28b6fbb691d3736d7d738a
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(), jcenter(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.