deweyreed / theme Goto Github PK

Even if I've disabled Theme in the edit mode, Theme still breaks MaterialButton in library modules. In the application mode, everything works fine. What's going on?

https://github.com/material-components/material-components-android/releases/tag/1.4.0

I notice something like colorOnPrimary has been added to material library. That definitely requires some work to adapt it.

Docs: https://github.com/material-components/material-components-android/blob/master/docs/theming/Color.md

https://github.com/material-components/material-components-android/releases/tag/1.2.0

Use compileOnly libs.material.

I've already used this theme to decorate my app. It's impossible for me not to use material library.

Material library will use implementation.

https://github.com/material-components/material-components-android/releases/tag/1.3.0

"TextView" -> ThemeTextView(context, attrs)

===>

"TextView" -> AppCompatTextView(context, attrs).tint()

After playing around with Jetpack Compose, I find that it supports changing view colors through color int instead of styles out of box. By the time of its stable release, this library may be replaced and deprecated.

Currently, all color values are retrieved through SharedPreferences which is created and destroyed according to Activity lifecycle.

Sometimes, color values are accessed when prefs are null and then everything explodes.

Maybe I should always pass a Context to Theme like getting a singleton database.

Currently, for some colors, Theme's isColorLight and Android give different answers. Therefore, the toolbar icon color and the navigation bar icon color are different.

There must be something like isColorLight in AOSP but where?