commit | 0f7da91cf17a089981e772ee3f34aed149fc8562 | [log] [tgz] |
---|---|---|
author | Yohei Yukawa <[email protected]> | Thu May 23 05:47:57 2019 +0800 |
committer | Yohei Yukawa <[email protected]> | Thu May 23 05:47:57 2019 +0800 |
tree | bef2ba3f0015f4f50dc6c062a90246b9fcb906dd | |
parent | b8e5e14d9d5ce939f9bffc04f59360cf57a26469 [diff] |
Make image keyboard API backport compatible to all previous impls This is a follow up CL to our recent attempt [1] to work around an unintentional protocol breakage in image keyboard API on API<25 that was accidentally introduced in AndroidX 1.0.0 [2]. Basically there are three versions of image keyboard API backports. - legacy support lib - AndroidX 1.0.0 - upcoming Android X 1.1.0 As a result, there are 9 cases to consider depending on which version is used in the app and which version is used by the IME. With this CL, Android X 1.1.0 version becomes compatible to all the versions above. This should make our life much easier, because regardless of whether it's an app or IME, apps/IMEs becomes compatible with other IMEs/apps that were built with whatever version of libraries above just by upgrading to AndroidX 1.1.0. Note that there is no behavior change for API 25+ devices, where the platform API is always used. [1]: I42a4a1a215a00d42fca62bec31e52b0947d1de74 08a73da29759682576450ea7c31ad49722265f2c [2]: I11a047324832801555673dac45ec1d6590a6338b b31c3281d870e9abb673db239234d580dcc4feff Bug: 129349688 Test: unittest Change-Id: I6cc9498151a09c4f62435e4dd07def63c223e140
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.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
Install 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
Configure Git with your real name and email address.
git config --global user.name “Your Name” git config --global user.email “[email protected]”
Create a directory for your checkout (it can be any name)
mkdir androidx-master-dev cd androidx-master-dev
Use repo
command to initialize the repository.
repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev
Now your repository is set to pull only what you need for building and running AndroidX libraries. Download the code (and grab a coffee while we pull down 6GB):
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 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 in your project build.gradle
file:
handler.maven { url '/path/to/checkout/out/support/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-4v-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.