BackboneJs - 模型或集合应该了解视图

发布于 2024-12-27 14:59:26 字数 892 浏览 5 评论 0原文

在我从此处的 SO 答案和许多 BackBoneJs 示例中挑选的示例之一中，我看到初始化函数知道模型将使用哪个视图进行渲染。我不知道我现在有点偏见，这是一个好的做法还是取决于正在开发的应用程序的类型。

示例

http://jsfiddle.net/thomas/Yqk5A/

编辑的小提琴

http://jsfiddle.net/Yqk5A/187/

代码参考

FriendList = Backbone.Collection.extend({
    initialize: function(){
        this.bind("add", function( model ){
            alert("hey");
            view.render( model );
        })
    }
});

上面是一个很好的做法还是下面

var friendslist = new FriendList;
var view = new FriendView({el: 'body'});
friendslist.bind("add", function( model ){
            alert("hey" + model.get("name"));
            view.render( model );
        })

在编辑的小提琴集合中由视图渲染，我们还可以使用更多视图来渲染集合。

原文

In one of the example i picked from SO answers here and many BackBoneJs examples i see that the initialize function knows which view the model is going to be rendered with. I don't know i am kind of biased now, is this a good practice or it depends on type of application being developed.

Example

http://jsfiddle.net/thomas/Yqk5A/

Edited Fiddle

http://jsfiddle.net/Yqk5A/187/

Code Reference

FriendList = Backbone.Collection.extend({
    initialize: function(){
        this.bind("add", function( model ){
            alert("hey");
            view.render( model );
        })
    }
});

Is the above a good practice or below

var friendslist = new FriendList;
var view = new FriendView({el: 'body'});
friendslist.bind("add", function( model ){
            alert("hey" + model.get("name"));
            view.render( model );
        })

in the edited fiddle collection is rendered by a view, and we also can use many more views to render the collection.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

合约呢 2025-01-03 14:59:26

我完全赞成使用事件，
我自己不想将绑定移到模型之外，我会像原始示例一样将它们保留在那里

var app = {};
app.evt = _.extend({}, Backbone.Events);  // adding a global event aggregator 

FriendList = Backbone.Collection.extend({
    initialize: function(){
        this.bind("add", function( model ){
            alert("hey");
            app.evt.trigger('addfriend', model);
        })
    }
});

//further in your code you can bind to that event
app.evt.bind("addfriend", function(model){
    var view = new FriendView({el: 'body'});
    view.render(model);
});

，但是，我发现这个示例有点奇怪，创建一个新视图，以主体作为元素，并通过给出模型到渲染函数。如果使用模型作为属性创建视图，然后将内容渲染到正文中，我会发现它更有逻辑。但这是另一个话题了。

简而言之，我在外部创建视图，监听正在触发的事件，但集合上的绑定保留在集合代码中。我发现将所有集合代码保存在同一个地方更易于管理。

I am all for using events,
I myself don't want to move the bind's outside the model, I'd keep them there like the original example

var app = {};
app.evt = _.extend({}, Backbone.Events);  // adding a global event aggregator 

FriendList = Backbone.Collection.extend({
    initialize: function(){
        this.bind("add", function( model ){
            alert("hey");
            app.evt.trigger('addfriend', model);
        })
    }
});

//further in your code you can bind to that event
app.evt.bind("addfriend", function(model){
    var view = new FriendView({el: 'body'});
    view.render(model);
});

however, i find the example a bit weird, creating a new view, with body as element, and rendering it with giving a model to the render function. i'd find it more logic if the view is created with a model as attribute, and then rendering the content into the body. but thats another subject all together.

in short, i move creating the view outside, listening to an event being triggered, but the bind on the collection stays in the collection code. i find it more managable to keep all the collection code at the same place.

回复收藏 0 原文