| commit | 24a94850017dc5a03f119ec491d1beaf49772a2a | [log] [tgz] |
|---|---|---|
| author | Jakub Gielzak <[email protected]> | Wed Apr 27 15:13:59 2022 +0100 |
| committer | Jakub Gielzak <[email protected]> | Wed May 04 16:39:59 2022 +0000 |
| tree | 8adb356ac30fed16021ac5da40bb22a6b6af1fcb | |
| parent | a451505922cef7fbc7421247d5e2df661c328d1e [diff] |
New library compose:runtime:runtime-tracing When added as a dependency to a Compose application, enables recomposition tracing: - declares a dependency on tracing-perfetto - registers tracing-perfetto with Compose Remaining steps to trace have to be performed by tooling (e.g. Android Studio Profiler): - provide tracing-perfetto-binary dependencies required for tracing - notify the app to register with Perfetto SDK (using androidx.tracing.perfetto.TracingReceiver) - include track_event as a category in its Perfetto capture config - capture and present a Perfetto trace End-to-end test covered by TracingInitializerTest where Macrobenchmark performs the steps described in the previous paragraph. Bug: 214560409 Bug: 214560414 Bug: 214562374 Test: ./gradlew :compose:runtime:runtime-tracing:connectedCheck -Pandroid.testInstrumentationRunnerArguments.class=androidx.compose.runtime.tracing.test.TracingInitializerTest Test: ./gradlew :compose:integration-tests:macrobenchmark-target:installRelease && ./gradlew :compose:integration-tests:macrobenchmark:connectedCheck -Pandroid.testInstrumentationRunnerArguments.class=androidx.compose.integration.macrobenchmark.TrivialTracingBenchmark Change-Id: Id1ea30fdea39da8d63b8c0963d9e8e351704985b
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.
