commit | bc058ca6c9625bbd3c85bd2da7bbb11376ab6760 | [log] [tgz] |
---|---|---|
author | Nader Jawad <njawad@google.com> | Wed Sep 16 21:32:49 2020 -0700 |
committer | Nader Jawad <njawad@google.com> | Tue Sep 22 13:46:14 2020 -0700 |
tree | 064c63371f07efec914e81b9c164e4d78de2befc | |
parent | 955e695895fa50520d3326fa832716be20594bf2 [diff] |
Address API council feedback on compose graphics APIs Relnote: "--Updated scale and rotation transformation APIs to consume a single Offset parameter to represent the pivot coordinate instead of separate float parameters for the x/y coordinates in DrawScope and DrawTransform --Removed Rect.expandToInclude and Rect.join methods --Updated Radius documentation to say oval in addition to elliptical --Added documentation to indicate the public constructor for the inline Radius class is not to be called directly but instead Radius objects should be instantiated through their function constructors --Removed RoundRect APIs to query topRight, bottomRight, bottomCenter, etc. --Deprecated Rect.shift in favor of Rect.translate --Removed RoundRect.grow and Rect.shrink APIs --Renamed RoundRect.outerRect to Rect.boundingRect --Removed RoundRect.middleRect/tallMiddleRect/wideMiddleRect and Rect.isStadium methods --Renamed RoundRect.longestSide to RoundRect.maxDimension --Renamed RoundRect.shortestSide to RoundRect.minDimension --Changed RoundRect.center to be a property instead of a function --Updated RoundRect constructor to consume Radius properties instead of individual parameters for x/y radius values --Removed Size APIs that assumed it was a Rectangle with origin at 0,0 --Added a destructing API to Radius --Migrated various RoundRect extension functions to be properties instead" Bug: 168762961 Test: re-ran compose tests and added unit tests to newly added APIs Change-Id: I8f5c738d1629b2cabd1b6e9fc8e8241dd06cfe2c
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 Paging, Room and WorkManager are being accepted at this time.
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
repo
(Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)mkdir ~/bin PATH=~/bin:$PATH curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
git config --global user.name "Your Name" git config --global user.email "you@example.com"
mkdir androidx-master-dev cd androidx-master-dev
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev --partial-clone
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ./studiow
and accept the license agreement when prompted. Now you're ready to edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
You can build maven artifacts locally, and test them directly in your app:
./gradlew createArchive
And put the following at the top of your ‘repositories’ property in your project build.gradle
file:
maven { url '/path/to/checkout/out/androidx/build/support_repo/' }
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.
Run FooBarTest
Run androidx.foobar
The AndroidX repository has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named either <libraryname>-integration-tests-testapp
, or support-\*-demos
(e.g. support-v4-demos
or support-leanback-demos
). You can run them by clicking Run > Run ...
and choosing the desired application.
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
cd path/to/checkout/frameworks/support/ repo start my_branch_name . # make needed modifications... git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?
If the upload succeeds, you'll see output like:
remote: remote: New Changes: remote: https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates remote:
To edit your change, use git commit --amend
, and re-upload.
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.