@openui5/sap.ui.core 1.113.0 → 1.114.1

package/src/sap/ui/core/routing/Targets.js

@@ -73,219 +73,10 @@ sap.ui.define([
 		 * If you are using a component and add the routing.targets <b>do not set this parameter</b>,
 		 * since the component will set the rootView to the view created by the {@link sap.ui.core.UIComponent#createContent} function.
 		 * If you specify the "parent" property of a target, the control will not be searched in the root view but in the view Created by the parent (see parent documentation).
-		 * @param {boolean} [oOptions.config.async=false] @since 1.34 Whether the views which are created through this Targets are loaded asyncly. This option can be set only when the Targets
+		 * @param {boolean} [oOptions.config.async=false] @since 1.34 Whether the views which are created through this Targets are loaded asynchronously. This option can be set only when the Targets
 		 * is used standalone without the involvement of a Router. Otherwise the async option is inherited from the Router.
 
-		 * @param {object} oOptions.targets One or multiple targets in a map.
-		 * @param {object} oOptions.targets.anyName a new target, the key severs as a name. An example:
-		 * <pre>
-		 * <code>
-		 * {
-		 *     targets: {
-		 *         welcome: {
-		 *             type: "View",
-		 *             name: "Welcome",
-		 *             viewType: "XML",
-		 *             ....
-		 *             // Other target parameters
-		 *         },
-		 *         goodbye: {
-		 *             type: "Component",
-		 *             usage: "myreuse",
-		 *             containerSettings: {
-		 *                 // settings for the component container
-		 *             }
-		 *             ....
-		 *             // Other target parameters
-		 *         }
-		 *     }
-		 * }
-		 * </code>
-		 * </pre>
-		 *
-		 * This will create two targets named 'welcome' and 'goodbye' you can display both of them or one of them using the {@link #display} function.
-		 *
-		 * The 'welcome' target creates a View instance when it's displayed. The 'goodbye' target creates a Component instance.<br/>
-		 *
-		 * The settings for the Component are defined in the manifest of the owner component of the router under path '/sap.ui5/componentUsages' and it can be used in the target by setting the 'usage' option with the name in the 'componentUsages'.<br/>
-		 * See the following manifest.json example of the owner component. There's a component settings object defined with name "myreuse" which can be used to set the "usage" option in a target's configuration.
-		 * <pre>
-		 * <code>
-		 * {
-		 *     "sap.ui5": {
-		 *         "componentUsages": {
-		 *             "myreuse": {
-		 *                 "name": "reuse.component",
-		 *                 "settings": {},
-		 *                 "componentData": {},
-		 *                 "lazy": false,
-		 *             }
-		 *         }
-		 *     }
-		 * }
-		 * </code>
-		 * </pre>
-		 *
-		 * @param {string} oOptions.targets.anyName.type Defines whether the target creates an instance of 'View' or 'Component'.
-		 * @param {string} [oOptions.targets.anyName.name] Defines the name of the View or Component that will be
-		 * created. For type 'Component', use option 'usage' instead if an owner component exists.
-		 * To place the view or component into a Control, use the options <code>controlAggregation</code> and
-		 * <code>controlId</code>. Instance of View or Component will only be created once per <code>name</code> or
-		 * <code>usage</code> combined with <code>id</code>.
-		 * <pre>
-		 * <code>
-		 * {
-		 *     targets: {
-		 *         // If display("masterWelcome") is called, the master view will be placed in the 'MasterPages' of a control with the id splitContainter
-		 *         masterWelcome: {
-		 *             type: "View",
-		 *             name: "Welcome",
-		 *             controlId: "splitContainer",
-		 *             controlAggregation: "masterPages"
-		 *         },
-		 *         // If display("detailWelcome") is called after the masterWelcome, the view will be removed from the master pages and added to the detail pages, since the same instance is used. Also the controls inside of the view will have the same state.
-		 *         detailWelcome: {
-		 *             // same view here, that's why the same instance is used
-		 *             type: "View",
-		 *             name: "Welcome",
-		 *             controlId: "splitContainer",
-		 *             controlAggregation: "detailPages"
-		 *         }
-		 *     }
-		 * }
-		 * </code>
-		 * </pre>
-		 *
-		 *
-		 * If you want to have a second instance of the 'welcome' view you can set different 'id' to the targets:
-		 *
-		 * <pre>
-		 * <code>
-		 * {
-		 *     targets: {
-		 *         // If display("masterWelcome") is called, the view with name "Welcome" will be placed in the 'MasterPages' of a control with the id splitContainter
-		 *         masterWelcome: {
-		 *             type: "View",
-		 *             name: "Welcome",
-		 *             id: "masterWelcome",
-		 *             controlId: "splitContainer",
-		 *             controlAggregation: "masterPages"
-		 *         },
-		 *         // If display("detailWelcome") is called after the "masterWelcome" target, a second instance of the same view with its own controller instance will be added in the detail pages.
-		 *         detailWelcome: {
-		 *             type: "View",
-		 *             name: "Welcome",
-		 *             // another instance will be created because a different id is used
-		 *             id: "detailWelcome",
-		 *             controlId: "splitContainer",
-		 *             controlAggregation: "detailPages"
-		 *         }
-		 *     }
-		 * }
-		 * </code>
-		 * </pre>
-		 *
-		 *
-		 * @param {string} [oOptions.targets.anyName.usage] Defines the 'usage' name for 'Component' target which refers to the '/sap.ui5/componentUsages' entry in the owner component's manifest.
-		 * @param {string} [oOptions.targets.anyName.viewType=oOptions.config.viewType] The type of the view that is going to be created. These are the supported types: {@link sap.ui.core.mvc.ViewType}.
-		 * You always have to provide a viewType except if <code>oOptions.config.viewType</code> is set or when using {@link sap.ui.core.routing.Views#setView}.
-		 * @param {string} [oOptions.targets.anyName.path]
-		 * A prefix that will be prepended in front of the <code>name</code>.<br/>
-		 * <b>Example:</b> <code>name</code> is set to "myView" and <code>path</code> is set to "myApp" - the created view's name will be "myApp.myView".
-		 * @param {string} [oOptions.targets.anyName.id] The ID of the created instance.
-		 * This is will be prefixed with the id of the component set to the views instance provided in oOptions.views. For details see {@link sap.ui.core.routing.Views#getView}.
-		 * @param {string} [oOptions.targets.anyName.targetParent]
-		 * The id of the parent of the controlId - This should be the id of the view that contains your controlId,
-		 * since the target control will be retrieved by calling the {@link sap.ui.core.mvc.View#byId} function of the targetParent. By default,
-		 * this will be the view created by a component, so you do not have to provide this parameter.
-		 * If you are using children, the view created by the parent of the child is taken.
-		 * You only need to specify this, if you are not using a Targets instance created by a component
-		 * and you should give the id of root view of your application to this property.
-		 * @param {string} [oOptions.targets.anyName.controlId] The ID of the control where you want to place the instance created by this target. You also need to set "controlAggregation" property to specify to which aggregation of the control should the created instance be added.
-		 * An example for containers are {@link sap.ui.ux3.Shell} with the aggregation 'content' or a {@link sap.m.NavContainer} with the aggregation 'pages'.
-		 *
-		 * @param {string} [oOptions.targets.anyName.controlAggregation] The name of an aggregation of the controlId, where the created instance from the target will be added.
-		 * Eg: a {@link sap.m.NavContainer} has an aggregation 'pages', another Example is the {@link sap.ui.ux3.Shell} it has 'content'.
-		 * @param {boolean} [oOptions.targets.anyName.clearControlAggregation] Defines a boolean that can be passed to specify if the aggregation should be cleared
-		 * - all items will be removed - before adding the View to it.
-		 * When using a {@link sap.ui.ux3.Shell} this should be true. For a {@link sap.m.NavContainer} it should be false. When you use the {@link sap.m.routing.Router} the default will be false.
-		 * @param {string} [oOptions.targets.anyName.parent] A reference to another target, using the name of the target.
-		 * If you display a target that has a parent, the parent will also be displayed.
-		 * Also the control you specify with the controlId parameter, will be searched inside of the created instance of the parent not in the rootView, provided in the config.
-		 * The control will be searched using the byId function of a view. When it is not found, the global id is checked.
-		 * <br/>
-		 * The main usecase for the parent property is placing a view or component inside a smaller container of an instance, which is also created by targets.
-		 * This is useful for lazy loading views or components, only if the user really navigates to this part of your application.
-		 * <br/>
-		 * <b>Example:</b>
-		 * Our aim is to lazy load a tab of an IconTabBar (a control that displays a view initially and when a user clicks on it the view changes).
-		 * It's a perfect candidate to lazy load something inside of it.
-		 * <br/>
-		 * <b>Example app structure:</b><br/>
-		 * We have a rootView that is returned by the createContent function of our UIComponent. This view contains an sap.m.App control with the id 'myApp'
-		 * <pre>
-		 * <code>
-		 * &lt;View xmlns="sap.m"&gt;
-		 *     &lt;App id="myApp"/&gt;
-		 * &lt;/View&gt;
-		 * </code>
-		 * </pre>
-		 * an xml view called 'Detail'
-		 * <pre>
-		 * <code>
-		 * &lt;View xmlns="sap.m"&gt;
-		 *     &lt;IconTabBar&gt;
-		 *         &lt;items&gt;
-		 *             &lt;IconTabFilter&gt;
-		 *                 &lt;!-- content of our first tab --&gt;
-		 *             &lt;IconTabFilter&gt;
-		 *             &lt;IconTabFilter id="mySecondTab"&gt;
-		 *                 &lt;!-- nothing here, since we will lazy load this one with a target --&gt;
-		 *             &lt;IconTabFilter&gt;
-		 *         &lt;/items&gt;
-		 *     &lt;/IconTabBar&gt;
-		 * &lt;/View&gt;
-		 * </code>
-		 * </pre>
-		 * and a view called 'SecondTabContent', this one contains our content we want to have lazy loaded.
-		 * Now we need to create our Targets instance with a config matching our app:
-		 * <pre>
-		 * <code>
-		 *     new Targets({
-		 *         //Creates our views except for root, we created this one before - when using a component you
-		 *         views: new Views(),
-		 *         config: {
-		 *             // all of our views have that type
-		 *             viewType: 'XML',
-		 *             // a reference to the app control in the rootView created by our UIComponent
-		 *             controlId: 'myApp',
-		 *             // An app has a pages aggregation where the views need to be put into
-		 *             controlAggregation: 'pages'
-		 *         },
-		 *         targets: {
-		 *             detail: {
-		 *                 type: "View",
-		 *                 name: 'Detail'
-		 *             },
-		 *             secondTabContent: {
-		 *                 // A reference to the detail target defined above
-		 *                 parent: 'detail',
-		 *                 // A reference to the second Tab container in the Detail view. Here the target does not look in the rootView, it looks in the Parent view (Detail).
-		 *                 controlId: 'mySecondTab',
-		 *                 // An IconTabFilter has an aggregation called content so we need to overwrite the pages set in the config as default.
-		 *                 controlAggregation: 'content',
-		 *                 // A view containing the content
-		 *                 type: "View",
-		 *                 name: 'SecondTabContent'
-		 *             }
-		 *         }
-		 *     });
-		 * </code>
-		 * </pre>
-		 *
-		 * Now if we call <code> oTargets.display("secondTabContent") </code>, 2 views will be created: Detail and SecondTabContent.
-		 * The 'Detail' view will be put into the pages aggregation of the App. And afterwards the 'SecondTabContent' view will be put into the content Aggregation of the second IconTabFilter.
-		 * So a parent will always be created before the target referencing it.
+		 * @param {Object<string,sap.ui.core.routing.$TargetSettings>} oOptions.targets One or multiple targets in a map.
 		 *
 		 * @since 1.28.1
 		 * @public
@@ -402,7 +193,7 @@ sap.ui.define([
 			 * @param {object} [oData] an object that will be passed to the display event in the data property. If the target has parents, the data will also be passed to them.
 			 * @param {string} [sTitleTarget] the name of the target from which the title option is taken for firing the {@link sap.ui.core.routing.Targets#event:titleChanged titleChanged} event
 			 * @public
-			 * @returns {sap.ui.core.routing.Targets|Promise} this pointer for chaining or a Promise
+			 * @returns {this|Promise<Array<{name: string, view: sap.ui.core.mvc.View, control: sap.ui.core.Control, targetInfo: sap.ui.core.routing.TargetInfo}>>} this pointer for chaining or a Promise
 			 * @name sap.ui.core.routing.Targets#display
 			 * @function
 			 */
@@ -462,7 +253,7 @@ sap.ui.define([
 			 * an error log will be written to the console.
 			 *
 			 * @param {string} sName Name of a target
-			 * @param {object} oTargetOptions Options of a target. The option names are the same as the ones in "oOptions.targets.anyName" of {@link #constructor}.
+			 * @param {sap.ui.core.routing.$TargetSettings} oTargetOptions Options of a target. The option names are the same as the ones in "oOptions.targets.anyName" of {@link #constructor}.
 			 * @returns {this} Reference to <code>this</code> in order to allow method chaining
 			 * @public
 			 *

package/src/sap/ui/core/routing/Views.js

@@ -64,7 +64,7 @@ sap.ui.define([
 			 * So you can retrieve the view later by calling the {@link sap.ui.core.UIComponent#byId} function of the UIComponent.
 			 *
 			 * @param {string} oOptions.viewName If you do not use setView please see {@link sap.ui.view} for the documentation. This is used as a key in the cache of the Views instance. If you want to retrieve a view that has been given an alternative name in {@link #setView} you need to provide the same name here and you can skip all the other viewOptions.
-			 * @return {Promise} A promise that is resolved when the view is loaded {@link sap.ui.core.mvc.View#loaded}. The view instance will be passed to the promise.
+			 * @return {Promise<sap.ui.core.mvc.View>} A promise that is resolved when the view is loaded {@link sap.ui.core.mvc.View#loaded}. The view instance will be passed to the promise.
 			 * @public
 			 */
 			getView: function(oOptions) {

package/src/sap/ui/core/search/OpenSearchProvider.js

@@ -27,7 +27,7 @@ sap.ui.define([
 	 * @class
 	 * A SearchProvider which uses the OpenSearch protocol (either JSON or XML).
 	 * @extends sap.ui.core.search.SearchProvider
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 *
 	 * @public
 	 * @alias sap.ui.core.search.OpenSearchProvider

package/src/sap/ui/core/search/SearchProvider.js

@@ -23,7 +23,7 @@ sap.ui.define(['sap/ui/core/Element', "sap/base/Log", 'sap/ui/core/library'],
 	 *
 	 * Do not create instances of this class, but use a concrete subclass instead.
 	 * @extends sap.ui.core.Element
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 *
 	 * @public
 	 * @alias sap.ui.core.search.SearchProvider

package/src/sap/ui/core/service/Service.js

@@ -71,7 +71,7 @@ sap.ui.define(['sap/ui/base/Object', "sap/base/assert", "sap/base/Log"],
 	 *
 	 * @extends sap.ui.base.Object
 	 * @author SAP SE
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 * @alias sap.ui.core.service.Service
 	 * @abstract
 	 * @private

package/src/sap/ui/core/service/ServiceFactory.js

@@ -83,7 +83,7 @@ sap.ui.define(['sap/ui/base/Object', 'sap/ui/core/service/Service', "sap/base/as
 	 *
 	 * @extends sap.ui.base.Object
 	 * @author SAP SE
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 * @alias sap.ui.core.service.ServiceFactory
 	 * @private
 	 * @ui5-restricted sap.ushell

package/src/sap/ui/core/service/ServiceFactoryRegistry.js

@@ -18,7 +18,7 @@ sap.ui.define(['./ServiceFactory', "sap/base/assert"],
 	 * The service factory registry.
 	 *
 	 * @author SAP SE
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 * @alias sap.ui.core.service.ServiceFactoryRegistry
 	 * @private
 	 * @ui5-restricted sap.ushell

package/src/sap/ui/core/support/Plugin.js

@@ -17,7 +17,7 @@ sap.ui.define(['sap/ui/base/Object', "sap/ui/thirdparty/jquery", "sap/base/util/
 	 *
 	 * @abstract
 	 * @extends sap.ui.base.Object
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 * @private
 	 * @ui5-restricted
 	 * @alias sap.ui.core.support.Plugin

package/src/sap/ui/core/support/Support.js

@@ -33,7 +33,7 @@ sap.ui.define([
 	 * @class This class provides the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 	 *
 	 * @extends sap.ui.base.EventProvider
-	 * @version 1.113.0
+	 * @version 1.114.1
 	 * @private
 	 * @alias sap.ui.core.support.Support
 	 */

package/src/sap/ui/core/support/controls/InteractionTree.js

@@ -17,7 +17,8 @@ sap.ui.define([
 	'sap/m/Link',
 	'sap/ui/core/HTML',
 	'sap/ui/core/Title',
-	"sap/ui/thirdparty/jquery"
+	"sap/ui/thirdparty/jquery",
+   'sap/ui/core/date/UI5Date'
 ],
     function(
 		ManagedObject,
@@ -32,7 +33,8 @@ sap.ui.define([
 	   Link,
 	   HTML,
 	   Title,
-	   jQuery
+	   jQuery,
+      UI5Date
 	) {
        'use strict';
 
@@ -1089,7 +1091,7 @@ sap.ui.define([
 
        InteractionTree.prototype.formatTime = function (now) {
 
-          var oNow = new Date(now);
+          var oNow = UI5Date.getInstance(now);
 
           return this.pad0(oNow.getHours(), 2) + ":" + this.pad0(oNow.getMinutes(), 2) + ":" + this.pad0(oNow.getSeconds(), 2) + "." + this.pad0(oNow.getMilliseconds(), 3);
        };

package/src/sap/ui/core/support/plugins/Breakpoint.js

@@ -509,13 +509,13 @@ sap.ui.define(['sap/ui/Device', 'sap/ui/core/ElementMetadata', '../Plugin', "sap
 
 			return function() {
 
-				var time = (new Date()).getTime();
+				var time = Date.now();
 
 				/*eslint-disable no-debugger */
 				debugger;
 				/*eslint-enable no-debugger */
 
-				if ((new Date().getTime()) - time < 50) {
+				if (Date.now() - time < 50) {
 					that._alertNoDebugger();
 				}
 

package/src/sap/ui/core/support/plugins/ControlTree.js

@@ -60,7 +60,7 @@ sap.ui.define([
 		 * @class This class represents the ControlTree plugin for the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.ControlTree
 		 */

package/src/sap/ui/core/support/plugins/Interaction.js

@@ -15,7 +15,8 @@ sap.ui.define([
 	'sap/ui/thirdparty/jszip',
 	'sap/ui/core/util/File',
 	"sap/ui/performance/trace/Interaction",
-	"sap/ui/performance/Measurement"
+	"sap/ui/performance/Measurement",
+	"sap/ui/core/date/UI5Date"
 	],
 	function(
 		jQuery,
@@ -27,7 +28,8 @@ sap.ui.define([
 		JSZip,
 		File,
 		TraceInteraction,
-		Measurement
+		Measurement,
+		UI5Date
 	) {
 		"use strict";
 
@@ -38,7 +40,7 @@ sap.ui.define([
 		 * With this plugIn the performance measurements are displayed
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.Interaction
 		 */
@@ -60,7 +62,7 @@ sap.ui.define([
 						return ("000" + String(i)).slice(-w);
 					};
 					this._fnFormatTime = function(fNow) {
-						var oNow = new Date(fNow),
+						var oNow =  UI5Date.getInstance(fNow),
 							iMicroSeconds = Math.floor((fNow - Math.floor(fNow)) * 1000);
 						return pad0(oNow.getHours(),2) + ":" + pad0(oNow.getMinutes(),2) + ":" + pad0(oNow.getSeconds(),2) + "." + pad0(oNow.getMilliseconds(),3) + pad0(iMicroSeconds,3);
 					};

package/src/sap/ui/core/support/plugins/LocalStorage.js

@@ -15,7 +15,7 @@ sap.ui.define(['sap/ui/core/support/Plugin', "sap/base/Log"],
 		 * @class This class represents the LocalStorage plugin for the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.LocalStorage
 		 */

package/src/sap/ui/core/support/plugins/Performance.js

@@ -56,7 +56,7 @@ sap.ui.define([
 		 * With this plugIn the performance measurements are displayed
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.Performance
 		 */

package/src/sap/ui/core/support/plugins/Selector.js

@@ -20,7 +20,7 @@ sap.ui.define([
 		 * @class This class represents the selector plugin for the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.Selector
 		 */

package/src/sap/ui/core/support/plugins/TechInfo.js

@@ -26,7 +26,7 @@ sap.ui.define([
 		 * @class This class represents the technical info plugin for the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.TechInfo
 		 */

package/src/sap/ui/core/support/plugins/Trace.js

@@ -8,10 +8,11 @@
 sap.ui.define([
 	'sap/ui/core/support/Plugin',
 	'sap/ui/core/format/DateFormat',
+	'sap/ui/core/date/UI5Date',
 	"sap/base/Log",
 	"sap/base/security/encodeXML"
 ],
-	function(Plugin, DateFormat, Log, encodeXML) {
+	function(Plugin, DateFormat, UI5Date, Log, encodeXML) {
 	"use strict";
 
 		/**
@@ -19,7 +20,7 @@ sap.ui.define([
 		 * @class This class represents the trace plugin for the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 		 *
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.Trace
 		 */
@@ -228,7 +229,7 @@ sap.ui.define([
 		function getEntryHTML(oPlugin, oEntry){
 			var aLevelInfo = oEntry._levelInfo;
 			var sResult = "<div class='sapUiSupportTraceEntry'><span class='sapUiSupportTraceEntryLevel sapUiSupportTraceEntryLevel_" + aLevelInfo[0] + "'>" + aLevelInfo[0] +
-					"</span><span class='sapUiSupportTraceEntryTime'>" + oPlugin._oDateFormat.format(new Date(oEntry.timestamp)) +
+					"</span><span class='sapUiSupportTraceEntryTime'>" + oPlugin._oDateFormat.format(UI5Date.getInstance(oEntry.timestamp)) +
 					"</span><span class='sapUiSupportTraceEntryMessage'>" + encodeXML(oEntry.message || "") + "</div>";
 			return sResult;
 		}

package/src/sap/ui/core/support/plugins/ViewInfo.js

@@ -19,7 +19,7 @@ sap.ui.define([
 		 * Creates an instance of sap.ui.core.support.plugins.ViewInfo.
 		 * @class This class represents the ViewInfo plugin for the support tool functionality of UI5. This class is internal and all its functions must not be used by an application.
 		 * @extends sap.ui.core.support.Plugin
-		 * @version 1.113.0
+		 * @version 1.114.1
 		 * @private
 		 * @alias sap.ui.core.support.plugins.ViewInfo
 		 */