This also moves expandable and transformation into their own packages, as was originally intended (but they had resources, which was problematic at that time). CoordinatorLayout has been moved out of the typical source root to ease its later deletion (when it has made it into core-ui).
PiperOrigin-RevId: 180728823
The code sample said to use the itemBackground attribute to set a color on the bottom nav, but that attribute is meant for the ripple and should not be overridden. Instead, clients should set android:background.
Also updated some color values to suggest colors that are closer to our guidance from spec.
PiperOrigin-RevId: 179946811
Correct guidance for ColorStateList creation. It now says to use state_checked instead of state_enabled.
Also includes some minor naming changes.
PiperOrigin-RevId: 179940335
Bazel is happier if Java/Java test roots are named 'java' and 'javatests', and
this will mean that once we create a BUILD file for
android/support/design/{widget,internal}/ we'll no longer need a custom package
specified in our build (which tends to cause build problems that manifest quite
weirdly). This commit doesn't attempt to refactor the build at all yet, and is
just a pure move.
PiperOrigin-RevId: 178060739
- Update page title for each piece of documentation to use the vernacular concept rather
than the class name for the component.
- Treat all instances of class names as proper nouns and mark them as code names.
PiperOrigin-RevId: 155705022
The link to a method on Android's doc site had slashes in it, so it linked to the right documentation page, but not the specific method.
PiperOrigin-RevId: 155658544
I'm updating this CL as I go to fix all the issue we can find.
* Icon lists items now use correct icons, and are rearranged to be consistent.
* Removed HTML comments that were interfering with the Liquid templates.
* Added the benefits list to the docsite-index.
* Capitalized "Design" in Material Design.
* Spec links in icon list now use consistent labels.
* URLs, headings and page titles are now internally consistent within the platform.
PiperOrigin-RevId: 155445665
Follows these rules:
Title is the Component Name as it appears in spec.
Justification: Formatting and display on small width screens.
Excerpt includes the CamelCase name of the java class.
Justification: This document is not a rehash of spec, it's a specific resource for Android devs. Title and excerpt are displayed in the same context.
Header is the CamelCase name of the java class.
Justification: Similar to excerpt. This is documentation on a specific Android widget.
Path is the dash-deliminated name of the java class.
Justification: Similar to header. This is documentation on a specific Android widget.
PiperOrigin-RevId: 155134932
In order to solve overflow I have renamed the pages for BottomSheetBehavior and BottomSheetDialogFragment to "Bottom Sheets" and "Modal Bottom Sheets", reflecting their name in the spec (and usage) rather than the Android class name. This is consistent with how most other components's pages are named.
Furthermore I switched the excerpts to describe their use in the spec, and made that the first sentence in the intro for consistency.
PiperOrigin-RevId: 154995463
