when dealing with dates you need to know, that the OData JSON format does represent dates as timestamps. These timestamps are pointingto the represented date, 0:00 UTC.
this.app = new sap.m.SplitApp(); this.app.addPage(master, true);
it has one internal attribute _aMasterPages and _aDetailPages.
app.getPage(pageId, master-boolean);
Create dummy constructor which loads the class on demand
this is a derived ( generated ) file. Change should be done in the underlying source files only(*.control, *.js) or they will be lost after the next generation.
extend is actually returning a new class by Metadata.createClass
create prototype chain
fnClass.prototype = jQuery.sap.newObject(fnBaseClass.prototype);
fnClass.prototype.constructor = fnClass;
Make the class visible as JS Object: jQuery.sap.setObject(sClassName, fnClass);
fnClass.getMetadata = fnCl
For example, if you would like know what is the magic behind “property binding”, say you have bind one attribute “SoId” in json model to an attribute in UI “titlle”,
And you would like to know how can UI knows and display value “30000097” in the runtime,