Closed zhizhangchen closed 12 years ago
It's weird to create the need to parse a range, and also lose some flexibility. Better to have a separate min and max. Then you can leave one off if you like. I'll probably just make that change myself, but noting it here in case I don't get to it.
This patch breaks integers that do not have a range, such as the "width" property on the Image widget.
I would prefer that getPropertyRange return an object: { minimum: 2, maximum 5 }. This would also allow flexibility like: { minimum: 1 } (i.e., no maximum)... which we might use for Grid rows if we fix the performance issues.
Replace the "range:" field within widget definitions with "minimum:" and "maximum:".
Also put in the comments that this is only defined for integer properties currently.
Updated using { min: 2, max: 5} as range
Rebased for #262