| commit | fe1c0879d8a72e11a6d2d6662c6c69d64c18fd56 | [log] [tgz] |
|---|---|---|
| author | Doris Liu <[email protected]> | Tue Jun 14 10:58:23 2022 -0700 |
| committer | Doris Liu <[email protected]> | Tue Mar 07 07:53:10 2023 -0800 |
| tree | e571c8d4d26982a925adc07e83a7d874ba309a93 | |
| parent | 965684cb54b60ae2177081628c8d17437e7db98c [diff] |
Lookahead API improvements
This CL introduces a new LookaheadScope that replaces LookaheadLayout and
allows the LookaheadScope to be created without needing an
additional Layout. This enables children of LookaheadScope to
be directly managed by the parent's measure/layout logic.
The new LookaheadScope also supports query of scope coordinates during
placement, as well as conversion from LayoutCoordinates to
LookaheadCoordinates.
The IntermediateLayoutModifier is now a LayoutModifierNode that has both
measure and intermediateMeasure implementation for the lookahead pass
and main pass respectively.
Modifier.intermediateLayout no longer requires a LookaheadScope, it will
instead implicitly create a LookaheadScope if it's not already in
a LookaheadScope.
New IntermediateMeasureScope that conveniently provides LookaheadScope,
CoroutineScope and MeasureScope to the measure logic in intermediateLayout.
Future work:
1) An API will be needed for devs to express whether the intermediate
changes have finished. The implementation for wiring that up to snap to
lookahead is already in place.
2) Ideally, the intermediateLayout modifier API should not require the
use of composed {}.
In an effort to reduce churns for developers, both 1) an 2) are deferred
till Modifier.Node Delegate design is finished.
Relnote: "
- Modifier.intermediateLayout now doesn't require an explicit LookaheadScope.
The measure block in intermediateLayout has IntermediateMeasureScope as
receiver, which provides convenient CoroutineScope, LookaheadScope and
MeasureScope.
- LookaheadLayout has been replaced by LookaheadScope, which is no longer
a Layout. This allows chid content in a LookaheadScope to be directly
controlled by parent's MeasurePolicy.
"
Test: Included
Change-Id: Ibe2e5e20a833d3824213e86e5c1e155f65647ad7
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.
