View behaviors, binders, and common operations #5
Labels
Comments
thejohnfreeman
added a commit
to thejohnfreeman/hotdrink
that referenced
this issue
May 9, 2012
Issue HotDrink#5 - All binders are in hd.binders. - Assume that built-in binders will never need to be undefined. - Custom binders can extend sub-contexts with custom values, e.g., $index. - Binding controller is a singleton with two entries: hd.bind for users and hd.subbind for binders. - View behaviors use sensible defaults for view methods based on the assumption that the view is an HTML widget.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
View behavior helpers should accept a hash of operations and directly resort to the common operations if left unspecified. The common operations presume the view type when the helpers should be generic, but that's ok---caller beware.
We should not expect that the built-in binders will ever need to be undefined. If they do, the client can always delete them.
We can tolerate tighter coupling between the binding controller singleton and the built-in binders. No need for an html namespace; just attach the binders directly to the binding controller singleton.
The text was updated successfully, but these errors were encountered: