Change the way how component color is defined and set

[Dzoukr]

As agreed in #20, we should rethink how to work with colors.
One way would be having button.color color.isDanger, or just have long list of possible colors and using it directly color.isDanger (which I like more right now). Should discuss further.

[Dzoukr]

Ok, let's focus on this now.

I think the approach for this should be:

• get rid of component color modifiers like 'button.isDanger'
• have just 'color.isDanger' everywhere

Then we would have unified way how to work with colors + less code in modifiers file

[MangelMaxime]

@Dzoukr

I am not sure which API you are choosing but if it is button.color.isDanger and not button.color color.isDanger.

Then you should first try to design and extend button.color.isDanger API on a some portion or in Fable REPL. Personnally I didn't found a way to do it.

[Dzoukr]

I was thinking just about

Bulma.button.a [
    color.isDanger
]

I am aware of that it could theoretically lead to setting colors for components which don't support it, but we cannot prevent it anyway (you can still mixup various helpers - they are just classes) and API would be way cleaner.

[MangelMaxime]

I didn't think about this solution.

It's the same way of thinking as for text modifiers for example 👍

[Dzoukr]

I think we have this finished as well.