Exemple #1
0
 /// <summary>
 /// Asynchronously loads a component class without instantiating it; returns a promise on the loaded class.
 ///
 /// Beware: "Asynchronous component loading" doesn't necessarily mean that no more synchronous loading occurs. Both the framework as well as component implementations might still execute synchronous requests. <code>Component.load</code> just allows to use async calls internally.
 ///
 /// When a manifest is referenced in <code>mOptions</code>, this manifest is not automatically used for instances of the Component class that are created after loading. The manifest or the manifest url must be provided for every instance explicitly.
 ///
 /// To optimize the loading process, additional <code>asyncHints</code> can be provided. If components and/or libraries are listed in the <code>asyncHints</code>, all the corresponding preload files will be requested in parallel, loading errors (404s) will be ignored. The constructor class will only be required after all preloads have been rejected or resolved. The structure of the hints and how they impact the loading of components is an internal feature of this API and reserved for UI5 internal use only. Code that wants to be safe wrt. version updates, should not use the <code>asyncHints</code> property.
 /// </summary>
 /// <param name="mOptions">Configuration options</param>
 /// <returns>A Promise that resolves with the loaded component class or <code>undefined</code> in case <code>mOptions.asyncHints.preloadOnly</code> is set to <code>true</code></returns>
 public extern static es5.Promise <object> load(sap.ui.core.Component.LoadOptions mOptions);
Exemple #2
0
 /// <summary>
 /// Asynchronously loads a component class without instantiating it; returns a promise on the loaded class.
 ///
 /// Beware: "Asynchronous component loading" doesn't necessarily mean that no more synchronous loading occurs. Both the framework as well as component implementations might still execute synchronous requests. <code>Component.load</code> just allows to use async calls internally.
 ///
 /// When a manifest is referenced in <code>mOptions</code>, this manifest is not automatically used for instances of the Component class that are created after loading. The manifest or the manifest url must be provided for every instance explicitly.
 ///
 /// To optimize the loading process, additional <code>asyncHints</code> can be provided. If components and/or libraries are listed in the <code>asyncHints</code>, all the corresponding preload files will be requested in parallel, loading errors (404s) will be ignored. The constructor class will only be required after all preloads have been rejected or resolved. The structure of the hints and how they impact the loading of components is an internal feature of this API and reserved for UI5 internal use only. Code that wants to be safe wrt. version updates, should not use the <code>asyncHints</code> property.
 /// </summary>
 /// <param name="mOptions">Configuration options</param>
 /// <returns>A Promise that resolves with the loaded component class or <code>undefined</code> in case <code>mOptions.asyncHints.preloadOnly</code> is set to <code>true</code></returns>
 public extern static jquery.JQueryPromise <object> load(sap.ui.core.Component.LoadOptions mOptions);