Used to get the required access privileges provided by a provider package. Optional additional parameter used for getting required API access privileges for application control requests Optional additional parameters used for resolving application control requests Mandatory string that defines the action to be performed If the required_version in the application's config.xml file is set to a version older than Tizen 2.4, and the reload attribute is used, the application installation fails. Note The reload attribute is supported since Tizen 2.4. Optional sets whether the page is reloaded when it is already loaded (available values: enable (default), disable) For more information, see Application Information and Controls. Used to indicate that the Web application can handle a specific operation with the specified MIME type and URI. If more than 1, the first occurrence is applied. Used to define a list of URL domains that are allowed to be navigated in using the Web application. Mandatory indicates whether multiple accounts are supported (available values: true, false) Capabilities are defined in the IRI format. Optional capability of the account provider. Mandatory display name of the account provider AccountSmall: File path of the account provider small icon.Account: File path of the account provider icon.Since the icons are used on the device under Settings > Accounts, place them in a shared directory. Used to register account provider information. In this case, leftover bytes are ignored. The maximum length of the attribute and the element (except, W3C preference element) can be limited to 2048 bytes. Note The extension elements are denoted as though the xmlns:tizen="" namespace declaration is in effect. For a quick view of the entire element hierarchy, see Configuration Element Hierarchy. The following sections show additional configuration elements used in the config.xml file of a Web application, but not included in the Widget Packaging and XML Configuration guidelines. Represents the generic container used mainly for internationalization.Įxtending Configuration Elements in Mobile Applications In that case, leftover bytes are ignored. The maximum length can be limited to 8192 bytes. The maximum length can be limited to 80 bytes. Used to declare preferences as key-value pairs for the Web application for use at runtime. Used to declare parameters to be used with a feature in mobile and wearable applications. Represents the Web application name used, for example, in the application menu.
#SMART PHOTO EDITOR STUDIO 1 LICENSE#
Represents the license under which the Web application is distributed. Represents text describing the purpose of the Web application. Represents the boot-strapping mechanism used to point to the main file of the Web application. Represents the person who created the Web application. Used to control network access from within a Web application and to request access to certain network resources from the user agent. Represents the root element of a configuration document. For a quick view of the element hierarchy, see Configuration Element Hierarchy. For more information on the W3C element details, see Widget Packaging and XML Configuration (the details of the Tizen extending configuration elements are described in Extending Configuration Elements in Mobile Applications and Extending Configuration Elements in Wearable Applications). The following tables summarize the W3C configuration elements used in the config.xml file of a Web application. The following tree structure shows the relationship between the elements of the config.xml file. The Tizen Web application configuration file consists of XML elements organized in a hierarchy. Select one of the form tabs ( Overview, Features, Privileges, Localization, Policy, Preferences, Tizen).Double-click the config.xml file in the Project Explorer view.There are 2 different ways to edit the config.xml file: Editing the file XML structure with the configuration source editor is intended for advanced users only. Note The config.xml must conform to both the XML file format and the W3C specification requirements.
0 kommentar(er)
