frankban: ideas for tracking changes to computed attribute in our databinding

(1) polling, expensive (angular)

(2) like ember, you can say that a property depends on other attributes

See and

Ben: sure?

Jeff: what is use case? Francesco: when UX for one widget is based on two or more values. Example in our UX is the spinner while we are waiting on units to catch up to target.

Ben: concerned about interactions between triggers

Discussion: we only need any trigger (OR) causes computed value to render in widget.

Result: we are all happy.

ACTION: Gary will make card for Ben to implement databinding feature.