travisc 04bf0a7c42 Move themes into theme package, invert dependency structures around components. ...

Previously [most of] the components were either in `widget` or depended on it,
and all theme-related resources (attributes, styles, etc.) were placed there.
This structure doesn't really work for our goals, and makes it harder to split
components by functional area. In this commit, I move all the theme definitions
to `theme` (as well as `dialog` and `bottomsheet` since they also have relevant
themes, and splitting them into separate packages is the only way to make the
dep tree non-circular). Component packages declare their own theme attributes
(e.g. `chip` declares all the theme attributes necessary for chips), as well as
styles, colors, dimens, drawables, etc.

This move isn't entirely complete in this commit, but it is enough to get
things building with this setup. I'll move the rest of the components' resources
in follow-up commits.

PiperOrigin-RevId: 182611275

2018-01-25 18:12:31 -05:00

..

res

Update button style names

2018-01-25 18:11:50 -05:00

AndroidManifest.xml

Move lib/src/ to lib/java/, and lib/jvmtests/javatests/ to lib/javatests/.

2018-01-11 10:50:18 -05:00

build.gradle

Move ThemeUtils to internal package and rename to ThemeEnforcement.

2018-01-11 11:09:46 -05:00

MaterialButton.java

Move themes into theme package, invert dependency structures around components.

2018-01-25 18:12:31 -05:00

MaterialButtonHelper.java

Update button tinting to support ViewCompat.setBackgroundTintList()

2018-01-25 18:09:04 -05:00