I don't plan on having this out by 1.8. However, for rich-click 1.9, I want to focus on having a set of default styles for users to choose from.
The issue is basically that rich-click provides a lot of powerful functionality for customization, but actually customizing rich-click is more work than is reasonable for a lot of users. "Compressing" the workload into a higher level API with a small handful of options (or even just one option, i.e. a single string name for a style) would be very convenient.
There are a few things to consider:
What does the API look like? I think, to start, rich-click needs to make some sort of distinction between "style" config and other config. Then some way to load a style config needs to be defined.
Obviously, what styles do we include? I want to have, at minimum, styles that correspond with basic colors. More advanced options may be to have styles that have two colors, e.g. "red primary, blue secondary."
I don't plan on having this out by 1.8. However, for rich-click 1.9, I want to focus on having a set of default styles for users to choose from.
The issue is basically that rich-click provides a lot of powerful functionality for customization, but actually customizing rich-click is more work than is reasonable for a lot of users. "Compressing" the workload into a higher level API with a small handful of options (or even just one option, i.e. a single string name for a style) would be very convenient.
There are a few things to consider: