Removed hard-coded values from theme-manager

[shaurya947]

Made component-level theme values consistent with the raw theme
Renamed canvasColor raw theme key to alternateTextColor
Updated docs to use new theming values

[clarkie]

This is a breaking change and as such should not go into a patch release.

[oliviertassinari]

Are you saying this regarding canvasColor. Yes, I agree using v0.13.0 instead of v0.12.1 may have been better.

[clarkie]

Yes, I have 0.12.x in my package.json so I wouldn't expect any breaking changes. However, according to semver you can change whatever you like when the version is < 1.0

[shaurya947]

Sorry about that @clarkie. I truly failed to think about that in the midst of getting rid of hard-coded color values.

Nevertheless, there have been a couple issues recently complaining about the lack of keys in palette and it seems like canvasColor may be coming back. So perhaps the breaking change wouldn't be so breaking after all :-)

[shaurya947]

#1762

[KapJI]

This PR changed appearance for some components such as Slider and LinearProgress. What is the reason for doing that?

[shaurya947]

@KapJI the purpose of this PR was to remove hard-coded color values from theme-manager. All color values in the theme-manager should ideally come from the raw-theme, and this was an effort in that direction.

If you don't like the colors, feel free to modify them either in dark-raw-theme, or override component-level styles in your muiTheme object. See http://material-ui.com/#/customization/themes for more details on how to do that.