- 浏览: 7836 次
- 性别:
- 来自: 南京
最新评论
-
since1027:
Backbone系列教程的最后一章了,希望对Backbone入 ...
Part 8: Understanding Backbone.js Events
In this article we will look at some more concepts related to backbone models. We will try to see how we can override the default model behavior. We will look at the signification of model IDs, how we can validate a model and finally how a model can be persisted either locally or on a server.
Link to complete series:
The Initialize function and the Constructor
Whenever we create a model, the backbone will call its initialize function. We can override this function to provide custom behavior to it.
So when we create this object the output will be:
Internally what happens is that whenever a backbone model is created, its constructor gets called. The constructor will call the initialize function. It is also possible to provide out own constructor and provide the custom behavior.
The output when creating this model:
Now the problem with this constructor is that whenever the backbone model is getting created our constructor will be called. But the default constructor also does a lot of other activities at the time of object construction like calling the initialize function. So to make sure that our custom constructor works in unison with all that default behavior we need to let the backbone framework know that we still wants that default behavior. This can be done by calling Backbone.Model.apply(this, arguments); at the end of our custom constructor. This will make sure that our custom constructor will be called and then all the other activities that the default constructor is supposed to do are also done.
Now the output will be:
Note: For most of practical purposes overriding the initialize function will suffice. There is seldom a need to override the constructor but in case one decide to override the constructor, this should be the way to do it.
Model identifiers – id, cid and idAttribute
Every model needs to be uniquely identified. For this backbone gives us the model identifiers. The first one to look at is the cid. The cid or the client id is the auto-generated by backbone so that every model can be uniquely identified on the client.
Backbone also provides an identifier id to uniquely identify the model entity. This is the id that will be used to identify the model when the model data is actually being synced with server i.e. getting persisted. the cid is more useful for debugging purpose but the id attribute will determine the uniqueness of the model when it comes to CRUD operations on the model. Its fairly straight forward to set and get the id property.
Output for the above code will be: 3.
Now it gets a little confusing at this point. Since most of our models will have an attribute that will correspond to the primary key/unique identifier of the entity. Do we need to explicitly set the id value to that attribute. The answer if yes and no. We have to somehow indicate the backbone model what attribute should be used as id but we don’t have to set the id explicitly. we can use the idAttribute to accomplish this.
Now in the above code we have specified that the ID should be used as id by specifying the idAttribute. Lets try to create a new model with ID value now.
And we can see that the id value is taken from the specified attribute.
and thus this makes it very easier for the backbone models to work with server side entities and makes the model identification seamless.
Validating the model
When we are working on business applications it is often required that we validate the model before persisting the data. Backbone provides a very easy way of validating the model data. We just need to implement the models validate function.
What happens here is that whenever we try to save the model(which we will see in next section), the Validate function will get called. It will check the custom
validation logic that we have put in place and validate the model. To test the validate method, we can use models isValid function.
Another way to prevent the invalid values in the model attributes is by passing the validate:true while setting the models attribute. This will also trigger the validate function
What this will do is that this will not even allow setting of invalid values if the value that we are trying to set is invalid as per our custom logic.
How this validation works is that whenever the user chooses to save the model, the validate function will be called. if there is any validation error then the model save will fail. alternatively, the user can choose to pass validate:true whenever he want to restrict the setting of invalid values in the model attributes.
If we want to check the validity of the model at any particular instance, we can use the isValid function to test this. Having said that one important thing to know here is that whenever our validation function fails to validate the model an event invalid is raised by backbone. If we want to listen to this event, we can subscribe to this.
Lets try to hook up to this event and see the validation errors. We will do this in the initialize function of the model.
Saving the model
The backbone models inherently supports saving on the server using a restful web api. To save the model using a HTTP REST service, we need to specify the urlRoot in the backbone model. To actually save the model, we can call the save on the backbone model. The save method will trigger the validations and if the validations are successful, it will try to identify the action to be performed i.e. create or update and based on that action, it will use urlRoot and call the appropriate REST API to perform the operation.
So if I have a service running on my local machine, i first need to specify the urlRoot for the service in my model.
and to save this model using this service, I could do something like:
The save function also accepts success and error callback functions so that appropriate action can be taken based on the response from the server.
Now if we want to save the model on local storage rather than on a server, we just need to keep in mind that save function actually calls sync function to actually save/retrieve the model information. So if we need to save the model on a local storage, we need to override the sync function and provide the custom code to save on local storage.
Note: The code shown above(for save model) is syntactically correct but it will not work unless we have a REST service running at mentioned urlRoot. In coming articles, I will explain the model save using the REST service in details along with the sample service and HTML code.
Point of interest
So we saw a few more details about the backbone models. We have not yet looked at how to save the model either locally or via using a service. Perhaps in my next articles, we will talk about that only.
原文链接:http://rahulrajatsingh.com/2014/07/backbone-tutorial-part-3-more-about-backbone-models/
Link to complete series:
- Part 1: Introduction to Backbone.Js
- Part 2: Understanding the basics of Backbone Models
- Part 3: More about Backbone Models
- Part 4: CRUD Operations on BackboneJs Models using HTTP REST Service
- Part 5: Understanding Backbone.js Collections
- Part 6: Understanding Backbone.js Views
- Part 7: Understanding Backbone.js Routes and History
- Part 8: Understanding Backbone.js Events
The Initialize function and the Constructor
Whenever we create a model, the backbone will call its initialize function. We can override this function to provide custom behavior to it.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, initialize: function () { console.log('Book has been intialized'); }, });
So when we create this object the output will be:
Internally what happens is that whenever a backbone model is created, its constructor gets called. The constructor will call the initialize function. It is also possible to provide out own constructor and provide the custom behavior.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, initialize: function () { console.log('Book has been intialized'); }, constructor: function (attributes, options) { console.log('Book\'s constructor had been called'); }, });
The output when creating this model:
Now the problem with this constructor is that whenever the backbone model is getting created our constructor will be called. But the default constructor also does a lot of other activities at the time of object construction like calling the initialize function. So to make sure that our custom constructor works in unison with all that default behavior we need to let the backbone framework know that we still wants that default behavior. This can be done by calling Backbone.Model.apply(this, arguments); at the end of our custom constructor. This will make sure that our custom constructor will be called and then all the other activities that the default constructor is supposed to do are also done.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, initialize: function () { console.log('Book has been intialized'); }, constructor: function (attributes, options) { console.log('Book\'s constructor had been called'); Backbone.Model.apply(this, arguments); }, });
Now the output will be:
Note: For most of practical purposes overriding the initialize function will suffice. There is seldom a need to override the constructor but in case one decide to override the constructor, this should be the way to do it.
Model identifiers – id, cid and idAttribute
Every model needs to be uniquely identified. For this backbone gives us the model identifiers. The first one to look at is the cid. The cid or the client id is the auto-generated by backbone so that every model can be uniquely identified on the client.
var book1 = new Book(); var book2 = new Book();
Backbone also provides an identifier id to uniquely identify the model entity. This is the id that will be used to identify the model when the model data is actually being synced with server i.e. getting persisted. the cid is more useful for debugging purpose but the id attribute will determine the uniqueness of the model when it comes to CRUD operations on the model. Its fairly straight forward to set and get the id property.
var book2 = new Book(); book2.id = 3; console.log(book2.id);
Output for the above code will be: 3.
Now it gets a little confusing at this point. Since most of our models will have an attribute that will correspond to the primary key/unique identifier of the entity. Do we need to explicitly set the id value to that attribute. The answer if yes and no. We have to somehow indicate the backbone model what attribute should be used as id but we don’t have to set the id explicitly. we can use the idAttribute to accomplish this.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, idAttribute: "ID", initialize: function () { console.log('Book has been intialized'); }, constructor: function (attributes, options) { console.log('Book\'s constructor had been called'); Backbone.Model.apply(this, arguments); }, });
Now in the above code we have specified that the ID should be used as id by specifying the idAttribute. Lets try to create a new model with ID value now.
var book3 = new Book({ ID: 43 }); console.log(book1.id);
And we can see that the id value is taken from the specified attribute.
and thus this makes it very easier for the backbone models to work with server side entities and makes the model identification seamless.
Validating the model
When we are working on business applications it is often required that we validate the model before persisting the data. Backbone provides a very easy way of validating the model data. We just need to implement the models validate function.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, idAttribute: "ID", initialize: function () { console.log('Book has been intialized'); }, constructor: function (attributes, options) { console.log('Book\'s constructor had been called'); Backbone.Model.apply(this, arguments); }, validate: function (attr) { if (attr.ID <= 0) { return "Invalid value for ID supplied." } } });
What happens here is that whenever we try to save the model(which we will see in next section), the Validate function will get called. It will check the custom
validation logic that we have put in place and validate the model. To test the validate method, we can use models isValid function.
var book4 = new Book({ ID: -4 }); var result = book4.isValid(); // false
Another way to prevent the invalid values in the model attributes is by passing the validate:true while setting the models attribute. This will also trigger the validate function
var book5 = new Book(); book5.set("ID", -1, {validate:true});
What this will do is that this will not even allow setting of invalid values if the value that we are trying to set is invalid as per our custom logic.
How this validation works is that whenever the user chooses to save the model, the validate function will be called. if there is any validation error then the model save will fail. alternatively, the user can choose to pass validate:true whenever he want to restrict the setting of invalid values in the model attributes.
If we want to check the validity of the model at any particular instance, we can use the isValid function to test this. Having said that one important thing to know here is that whenever our validation function fails to validate the model an event invalid is raised by backbone. If we want to listen to this event, we can subscribe to this.
Lets try to hook up to this event and see the validation errors. We will do this in the initialize function of the model.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, idAttribute: "ID", initialize: function () { console.log('Book has been intialized'); this.on("invalid", function (model, error) { console.log("Houston, we have a problem: " + error) }); }, constructor: function (attributes, options) { console.log('Book\'s constructor had been called'); Backbone.Model.apply(this, arguments); }, validate: function (attr) { if (attr.ID <= 0) { return "Invalid value for ID supplied." } } });
Saving the model
The backbone models inherently supports saving on the server using a restful web api. To save the model using a HTTP REST service, we need to specify the urlRoot in the backbone model. To actually save the model, we can call the save on the backbone model. The save method will trigger the validations and if the validations are successful, it will try to identify the action to be performed i.e. create or update and based on that action, it will use urlRoot and call the appropriate REST API to perform the operation.
So if I have a service running on my local machine, i first need to specify the urlRoot for the service in my model.
var Book = Backbone.Model.extend({ defaults: { ID: "", BookName: "" }, idAttribute: "ID", initialize: function () { console.log('Book has been initialized'); this.on("invalid", function (model, error) { console.log("Houston, we have a problem: " + error) }); }, constructor: function (attributes, options) { console.log('Book\'s constructor had been called'); Backbone.Model.apply(this, arguments); }, validate: function (attr) { if (attr.ID <= 0) { return "Invalid value for ID supplied." } }, urlRoot: 'http://localhost:51377/api/Books' });
and to save this model using this service, I could do something like:
var book = new Book({ BookName: "Backbone Book 43" }); book.save({}, { success: function (model, response, options) { console.log("The model has been saved to the server"); }, error: function (model, xhr, options) { console.log("Something went wrong while saving the model"); } });
The save function also accepts success and error callback functions so that appropriate action can be taken based on the response from the server.
Now if we want to save the model on local storage rather than on a server, we just need to keep in mind that save function actually calls sync function to actually save/retrieve the model information. So if we need to save the model on a local storage, we need to override the sync function and provide the custom code to save on local storage.
Note: The code shown above(for save model) is syntactically correct but it will not work unless we have a REST service running at mentioned urlRoot. In coming articles, I will explain the model save using the REST service in details along with the sample service and HTML code.
Point of interest
So we saw a few more details about the backbone models. We have not yet looked at how to save the model either locally or via using a service. Perhaps in my next articles, we will talk about that only.
原文链接:http://rahulrajatsingh.com/2014/07/backbone-tutorial-part-3-more-about-backbone-models/
- backboneModelsSample2.zip (127.1 KB)
- 下载次数: 0
发表评论
-
Part 8: Understanding Backbone.js Events
2016-06-22 10:34 774In this article, we will look a ... -
Part 7: Understanding Backbone.js Routes and History
2016-06-22 09:52 485In this article, we will try to ... -
Part 6: Understanding Backbone.js Views
2016-06-22 09:50 610In this article, we will try to ... -
Part 5: Understanding Backbone.js Collections
2016-06-21 14:39 569In this article we will discuss ... -
Part 4: CRUD Operations on BackboneJs Models using HTTP REST Service
2016-06-21 14:21 814In this article we will discuss ... -
Part 2: Understanding the basics of Backbone Models
2016-06-21 12:55 530When we talk about any MV* patt ... -
Part 1: Introduction to Backbone.Js
2016-06-21 11:12 675It was a long time ago (almost ...
相关推荐
NULL 博文链接:https://since1027.iteye.com/blog/2306311
本文对JavaScriptMVC框架Angular、Backbone、CanJS和Ember作了比较,供大家参考。选择JavaScriptMVC框架很难。一方面要考虑的因素非常多,另一方面这种框架也非常多,而要从中选择一个合适的,还真得费一番心思。想...
用于 Backbone 应用程序的 mixin 集合 Backbone.Mixins.RouteFilter 将“before:route:whatever”或“after:route:whatever”过滤器添加到主干路由器 使用 before 过滤器异步收集数据的示例: class TodosRouter ...
《Node应用程序构建:使用MongoDB和Backbone》 源码,里面有git地址
Mast带来了来自诸如Knockout和Angular之类的框架的一些更重要的贡献,并允许您使用Backbone Models,Collections和Views来利用它们,并着眼于为中型到大型团队进行切实有效的开发。 它并非旨在取代Angular之类的...
这是一个 Backbone 插件,它简化了 Backbone.Radio 在 Marionette 应用程序中的使用。 它允许使用简单的语法以声明方式配置事件、请求和命令: var MyApplication = Marionette.Application.extend({ channels: {...
模型和集合是每个 Backbone/Marionette 应用程序的重要组成部分。 这个 Marionette 模块允许模型和集合作为 jQuery Promises 运行,从而消除跟踪从 ajax 调用返回的 XHR 对象的需要。 Promisable Models 可用于例如...
骨干解析覆盖 Backbone.Sync 方法以使用其 REST API 自动将您的骨干模型保存在 Parse 上。 使您免于所有手动管道。 安装 步骤1: 下载backbone-parse.js 并在backbone.js 之后包含在你的应用程序中,例如 < ...
主干.js Shim 存储库。 包管理器 : components-backbone : components/backbone
第P9周:YOLOv5-Backbone模块实现
外装 用于增强backbone.js 应用程序的mixin 集合。 组合您需要的功能,并创建您自己的基本模块以扩展您的应用程序需要。 重要提示:随着 Backbone 1.2.0 的发布,需要对 ExoSuit 进行一些更改,导致当前版本仅支持 ...
骨干守望者Backbone Warden通过将模型数据设为本地和私有来保护您在Backbone Models中的数据。为什么? 开发人员通过“属性”属性使用点表示法访问模型中的数据时,我们遇到了一些问题。 Backbone Warden强制用户...
npm install backbone-tableview --save 代码 CI TableView持续集成由Wercker处理: 测验 TableView保持100%的测试覆盖率。 要手动运行测试,请使用--dev进行安装(如上所述)并运行: gulp testc 您可以通过...
1、官方源项目地址 :https://github.com/ultralytics/yolov5 2、在yolov5-6.1中修改backbone为SPPCSPC。 3、训练、测试、预测命令与官方版本一致。
1、官方源项目地址 :https://github.com/ultralytics/yolov5 2、在yolov5-6.1中修改backbone为ACMIX。 3、训练、测试、预测命令与官方版本一致。
1、官方源项目地址 :https://github.com/ultralytics/yolov5 2、在yolov5-6.1中修改backbone为mobileone。 3、训练、测试、预测命令与官方版本一致。
1、官方源项目地址 :https://github.com/ultralytics/yolov5 2、在yolov5-6.1中修改backbone为GCNET。 3、训练、测试、预测命令与官方版本一致。
1、官方源项目地址 :https://github.com/ultralytics/yolov5 2、在yolov5-6.1中修改backbone为ConvNeXt。 3、训练、测试、预测命令与官方版本一致。