Hey Alexander, all.
On 12/13/2013 07:41 PM, Alexander Surkov wrote:
> Said above can be applied to wrong value which is exposed as invalid
> state but nevertheless it's a state. So I don't see a semantical
> contradiction here. If the value is optimal then control is in optimal
> state.
On this
Hi Mike
Regarding the pretty arbitrary application of properties and
getters/setters, after giving some thought about this, I think that
everything that is inherent to the object, so can be requested to the
object without any extra parameter, should be a property. So applying
this to the examples
Hi, Joanie. I'm fine to go with any reasonable approach, anything that
helps you to expose widget features. If that's value interface then let's
do it. If states then I'm fine with it and agree to follow expected routine
like fire state change events. If we talk about state constants naming then
op
