cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From marc...@apache.org
Subject [04/12] CB-7383 delete 3.6.1 docs in preparation for 3.6.0 docs
Date Mon, 15 Sep 2014 20:07:42 GMT
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/amazonfireos/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/amazonfireos/plugin.md b/docs/en/3.6.1/guide/platforms/amazonfireos/plugin.md
deleted file mode 100644
index 3fc5ca9..0000000
--- a/docs/en/3.6.1/guide/platforms/amazonfireos/plugin.md
+++ /dev/null
@@ -1,100 +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.
----
-
-# Amazon Fire OS Plugins
-
-Follow the instructions provided in the Android Plugins Guide for an overview of developing custom plugins.
-
-## Echo Amazon Fire OS Plugin Example
-
-To match the JavaScript interface's _echo_ feature described in
-Application Plugins, use the `plugin.xml` to inject a `feature`
-specification to the local platform's `config.xml` file:
-
-    <platform name="amazon-fireos">
-        <config-file target="config.xml" parent="/*">
-            <feature name="Echo">
-                <param name="android-package" value="org.apache.cordova.plugin.Echo"/>
-            </feature>
-        </config-file>
-    </platform>
-
-Then add the following to the
-`src/org/apache/cordova/plugin/Echo.java` file:
-
-    package org.apache.cordova.plugin;
-
-    import org.apache.cordova.CordovaPlugin;
-    import org.apache.cordova.CallbackContext;
-
-    import org.json.JSONArray;
-    import org.json.JSONException;
-    import org.json.JSONObject;
-
-    /**
-     * This class echoes a string called from JavaScript.
-     */
-    public class Echo extends CordovaPlugin {
-
-        @Override
-        public boolean execute(String action, JSONArray args, CallbackContext callbackContext) throws JSONException {
-            if (action.equals("echo")) {
-                String message = args.getString(0);
-                this.echo(message, callbackContext);
-                return true;
-            }
-            return false;
-        }
-
-        private void echo(String message, CallbackContext callbackContext) {
-            if (message != null && message.length() > 0) {
-                callbackContext.success(message);
-            } else {
-                callbackContext.error("Expected one non-empty string argument.");
-            }
-        }
-    }
-
-If you want to reuse Android Plugin code for the Amazon Fire OS platform then modify the plugin.xml to point to the `android` specific source file. For example,
-
-    <platform name="amazon-fireos">
-        <config-file target="config.xml" parent="/*">
-            <feature name="Echo">
-                <param name="android-package" value="org.apache.cordova.plugin.Echo"/>
-            </feature>
-        </config-file>
-        <source-file src="src/android/Echo.java" target-dir="src/org/apache/cordova/plugin" />
-    </platform>
-
-If you want to write a customized plugin for the Amazon Fire OS platform then create a folder named `amazon` under your plugin src/ folder and modify the plugin.xml to point to the `amazon` specific source file. For example,
-
-    <platform name="amazon-fireos">
-        <config-file target="config.xml" parent="/*">
-            <feature name="Echo">
-                <param name="android-package" value="org.apache.cordova.plugin.Echo"/>
-            </feature>
-        </config-file>
-        <source-file src="src/amazon/Echo.java" target-dir="src/org/apache/cordova/plugin" />
-    </platform>
-
-## Using Amazon WebView in your plugin
-
-Cordova for Amazon Fire OS makes use of custom Amazon WebView that is built on the open-source Chromium project. It is GPU accelerated and optimized for fluid performance on Kindle Fire.
-
-To understand how to best use Amazon WebView in your project, check out the [Amazon Developer Portal](https://developer.amazon.com/sdk/fire/IntegratingAWV.html).

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/amazonfireos/webview.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/amazonfireos/webview.md b/docs/en/3.6.1/guide/platforms/amazonfireos/webview.md
deleted file mode 100644
index a14422c..0000000
--- a/docs/en/3.6.1/guide/platforms/amazonfireos/webview.md
+++ /dev/null
@@ -1,127 +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.
----
-
-# Amazon Fire OS WebViews
-
-Beginning with 3.3.0, you can use Cordova as a component in Amazon Fire OS applications. Amazon Fire OS refers to this component as `CordovaWebView`. `CordovaWebView` extends Amazon WebView that is built on the open source Chromium Project. By leveraging this feature, your web apps can utilize the latest HTML5 web standards running in a modern web runtime engine.
-
-If you're unfamiliar with Amazon Fire OS, you should first familiarize
-yourself with the Amazon Fire OS Platform Guide and have the latest SDKs installed before you attempt the more unusual development option of embedding a WebView.
-
-## Prerequisites
-
-* Cordova 3.3.0 or greater
-
-* Android SDK updated to the latest SDK
-
-* Amazon WebView SDK
-
-## Guide to using CordovaWebView in a Amazon Fire OS Project
-
-1. To follow these instructions, make sure you have the latest Cordova
-   distribution. Download it from
-   [cordova.apache.org](http://cordova.apache.org) and unzip its
-   Amazon Fire OS package.
-   
-2. Download and expand the [Amazon WebView SDK](https://developer.amazon.com/sdk/fire/IntegratingAWV.html#installawv) , then copy the awv_interface.jar into `/framework/libs` directory. Create a libs/ folder if it doesn't exist.
-
-3. Navigate to the package's `/framework` directory and run
-   `ant jar`. It creates the Cordova `.jar` file, formed as
-   `/framework/cordova-3.6.1.jar`.
-
-4. Copy the `.jar` file into the Android project's `/libs` directory.
-
-5. Add the following to the application's `/res/xml/main.xml` file,
-   with the `layout_height`, `layout_width` and `id` modified to suit
-   the application:
-
-        <org.apache.cordova.CordovaWebView
-            android:id="@+id/tutorialView"
-            android:layout_width="match_parent"
-            android:layout_height="match_parent" />
-
-6. Modify your activity so that it implements the `CordovaInterface`.  You should implement the included methods.  You may wish to copy them from `/framework/src/org/apache/cordova/CordovaActivity.java`, or implement them on your own.  The code fragment below shows a basic application that uses the interface. Note how the referenced view id matches the `id` attribute specified in the XML fragment shown above:
-
-        public class CordovaViewTestActivity extends Activity implements CordovaInterface {
-            CordovaWebView cwv;
-            /* Called when the activity is first created. */
-            @Override
-            public void onCreate(Bundle savedInstanceState) {
-                super.onCreate(savedInstanceState);
-                setContentView(R.layout.main);
-                cwv = (CordovaWebView) findViewById(R.id.tutorialView);
-                Config.init(this);
-                cwv.loadUrl(Config.getStartUrl());
-            }
-
-If you use the camera, you should also implement this:
-
-        @Override
-        public void setActivityResultCallback(CordovaPlugin plugin) {
-            this.activityResultCallback = plugin;
-        }
-        /**
-         * Launch an activity for which you would like a result when it finished. When this activity exits,
-         * your onActivityResult() method is called.
-         *
-         * @param command           The command object
-         * @param intent            The intent to start
-         * @param requestCode       The request code that is passed to callback to identify the activity
-         */
-        public void startActivityForResult(CordovaPlugin command, Intent intent, int requestCode) {
-            this.activityResultCallback = command;
-            this.activityResultKeepRunning = this.keepRunning;
-
-            // If multitasking turned on, then disable it for activities that return results
-            if (command != null) {
-                this.keepRunning = false;
-            }
-
-            // Start activity
-            super.startActivityForResult(intent, requestCode);
-        }
-
-        @Override
-        /**
-         * Called when an activity you launched exits, giving you the requestCode you started it with,
-         * the resultCode it returned, and any additional data from it.
-         *
-         * @param requestCode       The request code originally supplied to startActivityForResult(),
-         *                          allowing you to identify who this result came from.
-         * @param resultCode        The integer result code returned by the child activity through its setResult().
-         * @param data              An Intent, which can return result data to the caller (various data can be attached to Intent "extras").
-         */
-        protected void onActivityResult(int requestCode, int resultCode, Intent intent) {
-            super.onActivityResult(requestCode, resultCode, intent);
-            CordovaPlugin callback = this.activityResultCallback;
-            if (callback != null) {
-                callback.onActivityResult(requestCode, resultCode, intent);
-            }
-        }
-
-Finally, remember to add the thread pool, otherwise the plugins have no threads to run on:
-
-        @Override
-        public ExecutorService getThreadPool() {
-            return threadPool;
-        }
-
-7. Copy your application's HTML and JavaScript files to your Amazon Fire OS project's `/assets/www` directory.
-
-8. Copy `config.xml` from `/framework/res/xml` to your project's `/res/xml` directory.

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/android/config.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/android/config.md b/docs/en/3.6.1/guide/platforms/android/config.md
deleted file mode 100644
index 54db4be..0000000
--- a/docs/en/3.6.1/guide/platforms/android/config.md
+++ /dev/null
@@ -1,100 +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 Configuration
-
-The `config.xml` file controls an app's basic settings that apply
-across each application and CordovaWebView instance. This section
-details preferences that only apply to Android builds. See The
-config.xml File for information on global configuration options.
-
-- `KeepRunning` (boolean, defaults to `true`): Determines whether the
-  application stays running in the background even after a `pause`
-  event fires. Setting this to `false` does not kill the app after a
-  `pause` event, but simply halts execution of code within the cordova
-  webview while the app is in the background.
-
-        <preference name="KeepRunning" value="false"/>
-
-- `LoadUrlTimeoutValue` (number in milliseconds, default to `20000`,
-  20 seconds): When loading a page, the amount of time to wait before throwing
-  a timeout error. This example specifies 10 seconds rather than 20:
-
-        <preference name="LoadUrlTimeoutValue" value="10000"/>
-
-- `SplashScreen` (string, defaults to `splash`): The name of the file minus
-  its extension in the `res/drawable` directory.  Various assets must share
-  this common name in various subdirectories.
-
-        <preference name="SplashScreen" value="mySplash"/>
-
-- `SplashScreenDelay` (number in milliseconds, defaults to `3000`): The amount
-  of time the splash screen image displays.
-
-        <preference name="SplashScreenDelay" value="10000"/>
-
-- `InAppBrowserStorageEnabled` (boolean, defaults to `true`): Controls
-  whether pages opened within an InAppBrowser can access the same
-  localStorage and WebSQL storage as pages opened with the default
-  browser.
-
-        <preference name="InAppBrowserStorageEnabled" value="true"/>
-
-- `LoadingDialog` (string, defaults to `null`): If set, displays a dialog with
-  the specified title and message, and a spinner, when loading the first
-  page of an application. The title and message are separated by a comma
-  in this value string, and that comma is removed before the dialog is
-  displayed.
-
-        <preference name="LoadingDialog" value="My Title,My Message"/>
-
-- `LoadingPageDialog` (string, defaults to `null`): The same as `LoadingDialog`,
-  but for loading every page after the first page in the application.
-
-        <preference name="LoadingPageDialog" value="My Title,My Message"/>
-
-- `ErrorUrl` (URL, defaults to `null`):
-  If set, will display the referenced page upon an error in the application
-  instead of a dialog with the title "Application Error".
-
-        <preference name="ErrorUrl" value="myErrorPage.html"/>
-
-- `ShowTitle` (boolean, defaults to `false`): Show the title at the top
-  of the screen.
-
-        <preference name="ShowTitle" value="true"/>
-
-- `LogLevel` (string, defaults to `ERROR`): Sets the minimum log level
-  through which log messages from your application will be filtered. Valid
-  values are `ERROR`, `WARN`, `INFO`, `DEBUG`, and `VERBOSE`.
-
-        <preference name="LogLevel" value="VERBOSE"/>
-
-- `SetFullscreen` (boolean, defaults to `false`): Same as the `Fullscreen`
-  parameter in the global configuration of this xml file. This Android-specific
-  element is deprecated in favor of the global `Fullscreen` element, and will
-  be removed in a future version.
-
-- `AndroidLaunchMode` (string, defaults to `singleTop`): Sets the Activity
-  `android:launchMode` attribute.  This changes what happens when the app is
-  launched from app icon or intent and is already running.
-  Valid values are `standard`, `singleTop`, `singleTask`, `singleInstance`.
-
-        <preference name="AndroidLaunchMode" value="singleTop"/>
-

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/android/index.md b/docs/en/3.6.1/guide/platforms/android/index.md
deleted file mode 100644
index 9ba069e..0000000
--- a/docs/en/3.6.1/guide/platforms/android/index.md
+++ /dev/null
@@ -1,328 +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 Platform Guide
-
-This guide shows how to set up your SDK environment to deploy Cordova
-apps for Android devices, and how to optionally use Android-centered
-command-line tools in your development workflow.  You need to install
-the Android SDK regardless of whether you want to use these
-platform-centered shell tools or cross-platform Cordova CLI for
-development. For a comparison of the two development paths, see the
-Overview.  For details on the CLI, see The Command-Line Interface.
-
-## Requirements and Support
-
-Cordova for Android requires the Android SDK. See the Android SDK's
-[System Requirements](http://developer.android.com/sdk/index.html).
-
-Cordova supports Android 2.3.x (Gingerbread, starting with Android API level 10)
-and 4.x.  As a general rule, Android versions become unsupported by Cordova as
-they dip below 5% on Google's
-[distribution dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions (Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-The Command-Line Interface.
-
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
-
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-Install the Android SDK from
-[developer.android.com/sdk](http://developer.android.com/sdk/). The android sdk
-is distributed as an 'adt-bundle-&lt;os&gt;-&lt;arch&gt;-&lt;ver&gt;' file.
-On windows, the adt-bundle is packaged with an installer.
-On OSX and Linux, simply unpack the 'adt-bundle' in the location you store development tools. 
-[More detailed information on Android SDK setup can be found here](http://developer.android.com/sdk/installing/bundle.html)
-
-
-For Cordova command-line tools to work, or the CLI that is based upon
-them, you need to include the SDK's `tools` and `platform-tools`
-directories in your `PATH`.  On a 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
-
-Add the paths for `java` and `ant` if needed. This line in `~/.bash_profile`
-exposes these tools in newly opened terminal windows. If your terminal
-window is already open in OSX, or to avoid a logout/login on Linux, run
-this to make them available in the current terminal window:
-
-        $ source ~/.bash_profile
-
-To modify the `PATH` environment on Windows 7:
-
-1. Click on the __Start__ menu in the lower-left corner of the desktop,
-   right-click on __Computer__, then select __Properties__.
-
-1. Select __Advanced System Settings__ in the column on the left.
-
-1. In the resulting dialog box, press __Environment Variables__.
-
-1. Select the __PATH__ variable and press __Edit__.
-
-1. 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
-
-1. 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 of
-these fails to run:
-
-        ;%JAVA_HOME%\bin;%ANT_HOME%\bin
-
-## Open a New Project in the SDK
-
-At this point, to create a new project you can choose between the
-cross-platform CLI tool described in The Command-Line Interface, or
-the set of Android-specific shell tools. From within a source-code
-directory, here's the CLI approach:
-
-        $ cordova create hello com.example.hello HelloWorld
-        $ cd hello
-        $ cordova platform add android
-        $ cordova build
-
-Here's the corresponding lower-level shell-tool approach for both Unix
-and Windows:
-
-        $ /path/to/cordova-android/bin/create /path/to/new/hello com.example.hello HelloWorld
-        C:\path\to\cordova-android\bin\create.bat C:\path\to\new\hello com.example.hello HelloWorld
-
-Here's how to use the SDK to modify it:
-
-1. Launch the __Eclipse__ application.
-
-1. Select the __New Project__ menu item.
-
-1. Choose __Android Project from Existing Code__ from the resulting
-   dialog box, and press __Next__:
-
-  ![](img/guide/platforms/android/eclipse_new_project.png)
-
-1. If you're using the CLI, navigate to the `hello` directory you
-   created for the project, then to the `platforms/android`
-   subdirectory. Alternately, if you use the `create` shell utility,
-   simply navigate to the `hello` directory.
-
-1. Press __Finish__.
-
-Once the Eclipse window opens, a red __X__ may appear to indicate
-unresolved problems. If so, follow these additional steps:
-
-1. Right-click on the project directory.
-
-1. In the resulting __Properties__ dialog, select __Android__ from the navigation pane.
-
-1. For the project build target, select the highest Android API level you have installed.
-
-1. Click __OK__.
-
-1. Select __Clean__ from the __Project__ menu. This should correct all the errors in the project.
-
-## Build the Project
-
-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:
-
-        $ cordova build
-        $ cordova build android   # do not rebuild other platforms
-
-If you are using the Android-specific shell tools in development,
-there is a different approach.  Once you generate the project, the
-default app's source is available in the `assets/www` subdirectory.
-Subsequent commands are available in its `cordova` subdirectory.
-
-The `build` command cleans project files and rebuilds the app. Here is
-the syntax for both Mac and Windows. The first pair of examples
-generate debugging information, and the second signs the apps for
-release:
-
-        $ /path/to/project/cordova/build --debug
-        C:\path\to\project\cordova\build.bat --debug
-        
-        $ /path/to/project/cordova/build --release
-        C:\path\to\project\cordova\build.bat --release
-
-## Configure an Emulator
-
-You can use either the `cordova` CLI utility or Cordova's
-Android-centered shell tools to run an app in an emulator.  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:
-
-1. Run `android` on the command line.
-
-1. From within Eclipse, press this toolbar icon:
-
-  ![](img/guide/platforms/android/eclipse_android_sdk_button.png)
-
-Once open, the Android SDK Manager displays various runtime libraries:
-
-![](img/guide/platforms/android/asdk_window.png)
-
-Choose __Tools &rarr; Manage AVDs__ (Android Virtual Devices), then
-choose any item from __Device Definitions__ in the resulting dialog
-box:
-
-![](img/guide/platforms/android/asdk_device.png)
-
-Press __Create AVD__, optionally modifying the name, then press __OK__
-to accept the changes:
-
-![](img/guide/platforms/android/asdk_newAVD.png)
-
-The AVD then appears in the __Android Virtual Devices__ list:
-
-![](img/guide/platforms/android/asdk_avds.png)
-
-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:
-
-![](img/guide/platforms/android/asdk_emulator.png)
-
-## Deploy to Emulator
-
-At this point you can use the `cordova` CLI utility to deploy the
-application to the emulator from the command line:
-
-        $ cordova emulate android
-
-Otherwise use the alternate shell interface:
-
-        $ /path/to/project/cordova/run --emulator
-
-Instead of relying on whichever emulator is currently enabled within
-the SDK, you can refer to each by the names you supply:
-
-        $ /path/to/project/cordova/run --target=NAME
-
-This pushes the app to the home screen and launches it:
-
-![](img/guide/platforms/android/emulator2x.png)
-
-When you `run` the app, you also `build` it. You can append additional
-`--debug`, `--release`, and `--nobuild` flags to control how it is
-built, or even whether a rebuild is necessary:
-
-        $ /path/to/project/cordova/run --emulator --nobuild
-
-If instead you are working within Eclipse, right-click the project and
-choose __Run As &rarr; Android Application__. You may be asked to
-specify an AVD if none are already open.
-
-For a faster experience, you can use the `Virtual Machine Acceleration` to improve 
-the execution speed.
-Many modern CPUs provide extensions to execute Virtual Machines more efficiently.
-Before attempting to use this type of acceleration, you need to determine if your 
-current development system's CPU, supports one the following virtualization technologies:
-
-* __Intel Virtualization Technology__ (VT-x, vmx) &rarr; [Intel VT-x supported processor list](http://ark.intel.com/products/virtualizationtechnology)
-* __AMD Virtualization__ (AMD-V, SVM), only supported for Linux (Since May 2006, all CPUs AMD include AMD-V, except Sempron).
-
-Another way to find out if your Intel processor supports VT-x Technology, it's by executing the 
-`Intel Processor Identification Utility`, for `Windows`you can download it from the Intel [Download Center](https://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=1881&DwnldID=7838),
-or you can use the [booteable utility](https://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=1881&DwnldID=7840&lang=eng), which is `OS Independent`.
-
-After install and execute the `Intel Processor Identification Utility` over Windows, you will get the following window, 
-in order to check if your CPU supports the Virtualization Technologies:
-
-![](img/guide/platforms/android/intel_pid_util_620px.png)
-
-In order to speed up the emulator, you need to download and install one or more `Intel x86 Atom` System Images, 
-as well as the `Intel Hardware Accelerated Execution Manager (HAXM)`.
-
-Open your Android SDK Manager, and select the `Intel x86 Atom` System Image, for whichever version that you want to test. Then go to `Extras` 
-and select `Intel x86 Emulator Accelerator (HAXM)`, and install those packages:
-
-![](img/guide/platforms/android/asdk_man_intel_image_haxm.png)
-
-After download, run the Intel installer, which is available within your
-Android SDK at `extras/intel/Hardware_Accelerated_Execution_Manager`. 
-__Note__:`If you have any problems installing the package, you can find more information and step by step guidance check this` 
-[Intel Article](http://software.intel.com/en-us/android/articles/speeding-up-the-android-emulator-on-intel-architecture).
-
-1. Install one or more `Intel x86 Atom` System Images as well as the
-   `Intel Hardware Accelerated Execution Manager`, available under
-   __Extras__.
-
-1. Run the Intel installer, which is available within your Android SDK
-   at `extras/intel/Hardware_Accelerated_Execution_Manager`.
-
-1. Create a new AVD with the target set to an Intel image.
-
-1. 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 use this CLI command to push the app to the device:
-
-        $ cordova run android
-
-...or use this Android-centered shell interface:
-
-        $ /path/to/project/cordova/run --device
-
-With no flags specified, the `run` command detects a connected
-device, or a currently running emulator if no device is found,
-otherwise it prompts to specify an emulator.
-
-To run the app from within Eclipse, right-click the project and choose
-__Run As &rarr; Android Application__.
-
-## Other Commands
-
-The following generates a detailed log of the app as it runs:
-
-        $ /path/to/project/cordova/log
-        C:\path\to\project\cordova\log.bat
-
-The following cleans the project files:
-
-        $ /path/to/project/cordova/clean
-        C:\path\to\project\cordova\clean.bat
-

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/android/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/android/plugin.md b/docs/en/3.6.1/guide/platforms/android/plugin.md
deleted file mode 100644
index fb83ab8..0000000
--- a/docs/en/3.6.1/guide/platforms/android/plugin.md
+++ /dev/null
@@ -1,240 +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 Plugins
-
-This section provides details for how to implement native plugin code
-on the Android platform. Before reading this, see Application Plugins
-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.  For another sample, see also the comments in
-[CordovaPlugin.java](https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/CordovaPlugin.java).
-
-Android plugins are based on Cordova-Android, which consists of an
-Android WebView with hooks attached to it.  Plugins are represented as
-class mappings in the `config.xml` file.  A plugin consists of at
-least one Java class that extends the `CordovaPlugin` class,
-overriding one of its `execute` methods. As best practice, the plugin
-should also handle `pause` and `resume` events, along with any message
-passing between plugins.  Plugins with long-running requests,
-background activity such as media playback, listeners, or internal
-state should implement the `onReset()` method as well. It executes
-when the `WebView` navigates to a new page or refreshes, which reloads
-the JavaScript.
-
-## Plugin Class Mapping
-
-The plugin's JavaScript interface uses the `cordova.exec` method as
-follows:
-
-        exec(<successFunction>, <failFunction>, <service>, <action>, [<args>]);
-
-This marshals a request from the WebView to the Android native side,
-effectively calling the `action` method on the `service` class, with
-additional arguments passed in the `args` array.
-
-Whether you distribute a plugin as Java file or as a _jar_ file of its
-own, the plugin must be specified in your Cordova-Android
-application's `res/xml/config.xml` file. See Application Plugins for
-more information on how to use the `plugin.xml` file to inject this
-`feature` element:
-
-        <feature name="<service_name>">
-            <param name="android-package" value="<full_name_including_namespace>" />
-        </feature>
-
-The service name matches the one used in the JavaScript `exec` call.
-The value is the Java class's fully qualified namespace identifier.
-Otherwise, the plugin may compile but still be unavailable to Cordova.
-
-## Plugin Initialization and Lifetime
-
-One instance of a plugin object is created for the life of each
-`WebView`. Plugins are not instantiated until they are first
-referenced by a call from JavaScript, unless `<param>` with an `onload`
-`name` attribute is set to `"true"` in `config.xml`. E.g.:
-
-    <feature name="Echo">
-        <param name="android-package" value="<full_name_including_namespace>" />
-        <param name="onload" value="true" />
-    </feature>
-
-Plugins should use the `initialize` method for their start-up logic.
-
-    @Override
-    public void initialize(CordovaInterface cordova, CordovaWebView webView) {
-        super.initialize(cordova, webView);
-        // your init code here
-    }
-
-## Writing an Android Java Plugin
-
-A JavaScript call fires off a plugin request to the native side, and
-the corresponding Java plugin is mapped properly in the `config.xml`
-file, but what does the final Android Java Plugin class look like?
-Whatever is dispatched to the plugin with JavaScript's `exec` function
-is passed into the plugin class's `execute` method. Most `execute`
-implementations look like this:
-
-        @Override
-        public boolean execute(String action, JSONArray args, CallbackContext callbackContext) throws JSONException {
-            if ("beep".equals(action)) {
-                this.beep(args.getLong(0));
-                callbackContext.success();
-                return true;
-            }
-            return false;  // Returning false results in a "MethodNotFound" error.
-        }
-
-The JavaScript `exec` function's `action` parameter corresponds to a
-private class method to dispatch with optional parameters.
-
-When catching exceptions and returning errors, it's important for the
-sake of clarity that errors returned to JavaScript match Java's
-exception names as much as possible.
-
-## Threading
-
-The plugin's JavaScript does _not_ run in the main thread of the
-`WebView` interface; instead, it runs on the `WebCore` thread, as
-does the `execute` method.  If you need to interact with the user
-interface, you should use the following variation:
-
-        @Override
-        public boolean execute(String action, JSONArray args, final CallbackContext callbackContext) throws JSONException {
-            if ("beep".equals(action)) {
-                final long duration = args.getLong(0);
-                cordova.getActivity().runOnUiThread(new Runnable() {
-                    public void run() {
-                        ...
-                        callbackContext.success(); // Thread-safe.
-                    }
-                });
-                return true;
-            }
-            return false;
-        }
-
-Use the following if you do not need to run on the main interface's
-thread, but do not want to block the `WebCore` thread either:
-
-        @Override
-        public boolean execute(String action, JSONArray args, final CallbackContext callbackContext) throws JSONException {
-            if ("beep".equals(action)) {
-                final long duration = args.getLong(0);
-                cordova.getThreadPool().execute(new Runnable() {
-                    public void run() {
-                        ...
-                        callbackContext.success(); // Thread-safe.
-                    }
-                });
-                return true;
-            }
-            return false;
-        }
-
-## Echo Android Plugin Example
-
-To match the JavaScript interface's _echo_ feature described in
-Application Plugins, use the `plugin.xml` to inject a `feature`
-specification to the local platform's `config.xml` file:
-
-        <platform name="android">
-            <config-file target="config.xml" parent="/*">
-                <feature name="Echo">
-                    <param name="android-package" value="org.apache.cordova.plugin.Echo"/>
-                </feature>
-            </config-file>
-        </platform>
-
-Then add the following to the
-`src/org/apache/cordova/plugin/Echo.java` file:
-
-        package org.apache.cordova.plugin;
-
-        import org.apache.cordova.CordovaPlugin;
-        import org.apache.cordova.CallbackContext;
-
-        import org.json.JSONArray;
-        import org.json.JSONException;
-        import org.json.JSONObject;
-
-        /**
-         * This class echoes a string called from JavaScript.
-         */
-        public class Echo extends CordovaPlugin {
-
-            @Override
-            public boolean execute(String action, JSONArray args, CallbackContext callbackContext) throws JSONException {
-                if (action.equals("echo")) {
-                    String message = args.getString(0);
-                    this.echo(message, callbackContext);
-                    return true;
-                }
-                return false;
-            }
-
-            private void echo(String message, CallbackContext callbackContext) {
-                if (message != null && message.length() > 0) {
-                    callbackContext.success(message);
-                } else {
-                    callbackContext.error("Expected one non-empty string argument.");
-                }
-            }
-        }
-
-The necessary imports at the top of the file extends the class from
-`CordovaPlugin`, whose `execute()` method it overrides to receive
-messages from `exec()`.  The `execute()` method first tests the value
-of `action`, for which in this case there is only one valid `echo`
-value.  Any other action returns `false` and results in an
-`INVALID_ACTION` error, which translates to an error callback invoked
-on the JavaScript side.
-
-Next, the method retrieves the echo string using the `args` object's
-`getString` method, specifying the first parameter passed to the
-method.  After the value is passed to a private `echo` method, it is
-parameter-checked to make sure it is not `null` or an empty string, in
-which case `callbackContext.error()` invokes JavaScript's error
-callback.  If the various checks pass, the `callbackContext.success()`
-passes the original `message` string back to JavaScript's success
-callback as a parameter.
-
-## Android Integration
-
-Android features an `Intent` system that allows processes to
-communicate with each other.  Plugins have access to a
-`CordovaInterface` object, which can access the Android `Activity`
-that runs the application.  This is the `Context` required to launch a
-new Android `Intent`.  The `CordovaInterface` allows plugins to start
-an `Activity` for a result, and to set the callback plugin for when
-the `Intent` returns to the application.
-
-As of Cordova 2.0, Plugins can no longer directly access the
-`Context`, and the legacy `ctx` member is deprecated. All `ctx`
-methods exist on the `Context`, so both `getContext()` and
-`getActivity()` can return the required object.
-
-## Debugging Android Plugins
-
-Eclipse allows you to debug plugins as Java source included in the
-project.  Only the latest version of the Android Developer Tools
-allows you to attach source code to _JAR_ dependencies, so this
-feature is not yet fully supported.

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/android/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/android/tools.md b/docs/en/3.6.1/guide/platforms/android/tools.md
deleted file mode 100644
index 2084368..0000000
--- a/docs/en/3.6.1/guide/platforms/android/tools.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.
----
-
-# Android Shell Tool Guide
-
-This guide shows how to use Cordova's set of platform-centered shell
-tools to develop Android apps. This development path, discussed in the
-Overview, may offer you a greater range of development options than
-the cross-platform CLI tool described in The Command-Line Interface.
-For example, you need to use shell tools when deploying a custom
-Cordova WebView alongside native components.  Before using either
-development path, you must first configure the Android SDK environment
-as described in the Android Platform Guide.
-
-To enable shell tools for Android, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand each you wish to target,
-`android` in this case. The relevant tools are typically available in
-the top-level `bin` directory, otherwise consult the __README__ file
-for more detailed directions.
-
-These tools allow you to create, build, and run Android apps.  For
-information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Create a Project
-
-Run the `create` command, specifying the existing path to the project,
-the reverse-domain-style package identifier, and the app's display
-name.  Here is the syntax for both Mac/Linux and Windows:
-
-        $ /path/to/cordova-android/bin/create /path/to/project com.example.project_name ProjectName
-
-        C:\>\path\to\cordova-android\bin\create.bat \path\to\project com.example.project_name ProjectName
-
-## Build
-
-This cleans then builds a project.
-
-Debug, on Mac/Linux or Windows:
-
-        $ /path/to/project/cordova/build --debug
-
-        C:\>\path\to\project\cordova\build.bat --debug
-
-Release, on Mac/Linux or Windows:
-
-        $ /path/to/project/cordova/build --release
-
-        C:\>\path\to\project\cordova\build.bat --release
-
-## Run the App
-
-The `run` command accepts the following _optional_ parameters:
-
-  * Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
-
-  * Build specification. This includes `--debug`, `--release`, or `--nobuild`.
-
-        $ /path/to/project/cordova/run [Target] [Build]
-
-        C:\>\path\to\project\cordova\run.bat [Target] [Build]
-
-Make sure you create at least one Android Virtual Device, otherwise
-you're prompted to do so with the `android` command.  If more than one
-AVD is available as a target, you're prompted to select one. By
-default the `run` command detects a connected device, or a currently
-running emulator if no device is found.
-
-## Logging
-
-        $ /path/to/project/cordova/log
-
-        C:\>\path\to\project\cordova\log.bat
-
-## Cleaning
-
-        $ /path/to/project/cordova/clean
-
-        C:\>\path\to\project\cordova\clean.bat
-
-## Manual Use of Ant
-
-If you wish to call Ant directly from the command line such as
-`ant debug install`, you need to specify additional parameters to the ant
-command:
-
-        ant debug install -Dout.dir=ant-build -Dgen.absolute.dir=ant-gen
-
-This is because the directories used by Cordova's Ant scripts are different
-than the default. This is done to avoid conflicts when Ant is run from the
-command line versus inside Eclipse/ADT.
-
-These additional parameters are automatically added for you when using
-the `cordova/build` and `cordova/run` scripts described above. For this
-reason it is recommended to use the `cordova/build` and `cordova/run` scripts
-instead of calling Ant directly from the command line.
-

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/android/upgrade.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/android/upgrade.md b/docs/en/3.6.1/guide/platforms/android/upgrade.md
deleted file mode 100644
index 1e6b632..0000000
--- a/docs/en/3.6.1/guide/platforms/android/upgrade.md
+++ /dev/null
@@ -1,454 +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.
----
-
-# Upgrading Android
-
-This guide shows how to modify Android projects 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 for information how to update the
-version of the CLI.
-
-## Upgrading to 3.3.0 from 3.2.0
-
-Follow the same instructions as for `3.2.0`.
-
-Starting with 3.3.0, the Cordova runtime is now compiled as an Android Library
-instead of a Jar. This should have no effect for command-line usage, but IDE
-users will need to import the newly added `MyProject-CordovaLib` project into
-their workspace.
-
-## Upgrading to 3.2.0 from 3.1.0
-
-For projects that were created with the cordova CLI: 
-
-1. Update the `cordova` CLI version. See The Command-Line Interface.
-
-2. Run `cordova platform update android`
-        
-For projects not created with the cordova CLI, run:
-
-        bin/update <project_path>
-
-**WARNING:**  On Android 4.4 - Android 4.4.3, creating a file input element with type="file" will not open the file picker dialog.
-This is a regression with Chromium on Android and the problem can be reproduced in the standalone Chrome browser on Android (see http://code.google.com/p/android/issues/detail?id=62220)  The suggested workaround is to use the FileTransfer and File plugins for Android 4.4. You can listen for an onClick event from the input type="file" and then pop up a file picker UI. In order to tie the form data with the upload, you can use JavaScript to attach form values to the multi-part POST request that FileTransfer makes.
-
-
-## Upgrading to 3.1.0 from 3.0.0
-
-For projects that were created with the cordova CLI: 
-
-1. Update the `cordova` CLI version. See The Command-Line Interface.
-
-2. Run `cordova platform update android`
-        
-For projects not created with the cordova CLI, run:
-
-        bin/update <project_path>
-        
-## Upgrade to the CLI (3.0.0) from 2.9.0
-
-1. Create a new Apache Cordova 3.0.0 project using the cordova CLI, as
-   described in The Command-Line Interface.
-
-2. Add your platforms the cordova project, for example: `cordova
-   platform add android`.
-
-3. Copy the contents of your project's `www` directory to the `www` directory
-   at the root of the cordova project you just created.
-
-4. Copy any native assets from your old project into the appropriate
-   directories under `platforms/android`: this directory is where your
-   native cordova-android project exists.
-
-5. Use the cordova CLI tool to install any plugins you need. Note that
-   the CLI handles all core APIs as plugins, so they may need to be
-   added. Only 3.0.0 plugins are compatible with the CLI.
-
-## Upgrade to 3.0.0 from 2.9.0
-
-1. Create a new Apache Cordova Android project.
-
-2. Copy the contents of the `www` directory to the new project.
-
-3. Copy any native Android assets from the `res` directory to the new project.
-
-4. Copy over any plugins you installed from the `src` subdirectories into the new project.
-
-5. Make sure to upgrade any deprecated `<plugin>` references from your old `config.xml` file to the new `<feature>` specification.
-
-6. Update any references to the `org.apache.cordova.api` package to be `org.apache.cordova`.
-
-   __NOTE__: all core APIs have been removed and must be installed as plugins. Please see the Using Plugman to Manage Plugins Guide for details.
-
-## Upgrade to 2.9.0 from 2.8.0
-
-1. Run `bin/update <project_path>`.
-
-## Upgrade to 2.8.0 from 2.7.0
-
-1. Remove `cordova-2.7.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.8.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-<!-- SS Eclipse -->
-
-4. Copy the new `cordova.js` into your project.
-
-5. Update your HTML to use the new `cordova.js` file.
-
-6. Copy the `res/xml/config.xml` file to match `framework/res/xml/config.xml`.
-
-7. Update `framework/res/xml/config.xml` to have similar settings as it did previously.
-
-8. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.7.0 from 2.6.0
-
-1. Remove `cordova-2.6.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.7.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.7.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.7.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Update `framework/res/xml/config.xml` to have similar settings as it did previously.
-
-8. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.6.0 from 2.5.0
-
-1. Remove `cordova-2.5.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.6.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.6.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.6.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Update `framework/res/xml/config.xml` to have similar settings as it did previously.
-
-8. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-Run `bin/update <project>` with the project path listed in the Cordova Source directory.
-
-## Upgrade to 2.5.0 from 2.4.0
-
-1. Remove `cordova-2.4.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.5.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.5.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.5.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Update `framework/res/xml/config.xml` to have similar settings as it did previously.
-
-8. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.4.0 from 2.3.0
-
-1. Remove `cordova-2.3.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.4.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.4.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.4.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.3.0 from 2.2.0
-
-1. Remove `cordova-2.2.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.3.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.3.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.3.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.2.0 from 2.1.0
-
-1. Remove `cordova-2.1.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.2.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.2.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.2.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.1.0 from 2.0.0
-
-1. Remove `cordova-2.0.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.1.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.1.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.1.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-7. Copy files from `bin/templates/cordova` to the project's `cordova` directory.
-
-## Upgrade to 2.0.0 from 1.9.0
-
-1. Remove `cordova-1.9.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-2.0.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-2.0.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.0.0.js` file.
-
-6. Copy the `res/xml/config.xml` to match `framework/res/xml/config.xml`.
-
-In the 2.0.0 release, the `config.xml` file combines and replaces
-`cordova.xml` and `plugins.xml`.  The old files are deprecated, and
-while they still work in 2.0.0, will stop working in a future release.
-
-## Upgrade to 1.9.0 from 1.8.1
-
-1. Remove `cordova-1.8.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.9.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.9.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-1.9.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-Due to the introduction of the `CordovaWebView` in the 1.9.0 release,
-third-party plugins may not work.  These plugins need to get a context
-from the `CordovaInterface` using `getContext()` or `getActivity()`.
-If you are not an experienced Android developer, please contact the
-plugin maintainer and add this task to their bug tracker.
-
-## Upgrade to 1.8.0 from 1.8.0
-
-1. Remove `cordova-1.8.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.8.1.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.8.1.js` into your project.
-
-5. Update your HTML to use the new `cordova-1.8.1.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-## Upgrade to 1.8.0 from 1.7.0
-
-1. Remove `cordova-1.7.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.8.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.8.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-1.8.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-## Upgrade to 1.8.0 from 1.7.0
-
-1. Remove `cordova-1.7.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.8.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.8.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-1.8.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-## Upgrade to 1.7.0 from 1.6.1
-
-1. Remove `cordova-1.6.1.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.7.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.7.0.js` into your project.
-
-5. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-## Upgrade to 1.6.1 from 1.6.0
-
-1. Remove `cordova-1.6.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.6.1.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.6.1.js` into your project.
-
-5. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-## Upgrade to 1.6.0 from 1.5.0
-
-1. Remove `cordova-1.5.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.6.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.6.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-1.6.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-7. Replace `res/xml/phonegap.xml` with `res/xml/cordova.xml` to match `framework/res/xml/cordova.xml`.
-
-## Upgrade to 1.5.0 from 1.4.0
-
-1. Remove `phonegap-1.4.0.jar` from the project's `libs` directory.
-
-2. Add `cordova-1.5.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `cordova-1.5.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-1.5.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-7. Replace `res/xml/phonegap.xml` with `res/xml/cordova.xml` to match `framework/res/xml/cordova.xml`.
-
-## Upgrade to 1.4.0 from 1.3.0
-
-1. Remove `phonegap-1.3.0.jar` from the project's `libs` directory.
-
-2. Add `phonegap-1.4.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `phonegap-1.4.0.js` into your project.
-
-5. Update your HTML to use the new `phonegap-1.4.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-7. Update `res/xml/phonegap.xml` to match `framework/res/xml/phonegap.xml`.
-
-## Upgrade to 1.3.0 from 1.2.0
-
-1. Remove `phonegap-1.2.0.jar` from the project's `libs` directory.
-
-2. Add `phonegap-1.3.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `phonegap-1.3.0.js` into your project.
-
-5. Update your HTML to use the new `phonegap-1.2.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-7. Update `res/xml/phonegap.xml` to match `framework/res/xml/phonegap.xml`.
-
-## Upgrade to 1.2.0 from 1.1.0
-
-1. Remove `phonegap-1.1.0.jar` from the project's `libs` directory.
-
-2. Add `phonegap-1.2.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `phonegap-1.2.0.js` into your project.
-
-5. Update your HTML to use the new `phonegap-1.2.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-7. Update `res/xml/phonegap.xml` to match `framework/res/xml/phonegap.xml`.
-
-## Upgrade to 1.1.0 from 1.0.0
-
-1. Remove `phonegap-1.0.0.jar` from the project's `libs` directory.
-
-2. Add `phonegap-1.1.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `phonegap-1.1.0.js` into your project.
-
-5. Update your HTML to use the new `phonegap-1.1.0.js` file.
-
-6. Update `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-
-## Upgrade to 1.0.0 from 0.9.6
-
-1. Remove `phonegap-0.9.6.jar` from the project's `libs` directory.
-
-2. Add `phonegap-1.0.0.jar` to the project's `libs` directory.
-
-3. If you use Eclipse, please refresh your Eclipse project and do a clean.
-
-4. Copy the new `phonegap-1.0.0.js` into your project.
-
-5. Update your HTML to use the new `phonegap-1.0.0.js` file.
-
-6. Add the `res/xml/plugins.xml` to match `framework/res/xml/plugins.xml`.
-

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/android/webview.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/android/webview.md b/docs/en/3.6.1/guide/platforms/android/webview.md
deleted file mode 100644
index 1c497d5..0000000
--- a/docs/en/3.6.1/guide/platforms/android/webview.md
+++ /dev/null
@@ -1,131 +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 WebViews
-
-This guide shows how to embed a Cordova-enabled WebView component
-within a larger Android application. For details on how these
-components can communicate with each other, see Application Plugins.
-
-If you're unfamiliar with Android, you should first familiarize
-yourself with the Android Platform Guide and have the latest Android
-SDK installed before you attempt the more unusual development option
-of embedding a WebView.  Starting with Cordova 1.9, the Android
-platform relies on a `CordovaWebView` component, which builds on a
-legacy `CordovaActivity` component that pre-dates the 1.9 release.
-
-1. To follow these instructions, make sure you have the latest Cordova
-   distribution. Download it from
-   [cordova.apache.org](http://cordova.apache.org) and unzip its
-   Android package.
-
-1. Navigate to the Android package's `/framework` directory and run
-   `ant jar`. It creates the Cordova `.jar` file, formed as
-   `/framework/cordova-3.6.1.jar`.
-
-1. Copy the `.jar` file into the Android project's `/libs` directory.
-
-1. Add the following to the application's `/res/xml/main.xml` file,
-   with the `layout_height`, `layout_width` and `id` modified to suit
-   the application:
-
-        <org.apache.cordova.CordovaWebView
-            android:id="@+id/tutorialView"
-            android:layout_width="match_parent"
-            android:layout_height="match_parent" />
-
-1. Modify the activity so that it implements the `CordovaInterface`.
-   It should implement the included methods.  You may wish to copy
-   them from `/framework/src/org/apache/cordova/CordovaActivity.java`,
-   or else implement them on your own.  The following code fragment
-   shows a basic application that relies on the interface. Note how
-   the referenced view id matches the `id` attribute specified in the
-   XML fragment shown above:
-
-        public class CordovaViewTestActivity extends Activity implements CordovaInterface {
-            CordovaWebView cwv;
-            /* Called when the activity is first created. */
-            @Override
-            public void onCreate(Bundle savedInstanceState) {
-                super.onCreate(savedInstanceState);
-                setContentView(R.layout.main);
-                cwv = (CordovaWebView) findViewById(R.id.tutorialView);
-                Config.init(this);
-                cwv.loadUrl(Config.getStartUrl());
-            }
-
-1. If the application needs to use the camera, implement the
-   following:
-
-        @Override
-        public void setActivityResultCallback(CordovaPlugin plugin) {
-            this.activityResultCallback = plugin;
-        }
-        /**
-         * Launch an activity for which you would like a result when it finished. When this activity exits,
-         * your onActivityResult() method is called.
-         *
-         * @param command           The command object
-         * @param intent            The intent to start
-         * @param requestCode       The request code that is passed to callback to identify the activity
-         */
-        public void startActivityForResult(CordovaPlugin command, Intent intent, int requestCode) {
-            this.activityResultCallback = command;
-            this.activityResultKeepRunning = this.keepRunning;
-            
-            // If multitasking turned on, then disable it for activities that return results
-            if (command != null) {
-                this.keepRunning = false;
-            }
-        
-            // Start activity
-            super.startActivityForResult(intent, requestCode);
-        }   
-    
-        @Override
-        /**
-         * Called when an activity you launched exits, giving you the requestCode you started it with,
-         * the resultCode it returned, and any additional data from it.
-         *
-         * @param requestCode       The request code originally supplied to startActivityForResult(),
-         *                          allowing you to identify who this result came from.
-         * @param resultCode        The integer result code returned by the child activity through its setResult().
-         * @param data              An Intent, which can return result data to the caller (various data can be attached to Intent "extras").
-         */
-        protected void onActivityResult(int requestCode, int resultCode, Intent intent) {
-            super.onActivityResult(requestCode, resultCode, intent);
-            CordovaPlugin callback = this.activityResultCallback;
-            if (callback != null) {
-                callback.onActivityResult(requestCode, resultCode, intent);
-            }
-        }
-
-1. Finally, remember to add the thread pool, otherwise plugins
-   have no threads on which to run:
-
-        @Override
-        public ExecutorService getThreadPool() {
-            return threadPool;
-        }
-
-1. Copy the application's HTML and JavaScript files to the Android
-   project's `/assets/www` directory.
-
-1. Copy the `config.xml` file from `/framework/res/xml` to the
-   project's `/res/xml` directory.

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e361eb3d/docs/en/3.6.1/guide/platforms/blackberry/upgrade.md
----------------------------------------------------------------------
diff --git a/docs/en/3.6.1/guide/platforms/blackberry/upgrade.md b/docs/en/3.6.1/guide/platforms/blackberry/upgrade.md
deleted file mode 100644
index 3803df2..0000000
--- a/docs/en/3.6.1/guide/platforms/blackberry/upgrade.md
+++ /dev/null
@@ -1,431 +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.
----
-
-# Upgrading BlackBerry
-
-This guide shows how to modify BlackBerry projects to upgrade from
-older versions of Cordova.  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 for information
-how to update the version of the CLI.
-
-## Upgrading 2.8.0 projects to 2.9.0 ##
-
-BlackBerry 10:
-
-1. Download and extract the Cordova 2.9.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.9.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. This becomes the home of your updated project.
-
-5. Copy your project's source from the old project's `/www` directory to the new project's `/www` directory.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-### BlackBerryOS/Playbook ###
-
-1. Download and extract the Cordova 2.9.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.9.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in iOS Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova.js` file from the new project into the `www` directory, and delete the `www/cordova.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrading 2.7.0 projects to 2.8.0 ##
-
-BlackBerry 10:
-
-BlackBerry 10 uses the new CLI tooling and manages core APIs as plugins. The instructions migrate your project to a new project, rather than updating an existing project, due to the complexity of updating an old project.
-Also note that the cordova js script file is now called 'cordova.js' and no longer contains a version string.
-
-1. Download and extract the Cordova 2.8.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.8.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. This becomes the home of your updated project.
-
-5. Copy your project's source from the old project's `/www` directory to the new project's `/www` directory.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-BlackBerryOS/Playbook:
-
-1. Download and extract the Cordova 2.8.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.8.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in iOS Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova.js` file from the new project into the `www` directory, and delete the `www/cordova.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrading 2.6.0 projects to 2.7.0 ##
-
-1. Download and extract the Cordova 2.7.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.7.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova-2.7.0.js` file from the new project into the `www` directory, and delete the `www/cordova-2.6.0.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova-2.7.0.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrade to 2.6.0 from 2.5.0 ##
-
-Updating the PhoneGap download directory:
-
-It is recommended that you download a fresh copy of the entire directory.
-
-However, here are the new parts needed for the piecemeal update:
-
-1. Update the cordova.blackberry.js file in the `Phonegap-2.6.0/lib/blackberry/javascript` directory.
-
-2. Update the `ext`, `ext-air`, and `ext-qnx` in the `Phonegap-2.6.0/lib/blackberry/framework` directory.
-
-3. Update the `build.xml` file in the `Phonegap-2.6.0/lib/blackberry` directory.
-
-4. Update the `Phonegap-2.6.0/lib/blackberry/bin` directory.
-
-5. Update the `VERSION` file in the `Phonegap-2.6.0/lib/blackberry` directory.
-
-Updating the `example/` directory or migrating an existing project:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Update the contents of the `ext-qnx/` directory.
-
-4. Copy the new `cordova-2.6.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.6.0.js` file.
-
-## Upgrade to 2.5.0 from 2.4.0 ##
-
-Updating the PhoneGap download directory:
-
-It is recommended that you download a fresh copy of the entire directory.
-
-However, here are the new parts needed for the piecemeal update:
-
-1. Update the cordova.blackberry.js file in the `Phonegap-2.5.0/lib/blackberry/javascript` directory.
-
-2. Update the `ext`, `ext-air`, and `ext-qnx` in the `Phonegap-2.5.0/lib/blackberry/framework` directory.
-
-3. Update the `build.xml` file in the `Phonegap-2.5.0/lib/blackberry` directory.
-
-4. Update the `Phonegap-2.5.0/lib/blackberry/bin` directory.
-
-5. Update the `VERSION` file in the `Phonegap-2.5.0/lib/blackberry` directory.
-
-Updating the example/ directory or migrating an existing project:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Update the contents of the `ext-qnx/` directory.
-
-4. Copy the new `cordova-2.5.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.5.0.js` file.
-
-## Upgrade to 2.4.0 from 2.3.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.4.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.4.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.3.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.3.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.3.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.3.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.3.0/` directory to `cordova.2.4.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.4.0.js` file.
-
-## Upgrade to 2.3.0 from 2.2.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.3.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.3.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.2.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.2.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.2.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.2.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.2.0/` directory to `cordova.2.3.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.3.0.js` file.
-
-## Upgrade to 2.2.0 from 2.1.0 ##
-
-Updating just the www directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.2.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.2.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.1.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.1.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.1.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.1.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.1.0/` directory to `cordova.2.2.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.2.0.js` file.
-
-## Upgrade to 2.1.0 from 2.0.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.1.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-2.1.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.0.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.0.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.2.0.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.2.0.0/` directory to `cordova.2.1.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-2.1.0.js` file.
-
-## Upgrade to 2.0.0 from 1.9.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.0.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-2.0.0.js` file.
-
-6. Update the `www/plugins.xml` file. Two plugins changed their
-   namespace/service label. Change the old entries for the Capture and
-   Contact plugins from:
-
-        <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-        <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-
-   To:
-
-        <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-        <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.1.9.0/ext/` directory.
-
-3. Update the contents of the `cordova.1.9.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.1.9.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.1.9.0/` directory to `cordova.2.0.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-2.0.0.js` file.
-
-8. Open the `www` directory and update the `plugins.xml` file. Two plugins
-   changed their namespace/service label. Change the old entries for the
-   Capture and Contact plugins from:
-
-         <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-         <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-
-   To:
-
-         <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-         <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-
-- To upgrade to 1.8.0, please go from 1.7.0
-
-## Upgrade to 1.8.0 from 1.7.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-1.8.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-1.8.0.js` file.
-
-6. Update the `www/plugins.xml` file. Two plugins changed their
-   namespace/service label. Change the old entries for the Capture and
-   Contact plugins from:
-
-        <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-        <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-
-   To:
-
-        <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-        <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.1.7.0/ext/` directory.
-
-3. Update the contents of the `cordova.1.7.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.1.7.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.1.7.0/` directory to `cordova.1.8.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-1.8.0.js` file.
-
-8. Open the `www` directory and update the `plugins.xml` file. Two plugins
-   changed their namespace/service label. Change the old entries for the
-   Capture and Contact plugins from:
-
-         <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-         <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-
-   To:
-
-         <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-         <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-


Mime
View raw message