gmac
commented
11 years ago Thanks for the feedback. Can you please provide an example implementation where you feel a custom binding handler is inappropriately limiting? I don't necessarily disagree with anything you said here, although there's always a fine line between what's appropriate for automation versus what is truly unique and requires a custom setup. Also be aware, the current edge branch includes a "template" binding for attaching data to an Underscore template renderer, so this may help with your situation.
As for custom binding operators – yes, they're coming. They've been a bit slower to set up due to their complexity being inappropriate for a public API. The current edge branch does include an API and support docs for adding operators globally, and this will probably be expanded down to the individual view level as well. The current edge branch should be going to master sometime in the next week or two.
dspangen
Epoxy provides a great way of adding computed values to models, but I find that sometimes (a lot of the time) I really want to add a computed to provide very view-specific information. For instance, calculating a set of classes to apply to an element, formatting a value for human display (a value that contains conditional formatting in particular), etc. These type of data shouldn't be living on a model, IMO.
I could always add a binding handler, but having to write some jQuery to add a formatted piece of text to the DOM doesn't feel right. A binding operator may be right, but as far as I can tell, there isn't a hook to add a custom one. Is there a plan to add something of the sort, or do you have any thoughts as to where one might go and add this?