/// <summary> /// Instantiates a SAPUI5 mobile Router see {@link sap.ui.core.routing.Router} for the constructor arguments The difference to the {@link sap.ui.core.routing.Router} are the properties viewLevel, transition and transitionParameters you can specify in every Route or Target created by this router. /// </summary> /// <param name="oRoutes">may contain many Route configurations as {@link sap.ui.core.routing.Route#constructor}.<br/> Each of the routes contained in the array/object will be added to the router.<br/> /// /// One way of defining routes is an array: <pre> /// [ /// //Will create a route called 'firstRouter' you can later use this name in navTo to navigate to this route /// { /// name: "firstRoute" /// pattern : "usefulPattern" /// }, /// //Will create a route called 'anotherRoute' /// { /// name: "anotherRoute" /// pattern : "anotherPattern" /// } /// ] /// </pre> /// /// The alternative way of defining routes is an Object.<br/> If you choose this way, the name attribute is the name of the property. <pre> /// { /// //Will create a route called 'firstRouter' you can later use this name in navTo to navigate to this route /// firstRoute : { /// pattern : "usefulPattern" /// }, /// //Will create a route called 'anotherRoute' /// anotherRoute : { /// pattern : "anotherPattern" /// } /// } /// </pre> The values that may be provided are the same as in {@link sap.ui.core.routing.Route#constructor}</param> /// <param name="oConfig">Default values for route configuration - also takes the same parameters as {@link sap.ui.core.routing.Target#constructor}.<br/> This config will be used for routes and for targets, used in the router<br/> Eg: if the config object specifies : <pre> /// <code> /// { viewType : "XML" } /// </code> /// </pre> The targets look like this: <pre> /// { /// xmlTarget : { /// ... /// }, /// jsTarget : { /// viewType : "JS" /// ... /// } /// } /// </pre> Then the effective config will look like this: <pre> /// { /// xmlTarget : { /// viewType : "XML" /// ... /// }, /// jsTarget : { /// viewType : "JS" /// ... /// } /// } /// </pre> /// /// Since the xmlTarget does not specify its viewType, XML is taken from the config object. The jsTarget is specifying it, so the viewType will be JS.<br/></param> /// <param name="oOwner">the Component of all the views that will be created by this Router,<br/> will get forwarded to the {@link sap.ui.core.routing.Views#constructor}.<br/> If you are using the componentMetadata to define your routes you should skip this parameter.<br/></param> /// <param name="oTargetsConfig">a new target, the key severs as a name. An example: <pre> /// <code> /// { /// targets: { /// welcome: { /// viewName: "Welcome", /// viewType: "XML", /// .... /// // Other target parameters /// }, /// goodbye: { /// viewName: "Bye", /// viewType: "JS", /// .... /// // 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.</param> public extern Router(Union <sap.ui.core.routing.Route.RouteConfig, sap.ui.core.routing.Route.RouteConfig[]> oRoutes, sap.m.routing.Router.RouterConfig oConfig, sap.ui.core.UIComponent oOwner, Map <sap.m.RoutingRouterConfig> oTargetsConfig);
/// <summary> /// Instantiates a <code>sap.f.routing.Router</code>. /// </summary> /// <param name="oConfig">configuration object for the route</param> /// <param name="oOwner">the Component of all the views that will be created by this Router, will get forwarded to the {@link sap.ui.core.routing.Views#constructor}. If you are using the componentMetadata to define your routes you should skip this parameter.</param> /// <param name="oTargetsConfig">a new target, the key severs as a name. An example: <pre> /// <code> /// { /// targets: { /// welcome: { /// viewName: "Welcome", /// viewType: "XML", /// .... /// // Other target parameters /// }, /// goodbye: { /// viewName: "Bye", /// viewType: "JS", /// .... /// // 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.</param> public extern Router(sap.f.routing.Router.RouterConfig oConfig, sap.ui.core.UIComponent oOwner, Map <sap.m.RoutingRouterConfig> oTargetsConfig);
/// <summary> /// Sets the aggregated {@link #getRootComponent rootComponent}. /// </summary> /// <param name="oRootComponent">The rootComponent to set</param> /// <returns>Reference to <code>this</code> in order to allow method chaining</returns> public extern virtual sap.ui.app.Application setRootComponent(sap.ui.core.UIComponent oRootComponent);