Financial-Times/o-colors — pull request #30 by dansearle-ft (2014-03-19 17:00:26+00:00)
Title: Added dark-blue to palette, and new use cases for unified-design forms and buttons

@jamesnicholls , @natashabryony @Thurst-ft , @triblondon

Based on George's annotated designs for forms and buttons, I've added the new palette colour `dark-blue`, created a load of proposed new use cases using the agreed terminology, and deprecated some use cases that should no longer be required.

Using the o-colors' way of specifying a list of use-case preferences to the `oColorsGetColorFor` function, for buttons we'd specify a buttons use case, with a fallback to a general forms use-case. For example:

oColorsGetColorFor(button-standard form-field-standard, border);

or

oColorsGetColorFor(button-standout-standard button-standard form-field-standard, border);

As the `selected` and `disabled` versions of both the _standout_ and _default_ currently look identical, so they would also specify a standout use case, but there would be no need to define it, as it would fall back to the next preference which looks the same:

oColorsGetColorFor(button-standout-disabled button-disabled form-field-disabled, border);

(there's no use case for `button-standout-disabled`)

Does this make sense? Do the `form-field-` use cases make sense for you to use in the forms module?