Changing color and brush getter to properties for easier acces in MaterialSkinManager about materialskin

[IgnaceMaes]

Read-only properties you mean? Seems like a good idea to me, dropping the "Get" and "()" would make easier to read and less confusing when used in a complex draw method.

I'm not sure about the naming pattern, e.g. MainTextColor seems more logical to me than ColorMainText. However, with Intellisense code completion the second format would be easier to discover the right property quick.

[BigBauf]

That's my thought
problem would be the GetRaisedButtonTextBrush(bool primary) method, Didn't put much thought into that yet.
If you want i can Refactor that and think about a Solution to that

[Tempz]

^
In my (pending) pull request (#28), I added a color manager to select a different primary and secondary color based on Google's flat color palettes. We can (maybe) add namespaces to it with say, ColorManager...<color/brush/pen>, like ColorManager.FlatButton.Something.Brush
Wait for Ignace to merge it before continuing with this.

[IgnaceMaes]

I merged the PR from @Tempz. However, I modified his ColorManager class into ColorScheme. Because ColorScheme is just for the variable colors, it wouldn't make sense anymore to include the constant colors there.

I think it would be a good idea to separate the constant colors from the SkinManager, or at least put them in a region.

@BigBauf making 2 separate properties would be the easiest clean solution. e.g. SkinManager(?).BrushRaisedButtonText & SkinManager(?).BrushRaisedButtonTextPrimary.