commit | c471ce0a2df701fd55f3f3b93520e95fee521a0e | [log] [tgz] |
---|---|---|
author | Paul Rohde <codelogic@google.com> | Sat Aug 20 21:11:32 2022 -0700 |
committer | Paul Rohde <codelogic@google.com> | Sun Sep 18 14:00:44 2022 -0700 |
tree | 5e3d4ead23940d87d18cf3c3198f72e90fd4df50 | |
parent | 8b876a04a8b04bb73d68429576debc84ddbddd47 [diff] |
Deprecate CameraPipe.External This change begins the deprecation process for CameraPipe.External by creating a method that allows a developer to create a CameraGraph instance by providing a fully specified CameraBackend as part of the CameraGraph.Config object. There are two main benefits from this: 1. Both internal/external CameraGraphs are initialized using the same set of objects and classes, allowing caches to be reused. 2. More classes can be reused when creating a CameraGraph, which reduces code size, and reduces the risk a developer changes the behavior of a CameraGraph. The two main public interfaces this change introduces are the CaptureSequence and CaptureSequenceProcessor, which replaces the former RequestProcessor interface. The primary intent of this change is to allow more logic to be reused between building and submitting requests to the underlying camera. This change also has a large number of secondary improvements that ended up being required as part of refactoring the core APIs. These include: * Replacing runBlocking and runBlockingTest with runTest in tests. * Adding testOnlyDispatcher and testOnlyScope to the threads module. * Enforcing that several tests use dispatchers based on runTest * Replacing several test usages of GlobalScope with runTest and launch Test: ./gradlew --strict\ :camera:camera-camera2-pipe:testDebugUnitTest\ :camera:camera-camera2-pipe-testing:testDebugUnitTest\ :camera:camera-camera2-pipe-integration:testDebugUnitTest Change-Id: I2776f045312b04522e45e0faa971944988d5da29
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.