Fixed localization formatting for picker widgets

The data/time separators were picked from the string resources ("/",
":"). This however could create issues in terms of localization since
different locales could have different separators defined for their time
and date formats.
Switched to using DateFormat to extract a locale-based string pattern
for both date and time.
Also defined a new way of specifying the separators to cover the general
case of different locales having different set of separators between the
time/date fields based on the current date/time format.
Also refactored different chunks of TimePicker.

Bug: 63715369
Test: DatePickerTest#testExtractSeparatorsForDifferentLocales,
TimePickerTest#testExtractSeparatorsForDifferentLocales
Also manual inspection of date/time widgets for several locales.

Change-Id: I6cb934b4ddc4870a5f103d54ffb80ddd7bc6f23b
93 files changed
tree: dec1ea9e63e32bba5c9a070343dce067ae03456a
  1. .idea/
  2. annotations/
  3. api/
  4. app-toolkit/
  5. buildSrc/
  6. compat/
  7. core-ui/
  8. core-utils/
  9. customtabs/
  10. design/
  11. development/
  12. dynamic-animation/
  13. emoji/
  14. exifinterface/
  15. fragment/
  16. frameworks/
  17. gradle/
  18. graphics/
  19. lifecycle/
  20. media-compat/
  21. media-compat-test-client/
  22. media-compat-test-lib/
  23. media-compat-test-service/
  24. paging/
  25. percent/
  26. recommendation/
  27. room/
  28. samples/
  29. samples-flatfoot/
  30. scripts/
  31. testutils/
  32. transition/
  33. tv-provider/
  34. v13/
  35. v14/
  36. v17/
  37. v4/
  38. v7/
  39. wear/
  40. .gitignore
  41. Android.mk
  42. build.gradle
  43. CleanSpec.mk
  44. droiddoc.mk
  45. gradle.properties
  46. gradlew
  47. LICENSE.txt
  48. makeFlatfootRepo.sh
  49. pathmap.mk
  50. PREUPLOAD.cfg
  51. README.md
  52. settings.gradle
README.md

AOSP Support Library Contribution Guide

Accepted Types of Contributions

  • Bug fixes (needs a corresponding bug report in b.android.com)
  • 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

We are not currently accepting new modules, features, or behavior changes.

Checking Out the Code

NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.

Follow the “Downloading the Source” guide to install and set up repo tool, but instead of running the listed repo commands to initialize the repository, run the folowing:

repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master

Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):

repo sync -j8 -c

You will use this command to sync your checkout in the future - it’s similar to git fetch

Using Android Studio

Open path/to/checkout/frameworks/support/ in Android Studio. 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.

Optional - Full Build

You can do most of your work from Android Studio, however you can also build the full support library from command line:

cd path/to/checkout/frameworks/support/
./gradlew createArchive

Running Tests

Single Test Class or Method

  1. Open the desired test file in Android Studio.
  2. Right-click on a test class or @Test method name and select Run FooBarTest

Full Test Package

  1. In the project side panel open the desired module.
  2. Find the directory with the tests
  3. Right-click on the directory and select Run android.support.foobar

Running Sample Apps

Support library has a set of Android applications that exercise support library 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 support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ... and choosing the desired application.

Making a change

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)?

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)