You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by ra...@apache.org on 2016/03/08 01:05:01 UTC
[02/11] docs commit: Moving dev to 6.x. This closes #537
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/win8/index.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/index.md b/www/docs/en/6.x/guide/platforms/win8/index.md
index 214869f..7a6ee17 100644
--- a/www/docs/en/6.x/guide/platforms/win8/index.md
+++ b/www/docs/en/6.x/guide/platforms/win8/index.md
@@ -23,22 +23,17 @@ title: Windows Platform Guide
# Windows Platform Guide
This guide shows how to set up your SDK development environment to build
-and deploy Cordova apps for Windows 8, Windows 8.1, Windows Phone 8.1, and
+and deploy Cordova apps for Windows 8.1, Windows Phone 8.1, and
Windows 10 Universal App Platform. It shows how to use either shell tools
-to generate and build apps, or the cross-platform Cordova CLI discussed in
-[The Command-Line Interface](../../cli/index.html). (See the [Overview](../../overview/index.html) for a comparison of these
+to generate and build apps, or the cross-platform Cordova CLI. (See the [Overview](../../overview/index.html#development-paths) for a comparison of these
development options.) This section also shows how to modify Cordova apps
-within Visual Studio. Regardless of which approach you take, you need to
+within Visual Studio. Regardless of [which](../../overview/index.html#development-paths) approach you take, you need to
install the Visual Studio SDK, as described below.
-See [Upgrading Windows 8](upgrade.html) for information on how to upgrade existing
-Windows 8 Cordova projects.
+Developers wishing to target Windows Phone 8 should use the wp8 platform,
+see [Windows Phone 8 Platform Guide](../wp8/index.html) for details (Warning, the wp8 platform is deprecated).
-Window Phone 8 (wp8) stays as a separate platform,
-see [Windows Phone 8 Platform Guide](../wp8/index.html) for details.
-
-Cordova WebViews running on Windows rely on Internet Explorer 10 (Windows 8.0)
-and Internet Explorer 11 (Windows 8.1 and Windows Phone 8.1) as
+Cordova WebViews running on Windows rely on Internet Explorer 11 (Windows 8.1 and Windows Phone 8.1) as
their rendering engine, so as a practical matter you can use IE's
powerful debugger to test any web content that doesn't invoke Cordova
APIs. The Windows Phone Developer Blog provides
@@ -49,44 +44,25 @@ on how to support IE along with comparable WebKit browsers.
To develop apps for Windows platform you need:
-- A Windows 8.1, 32 or 64-bit machine (_Home_, _Pro_, or _Enterprise_ editions) with minimum 4 GB of RAM.
-
-- Windows 8.0, 8.1 or 10, 32 or 64-bit _Home_, _Pro_, or _Enterprise_
- editions, along with
- [Visual Studio 2012 Express](http://www.visualstudio.com/downloads)
- or Visual Studio 2013. Visual Studio 2015 is not able to build Windows 8.0 apps.
-
-To develop apps for Windows 8.0 and 8.1 (including Windows Phone 8.1):
-
-- Windows 8.1 or Windows 10, 32 or 64-bit _Home_, _Pro_, or _Enterprise_ editions,
- along with
- [Visual Studio 2013 Express](http://www.visualstudio.com/downloads)
- or higher. An evaluation version of Windows 8.1 Enterprise is
+- A Windows 8.1, 32 or 64-bit machine (_Home_, _Pro_, or _Enterprise_ editions)
+ with minimum 4 GB of RAM along with [Visual Studio 2015](http://www.visualstudio.com/downloads)
+ or Visual Studio 2013. An evaluation version of Windows 8.1 Enterprise is
available from the
- [Microsoft Developer Network](http://msdn.microsoft.com/en-US/evalcenter/jj554510).
+ [Microsoft Developer Network](https://technet.microsoft.com/evalcenter/hh699156.aspx).
- For the Windows Phone emulators, Windows 8.1 (x64) Professional edition or higher,
and a processor that supports <a href='https://msdn.microsoft.com/en-us/library/windows/apps/ff626524(v=vs.105).aspx#hyperv'>Client Hyper-V and Second Level Address Translation (SLAT)</a>.
-An evaluation version of Windows 8.1 Enterprise is available from the
-[Microsoft Developer Network](http://msdn.microsoft.com/en-US/evalcenter/jj554510).
-
-- [Visual Studio 2013 for Windows](http://www.visualstudio.com/downloads/download-visual-studio-vs#d-express-windows-8) (Express or higher).
To develop apps for Windows 10:
-- Windows 8.1 or Windows 10 Technical Preview 2, 32- or 64-bit, along with
- [Visual Studio 2015 RC](http://www.visualstudio.com/preview) or higher.
+- Windows 8.1 or Windows 10, 32- or 64-bit, along with
+ [Visual Studio 2015](http://www.visualstudio.com/downloads) or higher.
App compatibility is determined by the OS that the app targeted. Apps are forwardly-compatible
-but not backwardly-compatible, so an app targeting Windows 8.1 cannot run on 8.0, but
-an app built for 8.0 can run on 8.1.
-
-Follow the instructions at
-[windowsstore.com](http://www.windowsstore.com/)
-to submit the app to Windows Store.
+but not backwardly-compatible, so an app targeting Windows 10 cannot run on 8.1, but
+an app built for 8.1 can run on 10.
-To develop Cordova apps for Windows, you may use a PC running
-Windows, but you may also develop on a Mac, either by running a
+Cordova apps targeting Windows can be developed on a Mac, either by running a
virtual machine environment or by using Boot Camp to dual-boot a
Windows 8.1 partition. Consult these resources to set up the required
Windows development environment on a Mac:
@@ -96,90 +72,43 @@ Windows development environment on a Mac:
- [Parallels Desktop](http://msdn.microsoft.com/en-US/library/windows/apps/jj945424)
- [Boot Camp](http://msdn.microsoft.com/en-US/library/windows/apps/jj945423)
-
-## Using Cordova Shell Tools
-
-If you want to use Cordova's Windows-centered shell tools in
-conjunction with the SDK, you have two basic options:
-
-- Access them locally from project code generated by the CLI. They are
- available in the `platforms/windows/` directory after you add
- the `windows` platform as described below.
-- Download them from a separate distribution at
- [cordova.apache.org](https://www.apache.org/dist/cordova/platforms/).
- The Cordova distribution contains separate archives for each platform.
- Be sure to expand the appropriate archive, `cordova-windows` in
- this case, within an empty directory. The relevant batch utilities
- are available in `package/bin` directory. (Consult the
- __README__ file if necessary for more detailed directions.)
-
-These shell tools allow you to create, build, and run Windows apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins.
-
-## Install the SDK
+## Installing the Requirements
Install any edition of
[Visual Studio](http://www.visualstudio.com/downloads) matching the version
requirements listed above.
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_installSDK.png" /></p><br/>
For Windows 10, the Visual Studio installer has an option to install tools to
build Universal Windows Apps. You must ensure that this option is selected
when installing to install the required SDK.
-## Create a New Project
-
-At this point, to create a new project you can choose between the
-cross-platform CLI tool described in [The Command-Line Interface](../../cli/index.html), or
-the set of Windows-specific shell tools.
-The CLI approach below generates an app named _HelloWorld_
-within a new `hello` project directory:
-
- > cordova create hello com.example.hello HelloWorld
- > cd hello
- > cordova platform add windows
-
-Here's the corresponding lower-level shell-tool approach:
-
- C:\path\to\cordova-windows\package\bin\create.bat C:\path\to\new\hello com.example.hello HelloWorld
-
-This project targets Windows 8.1 as the default target OS. You can choose to target 8.0 or 10.0 (see "Configure target Windows version" below) for all builds, or you target specific a particular version during each build.
-
-## Build the Project
+## Project Configuration
-If you are using the CLI in development, the project directory's
-top-level `www` directory contains the source files. Run either of
-these within the project directory to rebuild the app:
+### Target Windows version
- > cordova build
- > cordova build windows # do not rebuild other platforms
- > cordova build windows --debug # generates debugging information
- > cordova build windows --release # signs the apps for release
+After installation, you should be ready to develop apps targetting Windows platform. Refer to [Create your first app](../../cli/index.html) guide for details.
-Here's the corresponding lower-level shell-tool approach:
-
- C:\path\to\project\cordova\build.bat --debug
- C:\path\to\project\cordova\build.bat --release
-
-The `clean` command helps flush out directories in preparation for the
-next `build`:
+By default the `cordova build` command produces two packages: Windows 8.1 and Windows Phone 8.1.
+To upgrade Windows package to version 10 the following configuration setting must be
+added to configuration file (`config.xml`).
- C:\path\to\project\cordova\clean.bat
+ <preference name="windows-target-version" value="10.0" />
-## Configure target Windows version
+Once you add this setting `build` command will start producing Windows 10 packages.
-By default `build` command produces two packages: Windows 8.0 and Windows Phone 8.1.
-To upgrade Windows package to version 8.1 the following configuration setting must be
-added to configuration file (`config.xml`).
+### Considerations for target Windows version
- <preference name="windows-target-version" value="8.1" />
+Windows 10 supports a new "Remote" mode for Cordova apps (and HTML apps in general). This mode enables
+apps to have much more freedom with respect to use of DOM manipulation and common web patterns such as the use
+of inline script, but does so by reducing the set of capabilities your app may use when
+submitted to the public Windows Store. For more information about Windows 10 and Remote Mode, look at
+the [Understanding Remote Mode vs Local Mode](#understanding-remote-mode-vs-local-mode) section.
-Once you add this setting `build` command will start producing Windows 8.1
-and Windows Phone 8.1 packages.
+When using Remote Mode, developers are encouraged to apply a Content Security Policy (CSP) to their application
+to prevent script injection attacks.
### The --appx parameter
@@ -191,18 +120,7 @@ The build system will ignore the preference set in config.xml for the target Win
Valid values for the `--appx` flag are `8.1-win`, `8.1-phone`, and `uap` (for Windows 10 Universal Apps). These options also apply to the `cordova run` command.
-### Considerations for target Windows version
-
-Windows 10 supports a new "Remote" mode for Cordova apps (and HTML apps in general). This mode enables
-apps much more freedom with respect to use of DOM manipulation and common web patterns such as the use
-of inline script, but does so by reducing the set of capabilities your app may use when
-submitted to the public Windows Store. For more information about Windows 10 and Remote Mode, look at
-the [Cordova for Windows 10](win10-support.md.html) documentation.
-
-When using Remote Mode, developers are encouraged to apply a Content Security Policy (CSP) to their application
-to prevent script injection attacks.
-
-## Deploy the app
+### Deploy options
To deploy Windows package:
@@ -214,39 +132,41 @@ To deploy Windows Phone package:
> cordova run windows -- --phone # deploy app to Windows Phone 8.1 emulator
> cordova run windows --device -- --phone # deploy app to connected device
-You can use __cordova run windows --list__ to see all available targets and
-__cordova run windows --target=target_name -- --phone__ to run application on a
-specific device or emulator
-(for example, `cordova run windows --target="Emulator 8.1 720P 4.7 inch" -- --phone`).
+This command will give you the list of all available targets:
+
+ > cordova run windows --list
-You can also use __cordova run --help__ to see additional build and run
-options.
+This allows you to run the application on a specific device or emulator, in this case "Emulator 8.1 720p 4.7 inch"
-## Open the Project in the SDK and Deploy the App
+ > cordova run windows --target="Emulator 8.1 720P 4.7 inch" -- --phone
-Once you build a Cordova app as described above, you can open it with
+You can also use __cordova run --help__ to see additional build and run options.
+
+### Using Visual Studio to deploy the app
+
+Once you build a Cordova app, you can open it with
Visual Studio. The various `build` commands generate a Visual Studio
Solution (_.sln_) file. Open the file in the File Explorer to modify
the project within Visual Studio:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk_openSLN.png" /></p><br/>
The `CordovaApp` component displays within the solution, and its `www`
directory contains the web-based source code, including the
`index.html` home page:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk.png" /></p><br/>
-The controls below Visual Studio's main menu allow you to test or
+The projects for different Windows versions are displayed separately in the solution explorer. You can choose the deploy target version by right clicking the 'solution' (topmost entry in the solution explorer) and then going into 'Properties'. Here you can update the 'Single start up' field. The controls below Visual Studio's main menu allow you to test or
deploy the app:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk_deploy.png" /></p><br/>
With __Local Machine__ selected, press the green arrow to install the
app on the same machine running Visual Studio. Once you do so, the app
-appears in Windows 8's app listings:
+appears in Windows' app listings:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk_runApp.png" /></p><br/>
Each time you rebuild the app, the version available in the interface
is refreshed.
@@ -254,18 +174,18 @@ is refreshed.
Once available in the app listings, holding down the __CTRL__ key
while selecting the app allows you to pin it to the main screen:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk_runHome.png" /></p><br/>
Note that if you open the app within a virtual machine environment,
you may need to click in the corners or along the sides of the windows
to switch apps or access additional functionality:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk_run.png" /></p><br/>
Alternately, choose the __Simulator__ deployment option to view the
app as if it were running on a tablet device:
-
+<br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_sdk_sim.png" /></p><br/>
Unlike desktop deployment, this option allows you to simulate the
tablet's orientation, location, and vary its network settings.
@@ -277,16 +197,156 @@ platform-specific files used by the SDK. If you want to use the SDK to
modify the project, use the lower-level shell tools as an alternative
to the CLI.
+## Debugging
+
+Visual Studio provides powerful tools to debug your application. You can refer to [this](https://msdn.microsoft.com/en-us/library/7seh8d72.aspx) article to get started with it.
+
+## Signing an App
+
+You can learn more about signing and packaging of Windows Store Apps on [MSDN][1].
+
+To be able to correctly package and sign Windows apps there are few things required:
+
+- A signing certificate
+- Identity details matching the provided signing certificate
+
+In Windows project, identity details are kept in a file named package.appxmanifest. This file is automatically populated every time a Cordova app is built. Identity holds 3 important fields.
+
+- Name
+- Publisher
+- Version
+
+*Name* and *Version* can be set from **config.xml**. *Publisher* can be provided as a build parameter or can be set on **build.json** file.
+
+
+
+A signing certificate can be provided from either CLI or through build.json file. The certificate related CLI flags are:
+
+| Parameter | Flag | Description
+|-----------------------|-------------------|-----------------------------------
+| Certificate File | `--packageCertificateKeyFile` | Path to the package signing certificate to be associated with the app
+| Thumb Print | `--packageThumbprint` | Used to validate the authenticity of package certificate key file. When creating a certificate key file, this value will be provided to the end user
+
+Example:
+```
+cordova build -- --packageCertificateKeyFile="platforms\windows\CordovaApp_TemporaryKey.pfx" --packageThumbprint="ABCABCABCABC123123123123"`
+```
+
+Alternatively, these values could be specified using a build configuration file (build.json) using CLI (--buildConfig). A sample build configuration file:
+
+ {
+ "windows": {
+ "debug": {
+ "packageCertificateKeyFile": "platforms\\windows\\CordovaApp_TemporaryKey.pfx"
+ },
+ "release": {
+ "packageCertificateKeyFile": "c:\\path-to-key\\keycert.pfx",
+ "packageThumbprint": "ABCABCABCABC123123123123",
+ "publisherId": "CN=FakeCorp.com, L=Redmond, S=Washington, C=US"
+ }
+ }
+ }
+
+There is also support to mix and match command line arguments and parameters in build.json file. Values from the command line arguments will get precedence.
+
+### Creating a certificate key
+Signing is required for distributing and installing Windows Store apps. This process is normally handled by Visual Studio when you deploy a package for release. To do this without Visual Studio we need to create our own certificates. [This](https://msdn.microsoft.com/en-us/library/windows/desktop/jj835832(v=vs.85).aspx) article has instructions on how to do that.
+
+Once you have the pfx file created and provided to build.json file, you might get the following error: "The key file may be password protected. To correct this, try to import the certificate manually into the current user's personal certificate store.". In order to import it you have to use [certutil][2] from an admin prompt:
+
+`certutil -user -p PASSWORD -importPFX FakeCorp.com.pfx`
+
+Where:
+
+- user : Specifies "current user" personal store
+- p : Password for pfx file
+- importPfx : Name of pfx file
+
+Once installed, next step is to add packageThumbprint and packageCertificateKeyFile to build.json. In order to find the packageThumbprint, search for the CommonName you've associated with the certificate:
+
+`powershell -Command " & {dir -path cert:\LocalMachine\My | where { $_.Subject -like \"*FakeCorp.com*\" }}"`
+
+Once these final values are provided. Cordova should successfully package and sign the app.
+
+## Platform Centered Workflow
+
+If you want to use Cordova's Windows-centered shell tools in conjunction with the SDK, you have two basic options:
+
+- Access them locally from project code generated by the CLI. They are
+ available in the `platforms/windows/` directory after you add
+ the `windows` platform as described below.
+
+- Download them from a separate distribution
+ [here](https://www.apache.org/dist/cordova/platforms/).
+ The Cordova distribution contains separate archives for each platform.
+ Be sure to expand the appropriate archive, `cordova-windows` in
+ this case, within an empty directory. The relevant batch utilities
+ are available in `package/bin` directory. (Consult the
+ __README__ file if necessary for more detailed directions.)
+
+These shell tools allow you to create, build, and run Windows apps. Each cordova command corresponds to one of these shell tool scripts.
+
+For example, the lower-level shell-tool approach corresponding to `cordova create HelloWorld` is:
+
+```
+C:\path\to\cordova-windows\package\bin\create.bat C:\path\to\new\hello HelloWorld
+```
+
+Similarly for `cordova build --debug`:
+
+```
+C:\path\to\project\cordova\build.bat --debug
+```
+
+## Upgrading
+
+Refer to [this](upgrade.html) article for instructions to upgrade your `cordova-windows` version.
+
## Supporting Toasts
Windows requires an app manifest capability declaration in order to support
toast notifications. When using the `cordova-plugin-local-notifications`
plugin, or any other plugin that is attempting to use toast notifications,
add the following preference to your config.xml to enable it to publish
-toast notifications:
+toast notifications, unless the plugin makes that change on it's own:
<preference name="WindowsToastCapable" value="true" />
-This preference sets the corresponding flag in your app manifest. Plugins
+This preference sets the corresponding flag in your app manifest. Plugins
should do the work necessary to configure the appearance of the
displayed notifications.
+
+## Understanding Remote Mode vs Local Mode
+Windows 10 introduces a new feature called "Remote mode" for HTML applications. Prior to it, Windows 8.1 apps
+worked on what is now termed as "Local Mode" in Windows 10, in which HTML Applications have full access to the native
+Windows API surface and capabilities. Local Mode disallows inline script in order to prevent script injection attacks,
+which could result in leaking personally-identifiable information due to malicious code. It also requires developers who
+perform DOM manipulation to do so within an explicit context
+(`MSApp.execUnsafeLocalFunction`).
+
+Remote Mode eliminates those requirements, which makes it possible to use unmodified libraries like jQuery
+or AngularJS directly in your code, without any changes. To do so, it removes your ability to declare certain
+capabilities when certifying your app in the Windows Store. The removal of these capabilities usually doesn't
+prevent accessing certain functionality, but it might require the use of a different combination of APIs or tactics.
+
+## Effect of Remote Mode on capabilities
+The following capabilities are unavailable when deploying your Remote Mode application to the Windows Store:
+
+- Enterprise Authentication (`enterpriseAuthentication`)
+- Shared User Certificates (`sharedUserCertificates`)
+- Documents Library (`documentsLibrary`)
+- Music Library (`musicLibrary`)
+- Pictures Library (`picturesLibrary`)
+- Videos Library (`videosLibrary`)
+- Removable [Storage](../../../cordova/storage/storage.html) (`removableStorage`)
+- Internet client/server (`internetClientServer`) - note that `internetClient` is still permitted
+- Private network client/server (`privateNetworkClientServer`)
+
+Each of the library restrictions may be worked around by requesting that the user interact with the file system via a [File Picker](https://msdn.microsoft.com/en-us/library/windows/apps/windows.storage.pickers.fileopenpicker.aspx). This prevents malicious injected code from arbitrarily accessing the file system.
+
+The network-related restrictions must be worked around by either using an API that doesn't use capability checks or by brokering communication via standard internet communication channels, such as `XMLHttpRequest` or Web Sockets.
+
+The Enterprise Authentication and Shared User Certificates capabilities are specifically targeted at Enterprise scenarios. These capabilities are supported for private/enterprise-enabled App Stores, so if you are building apps which are going to be deployed to an internal deployment mechanism, you can still support these. However, they are not supported for Remote Mode apps in the public Windows Store. When you build targeting Windows 10, if one of these capabilities is detected in your app manifest, a warning will be displayed.
+
+[1]: https://msdn.microsoft.com/en-us/library/hh446593(v=vs.85).aspx
+[2]: https://technet.microsoft.com/en-us/library/ee624045(v=ws.10).aspx
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/win8/packaging.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/packaging.md b/www/docs/en/6.x/guide/platforms/win8/packaging.md
deleted file mode 100644
index 76683c5..0000000
--- a/www/docs/en/6.x/guide/platforms/win8/packaging.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-license: >
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
-
-title: Windows Packaging
----
-
-# Windows Packaging
-
-You can learn more about signing and packaging of Windows Store Apps on [MSDN][1].
-
-To be able to correctly package and sign Windows apps there are few things required:
-
-- A signing certificate
-- Identity details matching the provided signing certificate
-
-In Windows project, identity details are kept in a file named package.appxmanifest. This file is automatically populated every time a Cordova app is built. Identity holds 3 important fields.
-
-- Name
-- Publisher
-- Version
-
-*Name* and *Version* can be set from **config.xml**. *Publisher* can be provided as a build parameter or can be set on **build.json** file.
-
-
-
-A signing certificate can be provided from either CLI or through build.json file. The certificate related CLI flags are:
-
-- `--packageCertificateKeyFile` : Once a package signing certificate is created, this parameter can be used to associate the certificate with the app. This flag takes a file path as an argument. Eg. `> cordova build -- --packageCertificateKeyFile="platforms\windows\CordovaApp_TemporaryKey.pfx"`
-- `--packageThumbprint` : Package thumbprint is used to validate the authenticity of package certificate key file. When creating a certificate key file, this value will be provided to the end user. Eg. `> cordova build -- --packageCertificateKeyFile="platforms\windows\CordovaApp_TemporaryKey.pfx" --packageThumbprint="ABCABCABCABC123123123123"`
-
-Alternatively, these values could be specified using a build configuration file (build.json) using CLI (--buildConfig). A sample build configuration file:
-
- {
- "windows": {
- "debug": {
- "packageCertificateKeyFile": "platforms\\windows\\CordovaApp_TemporaryKey.pfx"
- },
- "release": {
- "packageCertificateKeyFile": "c:\\path-to-key\\keycert.pfx",
- "packageThumbprint": "ABCABCABCABC123123123123",
- "publisherId": "CN=FakeCorp.com, L=Redmond, S=Washington, C=US"
- }
- }
- }
-
-There is also support to mix and match command line arguments and parameters in build.json file. Values from the command line arguments will get precedence.
-
-# How to create a certificate key and sign Cordova windows Apps
-Signing is required for distributing and installing Windows Store apps. This process is normally handled by Visual Studio when you deploy a package for release. To do tmhis without Visual Studio we need to create our own certificates.
-
-For creating certificates we need to use [makecert.exe][2] util. This tool ships with Windows SDK and can be found under `%ProgramFiles(x86)%\Windows Kits\8.1\bin\x64` or `%ProgramFiles(x86)%\Windows Kits\8.1\bin\x86`.
-
-The first thing we need to do is to create a root key for signing our app.
-
-`makecert.exe -n "CN=FakeCorp.com" -r -eku "1.3.6.1.5.5.7.3.3,1.3.6.1.4.1.311.10.3.13" -e "01/01/2020" –h 0 -sv FakeCorp.com.pvk FakeCorp.com.cer`
-
-To understand what makecert does, here's a brief explanation of what parameters do:
-
-- -n "CN=FakeCorp.com" : This is the certificate subject [X.509](http://en.wikipedia.org/wiki/X.509) name. In this example it's **C**ommon**N**ame=FakeCorp.com.
-- -r : Creates a [self signed certificate](http://en.wikipedia.org/wiki/Self-signed_certificate).
-- -eku #EKU_VAL# : Comma separated enhanced key usage OIDs.
- - 1.3.6.1.5.5.7.3.3 indicates that the certificate is valid for code signing. Always specify this value to limit the intended use for the certificate.
- - 1.3.6.1.4.1.311.10.3.13 indicates that the certificate respects lifetime signing. Typically, if a signature is time stamped, as long as the certificate was valid at the point when it was time stamped, the signature remains valid even if the certificate expires. This EKU forces the signature to expire regardless of whether the signature is time stamped.
-- -e "01/01/2020" : Sets the expiration date of the certificate.
-- -h 0 : Sets max height of the tree below this cert to 0 to prevent the certificate from being used as a Certification Authority (CA) that can issue other certificates.
-- -sv FakeCorp.com.pvk : Output PVK file. Windows uses PVK files to store private keys for code signing.
-- FakeCorp.com.cer : Output certificate file. CER file is used to store X.509 certificate.
-
-After running makecert for the first time, enter the private password on the screen that pops up:
-
-
-
-Once pvk and cer file is created, we need to create a pfx file from these certificates. A pfx (Personal Exchange Format) file contains a variety of cryptographic information, such as certificates, root authority certificates, certificate chains and private keys. To package the certs, we will use the a tool called [pvk2pfx][3]. This tool ships with Windows SDK and can be found under `%ProgramFiles(x86)%\Windows Kits\8.1\bin\x64` or `%ProgramFiles(x86)%\Windows Kits\8.1\bin\x86`.
-
-`pvk2pfx -pvk FakeCorp.com.pvk -pi pvkPassword -spc FakeCorp.com.cer -pfx FakeCorp.com.pfx -po pfxPassword`
-
-Where:
-
-- pvk : Input pvk file name
-- pi : pvk password
-- spc : Input cert file name
-- pfx : Output pfx file name
-- po : pfx password; same as pvk password if not provided
-
-If we provide this pfx file to build.json file, we will have the following error: "The key file may be password protected. To correct this, try to import the certificate manually into the current user's personal certificate store.". In order to import it we have to use [certutil][4] from an admin prompt:
-
-`certutil -user -p PASSWORD -importPFX FakeCorp.com.pfx`
-
-Where:
-
-- user : Specifies "current user" personal store
-- p : Password for pfx file
-- importPfx : Name of pfx file
-
-Once installed, next step is to add packageThumbprint and packageCertificateKeyFile to build.json. In order to find the packageThumbprint, search for the CommonName we've associated with the certificate:
-
-`powershell -Command " & {dir -path cert:\LocalMachine\My | where { $_.Subject -like \"*FakeCorp.com*\" }}"`
-
-Once these final values are provided. Cordova should successfully package and sign the app.
-
-[1]: https://msdn.microsoft.com/en-us/library/hh446593(v=vs.85).aspx
-[2]: https://msdn.microsoft.com/en-us/library/ff548309(v=vs.85).aspx
-[3]: https://msdn.microsoft.com/en-us/library/ff550672(v=vs.85).aspx
-[4]: https://technet.microsoft.com/en-us/library/ee624045(v=ws.10).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/win8/plugin.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/plugin.md b/www/docs/en/6.x/guide/platforms/win8/plugin.md
index 6a49de6..300dc9a 100644
--- a/www/docs/en/6.x/guide/platforms/win8/plugin.md
+++ b/www/docs/en/6.x/guide/platforms/win8/plugin.md
@@ -23,19 +23,16 @@ title: Windows Plugins
# Windows Plugins
This section provides details for how to implement a plugin for use in
-a Windows Store app. Before reading this, see Application Plugins for
+a Windows Store app. Before reading this, see Create your fist plugin for
an overview of the plugin's structure and its common JavaScript interface.
This section continues to demonstrate the sample _echo_ plugin that
communicates from the Cordova webview to the native platform and back.
-It is important to note that Windows supports developing directly in Javascript, which means developing the 'native' portions in only required in special cases.
+## Creating a Windows Plugin in JavaScript
-Creating a Windows Plugin in JavaScript
----
-
-These instructions are to create a pure JavaScript plugin. Understanding this is crucial to understanding how to add the native/managed bits.
+These instructions are to create a pure JavaScript plugin.
-Windows Cordova plugins are essentially a thin wrapper around existing WinJS provided functions, but assuming you will want to define your JS common interface for multiple devices, you will typically have 1 JS file that provides the API.
+Windows Cordova plugins are essentially a thin wrapper around existing WinJS provided functions, but assuming you will want to define your JS common interface for multiple devices, you will typically have one JS file that provides the API.
// inside file echoplugin.js
var EchoPlugin = {
@@ -46,61 +43,43 @@ Windows Cordova plugins are essentially a thin wrapper around existing WinJS pro
}
}
-Inside Cordova exec on Windows
----
-
-The cordova.exec function is defined differently on every platform, this is because each platform has it's own way of communicating between the application js code, and the native wrapper code. But in the case of Windows, there is no native wrapper, so the exec call is there for consistency. You could do your js only plugin work directly in EchoPlugin.echo, something like :
-
- // inside file echoplugin.js ( this is what NOT to do if you want to reuse the JS API cross platform )
- var EchoPlugin = {
- echo:function(successCallback,errorCallback,strInput) {
- if(!strInput || !strInput.length) {
- errorCallback("Error, something was wrong with the input string. =>" + strInput);
- }
- else {
- successCallback(strInput + "echo");
- }
- }
- }
-This would/could work fine, however it means that you will need different versions of echoPlugin.js for different platforms, and possibly you could have issues with inconsistencies in your implementations. As a best practice, we decided to mimic a native API inside cordova.exec on Windows, so we could run the same JS code, and not have to rewrite it for the platform, and also take advantage of any parameter checking, or other common code provided by developers who were working on other platforms.
+## The Cordova exec proxy
-The Cordova exec proxy
----
+The `cordova.exec` function is defined differently on every platform, this is because each platform has it's own way of communicating between the application js code, and the native wrapper code. But in the case of Windows, there is no native wrapper, so the exec call is there for consistency. So even though you could write the Windows specific code as a part of plugin's common JS code directly, this is not recommended and plugin authors should use the same exec API for Windows as for other platforms. This way the plugin API becomes consistent and you can also take advantage of any parameter checking, or other common code provided by developers who were working on other platforms.
-On Windows, cordova provides a proxy that you can use to register an object that will handle all cordova.exec calls to an API.
+On Windows, cordova provides a proxy that you can use to register an object that will handle all cordova.exec calls to an API. So in our case, we will assume that the code in `echoplugin.js` is handling cross platform relevant JavaScript, and we can simply write a proxy for Windows.
-For example if you wanted to provide the implementation for the Accelerometer API, you would do this :
+```
+// in file echoplugin.js
+window.echo = function(str, callback) {
+ cordova.exec(callback, function(err) {
+ callback('Nothing to echo.');
+ }, "Echo", "echo", [str]);
+};
+```
-cordova.commandProxy.add("Accelerometer",{
- start:function(){
- // your code here ...
+```
+// in file echopluginProxy.js
+cordova.commandProxy.add("Echo",{
+ echo:function(successCallback,errorCallback,strInput) {
+ if(!strInput || !strInput.length) {
+ errorCallback("Error, something was wrong with the input string. =>" + strInput);
+ }
+ else {
+ successCallback(strInput + "echo");
+ }
}
- // ,
- // ... and the rest of the API here
});
+```
-So in our case, we will assume that the code in echoplugin.js is handling cross platform relevant JavaScript, and we can simply write a proxy for Windows
-
- // in file echopluginProxy.js
- cordova.commandProxy.add("EchoPlugin",{
- echo:function(successCallback,errorCallback,strInput) {
- if(!strInput || !strInput.length) {
- errorCallback("Error, something was wrong with the input string. =>" + strInput);
- }
- else {
- successCallback(strInput + "echo");
- }
- }
- });
+The `echoplugin.js` file will forward the `echo` function call to this proxy through the `cordova.exec` command and execute this implementation.
-The plugin definition
-
-If we want users of our plugin to be able to easily install our plugin, we will need to define it according to how PlugMan defines plugins. More on this in the [Plugin Spec](plugin_ref_spec.md.html#Plugin%20Specification)
+The plugin.xml file will have the settings required for our plugin. In this case, we want to add our `echoplugin.js` file in the `www` directory and the `echopluginProxy.js` file inside the `windows` source code of our application. Details of these elements can be found in the [Plugin.xml](../../plugin_ref/spec.html) reference.
<?xml version="1.0" encoding="UTF-8"?>
<plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
- id="com.risingj.echoplugin"
+ id="echoplugin"
version="0.1.0">
<js-module src="www/echoplugin.js" name="echoplugin">
@@ -120,13 +99,11 @@ If we want users of our plugin to be able to easily install our plugin, we will
This gives us a working Windows JavaScript plugin that uses a common file ( echoplugin.js ) and uses a proxy to provide the Windows only portion of implementation ( echopluginProxy.js ). So how do we add native/managed code to this? Well we are going to start the same, the only difference will be what we do inside in echopluginProxy methods.
-How WinJS accesses native/managed code
-===
-
+## How WinJS accesses native/managed code
In Windows, WinJS authored apps are able to interact with native code, this inter-op is available for Windows Runtime Components. The details are numerous, and this guide will only cover the basics. Microsoft provides much more info [here](http://msdn.microsoft.com/en-us/library/windows/apps/hh441569.aspx).
-When you create your Windows Runtime Component, any class that is defined as 'public ref class sealed' is considered an 'activatable class' and will be callable from JavaScript.
+When you create your Windows Runtime Component, any class that is defined as `public ref class sealed` is considered an 'activatable class' and will be callable from JavaScript.
// in your header file .h
namespace EchoRuntimeComponent
@@ -156,8 +133,11 @@ When you create your Windows Runtime Component, any class that is defined as 'pu
Now in order for us to call the native code, we use the namespace, classname, and lowerCamelCase the method we are calling.
+```
var res = EchoRuntimeComponent.EchoPluginRT.echo("boom");
-Moving this to our echopluginProxy.js file, we get this :
+```
+
+Moving this to our echopluginProxy.js file, we get:
// in file echopluginProxy.js
cordova.commandProxy.add("EchoPlugin",{
@@ -174,22 +154,18 @@ Moving this to our echopluginProxy.js file, we get this :
And that's it, we have an end to end C++ backed js callable plugin for use in Apache Cordova Windows!
-Some technical notes:
-===
+## Considerations
-- the callback is typically async, so calling the callback right away is probably not expected by the caller. In practice, if the call is not async, you should at least use a javascript timeout to force the callback to be called async.
-- Activatable classes can do all kinds of awesome, like event dispatching, async callbacks, passing your own object types, arrays, collections, overloaded methods and much more. I recommend you do your homework.
-- If you stick to common Windows Phone 8.0 and Windows SDK API calls, you will be able to use the same runtime component ( native or managed bits ) in a Windows Phone 8.0 Apache Cordova plugin. ~stay tuned for that post.
+- The callback is typically async, so calling the callback right away is probably not expected by the caller. In practice, if the call is not async, you should at least use a javascript timeout to force the callback to be called asynchronously.
+- Activatable classes can be used to do event dispatching, async callbacks, passing your own object types, arrays, collections, overloaded methods and much more. Refer [here](http://msdn.microsoft.com/en-us/library/windows/apps/hh441569.aspx) for details.
-Defining your plugin
-===
+## Defining your plugin
-Now that we have a working plugin, we need to revisit the plugin definition from earlier so we can publish it. We can now add the runtime component as a framework.
-Note that the output type of a WindowsRuntimeComponent can be either .winmd or .dll
+Now that we have a working plugin, we need to revisit the plugin definition from earlier so we can publish it. We can now add the runtime component as a framework, through the `<framework>` tag inside our platfrom settings. Note that the output type of a WindowsRuntimeComponent can be either .winmd or .dll
<?xml version="1.0" encoding="UTF-8"?>
<plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
- id="com.risingj.echoplugin"
+ id="echoplugin"
version="0.2.0">
<js-module src="www/echoplugin.js" name="echoplugin">
@@ -208,14 +184,4 @@ Note that the output type of a WindowsRuntimeComponent can be either .winmd or .
</plugin>
-That's it, you now have a distributable plugin that you can share with the world!
-One thing to note, support for adding frameworks to Windows Cordova project was only recently added so you will need to make sure your cordova tooling current. The cordova-cli and cordova-plugman both support adding removing native backed plugins.
-
-\> cordova plugin add com.risingj.echoplugin
-
-or
-
-\> plugman install --platform windows --plugin com.risingj.echoplugin --project .
-
-https://github.com/purplecabbage/cordova-runtimecomp-echoplug
-
+That's it, you now have a distributable plugin that you can share with the world!
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/win8/upgrade.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/upgrade.md b/www/docs/en/6.x/guide/platforms/win8/upgrade.md
index 06dd39a..cc39ee3 100644
--- a/www/docs/en/6.x/guide/platforms/win8/upgrade.md
+++ b/www/docs/en/6.x/guide/platforms/win8/upgrade.md
@@ -17,12 +17,21 @@ license: >
specific language governing permissions and limitations
under the License.
-title: Upgrading Windows 8
+title: Upgrading Windows
---
+# Upgrading Windows
+
+For upgrading from `windows` version 4.0.0 or higher, run `cordova platform update windows`.
+
+For projects not created with the cordova CLI, run:
+
+ bin\update <project_path>
+
+
# Upgrading Windows 8
-This guide shows how to modify Windows 8 projects to upgrade from older versions of Cordova.
+This is for people still using `windows8` platform to upgrade from older versions of Cordova.
Most of these instructions apply to projects created with an older set
of command-line tools that precede the `cordova` CLI utility. See [The Command-Line Interface](../../cli/index.html) for information how to update the
version of the CLI.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/win8/win10-support.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/win10-support.md b/www/docs/en/6.x/guide/platforms/win8/win10-support.md
deleted file mode 100644
index ee04287..0000000
--- a/www/docs/en/6.x/guide/platforms/win8/win10-support.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-license: >
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
-
-title: Cordova for Windows 10 #
----
-
-# Cordova for Windows 10 #
-Maybe you could instead call it "Windows 10 for Cordova." Windows 10 has had its HTML and
-JavaScript Apps platform re-engineered to bring Cordova support to the web, and to get
-platform security restrictions out of your way.
-
-## Getting Started with Windows 10 ##
-Adding Windows 10 support to your app is as easy as setting your Windows target platform
-version to 10.0:
-
- <preference name="windows-target-version" value="10.0" />
- <preference name="windows-phone-target-version" value="10.0" />
-
-When you build with these preferences both set, only a single .appx (and .appxupload) will
-be built. They will require Windows 10 at a minimum.
-
-### Understanding Remote Mode vs. Local Mode ###
-Remote Mode is a new feature of the HTML Applications for Windows platform in Windows 10. In
-Windows 8 and 8.1, HTML Applications worked in what is called "Local Mode" in Windows 10. In
-Local Mode, HTML Applications have full access to the native Windows API surface and
-capabilities. In order to prevent script injection attacks which could result in leaking
-personally-identifiable information due to malicious code, Local Mode disallows inline script,
-and requires developers who perform DOM manipulation to do so within an explicit context
-(`MSApp.execUnsafeLocalFunction`).
-
-Remote Mode eliminates those requirements, which makes it possible to use unmodified libraries like jQuery or AngularJS directly in your code, without any changes. To do so, it removes your ability to declare certain capabilities when certifying your app in the Windows Store. The removal of these capabilities usually doesn't prevent getting to certain functionality, but it might require to use a different combination of APIs or tactics.
-
-### Effect of Remote Mode on capabilities ###
-The following capabilities are unavailable when deploying your Remote Mode application to the Windows Store:
-
-- Enterprise Authentication (`enterpriseAuthentication`)
-- Shared User Certificates (`sharedUserCertificates`)
-- Documents Library (`documentsLibrary`)
-- Music Library (`musicLibrary`)
-- Pictures Library (`picturesLibrary`)
-- Videos Library (`videosLibrary`)
-- Removable [Storage](../../../cordova/storage/storage.html) (`removableStorage`)
-- Internet client/server (`internetClientServer`) - note that `internetClient` is still permitted
-- Private network client/server (`privateNetworkClientServer`)
-
-Each of the library restrictions may be worked around by requesting that the user interact with the file system via a [File Picker](https://msdn.microsoft.com/en-us/library/windows/apps/windows.storage.pickers.fileopenpicker.aspx). This prevents malicious injected code from arbitrarily accessing the file system.
-
-The network-related restrictions must be worked around by either using an API that doesn't use capability checks or by brokering communication via standard internet communication channels, such as `XMLHttpRequest` or Web Sockets.
-
-The Enterprise Authentication and Shared User Certificates capabilities are specifically targeted at Enterprise scenarios. These capabilities are supported for private/enterprise-enabled App Stores, so if you are building apps which are going to be deployed to an internal deployment mechanism, you can still support these. However, they are not supported for Remote Mode apps in the public Windows Store. When you build targeting Windows 10, if one of these capabilities is detected in your app manifest, a warning will be displayed.
-
-## Reference ##
-
-### config.xml Preferences ###
-
-#### windows-target-version, windows-phone-target-version ####
- <preference name="windows-target-version" value="10.0" />
- <preference name="windows-phone-target-version" value="10.0" />
-
-*At least one is required.*
-
-These preferences identify the version of Windows or Windows Phone you would like your
-app package to target.
-
-**Valid Values**
-
-- `10.0`, `UAP`: Builds for Windows 10 Universal App Platform
-- `8.1`: Builds for Windows 8.1 or Windows Phone 8.1
-- `8.0`: Build for Windows 8.0. Not valid for Windows Phone (use the **wp8** Cordova
-platform instead)
-
-**Scenarios**
-
-If you are targeting Windows 10 only, you only need to have a single `windows-target-version`
-setting in your config.xml file.
-
-#### WindowsDefaultUriPrefix ####
- <preference name="WindowsDefaultUriPrefix" value="ms-appx://|ms-appx-web://" />
-
-This preference identifies whether you want your app to target the **local context** or **remote
-context** as its startup URI. When building for Windows 10, the default is the remote
-context (`ms-appx-web://`).
-
-In order to have a local-mode application that is not impacted by Remote Mode capability
-restrictions, you must set this preference to `ms-appx://` and not declare any `<access>`
-elements with remote URIs.
-
-**Valid Values**
-
-- `ms-appx://` (Default for Windows 8.0, 8.1): The start page runs in the local context
-- `ms-appx-web://` (Default for Windows 10): The start page runs in the remote context
-
-#### {SDK}-MinVersion, {SDK}-MaxVersionTested ####
-*Optional*
-
- <preference name="Windows.Universal-MinVersion" value="10.0.0.0" />
- <preference name="Windows.Mobile-MinVersion" value="10.0.9927.0" />
- <preference name="Windows.Mobile-MaxVersionTested" value="10.0.10031.0" />
- <preference name="Microsoft.Band-MinVersion" value="10.0.11.0" />
-
-These preferences identify which ecosystems (including but not limited to Windows Universal, Windows Mobile, or Xbox) and their min/max versions they are compatible with. They still require that the platforms have support for the Universal App Platform (so Windows 10 as the base OS). However, these may indicate that the application is aware of particular functionality that may only be available on certain devices (such as game streaming on Xbox).
-
-**Valid Values**
-
-There are three parts to each value: the **SDK**, the **version restriction**, and the **version value**. These preferences are detected by beginning with `Windows` or `Microsoft` and ending in `-MinVersion` or `-MaxVersionTested`:
-
-- The **SDK** defines what specialized platform you want to target. The default is `Windows.Universal`. Valid values for these are defined in the AppxManifest schema, in the `Package/Depednencies/TargetPlatform` elements.
-- The **version restriction** defines application compatibility rules. For example, if the `-MinVersion` is set to 10.1.0.0, then OS versions which don't support at least 10.1.0.0 of the corresponding SDK won't be able to load it.
- - `-MinVersion` specifies the minimum version of the SDK required
- - `-MaxVersionTested` specifies the highest-tested version of the SDK. If a new version of the corresponding SDK is released, it will run in compatibility mode for the specified version.
-- The **version value** is a 4-integer tuple in the form of *major.minor.build.qfe*.
-
-If no preferences of these types are specified in your config.xml file, then Windows.Universal version 10.0.0.0 will be chosen by default.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/wp8/home.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/wp8/home.md b/www/docs/en/6.x/guide/platforms/wp8/home.md
new file mode 100644
index 0000000..226958c
--- /dev/null
+++ b/www/docs/en/6.x/guide/platforms/wp8/home.md
@@ -0,0 +1,27 @@
+---
+license: >
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+title: WP8 Guides
+---
+
+# WP8 Guides
+
+* [Windows Phone 8 Platform Guide](index.html)
+* [Windows Phone 8 Plugins](plugin.html)
+* [Upgrading Windows Phone 8](upgrade.html)
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/platforms/wp8/plugin.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/wp8/plugin.md b/www/docs/en/6.x/guide/platforms/wp8/plugin.md
index 7153275..dae70e5 100644
--- a/www/docs/en/6.x/guide/platforms/wp8/plugin.md
+++ b/www/docs/en/6.x/guide/platforms/wp8/plugin.md
@@ -23,7 +23,7 @@ title: Windows Phone 8 Plugins
# Windows Phone 8 Plugins
This section provides details for how to implement native plugin code
-on the Windows Phone platform. Before reading this, see [Plugin Development Guide](../../hybrid/plugins/index.html)
+on the Windows Phone platform. Before reading this, see [Plugin Development Guide](../../hybrid/plugins/index.html)
for an overview of the plugin's structure and its common
JavaScript interface. This section continues to demonstrate the sample
_echo_ plugin that communicates from the Cordova webview to the native
@@ -70,7 +70,7 @@ most of the functionality you need:
See the
[BaseCommand.cs](https://github.com/apache/cordova-wp8/blob/master/wp8/template/cordovalib/Commands/BaseCommand.cs)
class for methods available for the plugin to override. For example,
-the plugin can capture '[pause](../../../cordova/events/events.pause.html)' and '[resume](../../../cordova/events/events.resume.html)' events.
+the plugin can capture [pause][PauseEvent] and [resume][ResumeEvent] events.
## Namespaces
@@ -236,3 +236,6 @@ yourself of errors.
calling `exec()`. Doing so allows you to re-use more code and pull
unnecessary functionality from the plugin's various native
implementations.
+
+[PauseEvent]: ../../../cordova/events/events.html#pause
+[ResumeEvent]: ../../../cordova/events/events.html#resume
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/guide/support/index.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/support/index.md b/www/docs/en/6.x/guide/support/index.md
index 1b926ee..8d4af80 100644
--- a/www/docs/en/6.x/guide/support/index.md
+++ b/www/docs/en/6.x/guide/support/index.md
@@ -17,7 +17,7 @@ license: >
specific language governing permissions and limitations
under the License.
-title: Platform Support
+title: Corodva support by platform
---
# Platform Support
@@ -35,14 +35,12 @@ CLI's shorthand names.
<thead>
<tr>
<th></td>
- <th>amazon-fireos</th>
<th>android</th>
<th>blackberry10</th>
- <th>Firefox OS</th>
<th>ios</th>
<th>Ubuntu</th>
<th>wp8<br/>(Windows Phone 8)</th>
- <th>windows<br/>(8.0, 8.1, 10,<br/>Phone 8.1)</th>
+ <th>windows<br/>(8.1, 10,<br/>Phone 8.1)</th>
</tr>
</thead>
@@ -50,10 +48,8 @@ CLI's shorthand names.
<tbody>
<tr>
<th><a href="../cli/index.html">cordova<br/>CLI</a></th>
- <td data-col="amazon-fireos" class="y">Mac, Windows, Linux</td>
<td data-col="android" class="y">Mac, Windows, Linux</td>
<td data-col="blackberry10" class="y">Mac, Windows</td>
- <td data-col="firefoxos" class="y">Mac, Windows, Linux</td>
<td data-col="ios" class="y">Mac</td>
<td data-col="ubuntu" class="y">Ubuntu</td>
<td data-col="winphone8" class="y">Windows</td>
@@ -62,10 +58,8 @@ CLI's shorthand names.
<tr>
<th><a href="../hybrid/webviews/index.html">Embedded<br/>WebView</a></th>
- <td data-col="amazon-fireos" class="y"><a href="../platforms/amazonfireos/webview.html">(see details)</a></td>
<td data-col="android" class="y"><a href="../platforms/android/webview.html">(see details)</a></td>
<td data-col="blackberry10" class="n"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"><a href="../platforms/ios/webview.html">(see details)</a></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="n"></td>
@@ -73,11 +67,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="../hybrid/plugins/index.html">Plug-in<br/>Interface</a></th>
- <td data-col="amazon-fireos" class="y"><a href="../platforms/amazonfireos/plugin.html">(see details)</a></td>
+ <th><a href="../hybrid/plugins/index.html">Plugin<br/>Interface</a></th>
<td data-col="android" class="y"><a href="../platforms/android/plugin.html">(see details)</a></td>
<td data-col="blackberry10" class="y"><a href="../platforms/blackberry10/plugin.html">(see details)</a></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"><a href="../platforms/ios/plugin.html">(see details)</a></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"><a href="../platforms/wp8/plugin.html">(see details)</a></td>
@@ -86,15 +78,13 @@ CLI's shorthand names.
<tr>
<th></th>
- <th colspan="20">Platform APIs</th>
+ <th colspan="20"><h2>Core Plugin APIs</h2></th>
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-device-motion">Accelerometer</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-device-motion/">Accelerometer</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -102,11 +92,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-battery-status">BatteryStatus</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-battery-status/">BatteryStatus</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="n"></td>
<td data-col="winphone8" class="y"></td>
@@ -114,11 +102,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-camera">Camera</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-camera/">Camera</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -126,11 +112,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-media-capture">Capture</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-media-capture/">Capture</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -138,11 +122,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-device-orientation">Compass</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-device-orientation/">Compass</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y">(3GS+)</td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -150,11 +132,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-network-information">Connection</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-network-information/">Connection</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -162,11 +142,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-contacts">Contacts</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-contacts/">Contacts</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -174,11 +152,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-device">Device</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-device/">Device</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -187,10 +163,8 @@ CLI's shorthand names.
<tr>
<th><a href="../../cordova/events/events.html">Events</a></th>
- <td data-col="amazon-fireos" class="y"></td>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -198,11 +172,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-file">File</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-file">File</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -210,11 +182,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-file-transfer">File Transfer</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-file-transfer/">File Transfer</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y">* Do not support onprogress nor abort</td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="n"></td>
<td data-col="winphone8" class="y">* Do not support onprogress nor abort</td>
@@ -222,11 +192,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-geolocation">Geolocation</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-geolocation/">Geolocation</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -234,11 +202,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-globalization">Globalization</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-globalization/">Globalization</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -246,11 +212,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-inappbrowser">InAppBrowser</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-inappbrowser/">InAppBrowser</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -258,11 +222,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-media">Media</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-media/">Media</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -270,11 +232,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-dialogs">Notification</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-dialogs/">Notification</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -282,11 +242,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-splashscreen">Splashscreen</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-splashscreen/">Splashscreen</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y"></td>
@@ -294,11 +252,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-statusbar">Status Bar</a></th>
- <td data-col="amazon-fireos" class="n"></td>
+ <th><a href="../../cordova-plugin-statusbar/">Status Bar</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="n"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="n"></td>
<td data-col="winphone8" class="y"></td>
@@ -307,10 +263,8 @@ CLI's shorthand names.
<tr>
<th><a href="../../cordova/storage/storage.html">Storage</a></th>
- <td data-col="amazon-fireos" class="y"></td>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="n"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="y"></td>
<td data-col="winphone8" class="y">localStorage & indexedDB</td>
@@ -318,11 +272,9 @@ CLI's shorthand names.
</tr>
<tr>
- <th><a href="https://www.npmjs.com/package/cordova-plugin-vibration">Vibration</a></th>
- <td data-col="amazon-fireos" class="y"></td>
+ <th><a href="../../cordova-plugin-vibration/">Vibration</a></th>
<td data-col="android" class="y"></td>
<td data-col="blackberry10" class="y"></td>
- <td data-col="firefoxos" class="y"></td>
<td data-col="ios" class="y"></td>
<td data-col="ubuntu" class="n"></td>
<td data-col="winphone8" class="y"></td>
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/index.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/index.md b/www/docs/en/6.x/index.md
index aa15fa2..ba58216 100644
--- a/www/docs/en/6.x/index.md
+++ b/www/docs/en/6.x/index.md
@@ -37,10 +37,6 @@ title: Guides
<span>Create, build, and deploy from the command-line.</span>
</li>
<li>
- <h2><a href="guide/platforms/index.html">Platform Guides</a></h2>
- <span>Set up each platform SDK and update projects.</span>
- </li>
- <li>
<h2><a href="plugin_ref/plugman.html">Using Plugman to Manage Plugins</a></h2>
<span>Manage plugins without the CLI when using the platform-centered workflow.</span>
</li>
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/28d8c235/www/docs/en/6.x/plugin_ref/plugman.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/plugin_ref/plugman.md b/www/docs/en/6.x/plugin_ref/plugman.md
index eb1f856..b7449fb 100644
--- a/www/docs/en/6.x/plugin_ref/plugman.md
+++ b/www/docs/en/6.x/plugin_ref/plugman.md
@@ -68,21 +68,21 @@ with just `plugman`.
Before you can use Plugman, you must create a Cordova project. You can do this with either the Command-line Interface or with
the lower level shell scripts. Instructions for using the shell scripts to create your project are located in the various "Command-line Tools" guides
-listed on the [Platform Guides](../guide/platforms/index.html) page.
+listed on the Platform guides page.
## Adding a Plugin
Once you have installed Plugman and have created a Cordova project, you can start adding plugins to the platform with:
- $ plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin <name|url|path> [--plugins_dir <directory>] [--www <directory>] [--variable <name>=<value> [--variable <name>=<value> ...]]
+ $ plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin <name|url|path> [--plugins_dir <directory>] [--www <directory>] [--variable <name>=<value> [--variable <name>=<value> ...]]
Using minimum parameters, this command installs a plugin into a cordova project. You must specify a platform and cordova project location for that platform. You also must specify a plugin, with the different `--plugin` parameter forms being:
* `name`: The directory name where the plugin contents exist. This must be an existing directory under the `--plugins_dir` path (see below for more info) or a plugin in the Cordova registry.
* `url`: A URL starting with https:// or git://, pointing to a valid git repository that is clonable and contains a `plugin.xml` file. The contents of this repository would be copied into the `--plugins_dir`.
* `path`: A path to a directory containing a valid plugin which includes a `plugin.xml` file. This path's contents will be copied into the `--plugins_dir`.
-
-Other parameters:
+
+Other parameters:
* `--plugins_dir` defaults to `<project>/cordova/plugins`, but can be any directory containing a subdirectory for each fetched plugin.
* `--www` defaults to the project's `www` folder location, but can be any directory that is to be used as cordova project application web assets.
@@ -92,7 +92,7 @@ Other parameters:
To uninstall a plugin, you simply pass the `--uninstall` flag and provide the plugin ID.
- $ plugman --uninstall --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin <id> [--www <directory>] [--plugins_dir <directory>]
+ $ plugman --uninstall --platform <ios|android|blackberry10|wp8> --project <directory> --plugin <id> [--www <directory>] [--plugins_dir <directory>]
## Help Commands
@@ -107,7 +107,7 @@ a list of all available Plugman commands and their syntax:
You can also append the `--debug|-d` flag to any Plugman command to run that command in verbose mode, which will display
-any internal debugging messages as they are emitted and may help you track down problems like missing files.
+any internal debugging messages as they are emitted and may help you track down problems like missing files.
# Adding Android battery-status plugin to "myProject":
plugman -d --platform android --project myProject --plugin cordova-plugin-battery-status
@@ -115,7 +115,7 @@ any internal debugging messages as they are emitted and may help you track down
Finally, you can use the `--version|-v` flag to see which version of Plugman you are using.
plugman -v
-
+
## Registry Actions
There are a number of plugman commands that can be used for interacting with the [Plugin registry](http://plugins.cordova.io).
@@ -141,7 +141,7 @@ You can get information about any specific plugin stored in the plugin repositor
plugman info <id>
-This will contact the plugin registry and fetch information such as the plugin's version number.
+This will contact the plugin registry and fetch information such as the plugin's version number.
## Installing Core Plugins
@@ -152,72 +152,72 @@ platform, and reference the platform's project directory.
* cordova-plugin-battery-status
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-battery-status`
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-battery-status`
* cordova-plugin-camera
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-camera`
-
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-camera`
+
* cordova-plugin-console
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-console`
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-console`
* cordova-plugin-contacts
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-contacts`
-
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-contacts`
+
* cordova-plugin-device
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device`
* cordova-plugin-device-motion (accelerometer)
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-motion`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-motion`
* cordova-plugin-device-orientation (compass)
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-orientation`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-orientation`
* cordova-plugin-dialogs
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-dialogs`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-dialogs`
* cordova-plugin-file
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file`
* cordova-plugin-file-transfer
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file-transfer`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file-transfer`
* cordova-plugin-geolocation
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-geolocation`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-geolocation`
* cordova-plugin-globalization
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-globalization`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-globalization`
* cordova-plugin-inappbrowser
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-inappbrowser`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-inappbrowser`
* cordova-plugin-media
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media`
* cordova-plugin-media-capture
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media-capture`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media-capture`
* cordova-plugin-network-information
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-network-information`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-network-information`
* cordova-plugin-splashscreen
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-splashscreen`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-splashscreen`
* cordova-plugin-vibration
-
- `plugman --platform <ios|amazon-fireos|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-vibration`
+
+ `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-vibration`
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org