'.search-dimension change': this.searchTermChanged,
'.search-dimension blur': this.searchTermChanged,
searchTermChanged: function(el, ev){
var searchTerm = el.val();
this.scope.attr('searchTerm', searchTerm);
},’el event’: ‘handler’
'.search-dimension change': 'searchTermChanged',
'.search-dimension blur': 'searchTermChanged',
'.search-dimension search': 'searchTermChanged',
Any reason why binding to a list internally would be a bad idea?
var Person = can.Map.extend({
define: {
items: {
set: function(val) {
val.bind('change', console.log);
return val;
}
}
}
});I believe we clean up those bindings when a new “items” list is set and when the instance of person is destroyed, but can’t recall offhand #lazyweb
also, should the can.List change event be adding nested properties to the index argument?
var list = new can.List();
list.bind(‘change’, function(ev, index) {});
var foo = new can.Map({ name: ‘foo’ });
list.push(foo); //index is 0, expected
foo.attr(‘name’, ‘bar’); //index is 0.name, I would expect 0What’s everyone’s approach to abstracting out arbitrary data from a model?
For instance, suppose a user model:
{ id: 0, name: ‘Alexis’ }However, in the template we would also want:
{ isEditing: false }You wouldn’t want to add that attribute directly to the model as it has no benefit being sent back to the server(just view noise).
The elegant answer is inheritable defines(I think), but I’m curious what everyone’s approach has been thus far.
jquery.js:300 Uncaught RangeError: Maximum call stack size exceeded
at Function.jQuery.extend.type (http://localhost:8126/bower_components/jquery/dist/jquery.js:300:16)
var PopUpController = can.Control.extend({
defaults: {
view: 'views/signup.hbs'
}
}, {
init: function(element, options) {
$('#popup').fadeIn('slow',function(element){
element.html(can.view(options.view, {}));
});
$('.content').click(function(){
$('#popup').fadeOut('slow');
})
},
})
return PopUpController;
})`
they would be on a viewmodel, just not the component’s necessarily. imagine you have a user model and your component has a user.list. user.isSelected could be some property you want to set.
In your view, you’d probably have something like:
{{#each users}}
<input type=“checkbox” can-value=“{isSelected}”/>
{{/each}}isSelected would be convenient at some lower level than the component viewmodel itself, but not necessarily all the way down to the model.
