activated The event fires when Windows Runtime activation has occurred. See MSDN docs for further details and activation types. Quick Example document.addEventListener("activated", activated, false); function activated(args) { if (args && args.kind === Windows.ApplicationModel.Activation.ActivationKind.file) { // Using args.raw to get the native StorageFile object Windows.Storage.FileIO.readTextAsync(args.raw.detail[0].files[0]).done(function (text) { con

Config.xml Config.xml is a global configuration file that controls many aspects of a cordova application's behavior. This platform-agnostic XML file is arranged based on the W3C's Packaged Web Apps (Widgets) specification, and extended to specify core Cordova API features, plugins, and platform-specific settings. For projects created with the Cordova CLI (described in The Command-Line Interface), this file can be found in the top-level directory: app/config.xml Note that before version 3.3.1-0

preference Sets various options as pairs of name/value attributes. Each preference's name is case-insensitive. Many preferences are unique to specific platforms, and will be indicated as such. Attributes(type) Only for platform: Description AllowInlineMediaPlayback(boolean) iOS Default: false Set to true to allow HTML5 media playback to appear inline within the screen layout, using browser-supplied controls rather than native controls. For this to work, add the webkit-playsinline attribute t

Config.xml Config.xml is a global configuration file that controls many aspects of a cordova application's behavior. This platform-agnostic XML file is arranged based on the W3C's Packaged Web Apps (Widgets) specification, and extended to specify core Cordova API features, plugins, and platform-specific settings. For projects created with the Cordova CLI (described in The Command-Line Interface), this file can be found in the top-level directory: app/config.xml Note that before version 3.3.1-0

plugin Specifies details about what plugin to restore during a prepare. This element is automatically added to a project's config.xml when a plugin is added using the --save flag. See the CLI reference for more information on adding plugins. Attributes(type) Only for platform: Description name(string) Required Name of the plugin to be restored spec(string) Required Details about the plugin to be restored. This could be a major.minor.patch version number, a directory containing the plugin o

platform When using the CLI to build applications, it is sometimes necessary to specify preferences or other elements specific to a particular platform. Use the element to specify configuration that should only appear in a single platform-specific config.xml file. Attributes(type) Only for platform: Description name(string) Required The platform whose preferences are being defined. Examples: <platform name="android"> <preference name="Fullscreen" value="true" /> </platfo

name Specifies the app's formal name, as it appears on the device's home screen and within app-store interfaces. Examples: <widget ...> <name>HelloCordova</name> </widget>

hook Represents your custom script which will be called by Cordova when certain action occurs (for example, after plugin is added or platform prepare logic is invoked). This is useful when you need to extend default Cordova functionality. See Hooks Guide for more information. Attributes(type) Only for platform: Description type(string) Required Specifies the action during which the custom script is to be called. src(string) Required Specifies the location of the script to be called when a

Config.xml Config.xml is a global configuration file that controls many aspects of a cordova application's behavior. This platform-agnostic XML file is arranged based on the W3C's Packaged Web Apps (Widgets) specification, and extended to specify core Cordova API features, plugins, and platform-specific settings. For projects created with the Cordova CLI (described in The Command-Line Interface), this file can be found in the top-level directory: app/config.xml Note that before version 3.3.1-0

feature If you use the CLI to build applications, you use the plugin command to enable device APIs. This does not modify the top-level config.xml file, so the element does not apply to your workflow. If you work directly in an SDK and using the platform-specific config.xml file as source, you use the tag to enable device-level APIs and external plugins. They often appear with custom values in platform-specific config.xml files. See the API Reference for details on how to specify each feature.