SAPUI5从入门到精通–PDF下载，其实吧，空上文件就是SAP官网的SAPUI5的标准文档的PDF，我一直学习都使用这个，感觉说的是很细致的了，多读些次数总是好的，我也不记得我看了多少遍了，但好像都没完整的学习完过，是应该要多化的时间学习一下的。
下载：
SAPUI5从入门到精通
What’s New in SAPUI5 1.52
With this release the UI development toolkit for HTML5 (SAPUI5) is upgraded from version 1.50 to 1.52.Improved FeaturesOData V2 Model
You can now optimize dependent bindings in OData V2 models. The OData V2 model now supports a preliminaryContext flag. When set to true, the OData model can bundle the OData calls for dependent bindings into fewer $batch requests. Two bindings are considered dependent if one cannot be resolved without the other being resolved first. For example, a relative binding cannot be resolved without a resolved absolute binding.SAPUI5 OData V4 Model
The new version of the SAPUI5 The OData V4 model has the following features:●
Handling of Edm.Stream in read-only mode●
Possibility to declare several batch groups as $auto or $direct●
Enhancements to the adapter to use the V4 model with an OData V2 service: handling of simple $filter expressionsCautionIncompatibility Due to a Bug Fix
If you call the sap.ui.model.odata.v4.Context#getObject() or the sap.ui.model.odata.v4.Context#requestObject() methods without a parameter, the expected and documented behavior is that the same result is returned as if the parameter sPath="" had been specified. However, due to a bug, the return value wraps the expected output and can only be accessed using .value[0], for example oContext.getObject().value[0].If you have used this workaround, your application will break as of SAPUI5 version 1.44.7.Solution: If your application needs to run with both the fixed and unfixed versions of SAPUI5, specify the sPath="" parameter, for the sPath parameter. In both cases, you must not use the .value[0]workaround any more.Restriction
Due to the limited feature scope of this version of the SAPUI5 OData V4 model, check that all required features are in place before developing applications. Check the detailed documentation of the features, as certain parts of a feature may be missing. While we aim to be compatible with existing controls, some controls might not work due to small incompatibilities compared to sap.ui.model.odata.(v2.)ODataModel, or due to missing features in the model (such as tree binding). This also applies to Smart Controls (sap.ui.comp library) and SAP Fiori elements that do not support the SAPUI5 OData V4 model, as well as controls such as TreeTable and AnalyticalTable, which are not supported together with the SAPUI5 OData V4 model. The interface for applications has been changed for easier and more efficient use of the model. For a summary of these changes, see Changes Compared to OData V2 Model [page 726].
