Gallery Template 6: Added more documentation for API changes.

Addressed API review questions:

1. Is priority used when there’s not enough space to fit everything? Or for ordering?

Priority is a number assigned to blocks to show the semantic importance of each block in a sequence. Different templates will interpret priority in different ways. Some may treat this as an ordering, some may only use it to define which elements are most important when showing smaller layouts.

2. What happens if two entities have equal priority and only one of them fits?

If two blocks has the same priority number, the default order (e.g. text before image) is used.

3. Does a larger priority value mean higher priority? Why is 0 the highest?

Priority number is zero based with smaller numbers being higher priority.

4. Why do not all blocks have a priority?

This is the current scope by design. We may include it in more block types should ordering be a designed feature.

5. AspectRatio: What about images that don’t fit those ratios, should this be customizable?

Images not in the selected ratio are cropped for display by design. Added more doc in CL. UX design might introduce more customization features on this later.

6. ImageSize: Can you provide more context as to what the “relative” means in the javadoc? Relative to what?

The image size describes image scale category in sizing. Actual size is implementation dependent. Removed the confusing notion of "relative". Added more doc in CL.

7. TextBlock: Why 3 text items? Could this take a List<TemplateText> instead?

Current limit of 3 text items is intentional by design to avoid unintentional clogging limited screen space, forcing users to pick three most important types of information to display.

8. TextBlock: Should we prevent text3 from being non-null if text2 is? Or is that an ok situation?

It is an ok situation that the code can handle to display only the non-null items.

Bug: 242826378
Bug: 214598261
Test: Integration Test Demo
Relnote: Add proiority number range for TextBlock and ImageBlock.
Change-Id: I73100492fedc879ea75b507b9fe302079baa4ef6
4 files changed
tree: 63e57ab746a9849e36010e7de9f981154bd02186
  1. .github/
  2. .idea/
  3. activity/
  4. ads/
  5. annotation/
  6. appcompat/
  7. appsearch/
  8. arch/
  9. asynclayoutinflater/
  10. autofill/
  11. benchmark/
  12. biometric/
  13. bluetooth/
  14. browser/
  15. buildSrc/
  16. buildSrc-tests/
  17. busytown/
  18. camera/
  19. car/
  20. cardview/
  21. collection/
  22. compose/
  23. concurrent/
  24. contentpager/
  25. coordinatorlayout/
  26. core/
  27. cursoradapter/
  28. customview/
  29. datastore/
  30. development/
  31. docs/
  32. docs-public/
  33. docs-tip-of-tree/
  34. documentfile/
  35. draganddrop/
  36. drawerlayout/
  37. dynamicanimation/
  38. emoji/
  39. emoji2/
  40. enterprise/
  41. exifinterface/
  42. external/
  43. fakeannotations/
  44. fragment/
  45. frameworks/
  46. glance/
  47. gradle/
  48. graphics/
  49. gridlayout/
  50. health/
  51. heifwriter/
  52. hilt/
  53. inspection/
  54. interpolator/
  55. javascriptengine/
  56. leanback/
  57. lifecycle/
  58. lint-checks/
  59. loader/
  60. media/
  61. media2/
  62. mediarouter/
  63. metrics/
  64. navigation/
  65. paging/
  66. palette/
  67. percentlayout/
  68. placeholder-tests/
  69. playground-common/
  70. preference/
  71. print/
  72. privacysandbox/
  73. profileinstaller/
  74. recommendation/
  75. recyclerview/
  76. remotecallback/
  77. resourceinspection/
  78. room/
  79. samples/
  80. savedstate/
  81. security/
  82. sharetarget/
  83. slice/
  84. slidingpanelayout/
  85. sqlite/
  86. startup/
  87. swiperefreshlayout/
  88. test/
  89. testutils/
  90. text/
  91. tracing/
  92. transition/
  93. tv/
  94. tvprovider/
  95. vectordrawable/
  96. versionedparcelable/
  97. viewpager/
  98. viewpager2/
  99. wear/
  100. webkit/
  101. window/
  102. work/
  103. .gitignore
  104. .mailmap
  105. build.gradle
  106. cleanBuild.sh
  107. code-review.md
  108. CONTRIBUTING.md
  109. gradle.properties
  110. gradlew
  111. include-composite-deps.gradle
  112. libraryversions.toml
  113. LICENSE.txt
  114. OWNERS
  115. PREUPLOAD.cfg
  116. README.md
  117. settings.gradle
  118. studiow
  119. TEXT_OWNERS
README.md

Android Jetpack

Revved up by Gradle Enterprise

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.

Contribution Guide

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:

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

Head over to the onboarding docs to learn more about getting set up and the development workflow!

Continuous integration

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.

Password and Contributor Agreement before making a change

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

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

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.