commit | fe769c76643ee7c93767f8e245d0eff6067b7866 | [log] [tgz] |
---|---|---|
author | Nick Ning <nickning@google.com> | Fri May 20 21:04:09 2022 +0000 |
committer | Nick Ning <nickning@google.com> | Tue Jun 21 15:34:19 2022 +0000 |
tree | 0942b337a71a1c6897ee6d4d2bb6c99811519ce7 | |
parent | 242e961f72d786eef45dd9712b86afece34a7a65 [diff] |
List Template: Add 4 list styles in demo with support to the Collapsed views. Implement the following features in for List Demo and List Template: 1. Added 4 List Styles by UX design in demo using List Template. 1). The Full Action style shows full list with header, header action button, and spacer between items. 2). The No Action style is the Full Action style without action button in the header. 3). The No Header style is the No Action style with no header and no list item front icon. 4). The Brief style is the No Header style with no list item label and no spacer between list items. All styles are using the same data set and list template. 2. Added the Collapsed View template viewable for each List Style when shrinking the list view. The optional header icon button is set to add an item as an example. The Expanded View inherits the same helper button which allows the removal of the "Add item" button in the List template. 3. Only the first items text is shown without the item icon and action button in the Collapsed view template. 4. The ListTemplateData's button is changed to the more general TemplateButton instead of the TemplateTextButton to allow image button to be used. List and List Item Glance Modifiers are added to API data enable more list view control such as spacer fine tuning. 5. Since the List remains the same for both Horizontal and Vertical views in design, they are combined for TemplateMode cases. 6. List "title" is not used in UX design and is removed in the demo. Can use Header text for its purpose. However it is still supported in List Template. Bug: 232938142 Test: List Template Demo integration test Relnote: Add List Template support to list styles and collapsed view. Change-Id: I50cdc75d8f72916fafa327fc85851f97b1856633
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.