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.
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.