Hi Sam, Interesting question; +1 to your change.
I think the usability improvement of the checkbox trumps the tertiary use-case; we can live with that.
If folk really want tertiary, they can/should use an enumeration (with the config's default being "none" or some such).
Out of interest, does the blank text box correspond to null, or does it correspond to an empty string? If an empty string, then what does that get coerced to when converting to a boolean? Is it really null?
Aled On 17/07/2015 12:11, Sam Corbett wrote:
I opened a pull request yesterday to render Boolean config keys as checkboxes in the js gui: https://github.com/apache/incubator-brooklyn/pull/750, see PR for a screenshot. Svet pointed out that this would leave users unable to `null` such config items through the UI. Is there any valid case for a tri-state true/false/null ConfigKey<Boolean>? And if you think there is, are you sure your design is correct? I just wanted to check/forewarn before merging the PR. Sam
