You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by ag...@apache.org on 2014/03/31 22:26:36 UTC
[09/31] docs commit: [CB-5122] rename 'Platform' guides to
'Installation' guides
[CB-5122] rename 'Platform' guides to 'Installation' guides
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/b731f46e
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/b731f46e
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/b731f46e
Branch: refs/heads/master
Commit: b731f46e82f60923b3185492af41d4154fb31764
Parents: 9ddf3c8
Author: Mike Sierra <ms...@adobe.com>
Authored: Tue Nov 5 08:52:28 2013 -0500
Committer: Mike Sierra <ms...@adobe.com>
Committed: Tue Nov 5 08:52:28 2013 -0500
----------------------------------------------------------------------
docs/en/edge/guide/platforms/android/index.md | 205 -----------------
docs/en/edge/guide/platforms/android/install.md | 205 +++++++++++++++++
.../en/edge/guide/platforms/blackberry/index.md | 207 -----------------
.../edge/guide/platforms/blackberry/install.md | 207 +++++++++++++++++
.../edge/guide/platforms/blackberry10/index.md | 205 -----------------
.../guide/platforms/blackberry10/install.md | 205 +++++++++++++++++
docs/en/edge/guide/platforms/ios/index.md | 225 -------------------
docs/en/edge/guide/platforms/ios/install.md | 225 +++++++++++++++++++
docs/en/edge/guide/platforms/tizen/index.md | 116 ----------
docs/en/edge/guide/platforms/tizen/install.md | 116 ++++++++++
docs/en/edge/guide/platforms/win8/index.md | 122 ----------
docs/en/edge/guide/platforms/win8/install.md | 122 ++++++++++
docs/en/edge/guide/platforms/wp7/index.md | 131 -----------
docs/en/edge/guide/platforms/wp7/install.md | 131 +++++++++++
docs/en/edge/guide/platforms/wp8/index.md | 162 -------------
docs/en/edge/guide/platforms/wp8/install.md | 162 +++++++++++++
16 files changed, 1373 insertions(+), 1373 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/index.md b/docs/en/edge/guide/platforms/android/index.md
deleted file mode 100644
index 14f8ddd..0000000
--- a/docs/en/edge/guide/platforms/android/index.md
+++ /dev/null
@@ -1,205 +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.
----
-
-# Android Installation Guide
-
-This section shows how to set up your SDK environment to deploy
-Cordova apps for Android devices. You need to install the Android SDK
-regardless of whether you want to use the cross-platform Cordova CLI
-for development, or a narrower set of platform-centered command-line
-tools. For a comparison of the two development paths, see the
-Overview. For details on each, see The Command-Line Interface and the
-Android Development Guide.
-
-## Requirements and Support
-
-See the [System Requirements](http://developer.android.com/sdk/index.html)
-for the Android SDK.
-
-Cordova supports Android 2.2, 2.3, and 4.x. As a general rule,
-platforms are deprecated as they dip below 5% on Google's
-[distribution dashboard](http://developer.android.com/about/dashboards/index.html).
-
-<!--
-NOTE, doc said:
-- Android 2.1 (Deprecated May 2013)
-- Android 3.x (Deprecated May 2013)
--->
-
-Developers should use the `cordova` utility in conjunction with
-the Android SDK. See The Command-line Interface for
-information how to install it, add projects, then build and deploy a
-project.
-
-## Install the SDK
-
-Install the Android SDK from
-[developer.android.com/sdk](http://developer.android.com/sdk/). You
-may be presented with a choice of where to install the SDK, otherwise
-move the downloaded `adt-bundle` tree to wherever you store
-development tools.
-
-For Cordova command-line tools to work, you need to include the SDK's
-`tools` and `platform-tools` directories in your PATH environment. On
-Mac, you can use a text editor to create or modify the
-`~/.bash_profile` file, adding a line such as the following, depending
-on where the SDK installs:
-
- export PATH=${PATH}:/Development/adt-bundle/sdk/platform-tools:/Development/adt-bundle/sdk/tools
-
-This exposes SDK tools in newly opened terminal windows. Otherwise run
-this to make them available in the current session:
-
- $ source ~/.bash_profile
-
-To modify the PATH environment on Windows 7:
-
-* Click on the __Start__ menu in the lower-left corner of the desktop,
- right-click on __Computer__, then click __Properties__.
-
-* Click __Advanced System Settings__ in the column on the left.
-
-* In the resulting dialog box, press __Environment Variables__.
-
-* Select the __PATH__ variable and press __Edit__.
-
-* Append the following to the PATH based on where you installed the
- SDK, for example:
-
- ;C:\Development\adt-bundle\sdk\platform-tools;C:\Development\adt-bundle\sdk\tools
-
-* Save the value and close both dialog boxes.
-
-You may also need to enable Java and Ant. Open a command prompt and
-type `java`, and also type `ant`. Append to the PATH whichever fail to
-run:
-
- ;%JAVA_HOME%\bin;%ANT_HOME%\bin
-
-## Open a Project in the SDK
-
-Use the `cordova` utility to set up a new project, as described in The
-Cordova The Command-line Interface. For example, in a source-code directory:
-
- $ cordova create hello com.example.hello "HelloWorld"
- $ cd hello
- $ cordova platform add android
- $ cordova build
-
-Once created, here's how to use the SDK to modify it:
-
-* Launch the __Eclipse__ application.
-
-* Select the __New Project__ menu item.
-
-* Choose __Android Project from Existing Code__ from the resulting dialog box, and press __Next__:
- 
-
-* Navigate to `hello`, or whichever directory you created for the project, then to the `platforms/android` subdirectory.
-
-* Press __Finish__.
-
-Once the Eclipse window opens, a red __X__ may appear to indicate
-unresolved problems. If so, follow these additional steps:
-
-* Right-click on the project directory.
-
-* In the resulting __Properties__ dialog, select __Android__ from the navigation pane.
-
-* For the project build target, select the highest Android API level you have installed.
-
-* Click __OK__.
-
-* Select __Clean__ from the __Project__ menu. This should correct all the errors in the project.
-
-## Deploy to Emulator
-
-You can use the `cordova` utility to run an app in an emulator, or you
-can run it within the SDK. Either way, the SDK must first be
-configured to display at least one device. To do so, use the Android
-SDK Manager, a Java application that runs separately from Eclipse.
-There are two ways to open it:
-
-* Run `android` on the command line.
-
-* From within Eclipse, press this toolbar icon:
-
- 
-
-Once open, the Android SDK Manager displays various runtime libraries:
-
-
-
-Choose __Tools → Manage AVDs__ (Android Virtual Devices), then
-choose any item from __Device Definitions__ in the resulting dialog
-box:
-
-
-
-Press __Create AVD__, optionally modifying the name, then press __OK__
-to accept the changes:
-
-
-
-The AVD then appears in the __Android Virtual Devices__ list:
-
-
-
-To open the emulator as a separate application, select the AVD and
-press __Start__. It launches much as it would on the device, with
-additional controls available for hardware buttons:
-
-
-
-At this point you can use the `cordova` utility to deploy the
-application to the emulator from the command line:
-
- $ cordova emulate android
-
-If instead you are working within Eclipse, right-click the project and
-choose __Run As → Android Application__. You may be asked to
-specify an AVD if none are already open.
-
-For a faster experience, use an Intel-based emulator image:
-
-* Install one or more `Intel x86 Atom` System Images as well as the
- `Intel Hardware Accelerated Execution Manager`, available under
- __Extras__.
-
-* Run the Intel installer, which is available within your Android SDK
- at `extras/intel/Hardware_Accelerated_Execution_Manager`.
-
-* Create a new AVD with the target set to an Intel image.
-
-* When starting the emulator, ensure there are no error messages
- indicating a failure to load HAX modules.
-
-## Deploy to Device
-
-To push an app directly to the device, make sure USB debugging is
-enabled on your device as described on the
-[Android Developer Site](http://developer.android.com/tools/device.html),
-and use a mini USB cable to plug it into your system.
-
-You can push the app to the device from the command line:
-
- $ cordova run android
-
-Alternately within Eclipse, right-click the project and choose __Run
-As → Android Application__.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/android/install.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/install.md b/docs/en/edge/guide/platforms/android/install.md
new file mode 100644
index 0000000..14f8ddd
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/install.md
@@ -0,0 +1,205 @@
+---
+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.
+---
+
+# Android Installation Guide
+
+This section shows how to set up your SDK environment to deploy
+Cordova apps for Android devices. You need to install the Android SDK
+regardless of whether you want to use the cross-platform Cordova CLI
+for development, or a narrower set of platform-centered command-line
+tools. For a comparison of the two development paths, see the
+Overview. For details on each, see The Command-Line Interface and the
+Android Development Guide.
+
+## Requirements and Support
+
+See the [System Requirements](http://developer.android.com/sdk/index.html)
+for the Android SDK.
+
+Cordova supports Android 2.2, 2.3, and 4.x. As a general rule,
+platforms are deprecated as they dip below 5% on Google's
+[distribution dashboard](http://developer.android.com/about/dashboards/index.html).
+
+<!--
+NOTE, doc said:
+- Android 2.1 (Deprecated May 2013)
+- Android 3.x (Deprecated May 2013)
+-->
+
+Developers should use the `cordova` utility in conjunction with
+the Android SDK. See The Command-line Interface for
+information how to install it, add projects, then build and deploy a
+project.
+
+## Install the SDK
+
+Install the Android SDK from
+[developer.android.com/sdk](http://developer.android.com/sdk/). You
+may be presented with a choice of where to install the SDK, otherwise
+move the downloaded `adt-bundle` tree to wherever you store
+development tools.
+
+For Cordova command-line tools to work, you need to include the SDK's
+`tools` and `platform-tools` directories in your PATH environment. On
+Mac, you can use a text editor to create or modify the
+`~/.bash_profile` file, adding a line such as the following, depending
+on where the SDK installs:
+
+ export PATH=${PATH}:/Development/adt-bundle/sdk/platform-tools:/Development/adt-bundle/sdk/tools
+
+This exposes SDK tools in newly opened terminal windows. Otherwise run
+this to make them available in the current session:
+
+ $ source ~/.bash_profile
+
+To modify the PATH environment on Windows 7:
+
+* Click on the __Start__ menu in the lower-left corner of the desktop,
+ right-click on __Computer__, then click __Properties__.
+
+* Click __Advanced System Settings__ in the column on the left.
+
+* In the resulting dialog box, press __Environment Variables__.
+
+* Select the __PATH__ variable and press __Edit__.
+
+* Append the following to the PATH based on where you installed the
+ SDK, for example:
+
+ ;C:\Development\adt-bundle\sdk\platform-tools;C:\Development\adt-bundle\sdk\tools
+
+* Save the value and close both dialog boxes.
+
+You may also need to enable Java and Ant. Open a command prompt and
+type `java`, and also type `ant`. Append to the PATH whichever fail to
+run:
+
+ ;%JAVA_HOME%\bin;%ANT_HOME%\bin
+
+## Open a Project in the SDK
+
+Use the `cordova` utility to set up a new project, as described in The
+Cordova The Command-line Interface. For example, in a source-code directory:
+
+ $ cordova create hello com.example.hello "HelloWorld"
+ $ cd hello
+ $ cordova platform add android
+ $ cordova build
+
+Once created, here's how to use the SDK to modify it:
+
+* Launch the __Eclipse__ application.
+
+* Select the __New Project__ menu item.
+
+* Choose __Android Project from Existing Code__ from the resulting dialog box, and press __Next__:
+ 
+
+* Navigate to `hello`, or whichever directory you created for the project, then to the `platforms/android` subdirectory.
+
+* Press __Finish__.
+
+Once the Eclipse window opens, a red __X__ may appear to indicate
+unresolved problems. If so, follow these additional steps:
+
+* Right-click on the project directory.
+
+* In the resulting __Properties__ dialog, select __Android__ from the navigation pane.
+
+* For the project build target, select the highest Android API level you have installed.
+
+* Click __OK__.
+
+* Select __Clean__ from the __Project__ menu. This should correct all the errors in the project.
+
+## Deploy to Emulator
+
+You can use the `cordova` utility to run an app in an emulator, or you
+can run it within the SDK. Either way, the SDK must first be
+configured to display at least one device. To do so, use the Android
+SDK Manager, a Java application that runs separately from Eclipse.
+There are two ways to open it:
+
+* Run `android` on the command line.
+
+* From within Eclipse, press this toolbar icon:
+
+ 
+
+Once open, the Android SDK Manager displays various runtime libraries:
+
+
+
+Choose __Tools → Manage AVDs__ (Android Virtual Devices), then
+choose any item from __Device Definitions__ in the resulting dialog
+box:
+
+
+
+Press __Create AVD__, optionally modifying the name, then press __OK__
+to accept the changes:
+
+
+
+The AVD then appears in the __Android Virtual Devices__ list:
+
+
+
+To open the emulator as a separate application, select the AVD and
+press __Start__. It launches much as it would on the device, with
+additional controls available for hardware buttons:
+
+
+
+At this point you can use the `cordova` utility to deploy the
+application to the emulator from the command line:
+
+ $ cordova emulate android
+
+If instead you are working within Eclipse, right-click the project and
+choose __Run As → Android Application__. You may be asked to
+specify an AVD if none are already open.
+
+For a faster experience, use an Intel-based emulator image:
+
+* Install one or more `Intel x86 Atom` System Images as well as the
+ `Intel Hardware Accelerated Execution Manager`, available under
+ __Extras__.
+
+* Run the Intel installer, which is available within your Android SDK
+ at `extras/intel/Hardware_Accelerated_Execution_Manager`.
+
+* Create a new AVD with the target set to an Intel image.
+
+* When starting the emulator, ensure there are no error messages
+ indicating a failure to load HAX modules.
+
+## Deploy to Device
+
+To push an app directly to the device, make sure USB debugging is
+enabled on your device as described on the
+[Android Developer Site](http://developer.android.com/tools/device.html),
+and use a mini USB cable to plug it into your system.
+
+You can push the app to the device from the command line:
+
+ $ cordova run android
+
+Alternately within Eclipse, right-click the project and choose __Run
+As → Android Application__.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/index.md b/docs/en/edge/guide/platforms/blackberry/index.md
deleted file mode 100644
index dcd4a96..0000000
--- a/docs/en/edge/guide/platforms/blackberry/index.md
+++ /dev/null
@@ -1,207 +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.
----
-
-# BlackBerry Installation Guide
-
-This section shows how to set up your SDK environment to deploy
-Cordova apps for BlackBerry devices prior to BlackBerry version 10.
-For BlackBerry 10, you need to use a different SDK environment,
-described in the BlackBerry 10 Installation Guide. You can't use the
-Cordova CLI (described in The Command-Line Interface) for development
-prior to version 10. Instead, you develop with a set of
-platform-centered shell tools described in BlackBerry Development
-Guide.
-
-## Requirements and Support
-
-This version of BlackBerry is not supported by the `cordova` utility
-described in The Command-line Interface, but by a separate set of
-command-line tools. Download the Cordova distribution from
-[cordova.apache.org](http://cordova.apache.org/#download).
-
-Cordova for BlackBerry relies on the [BlackBerry WebWorks
-framework](https://bdsc.webapps.blackberry.com/html5), which is
-available for Windows XP (32-bit), Windows 7 (32-bit and 64-bit), and
-Mac (OS X 10.6.4+). WebWorks applications can _only_ be deployed on
-the following BlackBerry platforms:
-
-* BlackBerry OS 5.0 and higher
-* BlackBerry PlayBook
-* BlackBerry 10 (QNX)
-
-WebWorks requires the Java Development Kit (JDK). For Windows, use the
-32-bit version of
-[Oracle JDK](http://www.oracle.com/technetwork/java/javase/downloads/index.html#jdk).
-Java in installed by default on Mac OS X up to version 10.7, which
-requires
-[a separate installation](http://support.apple.com/kb/DL1421).
-It also requires Apache Ant, which on Mac is part of the Java
-installation. The Windows version is available from
-[ant.apache.org](http://ant.apache.org/bindownload.cgi).
-
-## Install the SDK
-
-Download and install the appropriate WebWorks SDK for your
-development. BlackBerry PlayBook and BlackBerry Smartphone WebWorks
-SDKs can be downloaded from the following locations.
-
-- [BlackBerry PlayBook SDK] (https://developer.blackberry.com/html5/download/#playbook) and [Adobe Air SDK](http://www.adobe.com/devnet/air/air-sdk-download.html)
-
-- [BlackBerry Smartphones SDK] (https://developer.blackberry.com/html5/download/#smartphones)
-
-## Register for Signing Keys
-
-If you wish to publish your application on BlackBerry App World, or on
-an actual device, you’ll need to register for a set of free Code
-Signing Keys. To do so, complete the [BlackBerry Keys Order
-Form](https://www.blackberry.com/SignedKeys).
-Once you receive your Signing Keys, they require setup. See the [BlackBerry HTML5/WebWorks website](https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html) for information.
-
-## Install Cordova
-
-Download and extract the latest copy of [Cordova](http://cordova.apache.org/#download).
-
-## Set up a New Project
-
-- Open up a command-line terminal and navigate to where you extracted Cordova.
-
-- There is a directory for each platform that Cordova supports.
- Navigate to the `blackberry` directory.
-
-- The `blackberry` directory contains several subdirectories. The
- `example` directory contains a complete Cordova project. Copy the
- `example` directory to another location on your computer, and
- navigate there.
-
-- Edit the `project.properties` file to specify the WebWorks SDK you
- are using. For example, here are the respective settings for
- BlackBerry PlayBook, BlackBerry Smartphone (OS5-7), or BlackBerry 10
- (QNX):
-
- playbook.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks SDK for TabletOS 2.1.0.6\\bbwp
- blackberry.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks Packager
- qnx.bbwp.dir=C:\\Program Files (x86)\\Research In Motion\\BlackBerry 10 WebWorks SDK 1.0.2.9
-
-These correspond to parameters you specify when building your
-project. The first time you run these commands, they generate a
-"HelloWorld" application:
-
- cordova/build playbook
- cordova/build blackberry
- cordova/build qnx
-
-Along with the SDK, you also need to register for a code signing key
-and debug token. The signing key allows you to distribute apps through
-BlackBerry World. The debug token allows you to test unsigned apps on
-a BlackBerry emulator or device. You do not need to create and
-install the debug token yourself; if you supply the keystore password,
-the build script creates and installs the debug token for you. To set
-up the signing key, go to the BlackBerry website to obtain it, making
-sure to retain the password you specify. Then run the
-`blackberry-signer` utility that is included with the SDK.
-BlackBerry provides more information here:
-
-* [Register for your code signing key](https://www.blackberry.com/SignedKeys/codesigning.html)
-
-* [Set up your computer for code signing](http://developer.blackberry.com/html5/documentation/set_up_for_signing.html)
-
-* [comprehensive guide to setting up your SDK environment](http://developer.blackberry.com/native/documentation/bb10/com.qnx.doc.native_sdk.quickstart/topic/set_up_your_environment.html)
-
-## Deploy to Emulator
-
-BlackBerry smartphone emulators are only available on Windows.
-BlackBerry PlayBook emulators require VMWare Player (Windows) or
-VMWare Fusion (Mac OS X). The WebWorks SDK provides a default
-emulator, but additional emulators are [available through
-BlackBerry](http://us.blackberry.com/developers/resources/simulators.jsp).
-
-From your project directory, type `./cordova/run <target>`, replacing
-`<target>` with either `qnx`, `playbook`, or `blackberry`. Note that
-for BlackBerry 10 and PlayBook, the emulator virtual image must
-already be started.
-
-See the following for more information:
-
-* [BlackBerry PlayBook](https://developer.blackberry.com/html5/documentation/using_the_tablet_simulator_1866980_11.html)
-
-* [BlackBerry Smartphone](https://developer.blackberry.com/html5/documentation/run_your_app_on_smartphone_sim_1876976_11.html)
-
-For BlackBerry Playbook, edit the `project.properties` file to
-customize the `playbook.sim.ip` and `playbook.sim.password`
-properties. The emulator's IP address is available through the
-__Settings__ application on the home screen. Enable the __Security and
-Privacy → Development Mode__ option to display the address. The
-password can also be set in the __Security and Privacy__ tab.
-
-For BlackBerry Smartphone, edit the `project.properties` file to
-customize the `blackberry.sim.dir` and `blackberry.sim.bin`
-properties. You need to escape path delimiters when specifying
-directory paths on Windows, for example: `C:\\Program
-Files\\BlackBerry\\Simulator`.
-
-Once the emulator is installed and running, run either of the
-following to install an application to the home screen:
-
- cordova/run playbook
- cordova/run blackberry
-
-If you are prompted whether a device is connected to your computer,
-answer no.
-
-__NOTE:__ On BlackBerry OS 5, the application is installed in the
-`Downloads` directory.
-
-## Deploy to Device
-
-To deploy the app to a device, it must be connected, and you must be
-registered for code signing keys as described above. Also, to deploy
-apps on BlackBerry PlayBook, the __Settings → Security →
-Development Mode__ option must be enabled.
-
-On BlackBerry PlayBook, edit the `project.properties` file and modify
-the following to reflect the device's IP and password as descibed
-above, along with the signing key password you set up:
-
-From your project directory, type `./cordova/run <target>`, replacing
-`<target>` with either `qnx`, `playbook`, or `blackberry`.
-
-On BlackBerry Smartphone (OS5-7), specify the
-`blackberry.sigtool.password` property as the signing key password.
-
-Then from the project's directory, run either of the commands you
-would to view the app in an emulator:
-
- cordova/run playbook
- cordova/run blackberry
-
-If you are prompted whether a device is connected to your computer,
-answer yes.
-
-__NOTE:__ On BlackBerry OS 5, the application is installed in the
-`Downloads` directory.
-
-## Additional Information
-
-The following articles may help resolve common problems when
-developing applications built for the BlackBerry WebWorks framework:
-
-* [BlackBerry WebWorks Development Pitfalls](http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Common-BlackBerry-WebWorks-development-pitfalls-that-can-be/ta-p/624712)
-
-* [Best practices for packaging WebWorks applications](https://bdsc.webapps.blackberrycom/html5/documentation/ww_developing/bestpractice_compiling_ww_apps_1873324_11.html)
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/blackberry/install.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/install.md b/docs/en/edge/guide/platforms/blackberry/install.md
new file mode 100644
index 0000000..dcd4a96
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry/install.md
@@ -0,0 +1,207 @@
+---
+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.
+---
+
+# BlackBerry Installation Guide
+
+This section shows how to set up your SDK environment to deploy
+Cordova apps for BlackBerry devices prior to BlackBerry version 10.
+For BlackBerry 10, you need to use a different SDK environment,
+described in the BlackBerry 10 Installation Guide. You can't use the
+Cordova CLI (described in The Command-Line Interface) for development
+prior to version 10. Instead, you develop with a set of
+platform-centered shell tools described in BlackBerry Development
+Guide.
+
+## Requirements and Support
+
+This version of BlackBerry is not supported by the `cordova` utility
+described in The Command-line Interface, but by a separate set of
+command-line tools. Download the Cordova distribution from
+[cordova.apache.org](http://cordova.apache.org/#download).
+
+Cordova for BlackBerry relies on the [BlackBerry WebWorks
+framework](https://bdsc.webapps.blackberry.com/html5), which is
+available for Windows XP (32-bit), Windows 7 (32-bit and 64-bit), and
+Mac (OS X 10.6.4+). WebWorks applications can _only_ be deployed on
+the following BlackBerry platforms:
+
+* BlackBerry OS 5.0 and higher
+* BlackBerry PlayBook
+* BlackBerry 10 (QNX)
+
+WebWorks requires the Java Development Kit (JDK). For Windows, use the
+32-bit version of
+[Oracle JDK](http://www.oracle.com/technetwork/java/javase/downloads/index.html#jdk).
+Java in installed by default on Mac OS X up to version 10.7, which
+requires
+[a separate installation](http://support.apple.com/kb/DL1421).
+It also requires Apache Ant, which on Mac is part of the Java
+installation. The Windows version is available from
+[ant.apache.org](http://ant.apache.org/bindownload.cgi).
+
+## Install the SDK
+
+Download and install the appropriate WebWorks SDK for your
+development. BlackBerry PlayBook and BlackBerry Smartphone WebWorks
+SDKs can be downloaded from the following locations.
+
+- [BlackBerry PlayBook SDK] (https://developer.blackberry.com/html5/download/#playbook) and [Adobe Air SDK](http://www.adobe.com/devnet/air/air-sdk-download.html)
+
+- [BlackBerry Smartphones SDK] (https://developer.blackberry.com/html5/download/#smartphones)
+
+## Register for Signing Keys
+
+If you wish to publish your application on BlackBerry App World, or on
+an actual device, you’ll need to register for a set of free Code
+Signing Keys. To do so, complete the [BlackBerry Keys Order
+Form](https://www.blackberry.com/SignedKeys).
+Once you receive your Signing Keys, they require setup. See the [BlackBerry HTML5/WebWorks website](https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html) for information.
+
+## Install Cordova
+
+Download and extract the latest copy of [Cordova](http://cordova.apache.org/#download).
+
+## Set up a New Project
+
+- Open up a command-line terminal and navigate to where you extracted Cordova.
+
+- There is a directory for each platform that Cordova supports.
+ Navigate to the `blackberry` directory.
+
+- The `blackberry` directory contains several subdirectories. The
+ `example` directory contains a complete Cordova project. Copy the
+ `example` directory to another location on your computer, and
+ navigate there.
+
+- Edit the `project.properties` file to specify the WebWorks SDK you
+ are using. For example, here are the respective settings for
+ BlackBerry PlayBook, BlackBerry Smartphone (OS5-7), or BlackBerry 10
+ (QNX):
+
+ playbook.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks SDK for TabletOS 2.1.0.6\\bbwp
+ blackberry.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks Packager
+ qnx.bbwp.dir=C:\\Program Files (x86)\\Research In Motion\\BlackBerry 10 WebWorks SDK 1.0.2.9
+
+These correspond to parameters you specify when building your
+project. The first time you run these commands, they generate a
+"HelloWorld" application:
+
+ cordova/build playbook
+ cordova/build blackberry
+ cordova/build qnx
+
+Along with the SDK, you also need to register for a code signing key
+and debug token. The signing key allows you to distribute apps through
+BlackBerry World. The debug token allows you to test unsigned apps on
+a BlackBerry emulator or device. You do not need to create and
+install the debug token yourself; if you supply the keystore password,
+the build script creates and installs the debug token for you. To set
+up the signing key, go to the BlackBerry website to obtain it, making
+sure to retain the password you specify. Then run the
+`blackberry-signer` utility that is included with the SDK.
+BlackBerry provides more information here:
+
+* [Register for your code signing key](https://www.blackberry.com/SignedKeys/codesigning.html)
+
+* [Set up your computer for code signing](http://developer.blackberry.com/html5/documentation/set_up_for_signing.html)
+
+* [comprehensive guide to setting up your SDK environment](http://developer.blackberry.com/native/documentation/bb10/com.qnx.doc.native_sdk.quickstart/topic/set_up_your_environment.html)
+
+## Deploy to Emulator
+
+BlackBerry smartphone emulators are only available on Windows.
+BlackBerry PlayBook emulators require VMWare Player (Windows) or
+VMWare Fusion (Mac OS X). The WebWorks SDK provides a default
+emulator, but additional emulators are [available through
+BlackBerry](http://us.blackberry.com/developers/resources/simulators.jsp).
+
+From your project directory, type `./cordova/run <target>`, replacing
+`<target>` with either `qnx`, `playbook`, or `blackberry`. Note that
+for BlackBerry 10 and PlayBook, the emulator virtual image must
+already be started.
+
+See the following for more information:
+
+* [BlackBerry PlayBook](https://developer.blackberry.com/html5/documentation/using_the_tablet_simulator_1866980_11.html)
+
+* [BlackBerry Smartphone](https://developer.blackberry.com/html5/documentation/run_your_app_on_smartphone_sim_1876976_11.html)
+
+For BlackBerry Playbook, edit the `project.properties` file to
+customize the `playbook.sim.ip` and `playbook.sim.password`
+properties. The emulator's IP address is available through the
+__Settings__ application on the home screen. Enable the __Security and
+Privacy → Development Mode__ option to display the address. The
+password can also be set in the __Security and Privacy__ tab.
+
+For BlackBerry Smartphone, edit the `project.properties` file to
+customize the `blackberry.sim.dir` and `blackberry.sim.bin`
+properties. You need to escape path delimiters when specifying
+directory paths on Windows, for example: `C:\\Program
+Files\\BlackBerry\\Simulator`.
+
+Once the emulator is installed and running, run either of the
+following to install an application to the home screen:
+
+ cordova/run playbook
+ cordova/run blackberry
+
+If you are prompted whether a device is connected to your computer,
+answer no.
+
+__NOTE:__ On BlackBerry OS 5, the application is installed in the
+`Downloads` directory.
+
+## Deploy to Device
+
+To deploy the app to a device, it must be connected, and you must be
+registered for code signing keys as described above. Also, to deploy
+apps on BlackBerry PlayBook, the __Settings → Security →
+Development Mode__ option must be enabled.
+
+On BlackBerry PlayBook, edit the `project.properties` file and modify
+the following to reflect the device's IP and password as descibed
+above, along with the signing key password you set up:
+
+From your project directory, type `./cordova/run <target>`, replacing
+`<target>` with either `qnx`, `playbook`, or `blackberry`.
+
+On BlackBerry Smartphone (OS5-7), specify the
+`blackberry.sigtool.password` property as the signing key password.
+
+Then from the project's directory, run either of the commands you
+would to view the app in an emulator:
+
+ cordova/run playbook
+ cordova/run blackberry
+
+If you are prompted whether a device is connected to your computer,
+answer yes.
+
+__NOTE:__ On BlackBerry OS 5, the application is installed in the
+`Downloads` directory.
+
+## Additional Information
+
+The following articles may help resolve common problems when
+developing applications built for the BlackBerry WebWorks framework:
+
+* [BlackBerry WebWorks Development Pitfalls](http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Common-BlackBerry-WebWorks-development-pitfalls-that-can-be/ta-p/624712)
+
+* [Best practices for packaging WebWorks applications](https://bdsc.webapps.blackberrycom/html5/documentation/ww_developing/bestpractice_compiling_ww_apps_1873324_11.html)
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/blackberry10/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry10/index.md b/docs/en/edge/guide/platforms/blackberry10/index.md
deleted file mode 100644
index 5f60b61..0000000
--- a/docs/en/edge/guide/platforms/blackberry10/index.md
+++ /dev/null
@@ -1,205 +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.
----
-
-# BlackBerry 10 Installation Guide
-
-This section shows how to set up your SDK environment to deploy
-Cordova apps for BlackBerry 10 devices. For previous versions of
-BlackBerry, you need to use a different SDK environment and set of
-command-line tools, described in the BlackBerry Installation Guide.
-For BlackBerry 10, you need to install the SDK regardless of whether
-you want to use the cross-platform Cordova CLI for development, or a
-narrower set of platform-centered command-line tools. For a
-comparison of the two development paths, see the Overview. For
-details on each, see The Command-Line Interface and the BlackBerry 10
-Development Guide.
-
-## Requirements
-
-The development environment is available on Windows, Mac and Linux.
-
-Developers should use the `cordova` utility in conjunction with the
-Blackberry Native SDK. See The Command-line Interface for information
-how to install `cordova`, add projects, then build and deploy for each
-platform.
-
-## Install the BlackBerry Native SDK
-
-The BlackBerry Native SDK is available from
-[developer.blackberry.com](http://developer.blackberry.com/native/download/).
-Following installation, you need to add its command-line tools to your
-system path.
-
-On Windows:
-
-* Go to __My Computer → Properties → Advanced → Environment Variables__.
-
-* Append the Native SDK's install directory to the PATH, for example:
-
- ;C:\bbndk\host_10_1_0_132\darwin\x86\usr\bin\
-
-On Mac and Linux:
-
-* Edit the `~/.bash_profile` file, adding a line such as the
- following, depending on where the Native SDK was installed:
-
- $ export PATH=${PATH}:/Applications/bbndk/host_10_1_0_132/darwin/x86/usr/bin/
-
- or for the 10.2 Native SDK:
-
- $ export PATH=${PATH}:/Applications/Momentics.app/host_10_2_0_15/darwin/x86/usr/bin/
-
-* Run the following to apply the change in the current session:
-
- $ source ~/.bash_profile
-
-## Set up for Signing
-
-If you wish to test on a device or distribute apps through BlackBerry
-World, your system must be setup for code signing.
-
-To obtain a signing key, go to the BlackBerry website and make sure to
-retain the password you specify. Then run the `blackberry-signer`
-utility that is included with the BlackBerry Native SDK.
-
-Detailed instuctions can be found here:
-
-* [Register for your code signing key.](https://www.blackberry.com/SignedKeys/codesigning.html)
-
-* [Set up your system for code signing.](https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html)
-
-## Create a Project
-
-Use the `cordova` utility to set up a new project, as described in The
-Command-line Interface. For example, in a source-code directory:
-
- $ cordova create hello com.example.hello
- $ cd hello
- $ cordova platform add blackberry10
- $ cordova build
-
-## Deploy to Emulator
-
-If you wish to run a device emulator, download and install the
-BlackBerry 10 Simulator.
-
-* [Download](http://developer.blackberry.com/native/download/)
-* [Getting Started](http://developer.blackberry.com/devzone/develop/simulator/blackberry_10_simulator_start.html)
-
-Before testing an app on either an emulator or a device, you need to
-add a _target_ to your project. Each is identified with a unique name,
-and associated with an IP address. You need to get the IP address from
-the emulator before you use it to view apps.
-
-Launch the emulator image, then choose __Settings__ from the home screen:
-
-
-
-Navigate to the __Security and Privacy → Development Mode__
-section, enable the option, and obtain the IP address:
-
-
-
-An additional set of command-line utilities are included when you set
-up the BlackBerry 10 platform for your project. The following
-command, in this case invoked from the project top-level directory,
-associates a target named _emu_ with the IP address displayed above.
-
-* On Windows:
-
- $ platforms\blackberry10\cordova\target.bat add emu 169.254.0.1 -t simulator
-
-* On Mac/Linux:
-
- $ platforms/blackberry10/cordova/target add emu 169.254.0.1 -t simulator
-
-Then, run the `emulate` command to view the app:
-
- $ cordova emulate blackberry10
-
-## Deploy to Device
-
-To deploy to a device, make sure it is plugged into your computer.
-Enable development mode and obtain the IP address as desribed in the
-emulator section above. You will also need to obtain the PIN from the
-the __Settings__ application under __About → Hardware__:
-
-
-
-Run the target command-line utility to associate a name with an IP
-address, device password and PIN.
-
-* On Windows:
-
- $ platforms\blackberry10\cordova\target.bat add mydevice 169.254.0.1 -t device --password 123456 --pin FFFF972E
-
-* On Mac/Linux:
-
- $ platforms/blackberry10/cordova/target add mydevice 169.254.0.1 -t device --password 123456 --pin FFFF972E
-
-where:
-
-* `--password` refers to the password to unlock the device.
-
-* `--pin` refers to the device PIN obtained from the __Settings__ application.
-
-Then, run the `run` command to view the app:
-
- $ cordova run blackberry10
-
-If a debug token is not yet set up for the device, an error message
-prompts you to use the platform run script with the password you
-provided when registering for signing keys.
-
-* On Windows:
-
- $ platforms\blackberry10\cordova\run.bat --device --keystorepass mysecret
-
-* On Mac/Linux:
-
- $ platforms/blackberry10/cordova/run --device --keystorepass mysecret
-
-## Debugging with WebInspector
-
-When debugging on the device or an emulator, you may run WebInspector
-remotely to view the application's internal state. A prompt displays
-the URL that allows you to connect to the app with a standard web
-browser. For more information, see
-[Debugging using WebInspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
-
-## Building a Release Version
-
-By default, running the `cordova build` command creates an unsigned
-_.bar_ package file suitable for testing on a device or simulator.
-
-You need to run a different `build` command to create a release
-version suitable for distribution through BlackBerry World. It does
-not rely on the `cordova` CLI tool, and instead uses the following
-syntax:
-
-* On Windows:
-
- $ platforms\blackberry10\cordova\build.bat --release --keystorepass mysecret
-
-* On Mac/Linux:
-
- $ platforms/blackberry10/cordova/build --release --keystorepass mysecret
-
-The `--keystorepass` option specifies the password you defined when
-configuring your computer to sign applications.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/blackberry10/install.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry10/install.md b/docs/en/edge/guide/platforms/blackberry10/install.md
new file mode 100644
index 0000000..5f60b61
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry10/install.md
@@ -0,0 +1,205 @@
+---
+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.
+---
+
+# BlackBerry 10 Installation Guide
+
+This section shows how to set up your SDK environment to deploy
+Cordova apps for BlackBerry 10 devices. For previous versions of
+BlackBerry, you need to use a different SDK environment and set of
+command-line tools, described in the BlackBerry Installation Guide.
+For BlackBerry 10, you need to install the SDK regardless of whether
+you want to use the cross-platform Cordova CLI for development, or a
+narrower set of platform-centered command-line tools. For a
+comparison of the two development paths, see the Overview. For
+details on each, see The Command-Line Interface and the BlackBerry 10
+Development Guide.
+
+## Requirements
+
+The development environment is available on Windows, Mac and Linux.
+
+Developers should use the `cordova` utility in conjunction with the
+Blackberry Native SDK. See The Command-line Interface for information
+how to install `cordova`, add projects, then build and deploy for each
+platform.
+
+## Install the BlackBerry Native SDK
+
+The BlackBerry Native SDK is available from
+[developer.blackberry.com](http://developer.blackberry.com/native/download/).
+Following installation, you need to add its command-line tools to your
+system path.
+
+On Windows:
+
+* Go to __My Computer → Properties → Advanced → Environment Variables__.
+
+* Append the Native SDK's install directory to the PATH, for example:
+
+ ;C:\bbndk\host_10_1_0_132\darwin\x86\usr\bin\
+
+On Mac and Linux:
+
+* Edit the `~/.bash_profile` file, adding a line such as the
+ following, depending on where the Native SDK was installed:
+
+ $ export PATH=${PATH}:/Applications/bbndk/host_10_1_0_132/darwin/x86/usr/bin/
+
+ or for the 10.2 Native SDK:
+
+ $ export PATH=${PATH}:/Applications/Momentics.app/host_10_2_0_15/darwin/x86/usr/bin/
+
+* Run the following to apply the change in the current session:
+
+ $ source ~/.bash_profile
+
+## Set up for Signing
+
+If you wish to test on a device or distribute apps through BlackBerry
+World, your system must be setup for code signing.
+
+To obtain a signing key, go to the BlackBerry website and make sure to
+retain the password you specify. Then run the `blackberry-signer`
+utility that is included with the BlackBerry Native SDK.
+
+Detailed instuctions can be found here:
+
+* [Register for your code signing key.](https://www.blackberry.com/SignedKeys/codesigning.html)
+
+* [Set up your system for code signing.](https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html)
+
+## Create a Project
+
+Use the `cordova` utility to set up a new project, as described in The
+Command-line Interface. For example, in a source-code directory:
+
+ $ cordova create hello com.example.hello
+ $ cd hello
+ $ cordova platform add blackberry10
+ $ cordova build
+
+## Deploy to Emulator
+
+If you wish to run a device emulator, download and install the
+BlackBerry 10 Simulator.
+
+* [Download](http://developer.blackberry.com/native/download/)
+* [Getting Started](http://developer.blackberry.com/devzone/develop/simulator/blackberry_10_simulator_start.html)
+
+Before testing an app on either an emulator or a device, you need to
+add a _target_ to your project. Each is identified with a unique name,
+and associated with an IP address. You need to get the IP address from
+the emulator before you use it to view apps.
+
+Launch the emulator image, then choose __Settings__ from the home screen:
+
+
+
+Navigate to the __Security and Privacy → Development Mode__
+section, enable the option, and obtain the IP address:
+
+
+
+An additional set of command-line utilities are included when you set
+up the BlackBerry 10 platform for your project. The following
+command, in this case invoked from the project top-level directory,
+associates a target named _emu_ with the IP address displayed above.
+
+* On Windows:
+
+ $ platforms\blackberry10\cordova\target.bat add emu 169.254.0.1 -t simulator
+
+* On Mac/Linux:
+
+ $ platforms/blackberry10/cordova/target add emu 169.254.0.1 -t simulator
+
+Then, run the `emulate` command to view the app:
+
+ $ cordova emulate blackberry10
+
+## Deploy to Device
+
+To deploy to a device, make sure it is plugged into your computer.
+Enable development mode and obtain the IP address as desribed in the
+emulator section above. You will also need to obtain the PIN from the
+the __Settings__ application under __About → Hardware__:
+
+
+
+Run the target command-line utility to associate a name with an IP
+address, device password and PIN.
+
+* On Windows:
+
+ $ platforms\blackberry10\cordova\target.bat add mydevice 169.254.0.1 -t device --password 123456 --pin FFFF972E
+
+* On Mac/Linux:
+
+ $ platforms/blackberry10/cordova/target add mydevice 169.254.0.1 -t device --password 123456 --pin FFFF972E
+
+where:
+
+* `--password` refers to the password to unlock the device.
+
+* `--pin` refers to the device PIN obtained from the __Settings__ application.
+
+Then, run the `run` command to view the app:
+
+ $ cordova run blackberry10
+
+If a debug token is not yet set up for the device, an error message
+prompts you to use the platform run script with the password you
+provided when registering for signing keys.
+
+* On Windows:
+
+ $ platforms\blackberry10\cordova\run.bat --device --keystorepass mysecret
+
+* On Mac/Linux:
+
+ $ platforms/blackberry10/cordova/run --device --keystorepass mysecret
+
+## Debugging with WebInspector
+
+When debugging on the device or an emulator, you may run WebInspector
+remotely to view the application's internal state. A prompt displays
+the URL that allows you to connect to the app with a standard web
+browser. For more information, see
+[Debugging using WebInspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
+
+## Building a Release Version
+
+By default, running the `cordova build` command creates an unsigned
+_.bar_ package file suitable for testing on a device or simulator.
+
+You need to run a different `build` command to create a release
+version suitable for distribution through BlackBerry World. It does
+not rely on the `cordova` CLI tool, and instead uses the following
+syntax:
+
+* On Windows:
+
+ $ platforms\blackberry10\cordova\build.bat --release --keystorepass mysecret
+
+* On Mac/Linux:
+
+ $ platforms/blackberry10/cordova/build --release --keystorepass mysecret
+
+The `--keystorepass` option specifies the password you defined when
+configuring your computer to sign applications.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/index.md b/docs/en/edge/guide/platforms/ios/index.md
deleted file mode 100644
index e4a8b13..0000000
--- a/docs/en/edge/guide/platforms/ios/index.md
+++ /dev/null
@@ -1,225 +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.
----
-
-# iOS Installation Guide
-
-This section shows how to set up your SDK environment to deploy
-Cordova apps for iOS devices. You need to install Xcode, iOS's SDK,
-regardless of whether you want to use the cross-platform Cordova CLI
-for development, or a narrower set of platform-centered command-line
-tools. For a comparison of the two development paths, see the
-Overview. For details on each, see The Command-Line Interface and the
-iOS Development Guide.
-
-## Requirements and Support
-
-Apple® tools required to build iOS applications run only on the OS X
-operating system on Intel-based Macs. Xcode® 4.5 (the minimum required
-version) runs only on OS X version 10.7 (Lion) or greater, and
-includes the iOS 6 SDK (Software Development Kit). To submit apps to
-the Apple App Store℠ requires the latest versions of the Apple tools.
-
-You can test many of the Cordova features using the iOS emulator
-installed with the iOS SDK and Xcode, but you need an actual device to
-fully test all of the app's device features before submitting to the
-App Store. The device must have at least iOS 5.x installed, the
-minimum iOS version supported as of Cordova 2.3. Supporting devices
-include all iPad® models, iPhone® 3GS and above, and iPod® Touch 3rd
-Generation or later. To install apps onto a device, you must also be a
-member of Apple's
-[iOS Developer Program](https://developer.apple.com/programs/ios/),
-which costs $99 per year. This guide shows how to deploy apps to the
-iOS emulator, for which you don't need to register with the developer
-program.
-
-## Install the SDK
-
-There are two ways to download Xcode:
-
-* from the [App Store](https://itunes.apple.com/us/app/xcode/id497799835?mt=12),
- available by searching for "Xcode" in the __App Store__ application.
-
-* from [Apple Developer Downloads](https://developer.apple.com/downloads/index.action),
- which requires registration as an Apple Developer.
-
-Once Xcode is installed, several command-line tools need to be enabled
-for Cordova to run. From the __Xcode__ menu, select __Preferences__,
-then the __Downloads__ tab. From the __Components__ panel, press the
-__Install__ button next to the __Command Line Tools__ listing.
-
-## Open a Project in the SDK
-
-Use the `cordova` utility to set up a new project, as described in The
-Cordova The Command-line Interface. For example, in a source-code directory:
-
- $ cordova create hello com.example.hello "HelloWorld"
- $ cd hello
- $ cordova platform add ios
- $ cordova prepare # or "cordova build"
-
-Once created, you can open it from within Xcode. Double-click to open
-the `hello/platforms/ios/hello.xcodeproj` file. The screen should
-look like this:
-
-
-
-## Deploy to Emulator
-
-To preview the app in the iOS emulator:
-
-1. Make sure the _.xcodeproj_ file is selected in the left panel.
-
-2. Select the __hello__ app in the panel immediately to the right.
-
-3. Select the intended device from the toolbar's __Scheme__ menu, such
- as the iPhone 6.0 Simulator as highlighted here:
-
- 
-
-4. Press the __Run__ button that appears in the same toolbar to the
- left of the __Scheme__. That builds, deploys and runs the
- application in the emulator. A separate emulator application opens
- to display the app:
-
- 
-
- Only one emulator may run at a time, so if you want to test the app
- in a different emulator, you need to quit the emulator application
- and run a different target within Xcode.
-
-Xcode comes bundled with emulators for the lastest versions of iPhone
-and iPad. Older versions may be available from the __Xcode →
-Preferences → Downloads → Components__ panel.
-
-## Deploy to Device
-
-For details about various requirements to deploy to a device, refer
-to the _Configuring Development and Distribution Assets_ section of
-Apple's
-[Tools Workflow Guide for iOS](http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/00-About_the_iOS_Application_Development_Workflow/introduction.html#//apple_ref/doc/uid/TP40007959).
-Briefly, you need to do the following before deploying:
-
-1. Join the Apple iOS Developer Program.
-
-2. Create a _Provisioning Profile_ within the
- [iOS Provisioning Portal](https://developer.apple.com/ios/manage/overview/index.action).
- You can use its _Development Provisioning Assistant_ to create and
- install the profile and certificate Xcode requires.
-
-3. Verify that the _Code Signing_ section's _Code Signing Identity_
- within the project settings is set to your provisioning profile
- name.
-
-To deploy to the device:
-
-1. Use the USB cable to plug the device into your Mac.
-
-2. Select the name of the project in the Xcode window's __Scheme__
- drop-down list.
-
-3. Select your device from the __Device__ drop-down list. If it is
- plugged in via USB but still does not appear, press the
- __Organizer__ button to resolve any errors.
-
-4. Press the __Run__ button to build, deploy and run the application
- on your device.
-
-## Common Problems
-
-__Deprecation Warnings:__ When an application programming interface
-(API) is changed or replaced by another API, it is marked as
-_deprecated_. The API still works in the near term, but is eventually
-removed. Some of these deprecated interfaces are reflected in Apache
-Cordova, and Xcode issues warnings about them when you build and
-deploy an application.
-
-Xcode's warning about the `invokeString` method concerns functionality
-that launches an app from a custom URL. While the mechanism to load
-from a custom URL has changed, this code is still present to provide
-backwards functionality for apps created with older versions of
-Cordova. The sample app does not use this functionality, so these
-warnings can be ignored. To prevent these warnings from appearing,
-remove the code that references the deprecated invokeString API:
-
-* Edit the _Classes/MainViewController.m_ file, surround the following
- block of code with `/*` and `*/` comments as shown below, then type
- __Command-s__ to save the file:
-
- (void)webViewDidFinishLoad:(UIWebView*)theWebView
- {
- // only valid if ___PROJECTNAME__-Info.plist specifies a protocol to handle
- /*
- if (self.invokeString) {
- // this is passed before the deviceready event is fired, so you can access it in js when you receive deviceready
- NSLog(@"DEPRECATED: window.invokeString - use the window.handleOpenURL(url) function instead, which is always called when the app is launched through a custom scheme url.");
- NSString* jsString = [NSString stringWithFormat:@"var invokeString = \"%@\";", self.invokeString];
- [theWebView stringByEvaluatingJavaScriptFromString:jsString];
- }
- */
- // Black base color for background matches the native apps
- theWebView.backgroundColor = [UIColor blackColor];
-
- return [super webViewDidFinishLoad:theWebView];
- }
-
-* Edit the _Classes/AppViewDelegate.m_ file, comment out the following
- line by inserting a double slash as shown below, then type
- __Command-s__ to save the file:
-
- //self.viewController.invokeString = invokeString;
-
-* Press __Command-b__ to rebuild the project and eliminate the warnings.
-
-<!-- Does this fix only last until the next "cordova prepare"? -->
-
-__Missing Headers__: Compilation errors relating to missing headers
-result from problems with the build location, and can be fixed
-via Xcode preferences:
-
-1. Select __Xcode → Preferences → Locations__.
-
-2. In the __Derived Data__ section, press the __Advanced__ button and
- select __Unique__ as the __Build Location__ as shown here:
-
- 
-
-This is the default setting for a new Xcode install, but it may be set
-differently following an upgrade from an older version of Xcode.
-
-For further information, consult Apple's documentation:
-
-* [Start Developing iOS Apps Today](http://developer.apple.com/library/ios/#referencelibrary/GettingStarted/RoadMapiOS/index.html#//apple_ref/doc/uid/TP40011343) provides a quick overview of steps for developing iOS Apps.
-
-* [Member Center home page](https://developer.apple.com/membercenter/index.action)
- provides links to several iOS technical resources including
- technical resources, the provisioning portal, distribution guides
- and community forums.
-
-* [Tools Workflow Guide for iOS](http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/00-About_the_iOS_Application_Development_Workflow/introduction.html#//apple_ref/doc/uid/TP40007959)
-
-* [Xcode 4 User Guide](http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/000-About_Xcode/about.html#//apple_ref/doc/uid/TP40010215)
-
-* [Session Videos](https://developer.apple.com/videos/wwdc/2012/) from
- the Apple World Wide Developer Conference 2012 (WWDC2012)
-
-* The [xcode-select command](http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man1/xcode-select.1.html),
- which helps specify the correct version of Xcode if more than one is installed.
-
-(Mac®, OS X®, Apple®, Xcode®, App Store℠, iPad®, iPhone®, iPod® and Finder® are Trademarks of Apple Inc.)
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/ios/install.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/install.md b/docs/en/edge/guide/platforms/ios/install.md
new file mode 100644
index 0000000..e4a8b13
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/install.md
@@ -0,0 +1,225 @@
+---
+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.
+---
+
+# iOS Installation Guide
+
+This section shows how to set up your SDK environment to deploy
+Cordova apps for iOS devices. You need to install Xcode, iOS's SDK,
+regardless of whether you want to use the cross-platform Cordova CLI
+for development, or a narrower set of platform-centered command-line
+tools. For a comparison of the two development paths, see the
+Overview. For details on each, see The Command-Line Interface and the
+iOS Development Guide.
+
+## Requirements and Support
+
+Apple® tools required to build iOS applications run only on the OS X
+operating system on Intel-based Macs. Xcode® 4.5 (the minimum required
+version) runs only on OS X version 10.7 (Lion) or greater, and
+includes the iOS 6 SDK (Software Development Kit). To submit apps to
+the Apple App Store℠ requires the latest versions of the Apple tools.
+
+You can test many of the Cordova features using the iOS emulator
+installed with the iOS SDK and Xcode, but you need an actual device to
+fully test all of the app's device features before submitting to the
+App Store. The device must have at least iOS 5.x installed, the
+minimum iOS version supported as of Cordova 2.3. Supporting devices
+include all iPad® models, iPhone® 3GS and above, and iPod® Touch 3rd
+Generation or later. To install apps onto a device, you must also be a
+member of Apple's
+[iOS Developer Program](https://developer.apple.com/programs/ios/),
+which costs $99 per year. This guide shows how to deploy apps to the
+iOS emulator, for which you don't need to register with the developer
+program.
+
+## Install the SDK
+
+There are two ways to download Xcode:
+
+* from the [App Store](https://itunes.apple.com/us/app/xcode/id497799835?mt=12),
+ available by searching for "Xcode" in the __App Store__ application.
+
+* from [Apple Developer Downloads](https://developer.apple.com/downloads/index.action),
+ which requires registration as an Apple Developer.
+
+Once Xcode is installed, several command-line tools need to be enabled
+for Cordova to run. From the __Xcode__ menu, select __Preferences__,
+then the __Downloads__ tab. From the __Components__ panel, press the
+__Install__ button next to the __Command Line Tools__ listing.
+
+## Open a Project in the SDK
+
+Use the `cordova` utility to set up a new project, as described in The
+Cordova The Command-line Interface. For example, in a source-code directory:
+
+ $ cordova create hello com.example.hello "HelloWorld"
+ $ cd hello
+ $ cordova platform add ios
+ $ cordova prepare # or "cordova build"
+
+Once created, you can open it from within Xcode. Double-click to open
+the `hello/platforms/ios/hello.xcodeproj` file. The screen should
+look like this:
+
+
+
+## Deploy to Emulator
+
+To preview the app in the iOS emulator:
+
+1. Make sure the _.xcodeproj_ file is selected in the left panel.
+
+2. Select the __hello__ app in the panel immediately to the right.
+
+3. Select the intended device from the toolbar's __Scheme__ menu, such
+ as the iPhone 6.0 Simulator as highlighted here:
+
+ 
+
+4. Press the __Run__ button that appears in the same toolbar to the
+ left of the __Scheme__. That builds, deploys and runs the
+ application in the emulator. A separate emulator application opens
+ to display the app:
+
+ 
+
+ Only one emulator may run at a time, so if you want to test the app
+ in a different emulator, you need to quit the emulator application
+ and run a different target within Xcode.
+
+Xcode comes bundled with emulators for the lastest versions of iPhone
+and iPad. Older versions may be available from the __Xcode →
+Preferences → Downloads → Components__ panel.
+
+## Deploy to Device
+
+For details about various requirements to deploy to a device, refer
+to the _Configuring Development and Distribution Assets_ section of
+Apple's
+[Tools Workflow Guide for iOS](http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/00-About_the_iOS_Application_Development_Workflow/introduction.html#//apple_ref/doc/uid/TP40007959).
+Briefly, you need to do the following before deploying:
+
+1. Join the Apple iOS Developer Program.
+
+2. Create a _Provisioning Profile_ within the
+ [iOS Provisioning Portal](https://developer.apple.com/ios/manage/overview/index.action).
+ You can use its _Development Provisioning Assistant_ to create and
+ install the profile and certificate Xcode requires.
+
+3. Verify that the _Code Signing_ section's _Code Signing Identity_
+ within the project settings is set to your provisioning profile
+ name.
+
+To deploy to the device:
+
+1. Use the USB cable to plug the device into your Mac.
+
+2. Select the name of the project in the Xcode window's __Scheme__
+ drop-down list.
+
+3. Select your device from the __Device__ drop-down list. If it is
+ plugged in via USB but still does not appear, press the
+ __Organizer__ button to resolve any errors.
+
+4. Press the __Run__ button to build, deploy and run the application
+ on your device.
+
+## Common Problems
+
+__Deprecation Warnings:__ When an application programming interface
+(API) is changed or replaced by another API, it is marked as
+_deprecated_. The API still works in the near term, but is eventually
+removed. Some of these deprecated interfaces are reflected in Apache
+Cordova, and Xcode issues warnings about them when you build and
+deploy an application.
+
+Xcode's warning about the `invokeString` method concerns functionality
+that launches an app from a custom URL. While the mechanism to load
+from a custom URL has changed, this code is still present to provide
+backwards functionality for apps created with older versions of
+Cordova. The sample app does not use this functionality, so these
+warnings can be ignored. To prevent these warnings from appearing,
+remove the code that references the deprecated invokeString API:
+
+* Edit the _Classes/MainViewController.m_ file, surround the following
+ block of code with `/*` and `*/` comments as shown below, then type
+ __Command-s__ to save the file:
+
+ (void)webViewDidFinishLoad:(UIWebView*)theWebView
+ {
+ // only valid if ___PROJECTNAME__-Info.plist specifies a protocol to handle
+ /*
+ if (self.invokeString) {
+ // this is passed before the deviceready event is fired, so you can access it in js when you receive deviceready
+ NSLog(@"DEPRECATED: window.invokeString - use the window.handleOpenURL(url) function instead, which is always called when the app is launched through a custom scheme url.");
+ NSString* jsString = [NSString stringWithFormat:@"var invokeString = \"%@\";", self.invokeString];
+ [theWebView stringByEvaluatingJavaScriptFromString:jsString];
+ }
+ */
+ // Black base color for background matches the native apps
+ theWebView.backgroundColor = [UIColor blackColor];
+
+ return [super webViewDidFinishLoad:theWebView];
+ }
+
+* Edit the _Classes/AppViewDelegate.m_ file, comment out the following
+ line by inserting a double slash as shown below, then type
+ __Command-s__ to save the file:
+
+ //self.viewController.invokeString = invokeString;
+
+* Press __Command-b__ to rebuild the project and eliminate the warnings.
+
+<!-- Does this fix only last until the next "cordova prepare"? -->
+
+__Missing Headers__: Compilation errors relating to missing headers
+result from problems with the build location, and can be fixed
+via Xcode preferences:
+
+1. Select __Xcode → Preferences → Locations__.
+
+2. In the __Derived Data__ section, press the __Advanced__ button and
+ select __Unique__ as the __Build Location__ as shown here:
+
+ 
+
+This is the default setting for a new Xcode install, but it may be set
+differently following an upgrade from an older version of Xcode.
+
+For further information, consult Apple's documentation:
+
+* [Start Developing iOS Apps Today](http://developer.apple.com/library/ios/#referencelibrary/GettingStarted/RoadMapiOS/index.html#//apple_ref/doc/uid/TP40011343) provides a quick overview of steps for developing iOS Apps.
+
+* [Member Center home page](https://developer.apple.com/membercenter/index.action)
+ provides links to several iOS technical resources including
+ technical resources, the provisioning portal, distribution guides
+ and community forums.
+
+* [Tools Workflow Guide for iOS](http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/00-About_the_iOS_Application_Development_Workflow/introduction.html#//apple_ref/doc/uid/TP40007959)
+
+* [Xcode 4 User Guide](http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/000-About_Xcode/about.html#//apple_ref/doc/uid/TP40010215)
+
+* [Session Videos](https://developer.apple.com/videos/wwdc/2012/) from
+ the Apple World Wide Developer Conference 2012 (WWDC2012)
+
+* The [xcode-select command](http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man1/xcode-select.1.html),
+ which helps specify the correct version of Xcode if more than one is installed.
+
+(Mac®, OS X®, Apple®, Xcode®, App Store℠, iPad®, iPhone®, iPod® and Finder® are Trademarks of Apple Inc.)
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/tizen/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/tizen/index.md b/docs/en/edge/guide/platforms/tizen/index.md
deleted file mode 100644
index 212ac17..0000000
--- a/docs/en/edge/guide/platforms/tizen/index.md
+++ /dev/null
@@ -1,116 +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.
----
-
-# Tizen Installation Guide
-
-This guide describes how to set up your SDK development environment to
-deploy Cordova apps for devices running the Tizen operating system.
-
-## Requirements and Support
-
-The Tizen SDK requires Linux Ubuntu 10.04/10.10/11.04/11.10 (32-bit),
-or Windows XP SP3/7 (32-bit).
-
-Developers should use the `cordova` utility in conjunction with
-the Tizen SDK. See The Command-line Interface for information
-how to install it, add projects, then build and deploy a project.
-
-## Install the SDK
-
-Download the Tizen SDK from
-[tizen.org](https://developer.tizen.org/sdk).
-
-<!--
-
-- (optional) Install Tizen Cordova template projects: copy the
- `/templates` directory content into the Tizen Eclipse IDE web
- templates directory (e.g:
- `/home/my_username/tizen-sdk/IDE/Templates/web`).
-
-- __Method #2: Use Tizen Eclipse IDE Cordova Tizen project templates__
- - Launch Tizen Eclipse IDE
- - Select __File → New → Tizen Web Project__
- - Select __User Template__ and __User defined__ items
- - Select one of the Tizen Cordova template (e.g: __CordovaBasicTemplate__)
- - Fill the __Project name__ and its target __Location__
-
- 
-
- - Click __Finish__
-
- 
-
- - Your project should now appear in the __Project Explorer__ view
-
--->
-
-## Open a Project in the SDK
-
-1. Launch the Tizen Eclipse IDE.
-
-2. Select __File → Import → Tizen Web Project__:
-
- 
-
-3. Press __Next__.
-
-4. Make sure __Select root directory__ is checked.
-
-5. Make sure __Copy projects into workspace__ is checked.
-
-6. Press __Browse__ and select the Cordova Tizen `samples` project directory (such as `/cordova-basic`):
-
- 
-
-7. Press __Finish__. Your project should now be imported and appear in
- the __Project Explorer__ view:
-
- 
-
-To rebuild the project, right-click in the __Project Explorer__ view
-and Select __Build Project__:
-
-
-
-A widget package file such as _hello.wgt_ should generate in the
-project's root directory.
-
-## Deploy to Emulator
-
-Right-click the project in the __Project Explorer__ view and select
-__Run As → Tizen Web Simulator Application__:
-
-
-
-## Deploy to Device
-
-* Make sure that the target device is properly launched, connected and
- configured. Its __Date and Time__ settings must be set correctly.
-
-* Use the __Connection Explorer__ view to select the application
- deployment target: __Window → Show View → Connection
- Explorer__.
-
- 
-
-* Right-click the project in the __Project Explorer__ view, then
- select __Run As → Tizen Web Application__:
-
- 
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/b731f46e/docs/en/edge/guide/platforms/tizen/install.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/tizen/install.md b/docs/en/edge/guide/platforms/tizen/install.md
new file mode 100644
index 0000000..212ac17
--- /dev/null
+++ b/docs/en/edge/guide/platforms/tizen/install.md
@@ -0,0 +1,116 @@
+---
+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.
+---
+
+# Tizen Installation Guide
+
+This guide describes how to set up your SDK development environment to
+deploy Cordova apps for devices running the Tizen operating system.
+
+## Requirements and Support
+
+The Tizen SDK requires Linux Ubuntu 10.04/10.10/11.04/11.10 (32-bit),
+or Windows XP SP3/7 (32-bit).
+
+Developers should use the `cordova` utility in conjunction with
+the Tizen SDK. See The Command-line Interface for information
+how to install it, add projects, then build and deploy a project.
+
+## Install the SDK
+
+Download the Tizen SDK from
+[tizen.org](https://developer.tizen.org/sdk).
+
+<!--
+
+- (optional) Install Tizen Cordova template projects: copy the
+ `/templates` directory content into the Tizen Eclipse IDE web
+ templates directory (e.g:
+ `/home/my_username/tizen-sdk/IDE/Templates/web`).
+
+- __Method #2: Use Tizen Eclipse IDE Cordova Tizen project templates__
+ - Launch Tizen Eclipse IDE
+ - Select __File → New → Tizen Web Project__
+ - Select __User Template__ and __User defined__ items
+ - Select one of the Tizen Cordova template (e.g: __CordovaBasicTemplate__)
+ - Fill the __Project name__ and its target __Location__
+
+ 
+
+ - Click __Finish__
+
+ 
+
+ - Your project should now appear in the __Project Explorer__ view
+
+-->
+
+## Open a Project in the SDK
+
+1. Launch the Tizen Eclipse IDE.
+
+2. Select __File → Import → Tizen Web Project__:
+
+ 
+
+3. Press __Next__.
+
+4. Make sure __Select root directory__ is checked.
+
+5. Make sure __Copy projects into workspace__ is checked.
+
+6. Press __Browse__ and select the Cordova Tizen `samples` project directory (such as `/cordova-basic`):
+
+ 
+
+7. Press __Finish__. Your project should now be imported and appear in
+ the __Project Explorer__ view:
+
+ 
+
+To rebuild the project, right-click in the __Project Explorer__ view
+and Select __Build Project__:
+
+
+
+A widget package file such as _hello.wgt_ should generate in the
+project's root directory.
+
+## Deploy to Emulator
+
+Right-click the project in the __Project Explorer__ view and select
+__Run As → Tizen Web Simulator Application__:
+
+
+
+## Deploy to Device
+
+* Make sure that the target device is properly launched, connected and
+ configured. Its __Date and Time__ settings must be set correctly.
+
+* Use the __Connection Explorer__ view to select the application
+ deployment target: __Window → Show View → Connection
+ Explorer__.
+
+ 
+
+* Right-click the project in the __Project Explorer__ view, then
+ select __Run As → Tizen Web Application__:
+
+ 
+