You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by mw...@apache.org on 2013/07/04 20:19:36 UTC
[01/20] docs commit: [CB-3827] change Project Settings to
Configuration
Updated Branches:
refs/heads/master 26ec1cd65 -> 2a1e93283
[CB-3827] change Project Settings to Configuration
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/6ac5f0c1
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/6ac5f0c1
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/6ac5f0c1
Branch: refs/heads/master
Commit: 6ac5f0c109de3fa6798e15bcd911e82f2446aea9
Parents: 26ec1cd
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 10:21:21 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 10:21:21 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/getting-started/index.md | 57 +++++++++++++++-----
.../guide/plugin-development/android/index.md | 2 +-
.../plugin-development/blackberry/index.md | 2 +-
.../plugin-development/blackberry10/index.md | 2 +-
docs/en/edge/guide/plugin-development/index.md | 10 ++--
.../edge/guide/plugin-development/ios/index.md | 2 +-
.../plugin-development/windows-phone/index.md | 2 +-
.../guide/project-settings/android/index.md | 2 +-
.../guide/project-settings/blackberry/index.md | 2 +-
.../guide/project-settings/firefoxos/index.md | 2 +-
docs/en/edge/guide/project-settings/index.md | 14 ++---
.../en/edge/guide/project-settings/ios/index.md | 2 +-
.../guide/project-settings/windows8/index.md | 2 +-
.../en/edge/guide/project-settings/wp7/index.md | 2 +-
.../en/edge/guide/project-settings/wp8/index.md | 2 +-
15 files changed, 69 insertions(+), 36 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/getting-started/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/index.md b/docs/en/edge/guide/getting-started/index.md
index 6baa27d..28461fb 100644
--- a/docs/en/edge/guide/getting-started/index.md
+++ b/docs/en/edge/guide/getting-started/index.md
@@ -29,16 +29,49 @@ platform you are targeting. This installation is necessary regardless
of whether you do the majority of your work in the SDK or use the CLI
for your build cycle.
-This section tells you all you need to know to set up your development
-environment to support each platform: where to obtain the SDK, how to
+Each platform guide listed below tells you what you need to know to
+set up each development environment: where to obtain the SDK, how to
set up device emulators, how to connect devices for direct testing,
-and managing signing key requirements.
-
-- Android Platform Guide (Windows, Mac, Linux)
-- BlackBerry Platform Guide (Windows, Mac)
-- BlackBerry Platform Guide 10 (Windows, Mac)
-- iOS Platform Guide (Mac)
-- Windows Phone 7 Platform Guide (Windows 7 or 8)
-- Windows Phone 8 Platform Guide (Windows 8)
-- Windows 8 Platform Guide (Windows 8)
-- Tizen Platform Guide
+and managing signing key requirements. Additional guides provide
+information on each platform's available configuration settings,
+instructions to add plugins, how to upgrade each platform, and
+platform-specific command-line tools that serve as an alternative to
+the `cordova` command-line tool.
+
+## Android (Windows, Mac, Linux)
+
+* Android Platform Guide
+* Android Configuration
+* Android Plugins
+
+## BlackBerry (Windows, Mac)
+
+* BlackBerry Platform Guide
+* BlackBerry 10 Platform Guide
+* BlackBerry Configuration
+* BlackBerry 10 Plugins
+
+## iOS (Mac)
+
+* iOS Platform Guide
+* iOS Configuration
+* iOS Plugins
+
+## Windows Phone
+
+* Windows Phone 7 Platform Guide (Windows 7 or 8)
+* Windows Phone 7 Configuration
+
+* Windows Phone 8 Platform Guide (Windows 8)
+* Windows Phone 8 Configuration
+
+* Windows 8 Platform Guide (Windows 8)
+* Windows 8 Configuration
+
+## Tizen
+
+* Tizen Platform Guide
+
+## FirefoxOS
+
+* FirefoxOS Configuration
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/plugin-development/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/android/index.md b/docs/en/edge/guide/plugin-development/android/index.md
index 2f372e7..39a79d7 100644
--- a/docs/en/edge/guide/plugin-development/android/index.md
+++ b/docs/en/edge/guide/plugin-development/android/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Developing a Plugin on Android
+# Android Plugins
Writing a plugin requires an understanding of the architecture of Cordova-Android. Cordova-Android consists
of an Android WebView with hooks attached to it. These plugins are represented as class mappings in the config.xml
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/plugin-development/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/blackberry/index.md b/docs/en/edge/guide/plugin-development/blackberry/index.md
index 3e4fc30..ebdb780 100644
--- a/docs/en/edge/guide/plugin-development/blackberry/index.md
+++ b/docs/en/edge/guide/plugin-development/blackberry/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Developing a Plugin on BlackBerry
+BlackBerry Plugins
=================================
## How to make the Echo plugin on Blackberry
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/plugin-development/blackberry10/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/blackberry10/index.md b/docs/en/edge/guide/plugin-development/blackberry10/index.md
index 2b6bfca..5eb1401 100644
--- a/docs/en/edge/guide/plugin-development/blackberry10/index.md
+++ b/docs/en/edge/guide/plugin-development/blackberry10/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Developing a Plugin on BlackBerry 10
+# BlackBerry 10 Plugins
This is a continuation of the Plugin Development Guide for Cordova. Once you have reviewed that content, now let's look at things we need to have the Echo plugin for the BlackBerry 10 platform. Recall that the Echo plugin basically returns whatever string a user provides to the `window.echo` function:
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/plugin-development/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/index.md b/docs/en/edge/guide/plugin-development/index.md
index c2ad4c7..e90c415 100644
--- a/docs/en/edge/guide/plugin-development/index.md
+++ b/docs/en/edge/guide/plugin-development/index.md
@@ -101,10 +101,10 @@ with at least one native implementation. Details to do so for each
platform are listed below. These guides continue to build on the
simple Echo Plugin example discussed above.
-- Developing a Plugin on Android
-- Developing a Plugin on BlackBerry
-- Developing a Plugin on BlackBerry 10
-- Developing a Plugin on iOS
-- Developing a Plugin on Windows Phone
+- Android Plugins
+- BlackBerry Plugins
+- BlackBerry 10 Plugins
+- iOS Plugins
+- Windows Phone Plugins
The webOS and Tizen platforms currently do not support plugins.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/plugin-development/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/ios/index.md b/docs/en/edge/guide/plugin-development/ios/index.md
index 3f0d6d9..2e311e2 100644
--- a/docs/en/edge/guide/plugin-development/ios/index.md
+++ b/docs/en/edge/guide/plugin-development/ios/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Developing a Plugin on iOS
+# iOS Plugins
A plugin is an Objective-C class that extends the `CDVPlugin` class.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/plugin-development/windows-phone/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/windows-phone/index.md b/docs/en/edge/guide/plugin-development/windows-phone/index.md
index 8b16fe3..ed89361 100644
--- a/docs/en/edge/guide/plugin-development/windows-phone/index.md
+++ b/docs/en/edge/guide/plugin-development/windows-phone/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Developing a Plugin on Windows Phone
+Windows Phone Plugins
====================================
Writing a plugin for Cordova on Windows Phone requires a basic understanding of
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/android/index.md b/docs/en/edge/guide/project-settings/android/index.md
index e4b627a..b3c02b5 100644
--- a/docs/en/edge/guide/project-settings/android/index.md
+++ b/docs/en/edge/guide/project-settings/android/index.md
@@ -19,7 +19,7 @@
#
-->
-Project Settings for Android
+Android Configuration
===================================
The `config.xml` settings file controls various settings of Cordova. This is application wide, and not set per CordovaWebView Instance.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/blackberry/index.md b/docs/en/edge/guide/project-settings/blackberry/index.md
index 69b870b..ab266ad 100644
--- a/docs/en/edge/guide/project-settings/blackberry/index.md
+++ b/docs/en/edge/guide/project-settings/blackberry/index.md
@@ -19,7 +19,7 @@
#
-->
-Project Settings for BlackBerry
+BlackBerry Configuration
===================================
BlackBerry fully supports the
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/firefoxos/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/firefoxos/index.md b/docs/en/edge/guide/project-settings/firefoxos/index.md
index aed24a3..2806083 100644
--- a/docs/en/edge/guide/project-settings/firefoxos/index.md
+++ b/docs/en/edge/guide/project-settings/firefoxos/index.md
@@ -19,6 +19,6 @@
#
-->
-Project Settings for FirefoxOS
+FirefoxOS Configuration
===================================
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/index.md b/docs/en/edge/guide/project-settings/index.md
index 579e931..03df745 100644
--- a/docs/en/edge/guide/project-settings/index.md
+++ b/docs/en/edge/guide/project-settings/index.md
@@ -31,13 +31,13 @@ As with any abstraction layer, Apache Cordova cannot be a perfect silver bullet.
properties, characteristics and behaviours are encapsulated as much as possible as `<preference>` elements inside the
`config.xml` file. The following sub-sections linked to are guides which go into more details about these preferences.
-- Project Settings for iOS
-- Project Settings for Android
-- Project Settings for BlackBerry
-- Project Settings for Windows Phone 7
-- Project Settings for Windows Phone 8
-- Project Settings for Windows 8
-- Project Settings for FirefoxOS
+- iOS Configuration
+- Android Configuration
+- BlackBerry Configuration
+- Windows Phone 7 Configuration
+- Windows Phone 8 Configuration
+- Windows 8 Configuration
+- FirefoxOS Configuration
## config.xml Elements
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/ios/index.md b/docs/en/edge/guide/project-settings/ios/index.md
index 60e1129..ccb0ec4 100644
--- a/docs/en/edge/guide/project-settings/ios/index.md
+++ b/docs/en/edge/guide/project-settings/ios/index.md
@@ -19,7 +19,7 @@
#
-->
-Project Settings for iOS
+iOS Configuration
========================
The `config.xml` settings file controls various settings of Cordova. This is application wide, and not set per CDVViewController instance.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/windows8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/windows8/index.md b/docs/en/edge/guide/project-settings/windows8/index.md
index 7a4f706..dfeb618 100644
--- a/docs/en/edge/guide/project-settings/windows8/index.md
+++ b/docs/en/edge/guide/project-settings/windows8/index.md
@@ -19,7 +19,7 @@
#
-->
-Project Settings for Windows 8
+Windows 8 Configuration
===================================
Windows 8 does not currently support this feature.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/wp7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/wp7/index.md b/docs/en/edge/guide/project-settings/wp7/index.md
index 8c4da6c..23c8304 100644
--- a/docs/en/edge/guide/project-settings/wp7/index.md
+++ b/docs/en/edge/guide/project-settings/wp7/index.md
@@ -19,7 +19,7 @@
#
-->
-Project Settings for Windows Phone 7
+Windows Phone 7 Configuration
===================================
Windows Phone 7 does not currently have any additional configurable features.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/6ac5f0c1/docs/en/edge/guide/project-settings/wp8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/wp8/index.md b/docs/en/edge/guide/project-settings/wp8/index.md
index 5a59d78..de0e54b 100644
--- a/docs/en/edge/guide/project-settings/wp8/index.md
+++ b/docs/en/edge/guide/project-settings/wp8/index.md
@@ -19,7 +19,7 @@
#
-->
-Project Settings for Windows Phone 8
+Windows Phone 8 Configuration
===================================
Windows Phone 8 does not currently have any additional configurable features.
[14/20] [CB-3827] move platform-specific files within platforms dir;
rename dirs within platforms
Posted by mw...@apache.org.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/firefoxos/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/firefoxos/config.md b/docs/en/edge/guide/platforms/firefoxos/config.md
new file mode 100644
index 0000000..2806083
--- /dev/null
+++ b/docs/en/edge/guide/platforms/firefoxos/config.md
@@ -0,0 +1,24 @@
+<!--
+#
+# 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.
+#
+-->
+
+FirefoxOS Configuration
+===================================
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/ios/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/config.md b/docs/en/edge/guide/platforms/ios/config.md
new file mode 100644
index 0000000..ccb0ec4
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/config.md
@@ -0,0 +1,60 @@
+<!--
+#
+# 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 Configuration
+========================
+
+The `config.xml` settings file controls various settings of Cordova. This is application wide, and not set per CDVViewController instance.
+The `config.xml` file is located in your `<project folder>/<appname>` directory.
+
+## <preference>
+
+Various preferences (as **<preference>** tags) default on not breaking existing apps. The available preferences are:
+
+1. **DisallowOverscroll (boolean, defaults to false)** - set to true if you don't want the WebView to rubber-band
+
+2. **TopActivityIndicator (string, defaults to 'gray')** - this is the top spinning throbber in the status/battery bar, valid values are `whiteLarge`, `white`, and `gray`
+
+3. **EnableLocation (boolean, defaults to false)** - set to true, to initialize the Geolocation plugin at start-up (so the fix on your location can be more accurate) **DEPRECATED**: please set the **onload** attribute of the **Geolocation** plugin to **true** instead.
+
+4. **EnableViewportScale (boolean, defaults to false)** - set to true to prevent viewport scaling through a meta tag
+
+5. **AutoHideSplashScreen (boolean, defaults to true)** - set to false to control when the splashscreen is hidden through a JavaScript API
+
+6. **FadeSplashScreen (boolean, defaults to true)** - set to false to prevent the splash-screen to fade in and out when showing/hiding it.
+
+7. **FadeSplashScreenDuration (float, defaults to 2)** - The splash-screen Fade duration in seconds.
+
+8. **ShowSplashScreenSpinner (boolean, defaults to true)** - set to false to hide the splash-screen spinner
+
+9. **MediaPlaybackRequiresUserAction (boolean, defaults to false)** - set to true to not allow autoplayed HTML5 video
+
+10. **AllowInlineMediaPlayback (boolean, defaults to false)** - set to true to allow inline HTML5 media playback, also, the video element in the HTML document must also include the webkit-playsinline attribute
+
+11. **BackupWebStorage (string, defaults to 'cloud')** - valid values are 'none', 'cloud' and 'local'. Set to 'cloud' to allow the web storage data to be backed up to iCloud, and set to 'local' to only allow local backups (iTunes sync). Set to 'none' to not allow any backups of web storage.
+
+12. **KeyboardDisplayRequiresUserAction (boolean, defaults to true)** - set to false to open the keyboard when form elements get focus via the JavaScript focus() call.
+
+13. **SuppressesIncrementalRendering (boolean, defaults to false)** - set to true to wait until all new view content has been received before it is rendered.
+
+14. **HideKeyboardFormAccessoryBar (boolean, defaults to false)** - set to true to hide the additional toolbar that is on top of the keyboard (this is the toolbar that has the Prev, Next and Done buttons)
+
+15. **KeyboardShrinksView (boolean, defaults to false)** - set to true to shrink the WebView when the keyboard comes up. The WebView shrinks instead of the viewport shrinking and the page scrollable. This applies to apps that position their elements relative to the bottom of the WebView. This is the default behaviour on Android, and makes a lot of sense when building apps as opposed to webpages.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/ios/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/plugin.md b/docs/en/edge/guide/platforms/ios/plugin.md
new file mode 100644
index 0000000..61bc117
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/plugin.md
@@ -0,0 +1,230 @@
+---
+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 Plugins
+
+A plugin is an Objective-C class that extends the `CDVPlugin` class.
+
+Each plugin class must be registered using the config.xml file, as a <plugin> tag under the <plugins> key.
+
+## Plugin Class Mapping
+
+The JavaScript portion of a plugin always uses the `cordova.exec` method as follows:
+
+ exec(<successFunction>, <failFunction>, <service>, <action>, [<args>]);
+
+This marshals a request from the `UIWebView` to the iOS native side,
+more or less boiling down to calling the `action` method on the
+`service` class, with the arguments passed in the `args` array.
+
+The plugin must be added under the `<plugins>` tag of your Cordova-iOS
+application's project's `config.xml` file.
+
+ <feature name="LocalStorage">
+ <param name="ios-package" value="CDVLocalStorage" />
+ </feature>
+
+The feature name='name' should match what you use in the JavaScript
+`exec` call, and the value matches the name of the plugin's
+Objective-C class. param name should always be "ios-package".
+Otherwise the plugin may compile but would not be
+reachable by Cordova.
+
+## Plugin Initialization and Lifetime
+
+There is one instance of a plugin object that is created per-UIWebView, and the lifetime of the instance is tied to the UIWebView. Plugins are not instantiated until they are first referenced by a call from JS, unless the `onload` attribute set within config.xml. E.g.:
+
+ <plugin name="Echo" value="Echo" onload="true" />
+
+There is *no* designated initializer for plugins. Instead, plugins should use the `pluginInitialize` method for their start-up logic.
+
+Plugins with long-running requests, background activity (e.g. playing media), listeners or internal state should implement the `onReset` method and stop or clean up those activities. This method is run when the `UIWebView` navigates to a new page or refreshes, which reloads the JavaScript.
+
+## Writing an iOS Cordova Plugin
+
+We have JavaScript fire off a plugin request to the native side. We have the iOS Objective-C plugin mapped properly via the `config.xml` file. So what does the final iOS Objective-C Plugin class look like?
+
+What gets dispatched to the plugin via JavaScript's `exec` function gets passed into the corresponding Plugin class's `action` method. A plugin method has this signature:
+
+ - (void)myMethod:(CDVInvokedUrlCommand*)command
+ {
+ CDVPluginResult* pluginResult = nil;
+ NSString* myarg = [command.arguments objectAtIndex:0];
+
+ if (myarg != nil) {
+ pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK];
+ } else {
+ pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR messageAsString:@"Arg was null"];
+ }
+ [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
+ }
+
+1. [CDVInvokedUrlCommand.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVInvokedUrlCommand.h)
+2. [CDVPluginResult.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPluginResult.h)
+3. [CDVCommandDelegate.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVCommandDelegate.h)
+
+## iOS CDVPluginResult message types
+
+Using CDVPluginResult you can return a variety of result types back to your JavaScript callbacks, using class methods that look like:
+
+ + (CDVPluginResult*)resultWithStatus:(CDVCommandStatus)statusOrdinal messageAs...
+
+You can create `String`, `Int`, `Double`, `Bool`, `Array`,
+`Dictionary`, `ArrayBuffer`, and `Multipart` types. Or, don't attach
+any arguments (just send a status). Or, return an Error. You can
+even choose to not send any plugin result at all, in which case the
+callback does not fire.
+
+### Notes
+
+ * `messageAsArrayBuffer` expects `NSData*` and converts to an `ArrayBuffer` for your JavaScript callback (and `ArrayBuffers` sent to a plugin from JavaScript are converted to `NSData*`).
+ * `messageAsMultipart` expects an `NSArray*` containing any of the other supported types, and sends the whole array as the `arguments` to your JavaScript callback.
+ * Quirk: this is not just syntactic sugar (though it is sweet). This way, all of the arguments are serialized/deserialized as necessary. e.g. it is safe to return `NSData*` as multipart, but not as `Array`/`Dictionary`.
+
+## Plugin Signatures
+
+The **new signature** supported beginning in **Cordova 2.1.0** is:
+
+ - (void)myMethod:(CDVInvokedUrlCommand*)command;
+
+The **old (deprecated)** signature is:
+
+ - (void)myMethod:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
+
+Basically, the options dictionary has been removed for the new signature, and the callbackId is not the 0th index item for the arguments array, but it is now in a separate property.
+
+## Echo Plugin iOS Plugin
+
+We would add the following to the `<plugins>` tag of the project's `config.xml` file:
+
+ <plugin name="Echo" value="Echo" />
+
+Then we would add the following files (`Echo.h` and `Echo.m`) to the Plugins folder inside our Cordova-iOS
+application folder:
+
+ /********* Echo.h Cordova Plugin Header *******/
+
+ #import <Cordova/CDV.h>
+
+ @interface Echo : CDVPlugin
+
+ - (void)echo:(CDVInvokedUrlCommand*)command;
+
+ @end
+
+ /********* Echo.m Cordova Plugin Implementation *******/
+
+ #import "Echo.h"
+ #import <Cordova/CDV.h>
+
+ @implementation Echo
+
+ - (void)echo:(CDVInvokedUrlCommand*)command
+ {
+ CDVPluginResult* pluginResult = nil;
+ NSString* echo = [command.arguments objectAtIndex:0];
+
+ if (echo != nil && [echo length] > 0) {
+ pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:echo];
+ } else {
+ pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR];
+ }
+
+ [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
+ }
+
+ @end
+
+Let's take a look at the code. At the top we have all of the necessary
+Cordova imports. Our class extends from `CDVPlugin` - very important.
+
+This plugin only supports one action, the `echo` action. First, we
+grab the echo string using the `objectAtIndex` method on our `args`,
+telling it we want to get the 0th parameter in the arguments array. We
+do a bit of parameter checking: make sure it is not `nil`, and make
+sure it is not a zero-length string.
+
+If it is, we return a `PluginResult` with an `ERROR` status. If all of
+those checks pass, then we return a `PluginResult` with an `OK`
+status, and pass in the `echo` string we received in the first place
+as a parameter.
+
+Finally, we send the result to `self.commandDelegate`, which executes
+the `exec` method's success or failure callbacks on the JavaScript
+side. If the success callback is called, it passes in the `echo`
+parameter.
+
+## Threading
+
+Plugin methods are executed in the same thread as the UI. If your
+plugin requires a great deal of processing or requires a blocking
+call, you should use a background thread. For example:
+
+ - (void)myPluginMethod:(CDVInvokedUrlCommand*)command
+ {
+ // Check command.arguments here.
+ [self.commandDelegate runInBackground:^{
+ NSString* payload = nil;
+ // Some blocking logic...
+ CDVPluginResult* pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:payload];
+ // The sendPluginResult method is thread-safe.
+ [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
+ }];
+ }
+
+## Advanced Plugin Functionality
+
+See other methods that you can override in:
+
+1. [CDVPlugin.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.h)
+2. [CDVPlugin.m](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.m)
+
+For example, you can hook into the `pause`, `resume`, app terminate and `handleOpenURL` events.
+
+## Debugging Plugins
+
+To debug the Objective-C side, you would use Xcode's built-in debugger.
+For JavaScript, on iOS 5.0 you can use
+[Weinre, an Apache Cordova Project](https://github.com/apache/cordova-weinre) or
+[iWebInspector, a third-party utility](http://www.iwebinspector.com/)
+
+For iOS 6, you would use Safari 6.0 to simply attach to your app
+running in the iOS 6 Simulator.
+
+## Common Pitfalls
+
+* Don't forget to add your plugin's mapping to config.xml. If you forget, an error is logged in the Xcode console.
+* Don't forget to add any hosts you connect to in the whitelist, as described in Domain Whitelist Guide. If you forget, an error is logged in the Xcode console.
+
+## Deprecated Plugin Signature Note
+
+The **old (deprecated)** signature is:
+
+ - (void) myMethod:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
+
+The Objective-C plugin method's `options` parameter is deprecated, and
+should not be used. For legacy reasons, the last JavaScript object
+passed in the `args` array is passed in as the `options` dictionary of
+the Objective-C method. You must make sure that any JavaScript object
+that is passed in as an element in the `args` appears as the last item
+in the array. Otherwise it throws off the array index for all
+subsequent parameters of the Objective-C array. Only one JavaScript
+object is supported for the options dictionary, and only the last one
+encountered will be passed to the native method. Errors stemming from
+this problem are the reason `options` has been deprecated.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/ios/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/upgrading.md b/docs/en/edge/guide/platforms/ios/upgrading.md
new file mode 100644
index 0000000..4009bc2
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/upgrading.md
@@ -0,0 +1,438 @@
+---
+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 iOS
+=====================
+
+Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, you must use the latest shipped version of the iOS SDK, which is iOS 6. The iOS 6 SDK requires Xcode 4.5.
+
+## Upgrading 2.8.0 projects to 2.9.0 ##
+
+1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.9.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova.js** (note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your **www** folder, and delete your **www/cordova.js** file
+6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
+7. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
+
+## Upgrading 2.7.0 projects to 2.8.0 ##
+
+1. **Download and extract the Cordova 2.8.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.8.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova.js** (note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your **www** folder, and delete your **www/cordova-2.7.0.js** file
+6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
+7. Update any <plugin> tags that are in your **config.xml** to <feature> tags. Note that existing <plugin> tags will still work, but are deprecated. You can copy this information in the **config.xml** for a new project. For example:
+
+ <plugins>
+ <plugin name="LocalStorage" value="CDVLocalStorage" />
+ <!-- other plugins -->
+ </plugins>
+
+ <!-- change to: (note that a <feature> tag is on the same level as <plugins> -->
+ <feature name="LocalStorage">
+ <param name="ios-package" value="CDVLocalStorage" />
+ </feature>
+ <!-- other <feature> tags -->
+
+8. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
+9. Add these two frameworks to your project:
+
+ OpenAL
+ ImageIO
+
+10. Update your project's target **Build Settings**. Under **Linking** -> **Other Linker Flags**, edit **"-Obj-C"** to be **"-ObjC"**
+
+11. Update your project's target **Build Settings**. Under **Linking** -> **Other Linker Flags**, change **"-all\_load"** to be **"-force\_load ${TARGET\_BUILD\_DIR}/libCordova.a"**. You would only need to do this if you have the problem defined in [this issue.](https://issues.apache.org/jira/browse/CB-3458)
+
+## Upgrading 2.6.0 projects to 2.7.0 ##
+
+1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.7.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. you need the assets from this new project.
+5. **Copy** the **www/cordova-2.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.6.0.js** file
+6. **Update** the Cordova script reference in your **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. Update (or replace, if you never changed the file) your **AppDelegate.m** file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=5c05ac80e056753c0e8736f887ba9f28d5b0774c;hp=623ad8ec3c46f656ea18c6c3a190d650dd64e479;hb=c6e71147386d4ad94b07428952d1aae0a9cbf3f5;hpb=c017fda8af00375a453cf27cfc488647972e9a23))
+8. In your **config.xml** file, [remove this line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=537705d76a5ef6bc5e57a8ebfcab78c02bb4110b;hp=8889726d9a8f8c530fe1371c56d858c34552992a;hb=064239b7b5fa9a867144cf1ee8b2fb798ce1f988;hpb=c9f233250d4b800f3412eeded811daaafb17b2cc).
+9. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
+
+
+## Upgrading 2.5.0 projects to 2.6.0 ##
+
+1. **Download and extract the Cordova 2.6.0 source** to a **permanent folder location** on your hard drive (say to `~/Documents/Cordova-2.6.0`)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the project's `www/cordova-2.6.0.js` file into your `www` folder, and delete your `www/cordova-2.5.0.js` file.
+6. **Update** the Cordova script reference in your `www/index.html` file (along with any other files that reference the script) to refer to the new `cordova-2.6.0.js` file.
+7. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=124a56bb4f361e95616f44d6d6f5a96ffa439b60;hp=318f79326176be8f16ebc93bad85dd745f4205b6;hb=a28c7712810a63396e9f32fa4eb94fe3f8b93985;hpb=36acdf55e4cab52802d73764c8a4b5b42cf18ef9))
+8. In your `config.xml` file, [add this new line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=1555b5e81de326a07efe0bccaa5f5e2326b07a9a;hp=0652d60f8d35ac13c825c572dca6ed01fea4a540;hb=95f16a6dc252db0299b8e2bb53797995b1e39aa1;hpb=a2de90b8f5f5f68bd9520bcbbb9afa3ac409b96d).
+9. In your `config.xml` file, [add this new line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=d307827b7e67301171a913417fb10003d43ce39d;hp=04260aa9786d6d74ab20a07c86d7e8b34e31968c;hb=97b89edfae3527828c0ca6bb2f6d58d9ded95188;hpb=942d33c8e7174a5766029ea1232ba2e0df745c3f).
+10. In your `config.xml` file, [UIWebViewBounce has ben changed to DisallowOverscroll - and default values are different](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=8889726d9a8f8c530fe1371c56d858c34552992a;hp=d307827b7e67301171a913417fb10003d43ce39d;hb=57982de638a4dce6ae130a26662591741b065f00;hpb=ec411f18309d577b4debefd9a2f085ba719701d5).
+10. In your `config.xml` file, the **EnableLocation** preference has been **deprecated**.
+11. Delete your `CordovaLib` folder, and copy the `CordovaLib` folder from the new project into your project's root folder.
+
+## Upgrading 2.4.0 projects to 2.5.0 ##
+
+1. **Download and extract the Cordova 2.5.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.5.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova-2.5.0.js** file from the new project into your **www** folder and delete your **www/cordova-2.4.0.js** file
+6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.5.0.js** file
+7. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=318f79326176be8f16ebc93bad85dd745f4205b6;hp=6dc7bfc84f0ecede4cc43d2a3256ef7c5383b9fe;hb=4001ae13fcb1fcbe73168327630fbc0ce44703d0;hpb=299a324e8c30065fc4511c1fe59c6515d4842f09))
+8. In your `config.xml` file, [add these new lines](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=903944c4b1e58575295c820e154be2f5f09e6314;hp=721c734120b13004a4a543ee25f4287e541f34be;hb=ae467249b4a256bd31ee89aea7a06f4f2316b8ac;hpb=9e39f7ef8096fb15b38121ab0e245a3a958d9cbb).
+9. In your `config.xml` file, [edit the root element, change it from cordova to widget](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=64e71636f5dd79fa0978a97b9ff5aa3860a493f5;hp=d8579352dfb21c14e5748e09b2cf3f4396450163;hb=0e711f8d09377a7ac10ff6be4ec17d22cdbee88d;hpb=57c3c082ed9be41c0588d0d63a1d2bfcd2ed878c).
+10. In your `config.xml` file, [remove the OpenAllWhitelistURLsInWebView preference](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=721c734120b13004a4a543ee25f4287e541f34be;hp=7d67508b70914aa921a16e79f79c00512502a8b6;hb=187bf21b308551bfb4b98b1a5e11edf04f699791;hpb=03b8854bdf039bcefbe0212db937abd81ac675e4).
+11. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.5.0, this has updated scripts)**
+12. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
+
+## Upgrading 2.3.0 projects to 2.4.0 ##
+
+1. **Download and extract the Cordova 2.4.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.4.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova-2.4.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.3.0.js** file
+6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.4.0.js** file
+7. Update (or replace, if you never changed the files) your `MainViewController.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/MainViewController.m;h=5f9eeac15c2437cd02a6eb5835b48374e9b94100;hp=89da1082d06ba5e5d0dffc5b2e75a3a06d5c2aa6;hb=b4a2e4ae0445ba7aec788090dce9b822d67edfd8;hpb=a484850f4610e73c7b20cd429a7794ba829ec997)).
+8. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=6dc7bfc84f0ecede4cc43d2a3256ef7c5383b9fe;hp=1ca3dafeb354c4442b7e149da4f281675aa6b740;hb=6749c17640c5fed8a7d3a0b9cca204b89a855baa;hpb=deabeeb6fcb35bac9360b053c8bf902b45e6de4d))
+9. In your `config.xml` file, [add this new line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=7d67508b70914aa921a16e79f79c00512502a8b6;hp=337d38da6f40c7432b0bce05aa3281d797eec40a;hb=6749c17640c5fed8a7d3a0b9cca204b89a855baa;hpb=deabeeb6fcb35bac9360b053c8bf902b45e6de4d).
+10. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.4.0, this has fixed scripts)**
+11. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
+12. Add AssetsLibrary.framework as a resource to your project. (Go [here](https://developer.apple.com/library/ios/#recipes/xcode_help-project_editor/Articles/AddingaLibrarytoaTarget.html) for instructions on how to do so.)
+
+## Upgrading 2.2.0 projects to 2.3.0 ##
+
+1. **Download and extract the Cordova 2.3.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.3.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova-2.3.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.2.0.js** file
+6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.3.0.js** file
+7. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project.
+8. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.3.0, this has new scripts)**
+9. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
+10. Convert your `Cordova.plist` file to `config.xml`, by running the script **bin/cordova\_plist\_to\_config\_xml** on your project file.
+11. Add the InAppBrowser plugin to your `config.xml`, by adding this tag under **<cordova><plugins>**:
+
+ <plugin name="InAppBrowser" value="CDVInAppBrowser" />
+12. Note that Objective-C plugins are **not** whitelisted anymore. To whitelist your connections with the app whitelist, you will need to set the “User-Agent” header of the connection to the same user-agent as the main Cordova WebView.
+You can get this by accessing the **userAgent** property off the main view-controller. The main view-controller (CDVViewController) also has a **URLisAllowed** method for you to check whether a URL will pass the whitelist.
+13. Device API changes:
+ * For iOS, device.platform used to return “iPhone”, “iPad” or “iPod Touch” — now it returns (correctly) “iOS”.
+ * For iOS, device.name (now deprecated for all platforms) used to return the name of the user’s device (e.g ‘Shazron’s iPhone 5′) — now it returns what device.platform used to return: ”iPhone”, “iPad” or “iPod Touch”.
+ * For all platforms, there is a new property called device.model — this returns the specific device model, e.g “iPad2,5″ (for other platforms, this returns what device.name used to return).
+
+## Upgrading 2.1.0 projects to 2.2.0 ##
+
+1. **Download and extract the Cordova 2.2.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.2.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova-2.2.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.1.0.js** file
+6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.2.0.js** file
+7. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project:
+ - Updated → viewWillAppear
+8. Copy the **cordova** folder from the new project into your project's root folder **(in 2.2.0, this has an updated 'emulate' script)**
+9. Next, update your CordovaLib sub-project reference. Beginning with Cordova 2.1.0, we are not using the CORDOVALIB Xcode variable anymore when referencing where CordovaLib resides, the reference is an absolute file reference now.
+ 1. Launch **Terminal.app**
+ 2. Go to the location where you installed Cordova (see Step 1), in the **bin** sub-folder
+ 3. Run the script below where the first parameter is the path to your project's **.xcodeproj** file:
+
+ `update_cordova_subproject path/to/your/project/xcodeproj`
+
+__NOTE:__ In 2.2.0, the `bin/create` script copy in the CordovaLib sub-project into your project. To have the same kind of setup, just copy in the right CordovaLib into your project folder, and update the CordovaLib sub-project location (relative to the project) in the Xcode File Inspector.
+
+## Upgrading 2.0.0 projects to 2.1.0 ##
+
+With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Reference Counting (ARC)**. You don't need to upgrade to **ARC** to use CordovaLib, but if you want to upgrade your project to use **ARC**, please use the Xcode migration wizard from the menu: **Edit → Refactor → Convert to Objective-C ARC...**, **de-select libCordova.a**, then run the wizard to completion.
+
+1. **Download and extract the Cordova 2.1.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.1.0)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+5. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+6. **Copy** the **www/cordova-2.1.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.0.0.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.1.0.js** file
+8. Update (or replace, if you never changed the file) your `AppDelegate.m` according to the one from the new project:
+ - Edited -> application:didFinishLaunchingWithOptions:
+ - Added -> application:supportedInterfaceOrientationsForWindow:
+9. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project:
+ - Added -> viewWillAppear
+10. Copy the **cordova** folder from the new project into your project's root folder **(in 2.1.0, this has the updated scripts to support paths with spaces)**
+11. Remove the **VERSION** file reference from your **project** (_not_ the one in CordovaLib)
+12. Next, update your CordovaLib sub-project reference. Beginning with Cordova 2.1.0, we are not using the CORDOVALIB Xcode variable anymore when referencing where CordovaLib resides, the reference is an absolute file reference now.
+ 1. Launch **Terminal.app**
+ 2. Go to the location where you installed Cordova **(see Step 1)**, in the **bin** sub-folder
+ 3. Run the script below where the first parameter is the path to your project's **.xcodeproj** file:
+
+ `update_cordova_subproject path/to/your/project/xcodeproj`
+
+## Upgrading 1.9.0 projects to 2.0.0 ##
+
+1. **Install** Cordova 2.0.0
+2. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
+3. **Copy** the **www/cordova-2.0.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.9.0.js** file
+4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.0.0.js** file
+5. Copy the **cordova** folder from the new project into your project's root folder (if you want the project command-line tools)
+6. **Add** a new entry under **Plugins** in your `Cordova.plist` file (under the **Supporting Files** group) - the key is **Device** and the value is **CDVDevice**
+7. Remove `Cordova.framework`
+8. Remove `verify.sh` from the **Supporting Files** group
+9. Select the **project icon** in the Project Navigator, select your project **Target**, then select the **Build Settings** tab
+10. Search for **Preprocessor Macros**, then remove all **CORDOVA_FRAMEWORK=1** values
+11. Locate the **CordovaLib** folder that was installed in your hard-drive under your home folder's **Documents** sub-folder.
+12. Locate the `CordovaLib.xcodeproj` file in the **CordovaLib** folder, then **drag and drop** the file into your project - it should appear as a **sub-project**.
+13. **Build** your project, you should get some **errors** relating to **#import** directives
+14. For the **#import errors**, change any **quote-based** imports in this style:
+
+ #import "CDV.h"
+
+ to this **brackets-based** style:
+
+ #import <Cordova/CDV.h>
+
+ and remove any **#ifdef** wrappers around any Cordova imports, they are not needed anymore (the imports are **unified** now)
+15. **Build** your project again, and it should not have any **#import** errors.
+16. Select the **project icon** in the Project Navigator, select your project **Target**, then select the **Build Phases** tab
+17. Expand the **Target Dependencies** phase, then select the **+** button
+18. Select the **CordovaLib** target, then select the **Add** button
+19. Expand the **first** **Link Binary with Libraries** phase (it should already contain a bunch of frameworks), then select the **+** button
+20. Select the `libCordova.a` static library, then select the **Add** button
+21. Delete the **Run Script** phase.
+22. Select the **project icon** in the Project Navigator, select your project **Target**, then select the **Build Settings** tab
+23. Search for **Other Linker Flags**, and add the values **-all_load** and **-Obj-C**
+24. Expand the **CordovaLib** sub-project.
+25. Locate the **VERSION** file, drag it into your main project (we want to create a link to it, not a copy)
+26. Select the **Create groups for any added folders** radiobutton, then select the **Finish** button
+27. Select the **VERSION** file that you just dragged in a previous step
+28. Type the **Option-Command-1** key combination to show the **File Inspector** (or menuitem **View -> Utilities -> Show File Inspector**)
+29. Choose **Relative to CORDOVALIB** in the **File Inspector** for the drop-down menu for **Location**
+30. Set the Xcode preference **Xcode Preferences -> Locations -> Derived Data -> Advanced...** to **Unique** (this is so the unified headers can be found)
+31. Select the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
+32. Search for **Header Search Paths**. For that setting, add these three values below (with quotes):
+
+ "$(TARGET_BUILD_DIR)/usr/local/lib/include"
+
+ "$(OBJROOT)/UninstalledProducts/include"
+
+ "$(BUILT_PRODUCTS_DIR)"
+
+33. Search for **Other Linker Flags**. For that setting, add this value below:
+
+ -weak_framework CoreFoundation
+
+34. **Build** your project, it should compile and link with **no issues**.
+35. **Select your project** from the **Scheme** drop-down, and then select **iPhone 5.1 Simulator**
+36. Select the **Run** button
+
+__NOTE:__ If your project is **not working** as expected in the Simulator, please **take a note of any errors** in the **console log in Xcode** for clues.
+
+## Upgrading 1.8.x projects to 1.9.0 ##
+
+1. **Install** Cordova 1.9.0
+2. **Create a new project** - you will have to grab assets from this new project
+3. **Copy** the **www/cordova-1.9.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.8.x.js** file
+4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.9.0.js** file
+
+__NOTE:__ 1.9.0 supports the new **BackupWebStorage** boolean `Cordova.plist` setting. It's enabled by default, so set it to
+`false` to disable it, especially on iOS 6. See [Release Notes - Safari and UIKit Section](https://developer.apple.com/library/prerelease/ios/#releasenotes/General/RN-iOSSDK-6_0/_index.html)
+
+## Upgrading 1.7.0 projects to 1.8.x ##
+
+1. **Install** Cordova 1.8.0
+2. **Create a new project** - you will have to grab assets from this new project
+3. **Copy** the **www/cordova-1.8.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.7.x.js** file
+4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.8.0.js** file
+
+If you intend on using the **Capture API**, you will need the new **iPad retina-display** assets:
+
+1. **Copy** the `Resources/Capture.bundle` item from the new project into your project folder, over-writing your existing `Resources/Capture.bundle` item
+2. In your project, select the `Capture.bundle` item into your Project Navigator in Xcode, type the **Delete** key, then select **Remove Reference** from the resulting dialog.
+3. Drag the new `Capture.bundle` from Step 1 above into your Project Navigator in Xcode, then select the **Create groups for any added folders** radio button
+
+## Upgrading 1.6.x projects to 1.7.0 ##
+
+1. **Install** Cordova 1.7.0
+2. **Create a new project** - you will have to grab assets from this new project
+3. **Copy** the **www/cordova-1.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.6.0.js** file
+4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.7.0.js** file
+
+## Upgrading 1.5.0 projects to 1.6.x ##
+
+1. **Install** Cordova 1.6.1
+2. **Make a backup** of `AppDelegate.m`, `AppDelegate.h`, `MainViewController.m`, `MainViewController.h`, and `Cordova.plist` in your project
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** these files from the **new** project into your 1.5.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
+
+ AppDelegate.h
+ AppDelegate.m
+ MainViewController.h
+ MainViewController.m
+ Cordova.plist
+5. **Add** all the new **MainViewController** and **AppDelegate** files into your Xcode project
+6. **Copy** the **www/cordova-1.6.1.js** file from the new project into your **www** folder, and delete your **www/cordova-1.5.0.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.6.1.js** file
+8. **Add** the new `Cordova.plist` file into your project - this is because the core plugin service names needed to be changed to match the ones from Android and Blackberry, for a unified Cordova JavaScript file (cordova-js).
+9. **Integrate** any settings, **Plugins** and **ExternalHosts** entries that you had in your **backed-up Cordova.plist** into the new `Cordova.plist`
+10. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files. Any **UIWebViewDelegate** or **CDVCommandDelegate** code in `AppDelegate.m` will need to go into MainViewController.m now (see commented out sections in that file)
+11. **Integrate** any project-specific code that you have in your **backed-up MainViewController.h and MainViewController.m** into the new MainViewController files
+12. Click on the **project icon** in the Project Navigator, select your **Project**, then select the **Build Settings** tab
+13. Enter **Compiler for C/C++/Objective-C** in the search field
+14. Select the **Apple LLVM Compiler 3.1** value
+
+## Upgrading 1.4.x projects to 1.5.0 ##
+
+1. **Install** Cordova 1.5.0
+2. **Create a new project** and run it once - you will have to grab assets from this new project
+3. **Copy** the **www/cordova-1.5.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.4.x.js** file
+4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new Cordova **cordova-1.5.0.js** file
+5. Find `PhoneGap.framework` in your Project Navigator, select it
+6. Type the **Delete** key and delete the `PhoneGap.framework` reference in the Project Navigator
+7. Type the **Option-Command-A** key combination, which should drop down a sheet to add files to your project (the **Add Files...** sheet). Make sure the **Created groups for any added folders** radio button is selected
+8. Type the **Shift-Command-G** key combination, which should drop down another sheet for you to go to a folder (the **Go to the folder:** sheet)
+9. Enter **/Users/Shared/Cordova/Frameworks/Cordova.framework** in the **Go to the folder:** sheet and then press the **Go** button
+10. Press the **Add** button in the **Add Files...** sheet
+11. Select `Cordova.framework` in the Project Navigator
+12. Type the **Option-Command-1** key combination to show the **File Inspector**
+13. Choose **Absolute Path** in the **File Inspector** for the drop-down menu for **Location**
+14. Type the **Option-Command-A** key combination, which should drop down a sheet to add files to your project (the **Add Files...** sheet). Make sure the **Created groups for any added folders** radio button is selected
+15. Type the **Shift-Command-G** key combination, which should drop down another sheet for you to go to a folder (the **Go to the folder:** sheet)
+16. Enter **~/Documents/CordovaLib/Classes/deprecated** in the **Go to the folder:** sheet and then press the **Go** button
+17. Press the **Add** button in the **Add Files...** sheet
+18. In your **AppDelegate.h, AppDelegate.m, and MainViewController.h** files - replace the whole **#ifdef PHONEGAP_FRAMEWORK** block with:
+
+ #import "CDVDeprecated.h"
+19. Click on the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
+20. Search for **Framework Search Paths**
+21. Replace the existing value with **/Users/Shared/Cordova/Frameworks**
+22. Search for **Preprocessor Macros**
+23. For the first (combined) value, replace the value with **CORDOVA_FRAMEWORK=YES**
+24. Select the **Build Phases** tab
+25. Expand **Run Script**
+26. Replace any occurrences of **PhoneGap** with **Cordova**
+27. Find your `PhoneGap.plist` file in the Project Navigator, and click on the filename once to enter name edit mode
+28. Rename `PhoneGap.plist` to `Cordova.plist`
+29. Right-click on `Cordova.plist` and choose **Open As --> Source Code**
+30. Press **Option-Command-F**, choose **Replace** from the drop-down on the top left of the Source window
+31. Enter `com.phonegap` for the Find string, and `org.apache.cordova` for the Replace string - then press the **Replace All** button
+32. Enter **PG** for the Find string, and **CDV** for the Replace string - then press the **Replace All** button
+33. Press **Command-B** to build, you will still have deprecations that you can get rid of in the future (see `CDVDeprecated.h` - replace classes in your code that use PG* to CDV*, for example)
+
+## Upgrading 1.4.0 projects to 1.4.1 ##
+
+1. **Install** Cordova 1.4.1
+2. **Make a backup** of `MainViewController.m`
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** the `MainViewController.m` file from the **new** project into your 1.4.0-based project folder on disk, **replacing** the old file (**backup** your files first from step 2 above).
+5. **Add** the `MainViewController.m` file into your Xcode project
+6. **Integrate** any project-specific code that you have in your backed-up `MainViewController.m` into the new file
+7. Updating the `phonegap-1.4.0.js` file is optional, nothing has changed in the JavaScript between 1.4.0 and 1.4.1
+
+## Upgrading 1.3.0 projects to 1.4.0 ##
+
+1. **Install** Cordova 1.4.0
+2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** these files from the **new** project into your 1.3.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
+
+ AppDelegate.h
+ AppDelegate.m
+ MainViewController.h
+ MainViewController.m
+ MainViewController.xib
+5. **Add** all the **MainViewController** files into your Xcode project
+6. **Copy** the **www/phonegap-1.4.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.3.0.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.4.0.js** file
+8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
+9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
+
+## Upgrading 1.2.0 projects to 1.3.0 ##
+
+1. **Install** Cordova 1.3.0
+2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** these files from the **new** project into your 1.2.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
+
+ AppDelegate.h
+ AppDelegate.m
+ MainViewController.h
+ MainViewController.m
+ MainViewController.xib
+5. **Add** all the **MainViewController** files into your Xcode project
+6. **Copy** the **www/phonegap-1.3.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.2.0.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.3.0.js** file
+8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
+9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
+
+## Upgrading 1.1.0 projects to 1.2.0 ##
+
+1. **Install** Cordova 1.2.0
+2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** these files from the **new** project into your 1.1.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
+
+ AppDelegate.h
+ AppDelegate.m
+ MainViewController.h
+ MainViewController.m
+ MainViewController.xib
+5. **Add** all the **MainViewController** files into your Xcode project
+6. **Copy** the **www/phonegap-1.2.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.1.0.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.2.0.js** file
+8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
+9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
+
+## Upgrading 1.0.0 projects to 1.1.0 ##
+
+1. **Install** Cordova 1.1.0
+2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** these files from the **new** project into your 1.0.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
+
+ AppDelegate.h
+ AppDelegate.m
+ MainViewController.h
+ MainViewController.m
+ MainViewController.xib
+5. **Add** all the **MainViewController** files into your Xcode project
+6. **Copy** the **www/phonegap-1.1.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.0.0.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.1.0.js** file
+8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
+9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
+
+## Upgrading 0.9.6 projects to 1.0.0 ##
+
+1. **Install** Cordova 1.0.0
+2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
+3. **Create a new project** - you will have to grab assets from this new project
+4. **Copy** these files from the **new** project into your 0.9.6-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
+
+ AppDelegate.h
+ AppDelegate.m
+ MainViewController.h
+ MainViewController.m
+ MainViewController.xib
+5. **Add** all the **MainViewController** files into your Xcode project
+6. **Copy** the **www/phonegap-1.0.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-0.9.6.js** file
+7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.0.0.js** file
+8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
+9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/ios/webview.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/webview.md b/docs/en/edge/guide/platforms/ios/webview.md
new file mode 100644
index 0000000..445016a
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/webview.md
@@ -0,0 +1,136 @@
+---
+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 WebViews
+================================
+
+Beginning with Cordova 1.4, you can use Cordova as a component in your
+iOS applications. This component is code-named 'Cleaver'.
+
+New Cordova-based applications created using the Xcode template
+provided in Cordova 1.4 or greater use Cleaver. (The template is
+Cleaver's reference implementation.)
+
+Cordova 2.0.0 and subsequent versions only support the sub-project
+based Cleaver implementation.
+
+Prerequisites
+-------------
+
+1. **Cordova 2.3.0** or greater
+2. **Xcode 4.5** or greater
+3. `config.xml` file (from a newly created iOS project)
+
+Adding Cleaver to your Xcode project (CordovaLib sub-project)
+-------------------------------------------------------------
+
+1. **Download and extract the Cordova source** to a **permanent folder location** on your hard drive (say to `~/Documents/Cordova`)
+2. **Quit Xcode** if it is running.
+3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
+4. **Copy** the `config.xml` file into your project folder on disk (see **Prerequisites** above)
+5. **Drag and drop** the `config.xml` file into the Project Navigator of Xcode
+6. **Choose** the **Create groups for any added folders** radio button and press **Finish**
+7. **Drag and drop** the `CordovaLib.xcodeproj` file into the Project Navigator of Xcode (from the permanent folder location above, and it should be in the CordovaLib sub-folder)
+8. Select `CordovaLib.xcodeproj` in the Project Navigator
+9. Type the **Option-Command-1** key combination to show the **File Inspector**
+10. Choose **Relative to Group** in the **File Inspector** for the drop-down menu for **Location**
+11. Select the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
+12. Add `-all_load` and `-Obj-C` for the **Other Linker Flags** value
+13. Click on the **project icon** in the Project Navigator, select your **Target**, then select the **Build Phases** tab
+14. Expand **Link Binaries with Libraries**
+15. Select the **+** button, and add these **frameworks** (and optionally in the Project Navigator, **move** them under the Frameworks group):
+
+ AddressBook.framework
+ AddressBookUI.framework
+ AudioToolbox.framework
+ AVFoundation.framework
+ CoreLocation.framework
+ MediaPlayer.framework
+ QuartzCore.framework
+ SystemConfiguration.framework
+ MobileCoreServices.framework
+ CoreMedia.framework
+
+16. Expand **Target Dependencies** - the top box labeled like this if you have multiple boxes!
+17. Select the **+** button, and add the `CordovaLib` build product
+18. Expand **Link Binaries with Libraries** - the top box labeled like
+ this if you have multiple boxes!
+19. Select the **+** button, and add `libCordova.a`
+20. Set the Xcode preference **Xcode Preferences → Locations → Derived Data → Advanced...** to **Unique**
+21. Select the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
+22. Search for **Header Search Paths**. For that setting, add these three values below (with quotes):
+
+ "$(TARGET_BUILD_DIR)/usr/local/lib/include"
+ "$(OBJROOT)/UninstalledProducts/include"
+ "$(BUILT_PRODUCTS_DIR)"
+
+ With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Reference Counting (ARC)**. You don't need to upgrade to **ARC** to use CordovaLib, but if you want to upgrade your project to use **ARC**, please use the Xcode migration wizard from the menu: **Edit → Refactor → Convert to Objective-C ARC...**, **de-select libCordova.a**, then run the wizard to completion.
+
+Using CDVViewController in your code
+------------------------------------
+
+1. Add this **header**:
+
+ #import <Cordova/CDVViewController.h>
+
+2. Instantiate a **new** `CDVViewController`, and **retain it somewhere** (e.g. to a property in your class):
+
+ CDVViewController* viewController = [CDVViewController new];
+
+3. (_OPTIONAL_) Set the `wwwFolderName` property (defaults to `www`):
+
+ viewController.wwwFolderName = @"myfolder";
+
+4. (_OPTIONAL_) Set the start page in your config.xml, the `<content>` tag.
+
+ <content src="index.html" />
+
+ OR
+
+ <content src="http://apache.org" />
+
+5. (_OPTIONAL_) Set the `useSplashScreen` property (defaults to `NO`):
+
+ viewController.useSplashScreen = YES;
+
+6. Set the **view frame** (always set this as the last property):
+
+ viewController.view.frame = CGRectMake(0, 0, 320, 480);
+
+7. **Add** Cleaver to your view:
+
+ [myView addSubview:viewController.view];
+
+Adding your HTML, CSS and JavaScript assets
+-------------------------------------------
+
+1. Create a **new folder** in your project **on disk**, `www` for example.
+2. Put your **HTML, CSS and JavaScript** assets into this folder.
+3. **Drag and drop** the folder into the Project Navigator of Xcode.
+4. **Choose** the **Create folder references for any added folders** radio button.
+5. **Set the appropriate `wwwFolderName` and `startPage` properties** for the folder you created in **(1)** or use the defaults (see previous section) when you instantiate the `CDVViewController`.
+
+ /*
+ if you created a folder called 'myfolder' and
+ you want the file 'mypage.html' in it to be
+ the startPage
+ */
+ viewController.wwwFolderName = @"myfolder";
+ viewController.startPage = @"mypage.html"
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/win8/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/config.md b/docs/en/edge/guide/platforms/win8/config.md
new file mode 100644
index 0000000..dfeb618
--- /dev/null
+++ b/docs/en/edge/guide/platforms/win8/config.md
@@ -0,0 +1,26 @@
+<!--
+#
+# 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.
+#
+-->
+
+Windows 8 Configuration
+===================================
+
+Windows 8 does not currently support this feature.
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/win8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/index.md b/docs/en/edge/guide/platforms/win8/index.md
new file mode 100644
index 0000000..3372889
--- /dev/null
+++ b/docs/en/edge/guide/platforms/win8/index.md
@@ -0,0 +1,111 @@
+---
+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.
+---
+
+Windows 8 Platform Guide
+==================================
+
+This guide describes how to set up your Cordova development
+environment and run a sample application. Note that Cordova used to
+be called PhoneGap, so some of the sites still use the old PhoneGap
+name.
+
+Microsoft deprecated the name _Metro-style apps_ in Windows 8 and
+Windows RT. MSDN now refers to this type of app as a _Windows Store_
+app, and this guide follows that convention. Also, in this guide
+_Windows 8_ signifies both Windows 8 and Windows RT.
+
+1. Requirements
+---------------
+
+- Windows 8
+
+- Visual Studio 2012 Professional or better, or Visual Studio 2012 Express for Windows 8
+
+Follow the instructions [here](http://www.windowsstore.com/) to submit your apps Windows Store.
+
+2. Install SDK + Cordova
+----------------------------
+
+- Set up your preferred variant of Visual Studio 2012. All of the product's paid versions (Professional, etc.) let you build Windows Store apps. You need **Express for Windows 8** to build Windows Store apps using the [Express editions](http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products).
+- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-8` subfolder.
+
+3. Set up New Project
+--------------------
+
+You can already build Windows 8 apps using the _HTML/JavaScript track_
+available in Windows Store apps. Use Cordova in Windows Store apps to
+expose the same APIs as on other Cordova-supported platforms.
+
+- Open Visual Studio 2012 and choose **New Project**.
+- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as **CordovaWin8Foo** as in this example.
+
+ 
+
+- Microsoft continues to use `default.html` as the default home page, but most web developers use `index.html`. (Plus it's likely that in the other platform variants of your project you are using `index.html` as the name of your default page.) To fix this, in Solution Explorer rename the `default.html` file to `index.html`. Then double-click the `package.appxmanifest` file and change the **Start page** value to `index.html`.
+
+ 
+
+- To include `cordova.js` in your project, right-click on the **js** folder in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the **lib\windows-8** folder noted above.
+
+- Edit the code for `index.html`. Add a reference to `cordova.js`. You can do this manually, or by dragging the file from Solution Explorer.
+
+### Adding the reference...
+ <!-- WinJS references -->
+ <link href="//Microsoft.WinJS.1.0/css/ui-dark.css" rel="stylesheet" />
+ <script src="//Microsoft.WinJS.1.0/js/base.js"></script>
+ <script src="//Microsoft.WinJS.1.0/js/ui.js"></script>
+
+ <!-- Cordova -->
+ <script src="/js/cordova.js"></script>
+
+ <!-- CordovaWin8Foo references -->
+ <link href="/css/default.css" rel="stylesheet" />
+ <script src="/js/default.js"></script>
+
+- Next, add some code that demonstrates Cordova is working.
+
+### Adding a 'deviceready' handler...
+ <body>
+ <p>Content goes here</p>
+
+ <script type="text/javascript">
+
+ console.log("Subscribing...");
+ document.addEventListener("deviceready", function () {
+
+ navigator.notification.alert("The device is ready!");
+
+ });
+
+ </script>
+
+ </body>
+
+5. Test the Project
+-------------------------------
+
+- Run the project from Visual Studio. You'll see the message box appear:
+
+ 
+
+Done!
+-----
+
+That's it! You're now ready to build Windows Store apps with Cordova.
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/win8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/tools.md b/docs/en/edge/guide/platforms/win8/tools.md
new file mode 100644
index 0000000..9fbb26d
--- /dev/null
+++ b/docs/en/edge/guide/platforms/win8/tools.md
@@ -0,0 +1,44 @@
+---
+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.
+---
+
+# Windows 8 Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## Windows 8
+
+The Windows 8 command-line tools only support creating new projects.
+Commands must be run from a cmd or powershell prompt.
+
+## Create a project
+
+Run the `create` command with the following parameters:
+
+* Path to your new Cordova Windows 8 project
+* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
+* Project name
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/upgrading.md/index.md b/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
new file mode 100644
index 0000000..f5c3bea
--- /dev/null
+++ b/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
@@ -0,0 +1,39 @@
+---
+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 Windows 8
+===============================
+
+This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to applications targetting Windows 8 and the Windows Store.
+
+## Upgrade to 2.9.0 from 2.8.0 ##
+
+The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
+
+1. Remove cordova-2.8.0.js from the www directory in your project.
+2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
+3. Build and test!
+
+## Upgrade to 2.8.0 from 2.7.0 ##
+
+The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
+
+1. Remove cordova-2.7.0.js from the www directory in your project.
+2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
+3. Build and test!
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/windows-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-8/index.md b/docs/en/edge/guide/platforms/windows-8/index.md
deleted file mode 100644
index 3372889..0000000
--- a/docs/en/edge/guide/platforms/windows-8/index.md
+++ /dev/null
@@ -1,111 +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.
----
-
-Windows 8 Platform Guide
-==================================
-
-This guide describes how to set up your Cordova development
-environment and run a sample application. Note that Cordova used to
-be called PhoneGap, so some of the sites still use the old PhoneGap
-name.
-
-Microsoft deprecated the name _Metro-style apps_ in Windows 8 and
-Windows RT. MSDN now refers to this type of app as a _Windows Store_
-app, and this guide follows that convention. Also, in this guide
-_Windows 8_ signifies both Windows 8 and Windows RT.
-
-1. Requirements
----------------
-
-- Windows 8
-
-- Visual Studio 2012 Professional or better, or Visual Studio 2012 Express for Windows 8
-
-Follow the instructions [here](http://www.windowsstore.com/) to submit your apps Windows Store.
-
-2. Install SDK + Cordova
-----------------------------
-
-- Set up your preferred variant of Visual Studio 2012. All of the product's paid versions (Professional, etc.) let you build Windows Store apps. You need **Express for Windows 8** to build Windows Store apps using the [Express editions](http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products).
-- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-8` subfolder.
-
-3. Set up New Project
---------------------
-
-You can already build Windows 8 apps using the _HTML/JavaScript track_
-available in Windows Store apps. Use Cordova in Windows Store apps to
-expose the same APIs as on other Cordova-supported platforms.
-
-- Open Visual Studio 2012 and choose **New Project**.
-- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as **CordovaWin8Foo** as in this example.
-
- 
-
-- Microsoft continues to use `default.html` as the default home page, but most web developers use `index.html`. (Plus it's likely that in the other platform variants of your project you are using `index.html` as the name of your default page.) To fix this, in Solution Explorer rename the `default.html` file to `index.html`. Then double-click the `package.appxmanifest` file and change the **Start page** value to `index.html`.
-
- 
-
-- To include `cordova.js` in your project, right-click on the **js** folder in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the **lib\windows-8** folder noted above.
-
-- Edit the code for `index.html`. Add a reference to `cordova.js`. You can do this manually, or by dragging the file from Solution Explorer.
-
-### Adding the reference...
- <!-- WinJS references -->
- <link href="//Microsoft.WinJS.1.0/css/ui-dark.css" rel="stylesheet" />
- <script src="//Microsoft.WinJS.1.0/js/base.js"></script>
- <script src="//Microsoft.WinJS.1.0/js/ui.js"></script>
-
- <!-- Cordova -->
- <script src="/js/cordova.js"></script>
-
- <!-- CordovaWin8Foo references -->
- <link href="/css/default.css" rel="stylesheet" />
- <script src="/js/default.js"></script>
-
-- Next, add some code that demonstrates Cordova is working.
-
-### Adding a 'deviceready' handler...
- <body>
- <p>Content goes here</p>
-
- <script type="text/javascript">
-
- console.log("Subscribing...");
- document.addEventListener("deviceready", function () {
-
- navigator.notification.alert("The device is ready!");
-
- });
-
- </script>
-
- </body>
-
-5. Test the Project
--------------------------------
-
-- Run the project from Visual Studio. You'll see the message box appear:
-
- 
-
-Done!
------
-
-That's it! You're now ready to build Windows Store apps with Cordova.
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/windows-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-8/tools.md b/docs/en/edge/guide/platforms/windows-8/tools.md
deleted file mode 100644
index 9fbb26d..0000000
--- a/docs/en/edge/guide/platforms/windows-8/tools.md
+++ /dev/null
@@ -1,44 +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.
----
-
-# Windows 8 Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-## Windows 8
-
-The Windows 8 command-line tools only support creating new projects.
-Commands must be run from a cmd or powershell prompt.
-
-## Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova Windows 8 project
-* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
-* Project name
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/windows-phone-7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-phone-7/index.md b/docs/en/edge/guide/platforms/windows-phone-7/index.md
deleted file mode 100644
index a227130..0000000
--- a/docs/en/edge/guide/platforms/windows-phone-7/index.md
+++ /dev/null
@@ -1,95 +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.
----
-
-Windows Phone 7 Platform Guide
-==================================
-
-## Requirements and Support
-
-Requires Windows 7, Windows 8 or Windows Vista with SP2. Running
-Windows as a virtual machine does not work well, so Mac users should
-set up a Bootcamp partition to run Windows 7 or Vista.
-
-To install the app onto a device or submit it to the market place, you
-need to become an
-[App Hub member](http://create.msdn.com/en-US/home/membership).
-
-Developers should use the the `cordova` utility in conjunction with
-the Windows Phone SDK. Before installing it on Windows, open a
-command line and type `git` to make sure it is installed. If not,
-download it from [mysysgit.github.io](http://mysysgit.github.io). When
-prompted to configure your PATH, choose the option: __Run Git and
-included Unix tools from the Windows Command Prompt__. Once git is
-available, follow the instructions in The Cordova Command-line
-Interface for information how to install it, add projects, then build
-and deploy a project.
-
-## Install the SDK
-
-Download and install the
-[Windows Phone SDK](http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27570/)
-
-## Open a Project in the SDK
-
-After installing the `cordova` utility, use the following to create a
-new project, then add and build the Windows Phone 7 project.
-
- $ cordova create hello com.example.hello "Hello World"
- $ cd hello
- $ cordova platform add wp7
- $ cordova build
-
-Open Visual Studio and choose __Open Project__. Navigate to the
-`hello/platforms/wp7` directory and choose the `Hello_World.sln` file.
-The SDK displays the directory's contents:
-
-
-
-At this point you can modify the app within the SDK, but running the
-`build` or `prepare` commands again wipes out local changes. If Visual
-Studio is open, it alerts you about modified files and offers you the
-option to reload them. See The Cordova Command-line Interface for
-more information.
-
-## Deploy to Emulator
-
-Within the SDK, select the __Windows Phone Emulator__ target from the
-popup menu in the main menu bar, and press the green button to run the
-emulator:
-
-
-
-The app displays on the emulator's home screen as it would on a real
-device:
-
-
-
-## Deploy to Device
-
-To test your application on a device, the device must be registered.
-MSDN provides
-[documentation][http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx]
-to help deploy and test your Windows Phone.
-
-Once registered, you need to make sure the phone is connected via USB
-with its screen unlocked. In Visual Studio, choose the __Windows Phone
-Device__ target and press the green button to run it:
-
-
-
[07/20] docs commit: [CB-3827] rename & list WebViews sections within
Platforms
Posted by mw...@apache.org.
[CB-3827] rename & list WebViews sections within Platforms
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/f50e593d
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/f50e593d
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/f50e593d
Branch: refs/heads/master
Commit: f50e593d3ffae4360f26f30a66dd8199d5ae455a
Parents: a0baad9
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 12:58:50 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 12:58:50 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/cordova-webview/android.md | 2 +-
docs/en/edge/guide/cordova-webview/index.md | 6 +++---
docs/en/edge/guide/cordova-webview/ios.md | 2 +-
docs/en/edge/guide/getting-started/index.md | 3 +++
4 files changed, 8 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f50e593d/docs/en/edge/guide/cordova-webview/android.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/android.md b/docs/en/edge/guide/cordova-webview/android.md
index fa439fd..c3c96b3 100644
--- a/docs/en/edge/guide/cordova-webview/android.md
+++ b/docs/en/edge/guide/cordova-webview/android.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Embedding Cordova WebView on Android
+Android WebViews
====================================
Beginning in Cordova 1.9, with the assistance of the
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f50e593d/docs/en/edge/guide/cordova-webview/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/index.md b/docs/en/edge/guide/cordova-webview/index.md
index f7b58ba..649a5e8 100644
--- a/docs/en/edge/guide/cordova-webview/index.md
+++ b/docs/en/edge/guide/cordova-webview/index.md
@@ -17,11 +17,11 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Embedding WebView
+Embedding WebViews
=================
> Implement the Cordova WebView in your own project.
-- Embedding Cordova WebView on Android
-- Embedding Cordova WebView on iOS
+- Android WebViews
+- iOS WebViews
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f50e593d/docs/en/edge/guide/cordova-webview/ios.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/ios.md b/docs/en/edge/guide/cordova-webview/ios.md
index 5da6e36..445016a 100644
--- a/docs/en/edge/guide/cordova-webview/ios.md
+++ b/docs/en/edge/guide/cordova-webview/ios.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Embedding Cordova WebView on iOS
+iOS WebViews
================================
Beginning with Cordova 1.4, you can use Cordova as a component in your
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f50e593d/docs/en/edge/guide/getting-started/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/index.md b/docs/en/edge/guide/getting-started/index.md
index c58f0c7..b26e5f1 100644
--- a/docs/en/edge/guide/getting-started/index.md
+++ b/docs/en/edge/guide/getting-started/index.md
@@ -42,6 +42,7 @@ a lower-level alternative to the `cordova` command-line utility.
* Android Platform Guide
* Android Configuration
+* Android WebViews
* Android Plugins
* Android Command-line Tools
* Upgrading Android
@@ -55,6 +56,7 @@ a lower-level alternative to the `cordova` command-line utility.
## BlackBerry 10
+<!-- if "BlackBerry 10 Plugins" are available, how about WebViews? -->
* BlackBerry 10 Platform Guide
* BlackBerry 10 Plugins
* Blackberry 10 Command-line Tools
@@ -63,6 +65,7 @@ a lower-level alternative to the `cordova` command-line utility.
* iOS Platform Guide
* iOS Configuration
+* iOS WebViews
* iOS Plugins
* iOS Command-line Tools
* Upgrading iOS
[04/20] docs commit: [CB-3827] rm 'Command-Line Usage' sect;
correct prev commit to add separate CL tools guides within Platform
sects
Posted by mw...@apache.org.
[CB-3827] rm 'Command-Line Usage' sect; correct prev commit to add separate CL tools guides within Platform sects
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/02c44204
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/02c44204
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/02c44204
Branch: refs/heads/master
Commit: 02c4420456a2802d6c836f7a3a51a840487154d5
Parents: 4db1732
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 11:47:02 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 11:47:02 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/command-line/index.md | 407 -------------------
.../edge/guide/getting-started/android/tools.md | 80 ++++
.../guide/getting-started/blackberry/tools.md | 84 ++++
.../guide/getting-started/blackberry10/tools.md | 179 ++++++++
docs/en/edge/guide/getting-started/ios/tools.md | 59 +++
.../guide/getting-started/windows-8/tools.md | 44 ++
.../getting-started/windows-phone-8/tools.md | 77 ++++
docs/en/edge/index.md | 6 +-
8 files changed, 524 insertions(+), 412 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/command-line/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/command-line/index.md b/docs/en/edge/guide/command-line/index.md
deleted file mode 100644
index 485bdc1..0000000
--- a/docs/en/edge/guide/command-line/index.md
+++ /dev/null
@@ -1,407 +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.
----
-
-# Command-Line Usage
-
-Cordova now ships with a set of command-line tools that make it easier
-for you to develop cross-platform applications. You can build, clean,
-and launch an emulator with a single command. You can consider these
-instructions as an alternative to the Platform Guides. Whereas
-the Platform Guides help you get setup with the default IDEs and
-tooling surrounding the platforms you are working with, the command-line
-tools aim to provide a shell-based approach to creating and working with
-Cordova projects.
-
-## Supported Platforms
-
-* [iOS](#Command-Line%20Usage_ios)
-* [Android](#Command-Line%20Usage_android)
-* [BlackBerry](#Command-Line%20Usage_blackberry)
-* [BlackBerry 10](#Command-Line%20Usage_blackberry_10)
-* [Windows Phone](#Command-Line%20Usage_windows_phone)
-* [Windows 8](#Command-Line%20Usage_windows_8)
-
-## Windows Phone
-
-The Windows Phone command-line tools support creating, building, and
-running new projects. Commands must be run from a cmd or powershell prompt.
-
-The WP8 repo now includes code for building both WP7 + WP8 apps.
-The repo has subfolders for each: wp7/ and wp8/
-
-### Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova Windows Phone project
-* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
-* Project name
-
-<!-- -->
-
- // create a new wp8 Cordova project
- $ C:\path\to\cordova-wp8\wp8\bin\create C:\path\to\my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
- // create a new wp7 Cordova project
- $ C:\path\to\cordova-wp8\wp7\bin\create C:\path\to\my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
-### Building your project (cleans then builds)
-
-* Debug
-
-<!-- -->
-
- $ C:\path\to\my_new_cordova_project\cordova\build --debug
-
-* Release
-
-<!-- -->
-
- $ C:\path\to\my_new_cordova_project\cordova\build --release
-
-### Running your application
-
-Run the 'run' command with the following *optional* parameters
-
-* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
-* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
-
-<!-- -->
-
- $ C:\path\to\my_new_cordova_project\cordova\run [Target] [Build]
-
-By default the `run` command will look for a connected device, if no device is found it will look for any started emulators. If you have multiple emulators, you can specify a target ID.
-
-### Cleaning
-
- $ C:\path\to\my_new_cordova_project\cordova\clean
-
-## iOS
-
-The iOS command-line tools are built upon shell scripts and rely on
-Xcode command-line tools such as `xcode-select` and `xcodebuild`.
-
-### Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova iOS project
-* Package name, following reverse-domain style convention
-* Project name
-
-<!-- -->
-
- $ ./path/to/cordova-ios/bin/create /path/to/my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
-### Build a project
-
- $ /path/to/my_new_cordova_project/cordova/build
-
-### Run app on emulator
-
- $ /path/to/my_new_cordova_project/cordova/run
-
-### Releasing
-
- $ /path/to/my_new_cordova_project/cordova/release
-
-### Logging
-
- $ /path/to/my_new_cordova_project/cordova/log
-
-## Android
-
-The Android command-line tools are built upon shell scripts. You _must_
-have the Android SDK's `tools` and `platform-tools` folders in your
-PATH!
-
-### Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova Android project
-* Package name, following reverse-domain style convention
-* Main Activity name
-
-<!-- -->
-
- $ /path/to/cordova-android/bin/create /path/to/my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
-or, on *Windows*
-
- $ C:\path\to\cordova-android\bin\create.bat C:\path\to\my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
-### Building your project (cleans then builds)
-
-* **Debug**
-
-<!-- -->
-
- $ /path/to/my_new_cordova_project/cordova/build --debug
-
- or, on *Windows*
-
- $ C:\path\to\my_new_cordova_project\cordova\build.bat --debug
-
-* **Release**
-
-<!-- -->
-
- $ /path/to/my_new_cordova_project/cordova/build --release
-
- or, on *Windows*
-
- $ C:\path\to\my_new_cordova_project\cordova\build.bat --release
-
-
-### Running your application
-
-Run the 'run' command with the following *optional* parameters
-
-* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
-* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
-
-<!-- -->
- $ /path/to/my_new_cordova_project/cordova/run [Target] [Build]
-
- or, on *Windows*
-
- $ C:\path\to\my_new_cordova_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 you have
-multiple AVDs, you're prompted to select one. By default the `run`
-command will detect a connected device. When no device is found,
-it will detect a running emulator.
-
-### Logging
-
- $ /path/to/my_new_cordova_project/cordova/log
-
-or, on *Windows*
-
- $ C:\path\to\my_new_cordova_project\cordova\log.bat
-
-### Cleaning
-
- $ /path/to/my_new_cordova_project/cordova/clean
-
-or, on *Windows*
-
- $ C:\path\to\my_new_cordova_project\cordova\clean.bat
-
-## BlackBerry
-
-The BlackBerry command-line tools are built upon shell scripts.
-
-### Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova BlackBerry project
-* Placeholder package name
-* Application name
-
-<!-- -->
-
- $ /path/to/cordova-blackberry-webworks/bin/create /path/to/my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
-or, on **Windows**
-
- $ /path/to/cordova-blackberry-webworks/bin/create.bat /path/to/my_new_cordova_project com.example.cordova_project_name CordovaProjectName
-
-__NOTE:__ The Blackberry platform ignores the package name placeholder
-(`com.example.cordova_project_name`), but it's still required for use by
-cross-platform tools.
-
-### Build a project
-
-For BlackBerry projects, please make sure you customize the
-`project.properties` file in your Cordova project's root directory.
-You need to do so to supply your BlackBerry signing key password, and
-specify locations for the BlackBerry WebWorks SDK and BlackBerry
-simulator executables.
-
- $ /path/to/my_new_cordova_project/cordova/build <platform>
-
-or, on **Windows**
-
- $ /path/to/my_new_cordova_project/cordova/build.bat <platform>
-
-### Launch simulator
-
-For BlackBerry projects, please make sure you customize the
-`project.properties` file in the root of your Cordova project folder.
-You need to do so to supply your BlackBerry signing key password, and
-specify locations for the BlackBerry WebWorks SDK and BlackBerry
-simulator executables.
-
- $ /path/to/my_new_cordova_project/cordova/run <platform>
-
-and then choose 'no' when prompted with:
-
- Do you have a BlackBerry device connected to your computer? (y/n)
-
-or, on **Windows**
-
- $ /path/to/my_new_cordova_project/cordova/run <platform>
-
-and then choose 'no' when prompted with:
-
- Do you have a BlackBerry device connected to your computer? (y/n)
-
-### Logging
-
-Unfortunately, streaming logs directly from the device is currently
-unsupported. However, BlackBerry offers built-in Web Inspector support
-for Playbook and BlackBerry smartphone devices running BlackBerry OS
-7.0 and above. You can also access your application's logs (including
-any calls to `console.log`) on your device by holding down the ''ALT''
-key from the home screen and typing ''lglg'' keys.
-
-
-## BlackBerry 10
-
-Command-line tools are based on shell scripts. If you need help with a command, type the command with the `-h` or `-help` arguments, which are supported by all commands and which will provide descriptions for each of the available arguments.
-
-The following commands are available:
-
-## create
-
-The 'create' command creates a new project:
-
-```
-bin/create <path-to-project>
-```
-
-## target
-
-The `target` command allows you to manage the BlackBerry device(s) or simulator that you will use to test your app. You can add or remove a target, or set a target as the default target.
-
-### Add a target
-
-```
-<path-to-project>/cordova/target add <name> <ip-address> <device | simulator> [-p | --password <password>] [--pin <device-pin>]
-```
-
-where
-
-- `<name>` specifies a unique name for the target.
-- `<ip-address>` specifies the ip address of the BlackBerry device or simulator.
-- `-p|--password <password>` specifies the password for the device or simulator. This is required only if the device or simulator is password protected.
-- `--pin <device-pin>` specifies the PIN of the BlackBerry device, which identifies that device as a valid host for the debug token. This argument is required only if you are creating a debug token.
-
-### Remove a target
-
-```
-<path-to-project>/cordova/target remove <name>
-```
-
-### Set a target as the default
-
-```
-<path-to-project>/cordova/target default <name>
-```
-
-## build
-
-The `build` command builds the project as a .bar file. You can build your app in either release mode (which produces a signed .bar file) or in debug mode (which produces an unsigned .bar file).
-
-### Build your project in release mode
-
-```
-<path-to-project>/cordova/build release -k|--keystorepass <password> [-b|--buildId <number>] [-p|--params <params-JSON-file>]
-```
-where
-
-- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications.
-- `-b|--buildId <number>` specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
-- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
-
-### Build your project in debug mode
-
-```
-<path-to-project>/cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params <params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
-```
-
-where
-
-- `<target>` specifies the name of a previously added target. If `<target>` is not specified, the default target is used, if one has been created. This argument is only required if you want the script to deploy your app to a BlackBerry device or simulator and you have not created a default target. Additionally, if `<target>` is a device, then that device must be connected to your computer by USB connection or be connected to the same Wi-Fi network as your computer.
-- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications. This password is also used to create your debug token. This argument is only required if you want the script to create and install the debug token for you.
-- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools.
-- `-ll|--loglevel <level>` specifies the log level. The log level may be one of `error`, `warn`, or `verbose`.
-
-If you have previously defined a default target (and previously installed a debug token, if that target is a BlackBerry device), you can run the script with no arguments, and the script will package your app and deploy it to the default target. For example:
-
-```
-<path-to-project>/cordova/build debug
-```
-
-## run
-
-The `run` command deploys the app on the specified BlackBerry device or a simulator. Before deploying your app, you must first create a target for the device or simulator you want to deploy your app to. The deploy script will deploy the most recent build of your app.
-
-```
-<path-to-project>/cordova/run <target>
-```
-
-where
-- `<target> `specifies the name of a previously added target. If `<target> `is a device, then that device must be connected to your computer by USB connection or be connected to the same Wi-Fi network as your computer.
-
-## plugin
-
-The `target` command allows you to add and remove plugins
-
-### Fetch a locally-hosted plugin
-
-
-```
-<path-to-project>/cordova/plugin fetch <path-to-plugin>
-```
-
-### View a list of installed plugins
-
-```
-<path-to-project>/cordova/plugin ls
-```
-
-### Add a plugin
-
-```
-<path-to-project>/cordova/plugin add <name>
-```
-
-### Remove a plugin
-
-```
-<path-to-project>/cordova/plugin rm <name>
-```
-
-## Windows 8
-
-The Windows 8 command line tools support creating new projects only.
-Commands must be run from a cmd or powershell prompt.
-
-### Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova Windows 8 project
-* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
-* Project name
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/getting-started/android/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/android/tools.md b/docs/en/edge/guide/getting-started/android/tools.md
new file mode 100644
index 0000000..03b0ac2
--- /dev/null
+++ b/docs/en/edge/guide/getting-started/android/tools.md
@@ -0,0 +1,80 @@
+---
+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 Command-Line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## 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 and Windows:
+
+ $ /path/to/cordova-android/bin/create /path/to/project com.example.project_name ProjectName
+ $ C:\path\to\cordova-android\bin\create.bat C:\path\to\project com.example.project_name ProjectName
+
+## Build
+
+This cleans then builds a project.
+
+Debug, on Mac or Windows:
+
+ $ /path/to/project/cordova/build --debug
+ $ C:\path\to\project\cordova\build.bat --debug
+
+Release, on Mac 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
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/getting-started/blackberry/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry/tools.md b/docs/en/edge/guide/getting-started/blackberry/tools.md
new file mode 100644
index 0000000..f7f7447
--- /dev/null
+++ b/docs/en/edge/guide/getting-started/blackberry/tools.md
@@ -0,0 +1,84 @@
+---
+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 Command-Line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## 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 and Windows:
+
+ $ /path/to/cordova-blackberry-webworks/bin/create /path/to/my_new_project com.example.project_name ProjectName
+ $ /path/to/cordova-blackberry-webworks/bin/create.bat /path/to/my_new_project com.example.project_name ProjectName
+
+__NOTE:__ The Blackberry platform ignores the package name placeholder
+(`com.example.project_name`), but it's still required for use by
+cross-platform tools.
+
+## Build a project
+
+For BlackBerry projects, please make sure you customize the
+`project.properties` file in your Cordova project's root directory.
+You need to do so to supply your BlackBerry signing key password, and
+specify locations for the BlackBerry WebWorks SDK and BlackBerry
+simulator executables.
+
+ $ /path/to/my_new_project/cordova/build <platform>
+ $ /path/to/my_new_project/cordova/build.bat <platform>
+
+## Launch simulator
+
+For BlackBerry projects, please make sure you customize the
+`project.properties` file in the root of your Cordova project folder.
+You need to do so to supply your BlackBerry signing key password, and
+specify locations for the BlackBerry WebWorks SDK and BlackBerry
+simulator executables.
+
+ $ /path/to/my_new_project/cordova/run <platform>
+
+and then choose 'no' when prompted with:
+
+ Do you have a BlackBerry device connected to your computer? (y/n)
+ $ /path/to/my_new_project/cordova/run <platform>
+
+and then choose 'no' when prompted with:
+
+ Do you have a BlackBerry device connected to your computer? (y/n)
+
+## Logging
+
+Unfortunately, streaming logs directly from the device is currently
+unsupported. However, BlackBerry offers built-in Web Inspector support
+for Playbook and BlackBerry smartphone devices running BlackBerry OS
+7.0 and above. You can also access your application's logs (including
+any calls to `console.log`) on your device by holding down the ''ALT''
+key from the home screen and typing ''lglg'' keys.
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/getting-started/blackberry10/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry10/tools.md b/docs/en/edge/guide/getting-started/blackberry10/tools.md
new file mode 100644
index 0000000..e759738
--- /dev/null
+++ b/docs/en/edge/guide/getting-started/blackberry10/tools.md
@@ -0,0 +1,179 @@
+---
+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 Command-Line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+If you need help with any command listed below, type the command along
+with the `-h` or `-help` arguments, which are supported by all
+commands and which provide descriptions for each of the available
+arguments.
+
+## create
+
+The 'create' command creates a new project:
+
+```
+bin/create <path-to-project>
+```
+
+## target
+
+The `target` command allows you to manage the BlackBerry device(s) or
+simulator that you will use to test your app. You can add or remove a
+target, or set a target as the default target.
+
+### Add a target
+
+```
+<path-to-project>/cordova/target add <name> <ip-address> <device | simulator> [-p | --password <password>] [--pin <device-pin>]
+```
+
+where
+
+- `<name>` specifies a unique name for the target.
+- `<ip-address>` specifies the ip address of the BlackBerry device or
+ simulator.
+- `-p|--password <password>` specifies the password for the device or
+ simulator. This is required only if the device or simulator is
+ password protected.
+- `--pin <device-pin>` specifies the PIN of the BlackBerry device,
+ which identifies that device as a valid host for the debug
+ token. This argument is required only if you are creating a debug
+ token.
+
+### Remove a target
+
+```
+<path-to-project>/cordova/target remove <name>
+```
+
+### Set a target as the default
+
+```
+<path-to-project>/cordova/target default <name>
+```
+
+## build
+
+The `build` command builds the project as a .bar file. You can build
+your app in either release mode (which produces a signed .bar file) or
+in debug mode (which produces an unsigned .bar file).
+
+### Build your project in release mode
+
+```
+<path-to-project>/cordova/build release -k|--keystorepass <password> [-b|--buildId <number>] [-p|--params <params-JSON-file>]
+```
+where
+
+- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications.
+- `-b|--buildId <number>` specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
+- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
+
+### Build your project in debug mode
+
+```
+<path-to-project>/cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params <params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
+```
+
+where
+
+- `<target>` specifies the name of a previously added target. If
+ `<target>` is not specified, the default target is used, if one has
+ been created. This argument is only required if you want the script
+ to deploy your app to a BlackBerry device or simulator and you have
+ not created a default target. Additionally, if `<target>` is a
+ device, then that device must be connected to your computer by USB
+ connection or be connected to the same Wi-Fi network as your
+ computer.
+- `-k|--keystorepass <password>` specifies the password you defined
+ when you configured your computer to sign applications. This
+ password is also used to create your debug token. This argument is
+ only required if you want the script to create and install the debug
+ token for you.
+- `-p|--params <params-JSON-file>` specifies a JSON file containing
+ additional parameters to pass to downstream tools.
+- `-ll|--loglevel <level>` specifies the log level. The log level may
+ be one of `error`, `warn`, or `verbose`.
+
+If you have previously defined a default target (and previously
+installed a debug token, if that target is a BlackBerry device), you
+can run the script with no arguments, and the script will package your
+app and deploy it to the default target. For example:
+
+```
+<path-to-project>/cordova/build debug
+```
+
+## run
+
+The `run` command deploys the app on the specified BlackBerry device
+or a simulator. Before deploying your app, you must first create a
+target for the device or simulator you want to deploy your app to. The
+deploy script will deploy the most recent build of your app.
+
+```
+<path-to-project>/cordova/run <target>
+```
+
+where
+
+- `<target> `specifies the name of a previously added target. If
+ `<target> `is a device, then that device must be connected to your
+ computer by USB connection or be connected to the same Wi-Fi network
+ as your computer.
+
+## plugin
+
+The `target` command allows you to add and remove plugins
+
+### Fetch a locally-hosted plugin
+
+```
+<path-to-project>/cordova/plugin fetch <path-to-plugin>
+```
+
+### View a list of installed plugins
+
+```
+<path-to-project>/cordova/plugin ls
+```
+
+### Add a plugin
+
+```
+<path-to-project>/cordova/plugin add <name>
+```
+
+### Remove a plugin
+
+```
+<path-to-project>/cordova/plugin rm <name>
+```
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/getting-started/ios/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/ios/tools.md b/docs/en/edge/guide/getting-started/ios/tools.md
new file mode 100644
index 0000000..ea7cdee
--- /dev/null
+++ b/docs/en/edge/guide/getting-started/ios/tools.md
@@ -0,0 +1,59 @@
+---
+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 Command-Line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+The iOS command-line tools are built upon shell scripts and rely on
+Xcode command-line tools such as `xcode-select` and `xcodebuild`.
+
+## 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.
+
+ $ ./path/to/cordova-ios/bin/create /path/to/my_new_project com.example.project_name ProjectName
+
+## Build a project
+
+ $ /path/to/my_new_project/cordova/build
+
+## Run app on emulator
+
+ $ /path/to/my_new_project/cordova/run
+
+## Releasing
+
+ $ /path/to/my_new_project/cordova/release
+
+## Logging
+
+ $ /path/to/my_new_project/cordova/log
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/getting-started/windows-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-8/tools.md b/docs/en/edge/guide/getting-started/windows-8/tools.md
new file mode 100644
index 0000000..355016a
--- /dev/null
+++ b/docs/en/edge/guide/getting-started/windows-8/tools.md
@@ -0,0 +1,44 @@
+---
+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.
+---
+
+# Windows 8 Command-Line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## Windows 8
+
+The Windows 8 command-line tools only support creating new projects.
+Commands must be run from a cmd or powershell prompt.
+
+## Create a project
+
+Run the `create` command with the following parameters:
+
+* Path to your new Cordova Windows 8 project
+* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
+* Project name
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-phone-8/tools.md b/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
new file mode 100644
index 0000000..b096671
--- /dev/null
+++ b/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
@@ -0,0 +1,77 @@
+---
+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.
+---
+
+# Windows Phone Command-Line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## Windows Phone
+
+The Windows Phone command-line tools support creating, building, and
+running new projects. Commands must be run from a cmd or powershell
+prompt.
+
+The WP8 repo now includes code for building both WP7 + WP8 apps. The
+repo has subfolders for each: wp7/ and wp8/
+
+## 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 Windows Phone 7 and 8:
+
+ $ C:\path\to\cordova-wp8\wp7\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
+ $ C:\path\to\cordova-wp8\wp8\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
+
+## Building your project (cleans then builds)
+
+* Debug
+
+ $ C:\path\to\my_new_project\cordova\build --debug
+
+* Release
+
+ $ C:\path\to\my_new_project\cordova\build --release
+
+## Running your application
+
+Run the 'run' command with the following *optional* parameters
+
+* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
+* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
+
+ $ C:\path\to\my_new_project\cordova\run [Target] [Build]
+
+By default the `run` command will look for a connected device, if no
+device is found it will look for any started emulators. If you have
+multiple emulators, you can specify a target ID.
+
+## Cleaning
+
+ $ C:\path\to\my_new_project\cordova\clean
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/02c44204/docs/en/edge/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/index.md b/docs/en/edge/index.md
index 90cd846..24bb0a6 100644
--- a/docs/en/edge/index.md
+++ b/docs/en/edge/index.md
@@ -96,14 +96,10 @@ license: Licensed to the Apache Software Foundation (ASF) under one
<span>Setup each SDK and create your first Cordova app.</span>
</li>
<li>
- <h2>The Cordova Command-line Interface</h2>
+ <h2>The Cordova<br/>Command-line Interface</h2>
<span>Create, build, and deploy from the command-line.</span>
</li>
<li>
- <h2>Command-Line Usage</h2>
- <span>More command-line tools.</span>
- </li>
- <li>
<h2>Privacy Guide</h2>
<span>Learn about important mobile privacy issues.</span>
</li>
[08/20] [CB-3827] rename 'getting-started' dirs as 'platforms'
Posted by mw...@apache.org.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/windows-phone-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-phone-8/index.md b/docs/en/edge/guide/platforms/windows-phone-8/index.md
new file mode 100644
index 0000000..85a02ae
--- /dev/null
+++ b/docs/en/edge/guide/platforms/windows-phone-8/index.md
@@ -0,0 +1,135 @@
+---
+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.
+---
+
+Windows Phone 8 Platform Guide
+==================================
+
+This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
+
+__NOTE:__ Applications built with Apache Cordova for Windows Phone 8 run only on Windows Phone 8 devices. If you want to target both 7.5 'and' 8 devices, then use Apache Cordova for Windows Phone 7, which does not have all the advanced features included in IE10, but implements the same APIs.
+
+1. System Requirements
+---------------
+
+- Operating System:
+ - Windows 8 or Windows 8 Pro
+ - The 64-bit version (x64) of Windows is required for the SDK.
+ - The Pro version is recommended so you can run a device emulator.
+
+- Hardware:
+ - 6.5 GB of free hard disk space
+ - 4 GB RAM
+ - 64-bit (x64) CPU
+
+- Windows Phone 8 Emulator
+ - The phone emulator uses Hyper-V, so this list includes those pre-requisites.
+ - Windows 8 Pro 64-bit edition or greater
+ - Requires a processor that supports virtualization and [Second Level Address Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation)
+ - See the [list of Intel processors that support VT-x (virtualization) and EPT (SLAT)](http://ark.intel.com/Products/VirtualizationTechnology)
+ - Enable the virtualization capability (i.e., VT-x on Intel) in your BIOS settings, as usually this is disabled by default.
+
+- SDK + IDE ( Visual Studio )
+ - Visual Studio 2012 Professional, Premium, or Ultimate. Note that Visual Studio Express for Windows Phone (included in the SDK) is not recommended because you can not build the template (see below) with VS Express, as it does not have the __Export Template__ functionality, which is only in VS Pro or higher.
+
+- Register and pay for a [Windows Phone Dev Center](http://dev.windowsphone.com/en-us/publish) account if you want to install your app on a real device and/or submit it to Market Place.
+
+__NOTE:__ Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for [Windows Phone on a Mac](http://aka.ms/BuildaWP8apponaMac).
+
+2. Install SDK + Cordova
+----------------------------
+
+- Download and install [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
+- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-phone-8` subfolder.
+- Copy the file CordovaWP8_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
+
+2.1. Building the template
+-----------------------------
+
+__NOTE:__ this step may not be required. If the lib\windows-phone directory already contains a file CordovaWP8_x_x_x.zip then you may skip this step.
+
+In order to simplify the development process, Cordova comes with a Visual Studio template that allows creating a Cordova application rapidly. This template can be modified if needed and the below steps indicate how to proceed if you want to modify and re-generate the template.
+
+- Open the `lib\windows-phone\templates\standalone\CordovaSolution.sln` file in Visual Studio Express for Windows Phone.
+- Select __Export Template...__ from the __File__ menu.
+- Choose template type __Project template__
+- Give the exported template a name, such as `CordovaStarter-2.1.0`, which produces a `CordovaStarter-2.1.0.zip` archive.
+- Optionally, you may add a description, icon image, and preview image. These display in Visual Studio's __New Project__ dialog.
+- __NOTE:__ If you select __Automatically import the template...__, then you don't need to copy the `.zip` file over as outlined in step 2.
+- Press __Finish__
+
+2.2 About the different templates
+---------------------------------
+
+Apache Cordova for Windows Phone 8 only supports the standalone template.
+
+The 'Stand-Alone' template includes _all_ the source code for Apache
+Cordova. This project is easier to fine-tune to use just the features
+you need, thereby working around the permissions issues of the 'Full'
+template, however this type of project is more difficult to update, as
+you update individual files within your project and manage any
+dependancies yourself. In order to exclude an unused API, simply
+right-click-select the __Command__ class file in Visual Studio and
+choose __do not include in project__.
+
+3. Set up New Project
+--------------------
+
+- Open Visual Studio Express for Windows Phone and choose **New Project**.
+- Select **CordovaWP8**. (The version number is displayed in the template description.)
+- Give the project a name, and select __OK__.
+
+
+
+4. Review the project structure
+-------------------------------
+
+- The 'www' folder contains your Cordova html/js/css and any other resources included in your app.
+- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
+- Note: This screen capture was from the cordova-2.3.0 download, your listing will vary based on the actual version installed.
+
+
+
+5. Build and Deploy to Emulator
+-------------------------------
+
+- Make sure **Windows Phone Emulator** is selected in the main drop-down menu.
+- Press the green **play** button next to the drop-down menu to start debugging, or type __F5__.
+
+
+
+6. Build your project for the device
+------------------------------------
+
+In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 8.
+
+- Make sure your phone is connected, and the screen is unlocked.
+- In Visual Studio, select 'Device' from the top drop-down menu.
+- Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
+
+
+
+Done!
+-----
+
+Further Reading
+-------
+
+For more details on the specific differences between IE10 and WebKit browsers, and how to support both MS has a helpful [guide here](http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx)
+
+[register-url]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/windows-phone-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-phone-8/tools.md b/docs/en/edge/guide/platforms/windows-phone-8/tools.md
new file mode 100644
index 0000000..df821e2
--- /dev/null
+++ b/docs/en/edge/guide/platforms/windows-phone-8/tools.md
@@ -0,0 +1,77 @@
+---
+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.
+---
+
+# Windows Phone Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## Windows Phone
+
+The Windows Phone command-line tools support creating, building, and
+running new projects. Commands must be run from a cmd or powershell
+prompt.
+
+The WP8 repo now includes code for building both WP7 + WP8 apps. The
+repo has subfolders for each: wp7/ and wp8/
+
+## 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 Windows Phone 7 and 8:
+
+ $ C:\path\to\cordova-wp8\wp7\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
+ $ C:\path\to\cordova-wp8\wp8\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
+
+## Building your project (cleans then builds)
+
+* Debug
+
+ $ C:\path\to\my_new_project\cordova\build --debug
+
+* Release
+
+ $ C:\path\to\my_new_project\cordova\build --release
+
+## Running your application
+
+Run the 'run' command with the following *optional* parameters
+
+* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
+* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
+
+ $ C:\path\to\my_new_project\cordova\run [Target] [Build]
+
+By default the `run` command will look for a connected device, if no
+device is found it will look for any started emulators. If you have
+multiple emulators, you can specify a target ID.
+
+## Cleaning
+
+ $ C:\path\to\my_new_project\cordova\clean
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/AndroidFlow.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/AndroidFlow.png b/template/docs/default/img/guide/getting-started/android/AndroidFlow.png
deleted file mode 100644
index 7d019b6..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/AndroidFlow.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/asdk_avds.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/asdk_avds.png b/template/docs/default/img/guide/getting-started/android/asdk_avds.png
deleted file mode 100644
index c882cc3..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/asdk_avds.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/asdk_device.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/asdk_device.png b/template/docs/default/img/guide/getting-started/android/asdk_device.png
deleted file mode 100644
index 2873cec..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/asdk_device.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/asdk_emulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/asdk_emulator.png b/template/docs/default/img/guide/getting-started/android/asdk_emulator.png
deleted file mode 100644
index 0e8e954..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/asdk_emulator.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/asdk_newAVD.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/asdk_newAVD.png b/template/docs/default/img/guide/getting-started/android/asdk_newAVD.png
deleted file mode 100644
index b1f51a5..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/asdk_newAVD.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/asdk_window.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/asdk_window.png b/template/docs/default/img/guide/getting-started/android/asdk_window.png
deleted file mode 100644
index b134ef1..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/asdk_window.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/buildPath.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/buildPath.jpg b/template/docs/default/img/guide/getting-started/android/buildPath.jpg
deleted file mode 100755
index ae3f7ee..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/buildPath.jpg and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/eclipse_android_sdk_button.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/eclipse_android_sdk_button.png b/template/docs/default/img/guide/getting-started/android/eclipse_android_sdk_button.png
deleted file mode 100644
index 0e84666..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/eclipse_android_sdk_button.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/eclipse_new_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/eclipse_new_project.png b/template/docs/default/img/guide/getting-started/android/eclipse_new_project.png
deleted file mode 100644
index 9d9106e..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/eclipse_new_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/javaSrc.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/javaSrc.jpg b/template/docs/default/img/guide/getting-started/android/javaSrc.jpg
deleted file mode 100644
index ab93051..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/javaSrc.jpg and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/manifest.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/manifest.jpg b/template/docs/default/img/guide/getting-started/android/manifest.jpg
deleted file mode 100644
index 6039194..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/manifest.jpg and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/manifest.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/manifest.png b/template/docs/default/img/guide/getting-started/android/manifest.png
deleted file mode 100644
index 88163b1..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/manifest.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/new_android_project.jpeg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/new_android_project.jpeg b/template/docs/default/img/guide/getting-started/android/new_android_project.jpeg
deleted file mode 100644
index 20bc29d..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/new_android_project.jpeg and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/step_1.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/step_1.png b/template/docs/default/img/guide/getting-started/android/step_1.png
deleted file mode 100644
index bb3202a..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/step_1.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/step_2.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/step_2.png b/template/docs/default/img/guide/getting-started/android/step_2.png
deleted file mode 100644
index 20929e6..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/step_2.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/step_3.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/step_3.png b/template/docs/default/img/guide/getting-started/android/step_3.png
deleted file mode 100644
index cf3f87d..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/step_3.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/step_4.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/step_4.png b/template/docs/default/img/guide/getting-started/android/step_4.png
deleted file mode 100644
index d8033d8..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/step_4.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/android/step_5.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/android/step_5.png b/template/docs/default/img/guide/getting-started/android/step_5.png
deleted file mode 100644
index 9b64bfa..0000000
Binary files a/template/docs/default/img/guide/getting-started/android/step_5.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/bada/bada_1_run.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/bada/bada_1_run.png b/template/docs/default/img/guide/getting-started/bada/bada_1_run.png
deleted file mode 100644
index 64e41a7..0000000
Binary files a/template/docs/default/img/guide/getting-started/bada/bada_1_run.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/bada/bada_2_run.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/bada/bada_2_run.png b/template/docs/default/img/guide/getting-started/bada/bada_2_run.png
deleted file mode 100644
index a569a05..0000000
Binary files a/template/docs/default/img/guide/getting-started/bada/bada_2_run.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/bada/bada_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/bada/bada_project.png b/template/docs/default/img/guide/getting-started/bada/bada_project.png
deleted file mode 100644
index 9ec1534..0000000
Binary files a/template/docs/default/img/guide/getting-started/bada/bada_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/bada/bada_set_target.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/bada/bada_set_target.png b/template/docs/default/img/guide/getting-started/bada/bada_set_target.png
deleted file mode 100644
index 4b11851..0000000
Binary files a/template/docs/default/img/guide/getting-started/bada/bada_set_target.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/bada/import_bada_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/bada/import_bada_project.png b/template/docs/default/img/guide/getting-started/bada/import_bada_project.png
deleted file mode 100644
index 9a934b3..0000000
Binary files a/template/docs/default/img/guide/getting-started/bada/import_bada_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/bada/import_bada_project_2.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/bada/import_bada_project_2.png b/template/docs/default/img/guide/getting-started/bada/import_bada_project_2.png
deleted file mode 100644
index 61a3db8..0000000
Binary files a/template/docs/default/img/guide/getting-started/bada/import_bada_project_2.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/HelloWorldStandard.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/HelloWorldStandard.png b/template/docs/default/img/guide/getting-started/ios/HelloWorldStandard.png
deleted file mode 100644
index 3e6c0af..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/HelloWorldStandard.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/HelloWorldiPhone4.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/HelloWorldiPhone4.png b/template/docs/default/img/guide/getting-started/ios/HelloWorldiPhone4.png
deleted file mode 100644
index e2aa147..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/HelloWorldiPhone4.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/XCode4-templates.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/XCode4-templates.png b/template/docs/default/img/guide/getting-started/ios/XCode4-templates.png
deleted file mode 100644
index e3eee61..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/XCode4-templates.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/active_scheme_device.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/active_scheme_device.png b/template/docs/default/img/guide/getting-started/ios/active_scheme_device.png
deleted file mode 100644
index a77d70f..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/active_scheme_device.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/active_scheme_simulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/active_scheme_simulator.png b/template/docs/default/img/guide/getting-started/ios/active_scheme_simulator.png
deleted file mode 100644
index 7e952d2..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/active_scheme_simulator.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/bin_create_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/bin_create_project.png b/template/docs/default/img/guide/getting-started/ios/bin_create_project.png
deleted file mode 100644
index 8984141..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/bin_create_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/bin_dir_listing.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/bin_dir_listing.png b/template/docs/default/img/guide/getting-started/ios/bin_dir_listing.png
deleted file mode 100644
index 9e5bfc3..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/bin_dir_listing.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/bin_folder.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/bin_folder.png b/template/docs/default/img/guide/getting-started/ios/bin_folder.png
deleted file mode 100644
index 3848df7..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/bin_folder.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/create-folder-reference.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/create-folder-reference.png b/template/docs/default/img/guide/getting-started/ios/create-folder-reference.png
deleted file mode 100644
index 0ca53e5..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/create-folder-reference.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/create.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/create.png b/template/docs/default/img/guide/getting-started/ios/create.png
deleted file mode 100644
index 47f8227..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/create.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/helloworld_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/helloworld_project.png b/template/docs/default/img/guide/getting-started/ios/helloworld_project.png
deleted file mode 100644
index 71434b3..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/helloworld_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/index-not-found.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/index-not-found.png b/template/docs/default/img/guide/getting-started/ios/index-not-found.png
deleted file mode 100644
index 3ed84d3..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/index-not-found.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/make.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/make.png b/template/docs/default/img/guide/getting-started/ios/make.png
deleted file mode 100644
index 78cc848..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/make.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/project.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/project.jpg b/template/docs/default/img/guide/getting-started/ios/project.jpg
deleted file mode 100644
index 6e74ca2..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/project.jpg and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/select_xcode_scheme.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/select_xcode_scheme.png b/template/docs/default/img/guide/getting-started/ios/select_xcode_scheme.png
deleted file mode 100644
index 630dab0..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/select_xcode_scheme.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/www-folder.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/www-folder.png b/template/docs/default/img/guide/getting-started/ios/www-folder.png
deleted file mode 100644
index 8abcdd8..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/www-folder.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/xcode4-name_your_app.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/xcode4-name_your_app.png b/template/docs/default/img/guide/getting-started/ios/xcode4-name_your_app.png
deleted file mode 100644
index 22395e7..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/xcode4-name_your_app.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/ios/xcode_build_location.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/ios/xcode_build_location.png b/template/docs/default/img/guide/getting-started/ios/xcode_build_location.png
deleted file mode 100644
index 8fbb1b5..0000000
Binary files a/template/docs/default/img/guide/getting-started/ios/xcode_build_location.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/build_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/build_project.png b/template/docs/default/img/guide/getting-started/tizen/build_project.png
deleted file mode 100644
index 498b4c1..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/build_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/connection_explorer.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/connection_explorer.png b/template/docs/default/img/guide/getting-started/tizen/connection_explorer.png
deleted file mode 100644
index 55bfd95..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/connection_explorer.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/import_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/import_project.png b/template/docs/default/img/guide/getting-started/tizen/import_project.png
deleted file mode 100644
index f5207e0..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/import_project.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/import_widget.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/import_widget.png b/template/docs/default/img/guide/getting-started/tizen/import_widget.png
deleted file mode 100644
index af1330d..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/import_widget.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/project_explorer.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/project_explorer.png b/template/docs/default/img/guide/getting-started/tizen/project_explorer.png
deleted file mode 100644
index dd6a23c..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/project_explorer.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/project_template.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/project_template.png b/template/docs/default/img/guide/getting-started/tizen/project_template.png
deleted file mode 100644
index 9e6e6ab..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/project_template.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/runas_web_app.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/runas_web_app.png b/template/docs/default/img/guide/getting-started/tizen/runas_web_app.png
deleted file mode 100644
index 0e77483..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/runas_web_app.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/tizen/runas_web_sim_app.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/tizen/runas_web_sim_app.png b/template/docs/default/img/guide/getting-started/tizen/runas_web_sim_app.png
deleted file mode 100644
index d87039e..0000000
Binary files a/template/docs/default/img/guide/getting-started/tizen/runas_web_sim_app.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-8/wsalert.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-8/wsalert.png b/template/docs/default/img/guide/getting-started/windows-8/wsalert.png
deleted file mode 100755
index 9680e53..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-8/wsalert.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-8/wschangemanifest.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-8/wschangemanifest.png b/template/docs/default/img/guide/getting-started/windows-8/wschangemanifest.png
deleted file mode 100755
index 1dd67da..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-8/wschangemanifest.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-8/wsnewproject.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-8/wsnewproject.png b/template/docs/default/img/guide/getting-started/windows-8/wsnewproject.png
deleted file mode 100755
index 8e1df69..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-8/wsnewproject.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wp7emulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wp7emulator.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wp7emulator.png
deleted file mode 100644
index e3de172..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wp7emulator.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wp7projectstructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wp7projectstructure.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wp7projectstructure.png
deleted file mode 100644
index 0c7d42d..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wp7projectstructure.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wp7vs.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wp7vs.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wp7vs.png
deleted file mode 100644
index 4e14c2f..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wp7vs.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wpd.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wpd.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wpd.png
deleted file mode 100644
index 0a0b2db..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wpd.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wpfirstrun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wpfirstrun.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wpfirstrun.png
deleted file mode 100644
index 8a82ec6..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wpfirstrun.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wpnewproj.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wpnewproj.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wpnewproj.png
deleted file mode 100644
index ed2f143..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wpnewproj.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-7/wprun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-7/wprun.png b/template/docs/default/img/guide/getting-started/windows-phone-7/wprun.png
deleted file mode 100644
index ce67de9..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-7/wprun.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-8/BuidDevice.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-8/BuidDevice.png b/template/docs/default/img/guide/getting-started/windows-phone-8/BuidDevice.png
deleted file mode 100644
index 92ea56d..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-8/BuidDevice.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-8/BuildEmulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-8/BuildEmulator.png b/template/docs/default/img/guide/getting-started/windows-phone-8/BuildEmulator.png
deleted file mode 100644
index 5893f64..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-8/BuildEmulator.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-8/FullTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-8/FullTemplate.png b/template/docs/default/img/guide/getting-started/windows-phone-8/FullTemplate.png
deleted file mode 100644
index 85f49cf..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-8/FullTemplate.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-8/StandAloneTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-8/StandAloneTemplate.png b/template/docs/default/img/guide/getting-started/windows-phone-8/StandAloneTemplate.png
deleted file mode 100644
index 62a98c4..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-8/StandAloneTemplate.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/getting-started/windows-phone-8/projectStructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/getting-started/windows-phone-8/projectStructure.png b/template/docs/default/img/guide/getting-started/windows-phone-8/projectStructure.png
deleted file mode 100644
index 9956094..0000000
Binary files a/template/docs/default/img/guide/getting-started/windows-phone-8/projectStructure.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/AndroidFlow.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/AndroidFlow.png b/template/docs/default/img/guide/platforms/android/AndroidFlow.png
new file mode 100644
index 0000000..7d019b6
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/AndroidFlow.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/asdk_avds.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/asdk_avds.png b/template/docs/default/img/guide/platforms/android/asdk_avds.png
new file mode 100644
index 0000000..c882cc3
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/asdk_avds.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/asdk_device.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/asdk_device.png b/template/docs/default/img/guide/platforms/android/asdk_device.png
new file mode 100644
index 0000000..2873cec
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/asdk_device.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/asdk_emulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/asdk_emulator.png b/template/docs/default/img/guide/platforms/android/asdk_emulator.png
new file mode 100644
index 0000000..0e8e954
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/asdk_emulator.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/asdk_newAVD.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/asdk_newAVD.png b/template/docs/default/img/guide/platforms/android/asdk_newAVD.png
new file mode 100644
index 0000000..b1f51a5
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/asdk_newAVD.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/asdk_window.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/asdk_window.png b/template/docs/default/img/guide/platforms/android/asdk_window.png
new file mode 100644
index 0000000..b134ef1
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/asdk_window.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/buildPath.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/buildPath.jpg b/template/docs/default/img/guide/platforms/android/buildPath.jpg
new file mode 100755
index 0000000..ae3f7ee
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/buildPath.jpg differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/eclipse_android_sdk_button.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/eclipse_android_sdk_button.png b/template/docs/default/img/guide/platforms/android/eclipse_android_sdk_button.png
new file mode 100644
index 0000000..0e84666
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/eclipse_android_sdk_button.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/eclipse_new_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/eclipse_new_project.png b/template/docs/default/img/guide/platforms/android/eclipse_new_project.png
new file mode 100644
index 0000000..9d9106e
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/eclipse_new_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/javaSrc.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/javaSrc.jpg b/template/docs/default/img/guide/platforms/android/javaSrc.jpg
new file mode 100644
index 0000000..ab93051
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/javaSrc.jpg differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/manifest.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/manifest.jpg b/template/docs/default/img/guide/platforms/android/manifest.jpg
new file mode 100644
index 0000000..6039194
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/manifest.jpg differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/manifest.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/manifest.png b/template/docs/default/img/guide/platforms/android/manifest.png
new file mode 100644
index 0000000..88163b1
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/manifest.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/new_android_project.jpeg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/new_android_project.jpeg b/template/docs/default/img/guide/platforms/android/new_android_project.jpeg
new file mode 100644
index 0000000..20bc29d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/new_android_project.jpeg differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/step_1.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/step_1.png b/template/docs/default/img/guide/platforms/android/step_1.png
new file mode 100644
index 0000000..bb3202a
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/step_1.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/step_2.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/step_2.png b/template/docs/default/img/guide/platforms/android/step_2.png
new file mode 100644
index 0000000..20929e6
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/step_2.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/step_3.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/step_3.png b/template/docs/default/img/guide/platforms/android/step_3.png
new file mode 100644
index 0000000..cf3f87d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/step_3.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/step_4.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/step_4.png b/template/docs/default/img/guide/platforms/android/step_4.png
new file mode 100644
index 0000000..d8033d8
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/step_4.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/android/step_5.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/android/step_5.png b/template/docs/default/img/guide/platforms/android/step_5.png
new file mode 100644
index 0000000..9b64bfa
Binary files /dev/null and b/template/docs/default/img/guide/platforms/android/step_5.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/bada/bada_1_run.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/bada/bada_1_run.png b/template/docs/default/img/guide/platforms/bada/bada_1_run.png
new file mode 100644
index 0000000..64e41a7
Binary files /dev/null and b/template/docs/default/img/guide/platforms/bada/bada_1_run.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/bada/bada_2_run.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/bada/bada_2_run.png b/template/docs/default/img/guide/platforms/bada/bada_2_run.png
new file mode 100644
index 0000000..a569a05
Binary files /dev/null and b/template/docs/default/img/guide/platforms/bada/bada_2_run.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/bada/bada_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/bada/bada_project.png b/template/docs/default/img/guide/platforms/bada/bada_project.png
new file mode 100644
index 0000000..9ec1534
Binary files /dev/null and b/template/docs/default/img/guide/platforms/bada/bada_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/bada/bada_set_target.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/bada/bada_set_target.png b/template/docs/default/img/guide/platforms/bada/bada_set_target.png
new file mode 100644
index 0000000..4b11851
Binary files /dev/null and b/template/docs/default/img/guide/platforms/bada/bada_set_target.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/bada/import_bada_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/bada/import_bada_project.png b/template/docs/default/img/guide/platforms/bada/import_bada_project.png
new file mode 100644
index 0000000..9a934b3
Binary files /dev/null and b/template/docs/default/img/guide/platforms/bada/import_bada_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/bada/import_bada_project_2.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/bada/import_bada_project_2.png b/template/docs/default/img/guide/platforms/bada/import_bada_project_2.png
new file mode 100644
index 0000000..61a3db8
Binary files /dev/null and b/template/docs/default/img/guide/platforms/bada/import_bada_project_2.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/HelloWorldStandard.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/HelloWorldStandard.png b/template/docs/default/img/guide/platforms/ios/HelloWorldStandard.png
new file mode 100644
index 0000000..3e6c0af
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/HelloWorldStandard.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/HelloWorldiPhone4.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/HelloWorldiPhone4.png b/template/docs/default/img/guide/platforms/ios/HelloWorldiPhone4.png
new file mode 100644
index 0000000..e2aa147
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/HelloWorldiPhone4.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/XCode4-templates.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/XCode4-templates.png b/template/docs/default/img/guide/platforms/ios/XCode4-templates.png
new file mode 100644
index 0000000..e3eee61
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/XCode4-templates.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/active_scheme_device.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/active_scheme_device.png b/template/docs/default/img/guide/platforms/ios/active_scheme_device.png
new file mode 100644
index 0000000..a77d70f
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/active_scheme_device.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/active_scheme_simulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/active_scheme_simulator.png b/template/docs/default/img/guide/platforms/ios/active_scheme_simulator.png
new file mode 100644
index 0000000..7e952d2
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/active_scheme_simulator.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/bin_create_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/bin_create_project.png b/template/docs/default/img/guide/platforms/ios/bin_create_project.png
new file mode 100644
index 0000000..8984141
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/bin_create_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/bin_dir_listing.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/bin_dir_listing.png b/template/docs/default/img/guide/platforms/ios/bin_dir_listing.png
new file mode 100644
index 0000000..9e5bfc3
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/bin_dir_listing.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/bin_folder.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/bin_folder.png b/template/docs/default/img/guide/platforms/ios/bin_folder.png
new file mode 100644
index 0000000..3848df7
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/bin_folder.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/create-folder-reference.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/create-folder-reference.png b/template/docs/default/img/guide/platforms/ios/create-folder-reference.png
new file mode 100644
index 0000000..0ca53e5
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/create-folder-reference.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/create.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/create.png b/template/docs/default/img/guide/platforms/ios/create.png
new file mode 100644
index 0000000..47f8227
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/create.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/helloworld_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/helloworld_project.png b/template/docs/default/img/guide/platforms/ios/helloworld_project.png
new file mode 100644
index 0000000..71434b3
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/helloworld_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/index-not-found.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/index-not-found.png b/template/docs/default/img/guide/platforms/ios/index-not-found.png
new file mode 100644
index 0000000..3ed84d3
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/index-not-found.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/make.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/make.png b/template/docs/default/img/guide/platforms/ios/make.png
new file mode 100644
index 0000000..78cc848
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/make.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/project.jpg
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/project.jpg b/template/docs/default/img/guide/platforms/ios/project.jpg
new file mode 100644
index 0000000..6e74ca2
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/project.jpg differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/select_xcode_scheme.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/select_xcode_scheme.png b/template/docs/default/img/guide/platforms/ios/select_xcode_scheme.png
new file mode 100644
index 0000000..630dab0
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/select_xcode_scheme.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/www-folder.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/www-folder.png b/template/docs/default/img/guide/platforms/ios/www-folder.png
new file mode 100644
index 0000000..8abcdd8
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/www-folder.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/xcode4-name_your_app.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/xcode4-name_your_app.png b/template/docs/default/img/guide/platforms/ios/xcode4-name_your_app.png
new file mode 100644
index 0000000..22395e7
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/xcode4-name_your_app.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/ios/xcode_build_location.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/ios/xcode_build_location.png b/template/docs/default/img/guide/platforms/ios/xcode_build_location.png
new file mode 100644
index 0000000..8fbb1b5
Binary files /dev/null and b/template/docs/default/img/guide/platforms/ios/xcode_build_location.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/build_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/build_project.png b/template/docs/default/img/guide/platforms/tizen/build_project.png
new file mode 100644
index 0000000..498b4c1
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/build_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/connection_explorer.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/connection_explorer.png b/template/docs/default/img/guide/platforms/tizen/connection_explorer.png
new file mode 100644
index 0000000..55bfd95
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/connection_explorer.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/import_project.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/import_project.png b/template/docs/default/img/guide/platforms/tizen/import_project.png
new file mode 100644
index 0000000..f5207e0
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/import_project.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/import_widget.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/import_widget.png b/template/docs/default/img/guide/platforms/tizen/import_widget.png
new file mode 100644
index 0000000..af1330d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/import_widget.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/project_explorer.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/project_explorer.png b/template/docs/default/img/guide/platforms/tizen/project_explorer.png
new file mode 100644
index 0000000..dd6a23c
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/project_explorer.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/project_template.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/project_template.png b/template/docs/default/img/guide/platforms/tizen/project_template.png
new file mode 100644
index 0000000..9e6e6ab
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/project_template.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/runas_web_app.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/runas_web_app.png b/template/docs/default/img/guide/platforms/tizen/runas_web_app.png
new file mode 100644
index 0000000..0e77483
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/runas_web_app.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/tizen/runas_web_sim_app.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/tizen/runas_web_sim_app.png b/template/docs/default/img/guide/platforms/tizen/runas_web_sim_app.png
new file mode 100644
index 0000000..d87039e
Binary files /dev/null and b/template/docs/default/img/guide/platforms/tizen/runas_web_sim_app.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-8/wsalert.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-8/wsalert.png b/template/docs/default/img/guide/platforms/windows-8/wsalert.png
new file mode 100755
index 0000000..9680e53
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-8/wsalert.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png b/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png
new file mode 100755
index 0000000..1dd67da
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png b/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png
new file mode 100755
index 0000000..8e1df69
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png b/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png
new file mode 100644
index 0000000..e3de172
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png b/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png
new file mode 100644
index 0000000..0c7d42d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png b/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png
new file mode 100644
index 0000000..4e14c2f
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png b/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png
new file mode 100644
index 0000000..0a0b2db
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png b/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png
new file mode 100644
index 0000000..8a82ec6
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png b/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png
new file mode 100644
index 0000000..ed2f143
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png b/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png
new file mode 100644
index 0000000..ce67de9
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png b/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png
new file mode 100644
index 0000000..92ea56d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png b/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png
new file mode 100644
index 0000000..5893f64
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png b/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png
new file mode 100644
index 0000000..85f49cf
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png b/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png
new file mode 100644
index 0000000..62a98c4
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png b/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png
new file mode 100644
index 0000000..9956094
Binary files /dev/null and b/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png differ
[15/20] docs commit: [CB-3827] move platform-specific files within
platforms dir; rename dirs within platforms
Posted by mw...@apache.org.
[CB-3827] move platform-specific files within platforms dir; rename dirs within platforms
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/610314b2
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/610314b2
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/610314b2
Branch: refs/heads/master
Commit: 610314b2746ab2f429b7c7fbc24629f46b7dc702
Parents: cfebdc3
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 13:25:18 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 13:25:18 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/cordova-webview/android.md | 122 ------
docs/en/edge/guide/cordova-webview/index.md | 27 --
docs/en/edge/guide/cordova-webview/ios.md | 136 ------
docs/en/edge/guide/platforms/android/config.md | 43 ++
docs/en/edge/guide/platforms/android/plugin.md | 192 ++++++++
.../edge/guide/platforms/android/upgrading.md | 242 ++++++++++
docs/en/edge/guide/platforms/android/webview.md | 122 ++++++
.../edge/guide/platforms/blackberry/config.md | 29 ++
.../edge/guide/platforms/blackberry/plugin.md | 153 +++++++
.../guide/platforms/blackberry/upgrading.md | 311 +++++++++++++
.../edge/guide/platforms/blackberry10/plugin.md | 191 ++++++++
.../en/edge/guide/platforms/firefoxos/config.md | 24 +
docs/en/edge/guide/platforms/ios/config.md | 60 +++
docs/en/edge/guide/platforms/ios/plugin.md | 230 ++++++++++
docs/en/edge/guide/platforms/ios/upgrading.md | 438 +++++++++++++++++++
docs/en/edge/guide/platforms/ios/webview.md | 136 ++++++
docs/en/edge/guide/platforms/win8/config.md | 26 ++
docs/en/edge/guide/platforms/win8/index.md | 111 +++++
docs/en/edge/guide/platforms/win8/tools.md | 44 ++
.../guide/platforms/win8/upgrading.md/index.md | 39 ++
docs/en/edge/guide/platforms/windows-8/index.md | 111 -----
docs/en/edge/guide/platforms/windows-8/tools.md | 44 --
.../guide/platforms/windows-phone-7/index.md | 95 ----
.../guide/platforms/windows-phone-8/index.md | 135 ------
.../guide/platforms/windows-phone-8/tools.md | 77 ----
docs/en/edge/guide/platforms/wp7/config.md | 25 ++
docs/en/edge/guide/platforms/wp7/index.md | 95 ++++
docs/en/edge/guide/platforms/wp8/config.md | 25 ++
docs/en/edge/guide/platforms/wp8/index.md | 135 ++++++
docs/en/edge/guide/platforms/wp8/plugin.md | 194 ++++++++
docs/en/edge/guide/platforms/wp8/tools.md | 77 ++++
docs/en/edge/guide/platforms/wp8/upgrading.md | 236 ++++++++++
.../guide/plugin-development/android/index.md | 192 --------
.../plugin-development/blackberry/index.md | 153 -------
.../plugin-development/blackberry10/index.md | 191 --------
docs/en/edge/guide/plugin-development/index.md | 110 -----
.../edge/guide/plugin-development/ios/index.md | 230 ----------
.../plugin-development/windows-phone/index.md | 194 --------
docs/en/edge/guide/plugins/index.md | 110 +++++
.../guide/project-settings/android/index.md | 43 --
.../guide/project-settings/blackberry/index.md | 29 --
.../guide/project-settings/firefoxos/index.md | 24 -
.../en/edge/guide/project-settings/ios/index.md | 60 ---
.../guide/project-settings/windows8/index.md | 26 --
.../en/edge/guide/project-settings/wp7/index.md | 25 --
.../en/edge/guide/project-settings/wp8/index.md | 25 --
docs/en/edge/guide/upgrading/android/index.md | 242 ----------
.../en/edge/guide/upgrading/blackberry/index.md | 311 -------------
docs/en/edge/guide/upgrading/ios/index.md | 438 -------------------
docs/en/edge/guide/upgrading/windows-8/index.md | 39 --
.../edge/guide/upgrading/windows-phone/index.md | 236 ----------
docs/en/edge/guide/webviews/index.md | 27 ++
52 files changed, 3315 insertions(+), 3315 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/cordova-webview/android.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/android.md b/docs/en/edge/guide/cordova-webview/android.md
deleted file mode 100644
index c3c96b3..0000000
--- a/docs/en/edge/guide/cordova-webview/android.md
+++ /dev/null
@@ -1,122 +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
-====================================
-
-Beginning in Cordova 1.9, with the assistance of the
-`CordovaActivity`, you can use Cordova as a component in a larger
-native Android application. Android refers to this component as the
-`CordovaWebView`. New Cordova-based applications from 1.9 onwards use
-the `CordovaWebView` as its main view, regardless of whether the
-legacy `DroidGap` approach is used.
-
-If you're unfamiliar with Android application development, please read
-the Android Platform Guide to developing a Cordova Application before
-attempting to include a WebView. It's not the main way to author
-Android Cordova applications. These instructions are currently manual,
-but may be eventually be automated.
-
-Prerequisites
--------------
-
-1. **Cordova 1.9** or greater
-2. Android SDK updated with 15
-
-Guide to using CordovaWebView in an Android Project
----------------------------------------------------
-
-1. Use `bin/create` to fetch the `commons-codec-1.6.jar` file.
-2. `cd` into `/framework` and run `ant jar` to build the cordova jar. It creates the .jar file formed as `cordova-x.x.x.jar` in the `/framework` folder.
-3. Copy the cordova jar into your Android project's `/libs` directory.
-4. Edit your application's `main.xml` file (under `/res/xml`) to look like the following, with the `layout_height`, `layout_width` and `id` modified to suit your application:
-
- <org.apache.cordova.CordovaWebView
- android:id="@+id/tutorialView"
- android:layout_width="match_parent"
- android:layout_height="match_parent" />
-
-5. 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/DroidGap.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;
- }
-
-6. Copy your application's HTML and JavaScript files to your Android project's `/assets/www` directory.
-7. Copy `cordova.xml` and `plugins.xml` from `/framework/res/xml` to your project's `/res/xml` folder.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/cordova-webview/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/index.md b/docs/en/edge/guide/cordova-webview/index.md
deleted file mode 100644
index 649a5e8..0000000
--- a/docs/en/edge/guide/cordova-webview/index.md
+++ /dev/null
@@ -1,27 +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.
----
-
-Embedding WebViews
-=================
-
-> Implement the Cordova WebView in your own project.
-
-- Android WebViews
-- iOS WebViews
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/cordova-webview/ios.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/ios.md b/docs/en/edge/guide/cordova-webview/ios.md
deleted file mode 100644
index 445016a..0000000
--- a/docs/en/edge/guide/cordova-webview/ios.md
+++ /dev/null
@@ -1,136 +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 WebViews
-================================
-
-Beginning with Cordova 1.4, you can use Cordova as a component in your
-iOS applications. This component is code-named 'Cleaver'.
-
-New Cordova-based applications created using the Xcode template
-provided in Cordova 1.4 or greater use Cleaver. (The template is
-Cleaver's reference implementation.)
-
-Cordova 2.0.0 and subsequent versions only support the sub-project
-based Cleaver implementation.
-
-Prerequisites
--------------
-
-1. **Cordova 2.3.0** or greater
-2. **Xcode 4.5** or greater
-3. `config.xml` file (from a newly created iOS project)
-
-Adding Cleaver to your Xcode project (CordovaLib sub-project)
--------------------------------------------------------------
-
-1. **Download and extract the Cordova source** to a **permanent folder location** on your hard drive (say to `~/Documents/Cordova`)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Copy** the `config.xml` file into your project folder on disk (see **Prerequisites** above)
-5. **Drag and drop** the `config.xml` file into the Project Navigator of Xcode
-6. **Choose** the **Create groups for any added folders** radio button and press **Finish**
-7. **Drag and drop** the `CordovaLib.xcodeproj` file into the Project Navigator of Xcode (from the permanent folder location above, and it should be in the CordovaLib sub-folder)
-8. Select `CordovaLib.xcodeproj` in the Project Navigator
-9. Type the **Option-Command-1** key combination to show the **File Inspector**
-10. Choose **Relative to Group** in the **File Inspector** for the drop-down menu for **Location**
-11. Select the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
-12. Add `-all_load` and `-Obj-C` for the **Other Linker Flags** value
-13. Click on the **project icon** in the Project Navigator, select your **Target**, then select the **Build Phases** tab
-14. Expand **Link Binaries with Libraries**
-15. Select the **+** button, and add these **frameworks** (and optionally in the Project Navigator, **move** them under the Frameworks group):
-
- AddressBook.framework
- AddressBookUI.framework
- AudioToolbox.framework
- AVFoundation.framework
- CoreLocation.framework
- MediaPlayer.framework
- QuartzCore.framework
- SystemConfiguration.framework
- MobileCoreServices.framework
- CoreMedia.framework
-
-16. Expand **Target Dependencies** - the top box labeled like this if you have multiple boxes!
-17. Select the **+** button, and add the `CordovaLib` build product
-18. Expand **Link Binaries with Libraries** - the top box labeled like
- this if you have multiple boxes!
-19. Select the **+** button, and add `libCordova.a`
-20. Set the Xcode preference **Xcode Preferences → Locations → Derived Data → Advanced...** to **Unique**
-21. Select the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
-22. Search for **Header Search Paths**. For that setting, add these three values below (with quotes):
-
- "$(TARGET_BUILD_DIR)/usr/local/lib/include"
- "$(OBJROOT)/UninstalledProducts/include"
- "$(BUILT_PRODUCTS_DIR)"
-
- With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Reference Counting (ARC)**. You don't need to upgrade to **ARC** to use CordovaLib, but if you want to upgrade your project to use **ARC**, please use the Xcode migration wizard from the menu: **Edit → Refactor → Convert to Objective-C ARC...**, **de-select libCordova.a**, then run the wizard to completion.
-
-Using CDVViewController in your code
-------------------------------------
-
-1. Add this **header**:
-
- #import <Cordova/CDVViewController.h>
-
-2. Instantiate a **new** `CDVViewController`, and **retain it somewhere** (e.g. to a property in your class):
-
- CDVViewController* viewController = [CDVViewController new];
-
-3. (_OPTIONAL_) Set the `wwwFolderName` property (defaults to `www`):
-
- viewController.wwwFolderName = @"myfolder";
-
-4. (_OPTIONAL_) Set the start page in your config.xml, the `<content>` tag.
-
- <content src="index.html" />
-
- OR
-
- <content src="http://apache.org" />
-
-5. (_OPTIONAL_) Set the `useSplashScreen` property (defaults to `NO`):
-
- viewController.useSplashScreen = YES;
-
-6. Set the **view frame** (always set this as the last property):
-
- viewController.view.frame = CGRectMake(0, 0, 320, 480);
-
-7. **Add** Cleaver to your view:
-
- [myView addSubview:viewController.view];
-
-Adding your HTML, CSS and JavaScript assets
--------------------------------------------
-
-1. Create a **new folder** in your project **on disk**, `www` for example.
-2. Put your **HTML, CSS and JavaScript** assets into this folder.
-3. **Drag and drop** the folder into the Project Navigator of Xcode.
-4. **Choose** the **Create folder references for any added folders** radio button.
-5. **Set the appropriate `wwwFolderName` and `startPage` properties** for the folder you created in **(1)** or use the defaults (see previous section) when you instantiate the `CDVViewController`.
-
- /*
- if you created a folder called 'myfolder' and
- you want the file 'mypage.html' in it to be
- the startPage
- */
- viewController.wwwFolderName = @"myfolder";
- viewController.startPage = @"mypage.html"
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/android/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/config.md b/docs/en/edge/guide/platforms/android/config.md
new file mode 100644
index 0000000..b3c02b5
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/config.md
@@ -0,0 +1,43 @@
+<!--
+#
+# 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` settings file controls various settings of Cordova. This is application wide, and not set per CordovaWebView Instance.
+
+## <preference>
+
+Various **other** preferences (as **<preference>** tags) default on not breaking existing apps. The available preferences are:
+
+1. **useBrowserHistory (boolean, defaults to true)** - set to false if you want to use the history shim that was used to work around the hashtag error present in Android 3.x prior to the history fix. (Note: This setting will be deprecated in April 2013)
+2. **loadingDialog** - Display a native loading dialog when loading the app. The value's format is _Title, Message_
+3. **loadingPageDialog** - Display a native loading dialog when loading sub-pages. The value's format is _Title, Message_
+4. **errorUrl** - Set the error page for your application. Should be located in your Android project in file://android_asset/www/
+5. **backgroundColor** - Set the background color for your application. Supports a four-byte hex value, with the first byte representing alpha value, and the following three bytes with standard RGB values. (i.e. 0x00000000 = Black)
+6. **loadUrlTimeoutValue** - How much time Cordova should wait before throwing a timeout error on the application.
+7. **keepRunning (boolean, defaults to true)** - Determines whether Cordova will keep running in the background or not
+8. **splashscreen** - The name of the file minus its extension in the res/drawable directory. If you have multiple assets, they all must share this common name in their respective directories.
+9. **disallowOverscroll (boolean, defaults to false)** - set to true if you want to disable the glow when a user scrolls beyond the edge of the webview.
+
+## <plugin>
+
+Android supports using <feature> as analogues to <plugin> elements.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/android/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/plugin.md b/docs/en/edge/guide/platforms/android/plugin.md
new file mode 100644
index 0000000..39a79d7
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/plugin.md
@@ -0,0 +1,192 @@
+---
+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
+
+Writing a plugin requires an understanding of the architecture of Cordova-Android. Cordova-Android consists
+of an Android WebView with hooks attached to it. These 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. A plugin must override one
+of the `execute` methods from `CordovaPlugin`.
+As best practice, the plugin should handle `pause` and `resume` events, and any message passing between plugins.
+Plugins with long-running requests, background activity such as media payback, listeners, or internal state should implement the `onReset()` method as well. This method is run when the `WebView` navigates to a new page or refreshes, which reloads the JavaScript.
+
+## Plugin Class Mapping
+
+The JavaScript portion of a plugin always 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,
+more or less boiling down to calling the `action` method on the
+`service` class, with the arguments passed in the `args` Array.
+
+Whether you distribute your plugin as Java file or as a JAR of its own, the plugin must be added to the `config.xml` file in your Cordova-Android application's `res/xml/` folder.
+
+ <plugin name="<service_name>" value="<full_name_including_namespace>"/>
+
+The service name should match the one used in the JavaScript `exec`
+call, and the value is the Java classes full name, including the
+namespace. Otherwise the plugin may compile but still be unreachable
+by Cordova.
+
+## Writing an Android Java Plugin
+
+We have JavaScript to fire off a plugin request to the native side. We
+have the Android Java plugin mapped properly via the `config.xml` file.
+So what does the final Android Java Plugin class look like?
+
+What gets dispatched to the plugin via JavaScript's `exec` function gets
+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.
+ }
+
+We compare the value of the `action` parameter, and dispatch the
+request off to a (private) method in the class, optionally passing
+some of the parameters to the method.
+
+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
+
+JavaScript in the WebView does *not* run on the UI thread. It runs on
+the WebCore thread. The `execute` method also runs on the WebCore thread.
+
+If you need to interact with the UI, you should use the following:
+
+ @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;
+ }
+
+If you do not need to run on the UI thread, but do not want to block the WebCore thread:
+
+ @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
+
+We would add the following to our config.xml:
+
+ <plugin name="Echo" value="org.apache.cordova.plugin.Echo" />
+
+Then we would add the following file to
+`src/org/apache/cordova/plugin/Echo.java` inside our Cordova-Android
+application:
+
+ package org.apache.cordova.plugin;
+
+ import org.apache.cordova.api.CordovaPlugin;
+ import org.apache.cordova.api.PluginResult;
+ 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.");
+ }
+ }
+ }
+
+Let's take a look at the code. The necessary `imports` are at
+the top. Our class extends from `CordovaPlugin`. We override the
+execute() method in order to recieve messages from exec(). Our method
+first compares against `action`: this plugin only supports one action,
+the `echo` action. Any other action returns false, which results in an
+error of type `INVALID_ACTION`, which translates into an error
+callback invocation on the JavaScript side. Next, we grab the echo
+string using the `getString` method on our `args`, telling it we want
+to get the 0th parameter in the parameter array. We do a bit of
+parameter checking: make sure it is not `null`, and make sure it is
+not a zero-length string. If it is, we call `callbackContext.error()`
+(which, by now, you should know invokes the error callback). If all of
+those checks pass, then we call `callbackContext.success()` and pass
+in the `message` string we received as a parameter. This finally
+translates into a success callback invocation on the JavaScript
+side. It also passes the `message` parameter as a parameter into the
+JavaScript success callback function.
+
+## Debugging Plugins
+
+Eclipse can be used to debug an Android project, and the plugins can be debugged if the Java source is included in the project. Only the latest version of the Android Developer Tools is known to allow source code attachment to JAR dependencies, so this is not fully supported at this time.
+
+## Common Pitfalls
+
+* Plugins have access to a `CordovaInterface` object. This object has access to the Android `Activity` that is running 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` comes back to the application. This is important, since the
+`Intent`s system is how Android communicates between processes.
+* Plugins do not have direct access to the `Context` as they have in the past. The legacy `ctx` member is deprecated, and will be removed six months after 2.0 is released. All of `ctx` methods exist on the `Context`, so both `getContext()` and `getActivity()` are capable of returning the proper object required.
+
+## Use the Source
+
+One of the best ways to prepare yourself to write your own plugin is to
+[look over existing plugins](https://github.com/apache/cordova-android/tree/master/framework/src/org/apache/cordova).
+
+You should also read through the comments in [CordovaPlugin.java](https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/api/CordovaPlugin.java).
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/android/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/upgrading.md b/docs/en/edge/guide/platforms/android/upgrading.md
new file mode 100644
index 0000000..63019d3
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/upgrading.md
@@ -0,0 +1,242 @@
+---
+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 document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova.
+
+## 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 libs directory in your project
+2. Add cordova-2.8.0.jar to the libs directory in your project
+3. If you are using Eclipse, please refresh your eclipse project and do a clean
+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 to be the same as the one found in 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 cordova directory in your project
+
+## Upgrade to 2.7.0 from 2.6.0 ##
+1. Remove cordova-2.6.0.jar from the libs directory in your project
+2. Add cordova-2.7.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in 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 cordova directory in your project
+
+
+## Upgrade to 2.6.0 from 2.5.0 ##
+1. Remove cordova-2.5.0.jar from the libs directory in your project
+2. Add cordova-2.6.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in 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 cordova directory in your project
+
+. 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 libs directory in your project
+2. Add cordova-2.5.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in 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 cordova directory in your project
+
+## Upgrade to 2.4.0 from 2.3.0 ##
+
+1. Remove cordova-2.3.0.jar from the libs directory in your project
+2. Add cordova-2.4.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
+7. Copy files from bin/templates/cordova to the cordova directory in your project
+
+## Upgrade to 2.3.0 from 2.2.0 ##
+
+1. Remove cordova-2.2.0.jar from the libs directory in your project
+2. Add cordova-2.3.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
+7. Copy files from bin/templates/cordova to the cordova directory in your project
+
+## Upgrade to 2.2.0 from 2.1.0 ##
+
+1. Remove cordova-2.1.0.jar from the libs directory in your project
+2. Add cordova-2.2.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
+7. Copy files from bin/templates/cordova to the cordova directory in your project
+
+## Upgrade to 2.1.0 from 2.0.0 ##
+
+1. Remove cordova-2.0.0.jar from the libs directory in your project
+2. Add cordova-2.1.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
+7. Copy files from bin/templates/cordova to the cordova directory in your project
+
+## Upgrade to 2.0.0 from 1.9.0 ##
+
+1. Remove cordova-1.9.0.jar from the libs directory in your project
+2. Add cordova-2.0.0.jar to the libs directory in your project
+3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
+
+### Notes about 2.0.0 release
+config.xml will be replacing cordova.xml and plugins.xml. This new file is a combination of the previous two. However, the
+old files are deprecated, and and while currently still work, will cease working in a future release.
+
+## Upgrade to 1.9.0 from 1.8.1 ##
+
+1. Remove cordova-1.8.0.jar from the libs directory in your project
+2. Add cordova-1.9.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
+
+### Notes about 1.9.0 release
+
+- Third-Party plugins may or may not work. This is because of the introduction of the CordovaWebView. 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 libs directory in your project
+2. Add cordova-1.8.1.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
+
+## Upgrade to 1.8.0 from 1.7.0 ##
+
+1. Remove cordova-1.7.0.jar from the libs directory in your project
+2. Add cordova-1.8.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
+
+## Upgrade to 1.8.0 from 1.7.0 ##
+
+1. Remove cordova-1.7.0.jar from the libs directory in your project
+2. Add cordova-1.8.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
+
+## Upgrade to 1.7.0 from 1.6.1 ##
+
+1. Remove cordova-1.6.1.jar from the libs directory in your project
+2. Add cordova-1.7.0.jar to the libs directory in your project
+3. If you are using Eclipse, please refresh your eclipse project and do a clean
+4. Copy the new cordova-1.7.0.js into your project
+5. Update the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
+
+## Upgrade to 1.6.1 from 1.6.0 ##
+
+1. Remove cordova-1.6.0.jar from the libs directory in your project
+2. Add cordova-1.6.1.jar to the libs directory in your project
+3. If you are using Eclipse, please refresh your eclipse project and do a clean
+4. Copy the new cordova-1.6.1.js into your project
+5. Update the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
+
+## Upgrade to 1.6.0 from 1.5.0 ##
+1. Remove cordova-1.5.0.jar from the libs directory in your project
+2. Add cordova-1.6.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
+7. Replace the res/xml/phonegap.xml with res/xml/cordova.xml so that it is the same as the one found in framework/res/xml/cordova.xml
+
+## Upgrade to 1.5.0 from 1.4.0##
+1. Remove phonegap-1.4.0.jar from the libs directory in your project
+2. Add cordova-1.5.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
+7. Replace the res/xml/phonegap.xml with res/xml/cordova.xml so that it is the same as the one found in framework/res/xml/cordova.xml
+
+## Upgrade to 1.4.0 from 1.3.0 ##
+1. Remove phonegap-1.3.0.jar from the libs directory in your project
+2. Add phonegap-1.4.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
+7. Update the res/xml/phonegap.xml so that it is the same as the one found in framework/res/xml/phonegap.xml
+
+## Upgrade to 1.3.0 from 1.2.0 ##
+1. Remove phonegap-1.2.0.jar from the libs directory in your project
+2. Add phonegap-1.3.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
+7. Update the res/xml/phonegap.xml so that it is the same as the one found in framework/res/xml/phonegap.xml
+
+## Upgrade to 1.2.0 from 1.1.0 ##
+1. Remove phonegap-1.1.0.jar from the libs directory in your project
+2. Add phonegap-1.2.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
+7. Update the res/xml/phonegap.xml so that it is the same as the one found in framework/res/xml/phonegap.xml
+
+## Upgrade to 1.1.0 from 1.0.0 ##
+1. Remove phonegap-1.0.0.jar from the libs directory in your project
+2. Add phonegap-1.1.0.jar to the libs directory in your project
+3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
+
+## Upgrade to 1.0.0 from 0.9.6 ##
+1. Remove phonegap-0.9.6.jar from the libs directory in your project
+2. Add phonegap-1.0.0.jar to the libs directory in your project
+3. If you are using 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 so that it is the same as the one found in framework/res/xml/plugins.xml
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/android/webview.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/webview.md b/docs/en/edge/guide/platforms/android/webview.md
new file mode 100644
index 0000000..c3c96b3
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/webview.md
@@ -0,0 +1,122 @@
+---
+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
+====================================
+
+Beginning in Cordova 1.9, with the assistance of the
+`CordovaActivity`, you can use Cordova as a component in a larger
+native Android application. Android refers to this component as the
+`CordovaWebView`. New Cordova-based applications from 1.9 onwards use
+the `CordovaWebView` as its main view, regardless of whether the
+legacy `DroidGap` approach is used.
+
+If you're unfamiliar with Android application development, please read
+the Android Platform Guide to developing a Cordova Application before
+attempting to include a WebView. It's not the main way to author
+Android Cordova applications. These instructions are currently manual,
+but may be eventually be automated.
+
+Prerequisites
+-------------
+
+1. **Cordova 1.9** or greater
+2. Android SDK updated with 15
+
+Guide to using CordovaWebView in an Android Project
+---------------------------------------------------
+
+1. Use `bin/create` to fetch the `commons-codec-1.6.jar` file.
+2. `cd` into `/framework` and run `ant jar` to build the cordova jar. It creates the .jar file formed as `cordova-x.x.x.jar` in the `/framework` folder.
+3. Copy the cordova jar into your Android project's `/libs` directory.
+4. Edit your application's `main.xml` file (under `/res/xml`) to look like the following, with the `layout_height`, `layout_width` and `id` modified to suit your application:
+
+ <org.apache.cordova.CordovaWebView
+ android:id="@+id/tutorialView"
+ android:layout_width="match_parent"
+ android:layout_height="match_parent" />
+
+5. 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/DroidGap.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;
+ }
+
+6. Copy your application's HTML and JavaScript files to your Android project's `/assets/www` directory.
+7. Copy `cordova.xml` and `plugins.xml` from `/framework/res/xml` to your project's `/res/xml` folder.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/blackberry/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/config.md b/docs/en/edge/guide/platforms/blackberry/config.md
new file mode 100644
index 0000000..ab266ad
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry/config.md
@@ -0,0 +1,29 @@
+<!--
+#
+# 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 Configuration
+===================================
+
+BlackBerry fully supports the
+[W3C Widget Specification](http://www.w3.org/TR/widgets/)
+as well as proprietary RIM extensions. Please see the full
+[BlackBerry WebWorks documentation regarding config.xml](https://developer.blackberry.com/html5/documentation/working_with_config_xml_file_1866970_11.html)
+for details.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/blackberry/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/plugin.md b/docs/en/edge/guide/platforms/blackberry/plugin.md
new file mode 100644
index 0000000..ebdb780
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry/plugin.md
@@ -0,0 +1,153 @@
+---
+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 Plugins
+=================================
+
+## How to make the Echo plugin on Blackberry
+
+This guide explores how to develop the Echo plugin on BlackBerry.
+If you haven't read the top-level guide about the JavaScript part of
+the plugin, it would be best if you read that first and then this
+guide. In addition, please download the [Cordova Blackberry
+repo](https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry-webworks.git;a=summary).
+
+The Cordova-BlackBerry project allows you to deploy to BlackBerry
+devices such a the Torch and Bold, as well as the Playbook. There's a
+difference between deploying to normal BlackBerry handheld devices and
+the Playbook. They use two different code bases, so when you develop
+for one, you have to duplicate your efforts for the other! This guide
+focuses on the handheld devices rather than the tablet. (In the future,
+this guide should cover both platforms.)
+
+Continuing on from the previous guide, the Echo plugin essentially
+returns whatever message a user provides to the `window.echo`
+function.
+
+The Echo function:
+
+ window.echo = function(str, callback) {
+ cordova.exec(callback, function(err) {
+ callback('Nothing to echo.');
+ }, "Echo", "echo", [str]);
+ };
+
+## Modifying plugins.xml
+
+Your project's `www/plugins.xml` folder contains all of the necessary
+references to your Cordova project's plugins. Add an
+additional reference so that when `cordova.exec` is called, Cordova
+knows how to map the `Echo` argument of `cordova.exec` to the `Echo`
+class that we want to write natively:
+
+ <plugins>
+ ...
+ <plugin name="Echo" value="org.apache.cordova.echo.Echo"/>
+ ...
+ </plugins>
+
+## Adding Echo.java
+
+If you notice the structure of the value attribute, you'll see a
+defined path that leads to the Echo plugin. In the root folder of the
+Cordova BlackBerry WebWorks repo, look for a folder called framework.
+This folder contains all of the source code that runs natively on the
+BlackBerry. Navigate to `framework/ext/src/org/apache/cordova`. At
+this point, you'll see all of the plugin folders, inside of which is
+the source code. So add the folder echo to
+`framework/ext/src/org/apache/cordova/echo` and create a file called
+`Echo.java` at `framework/ext/src/org/apache/cordova/echo/Echo.java`.
+
+## Writing Echo.java
+
+The basic idea behind writing a plugin is to create a class that
+extends the Plugin class and have a method called `execute` to return
+a `PluginResult` class. Any call to `cordova.exec` passes in the
+action to execute within the class, as well as the arguments. In this
+case, "echo" is the action we want to execute within the class "Echo"
+and [str] are the arguments we are passing in.
+
+ package org.apache.cordova.echo;
+
+ import org.apache.cordova.api.Plugin;
+ import org.apache.cordova.api.PluginResult;
+ import org.apache.cordova.json4j.JSONArray;
+ import org.apache.cordova.json4j.JSONException;
+ import org.apache.cordova.json4j.JSONObject;
+ /**
+ * A simple plugin to demonstrate how to build a plugin for Blackberry
+ * Basically echos back the msg that a user calls to this plugin
+ */
+ public final class Echo extends Plugin {
+
+ public static final String echo = "echo";
+
+ public PluginResult execute(String action, JSONArray args, String callbackId) {
+ PluginResult result = new PluginResult(PluginResult.Status.INVALID_ACTION, "Echo: Invalid action:" + action);
+ if(action.equals(echo)){
+ try {
+ String theMsg = args.getString(0);
+ if(theMsg!= null || theMsg.length()>0){
+ result = new PluginResult(PluginResult.Status.OK, theMsg);
+ }else{
+ result = new PluginResult(PluginResult.Status.ERROR, "Nothing to echo.");
+ }
+ } catch (JSONException e) {
+ result = new PluginResult(PluginResult.Status.JSON_EXCEPTION, e.getMessage());
+ }
+ }
+
+ return result;
+ }
+
+ }
+
+So if we look at the code above, we can see that within the execute
+method, we are first looking for what actions are coming in. The Echo
+plugin has only one action, `echo`, so we will be only checking for
+that. If our plugin had more actions, it's simply a matter of adding
+more conditional tests to check for those actions.
+
+We are then going to grab the message coming in from the arguments
+which is supplied by the args parameter. We can grab the first
+argument by simply doing `String theMsg = args.getString(0);`.
+
+We will do some error checking and if the message looks okay, we will
+instantiate a new PluginResult with an ok status:
+`PluginResult.Status.OK` and return the message: `theMsg`. After this,
+we return the result which to be passed back to JavaScript to be fired
+in the success callback. If something fails, we can return various
+status exceptions like `PluginResult.Status.ERROR`,
+`PluginResult.Status.JSON_EXCEPTION`, or
+`PluginResult.Status.INVALID_ACTION`. When passed back, these types of
+results fire the fail callback in JavaScript.
+
+## Updating the .jar in your project's www folder
+
+The added `Echo.java` needs to be updated in your project. To build
+the `.jar` file, Navigate to the BlackBerry WebWorks repo's root
+directory and run the `ant` command:
+
+ ant update -Dproject.path="~/path_to_my_project"
+
+This builds a new `.jar` file in the `build/ext` directory. Copy the
+`build/ext/cordova.jar` file into your `project/www/ext` directory.
+
+If all goes well, that allows you to use the Echo plugin in
+BlackBerry.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/blackberry/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/upgrading.md b/docs/en/edge/guide/platforms/blackberry/upgrading.md
new file mode 100644
index 0000000..a50cddb
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry/upgrading.md
@@ -0,0 +1,311 @@
+---
+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 document describes the process of upgrading Cordova projects to the latest released version
+
+## Upgrading 2.8.0 projects to 2.9.0 ##
+
+### BlackBerry10 ###
+
+1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.9.0)
+2. **Quit any running IDE's** Eclipse, Momentics and the lik
+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 Command-line Tools. This becomes the home of your updated project.
+5. **Copy** your projects source from the old project's /www folder to the new project's /www folder
+6. **Update** the Cordova script reference in your **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 folder location** on your hard drive (say to ~/Cordova-2.9.0)
+2. **Quit any running IDE's** 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 Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova.js** file from the new project into your **www** folder, and delete your **www/cordova.js** file
+6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
+8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
+9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
+
+## Upgrading 2.7.0 projects to 2.8.0 ##
+
+### BlackBerry10 ###
+
+BlackBerry10 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 folder location** on your hard drive (say to ~/Cordova-2.8.0)
+2. **Quit any running IDE's** 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 Command-line Tools. This becomes the home of your updated project.
+5. **Copy** your projects source from the old project's /www folder to the new project's /www folder
+6. **Update** the Cordova script reference in your **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 folder location** on your hard drive (say to ~/Cordova-2.8.0)
+2. **Quit any running IDE's** 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 Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova.js** file from the new project into your **www** folder, and delete your **www/cordova.js** file
+6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
+8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
+9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
+
+## Upgrading 2.6.0 projects to 2.7.0 ##
+
+1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.7.0)
+2. **Quit any running IDE's** 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 Command-line Tools. You need the assets from this new project.
+5. **Copy** the **www/cordova-2.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.6.0.js** file
+6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
+8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
+9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
+
+## Upgrade to 2.6.0 from 2.5.0 ##
+
+Updating the PhoneGap download folder:
+
+It is recommended that you download a fresh copy of the entire folder.
+
+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’ folder
+2. Update the ‘ext’, ‘ext-air’, and ‘ext-qnx’ in the ‘Phonegap-2.6.0/lib/blackberry/framework’ folder
+3. Update the ‘build.xml’ file in the ‘Phonegap-2.6.0/lib/blackberry’ folder
+4. Update the the ‘Phonegap-2.6.0/lib/blackberry/bin’ folder
+5. Update the ‘VERSION’ file in the ‘Phonegap-2.6.0/lib/blackberry’ folder
+
+Updating the example/ folder or migrating an existing project:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Update the contents of the `ext-qnx/` folder.
+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 folder:
+
+It is recommended that you download a fresh copy of the entire folder.
+
+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’ folder
+2. Update the ‘ext’, ‘ext-air’, and ‘ext-qnx’ in the ‘Phonegap-2.5.0/lib/blackberry/framework’ folder
+3. Update the ‘build.xml’ file in the ‘Phonegap-2.5.0/lib/blackberry’ folder
+4. Update the the ‘Phonegap-2.5.0/lib/blackberry/bin’ folder
+5. Update the ‘VERSION’ file in the ‘Phonegap-2.5.0/lib/blackberry’ folder
+
+Updating the example/ folder or migrating an existing project:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Update the contents of the `ext-qnx/` folder.
+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 folder:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Copy the new `cordova-2.4.0.js` into your project.
+ - If playbook, then update the .js file in the `playbook/` folder.
+ - If BlackBerry10, then update the .js file in the `qnx/` folder.
+5. Update your HTML to use the new `cordova-2.4.0.js` file.
+
+
+Updating the sample folder (ie, updating using the ant tools):
+
+1. Open the `sample/lib/` folder.
+2. Update the .jar file in the `cordova.2.3.0/ext/` folder.
+3. Update the contents of the `cordova.2.3.0/ext-air/` folder.
+4. Update the contents of the `cordova.2.3.0/ext-qnx/` folder.
+5. Update the .js file in the `cordova.2.3.0/javascript/` folder.
+6. Open the `sample/lib/` folder and rename the `cordova.2.3.0/` folder to `cordova.2.4.0/`.
+7. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
+8. Open the `www/` folder 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` folder:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Copy the new `cordova-2.3.0.js` into your project.
+ - If playbook, then update the .js file in the `playbook/` folder.
+ - If BlackBerry10, then update the .js file in the `qnx/` folder.
+5. Update your HTML to use the new `cordova-2.3.0.js` file.
+
+
+Updating the sample folder (ie, updating using the ant tools):
+
+1. Open the `sample/lib/` folder.
+2. Update the .jar file in the `cordova.2.2.0/ext/` folder.
+3. Update the contents of the `cordova.2.2.0/ext-air/` folder.
+4. Update the contents of the `cordova.2.2.0/ext-qnx/` folder.
+5. Update the .js file in the `cordova.2.2.0/javascript/` folder.
+6. Open the `sample/lib/` folder and rename the `cordova.2.2.0/` folder to `cordova.2.3.0/`.
+7. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
+8. Open the `www/` folder 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 folder:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Copy the new `cordova-2.2.0.js` into your project.
+ - If playbook, then update the .js file in the `playbook/` folder.
+ - If BlackBerry10, then update the .js file in the `qnx/` folder.
+5. Update your HTML to use the new `cordova-2.2.0.js` file.
+
+
+Updating the sample folder (ie, updating using the ant tools):
+
+1. Open the `sample/lib/` folder.
+2. Update the .jar file in the `cordova.2.1.0/ext/` folder.
+3. Update the contents of the `cordova.2.1.0/ext-air/` folder.
+4. Update the contents of the `cordova.2.1.0/ext-qnx/` folder.
+5. Update the .js file in the `cordova.2.1.0/javascript/` folder.
+6. Open the `sample/lib/` folder and rename the `cordova.2.1.0/` folder to `cordova.2.2.0/`.
+7. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
+8. Open the `www/` folder 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 folder:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Copy the new `cordova-2.1.0.js` into your project.
+ - If playbook, then update the .js file in the `playbook/` folder.
+5. Update your HTML to use the new `cordova-2.1.0.js` file.
+
+
+Updating the sample folder (ie, updating using the ant tools):
+
+1. Open the `sample/lib/` folder.
+2. Update the .jar file in the `cordova.2.0.0/ext/` folder.
+3. Update the contents of the `cordova.2.0.0/ext-air/` folder.
+4. Update the .js file in the `cordova.2.0.0/javascript/` folder.
+5. Open the `sample/lib/` folder and rename the `cordova.2.0.0/` folder to `cordova.2.1.0/`.
+6. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
+7. Open the `www/` folder 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` folder:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Copy the new `cordova-2.0.0.js` into your project.
+ - If playbook, then update the .js file in the `playbook/` folder.
+5. Update your HTML to use the new `cordova-2.0.0.js` file.
+6. Update your `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 folder (ie, updating using the ant tools):
+
+1. Open the `sample/lib/` folder.
+2. Update the .jar file in the `cordova.1.9.0/ext/` folder.
+3. Update the contents of the `cordova.1.9.0/ext-air/` folder.
+4. Update the .js file in the `cordova.1.9.0/javascript/` folder.
+5. Open the `sample/lib/` folder and rename the `cordova.1.9.0/` folder to `cordova.2.0.0/`.
+6. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
+7. Open the `www/` folder and update your HTML to use the new `cordova-2.0.0.js` file.
+8. Open the `www/` folder 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` folder:
+
+1. Open your `www/` folder, which contains your app.
+2. Remove and update the .jar file in the `ext/` folder.
+3. Update the contents of the `ext-air/` folder.
+4. Copy the new `cordova-1.8.0.js` into your project.
+ - If playbook, then update the .js file in the `playbook/` folder.
+5. Update your HTML to use the new `cordova-1.8.0.js` file.
+6. Update your `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 folder (ie, updating using the ant tools):
+
+1. Open the `sample/lib/` folder.
+2. Update the .jar file in the `cordova.1.7.0/ext/` folder.
+3. Update the contents of the `cordova.1.7.0/ext-air/` folder.
+4. Update the .js file in the `cordova.1.7.0/javascript/` folder.
+5. Open the `sample/lib/` folder and rename the `cordova.1.7.0/` folder to `cordova.1.8.0/`.
+6. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
+7. Open the `www/` folder and update your HTML to use the new `cordova-1.8.0.js` file.
+8. Open the `www/` folder 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"/>
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/blackberry10/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry10/plugin.md b/docs/en/edge/guide/platforms/blackberry10/plugin.md
new file mode 100644
index 0000000..5eb1401
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry10/plugin.md
@@ -0,0 +1,191 @@
+---
+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 Plugins
+
+This is a continuation of the Plugin Development Guide for Cordova. Once you have reviewed that content, now let's look at things we need to have the Echo plugin for the BlackBerry 10 platform. Recall that the Echo plugin basically returns whatever string a user provides to the `window.echo` function:
+
+ window.echo = function(str, callback) {
+ cordova.exec(callback, function(err) {
+ callback('Nothing to echo.');
+ }, "Echo", "echo", [str]);
+ };
+
+A native BlackBerry 10 plugin for Cordova contains JavaScript code and may also contain native code. The Echo plugin example demonstrates how to invoke native functionality from JavaScript. The native and JavaScript code communicate with each other through a framework provided by JNEXT. Every plugin must also include a plugin.xml file.
+
+
+## Creating the native part of your plugin ##
+
+To create the native portion of your plugin, open the BlackBerry 10 NDK IDE and select File > New > BlackBerry Project > Native Extension > BlackBerry WebWorks. Enter your desired project name / location and click finish.
+
+The project created by the IDE contains sample code for a memory plugin. You may replace or modify these files to include your own functionality.
+
+- ***name*_js.hpp** - C++ header for the JNEXT code.
+- ***name*_js.cpp** - C++ code for JNEXT.
+
+The native interface for the JNEXT extension can be viewed in the plugin header file located in the public folder of your project. It also contains constants and utility functions that can be used in your native code. Your plugin must be derived from JSExt which is defined in plugin.h. That is, you must implement the following class:
+
+ class JSExt
+ {
+ public:
+ virtual ~JSExt() {};
+ virtual string InvokeMethod( const string& strCommand ) = 0;
+ virtual bool CanDelete( void ) = 0;
+ private:
+ std::string m_id;
+ };
+
+Therefore, your extension should include the plugin.h header file. In the Echo example, you use JSExt as follows in the echo_js.hpp file:
+
+ #include "../public/plugin.h"
+ #include <string>
+
+ #ifndef ECHO_JS_H_
+ #define ECHO_JS_H_
+
+ class Echo : public JSExt
+ {
+ public:
+ explicit Echo(const std::string& id);
+ virtual ~Echo();
+ virtual std::string InvokeMethod(const std::string& command);
+ virtual bool CanDelete();
+ private:
+ std::string m_id;
+ };
+
+ #endif // ECHO_JS_H_
+
+The `m_id` is an attribute that contains the JNEXT id for this object. The id is passed to the class as an argument to the constructor. It is needed to trigger events on the JavaScript side from native.
+The CanDelete method is used by JNEXT to determine whether your native object can be deleted.
+The InvokeMethod function is called as a result from a request from JavaScript to invoke a method of this particular object. The only argument to this function is a string passed from JavaScript that this method should parse in order to determine which method of the native object should be executed.
+Now we implement these functions in echo_js.cpp. For the Echo example, we implement InvokeMethod function as follows:
+
+ string Echo::InvokeMethod(const string& command) {
+
+ //parse command and args from string
+ int index = command.find_first_of(" ");
+ string strCommand = command.substr(0, index);
+ string strValue = command.substr(index + 1, command.length());
+
+ // Determine which function should be executed
+ if (strCommand == "echo") {
+ return strValue;
+ } else {
+ return "Unsupported Method";
+ }
+ }
+
+Your native plugin must also implement the following callback functions:
+
+- `extern char* onGetObjList( void );`
+- `extern JSExt* onCreateObject( const string& strClassName, const string& strObjId );`
+
+The `onGetObjList` function returns a comma separated list of classes supported by JNEXT. JNEXT uses this function to determine the set of classes that JNEXT can instantiate. In our Echo plugin, we have the following in `echo_js.cpp`:
+
+ char* onGetObjList() {
+ static char name[] = "Echo";
+ return name;
+ }
+
+The `onCreateObject ` function takes two parameters. The first parameter is the name of the class requested to be created from the JavaScript side. Valid names are those that are returned in `onGetObjList`. The second parameter is the unique object id for the class. This method returns a pointer to the created plugin object. In our Echo plugin, we have the following in `echo_js.cpp`:
+
+ JSExt* onCreateObject(const string& className, const string& id) {
+ if (className == "Echo") {
+ return new Echo(id);
+ }
+ return NULL;
+ }
+
+##Creating the JavaScript part of your plugin##
+
+The JavaScript portion of your plugin must contain the following files:
+
+- **client.js** – This is considered the client side and contains the API that a Cordova application can call. The API in client.js calls makes calls to index.js. The API in client.js also connects callback functions to the events that fire the callbacks.
+
+- **index.js** – Cordova loads index.js and makes it accessible through the cordova.exec bridge. The client.js file makes calls to the API in the index.js file, which in turn makes call to JNEXT to communicate with the native side.
+
+The client and server side (client.js and index.js) interacts through the `Cordova.exec `function. So, in client.js you invoke the exec function and provide the necessary arguments. In the Echo plugin, we have the following in the client.js file:
+
+ var service = "org.apache.cordova.blackberry.echo",
+ exec = cordova.require("cordova/exec");
+
+ module.exports = {
+ echo: function (data, success, fail) {
+ exec(success, fail, service, "echo", { data: data });
+ }
+ };
+
+Now, index.js interacts with the native side using JNEXT. So you attach a constructor function named Echo to JNEXT. Within the constructor you perform the following key operations using the init function:
+
+- Specify the required module exported by the native side. The name of the required module must match the name of a shared library file (.so file).
+
+`JNEXT.require("libecho")`
+
+- Create an object by using an acquired module and save the ID that's returned by the call.
+self.m_id = JNEXT.createObject("libecho.Echo");
+When your application calls the echo function in client.js, that call in turn calls the echo function in index.js, where the PluginResult object sends a response (data) back to client.js. Since the args argument passed into the functions was converted by JSON.stringfy() and encoded as a URIcomponent, you must call the following:
+
+`data = JSON.parse(decodeURIComponent(args.data));`
+
+You can now send the data back. Let’s put it all together:
+
+ module.exports = {
+
+ echo: function (success, fail, args, env) {
+
+ var result = new PluginResult(args, env),
+ data = JSON.parse(decodeURIComponent(args.data)),
+ response = echo.getInstance().echo(data);
+ result.ok(response, false);
+ }
+ };
+
+## Architecture of the plugin ##
+
+You can place the artifacts of the plugin, which includes the plugin.xml file, the source files (JavaScript, C++), and the binary files (.so) within any directory structure, as long as you correctly specify the file locations in the plugin.xml file. Below we show a typical structure that you can follow:
+
+***your_project_folder*** (>plugin.xml)
+
+- **www** (>client.js)
+- **src**
+ - **blackberry10** (>index.js, **native** >*.cpp, *.hpp)
+ - **device** (>*biary file* *.so)
+ - **simulator** (>*binary file* *.so)
+
+(The list shows the hierarchical relationship among the top level folders. The parenthesis shows the contents of a given folder. All folder names appear in bold text. File names are preceded by the '>' sign.)
+
+## Contents of the plugin.xml file##
+The plugin.xml file contains the namespace of the extension and other metadata. Define the namespace and specify other metadata for the Echo plugin as follows:
+
+ <plugin xmlns="http://www.phonegap.com/ns/plugins/1.0"
+ id="org.apache.cordova.blackberry.echo"
+ version="1.0.0">
+ <js-module src="www/client.js">
+ <merges target="navigator" />
+ </js-module>
+ <platform name="blackberry10">
+ <source-file src="src/blackberry10/index.js" />
+ <lib-file src="src/blackberry10/native/device/libecho.so" arch="device" />
+ <lib-file src="src/blackberry10/native/simulator/libecho.so" arch="simulator" />
+ <config-file target="www/config.xml" parent="/widget">
+ <feature name="org.apache.cordova.blackberry.echo" value="org.apache.cordova.blackberry.echo" />
+ </config-file>
+ </platform>
+ </plugin>
[13/20] [CB-3827] move platform-specific files within platforms dir;
rename dirs within platforms
Posted by mw...@apache.org.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/windows-phone-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-phone-8/index.md b/docs/en/edge/guide/platforms/windows-phone-8/index.md
deleted file mode 100644
index 85a02ae..0000000
--- a/docs/en/edge/guide/platforms/windows-phone-8/index.md
+++ /dev/null
@@ -1,135 +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.
----
-
-Windows Phone 8 Platform Guide
-==================================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-__NOTE:__ Applications built with Apache Cordova for Windows Phone 8 run only on Windows Phone 8 devices. If you want to target both 7.5 'and' 8 devices, then use Apache Cordova for Windows Phone 7, which does not have all the advanced features included in IE10, but implements the same APIs.
-
-1. System Requirements
----------------
-
-- Operating System:
- - Windows 8 or Windows 8 Pro
- - The 64-bit version (x64) of Windows is required for the SDK.
- - The Pro version is recommended so you can run a device emulator.
-
-- Hardware:
- - 6.5 GB of free hard disk space
- - 4 GB RAM
- - 64-bit (x64) CPU
-
-- Windows Phone 8 Emulator
- - The phone emulator uses Hyper-V, so this list includes those pre-requisites.
- - Windows 8 Pro 64-bit edition or greater
- - Requires a processor that supports virtualization and [Second Level Address Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation)
- - See the [list of Intel processors that support VT-x (virtualization) and EPT (SLAT)](http://ark.intel.com/Products/VirtualizationTechnology)
- - Enable the virtualization capability (i.e., VT-x on Intel) in your BIOS settings, as usually this is disabled by default.
-
-- SDK + IDE ( Visual Studio )
- - Visual Studio 2012 Professional, Premium, or Ultimate. Note that Visual Studio Express for Windows Phone (included in the SDK) is not recommended because you can not build the template (see below) with VS Express, as it does not have the __Export Template__ functionality, which is only in VS Pro or higher.
-
-- Register and pay for a [Windows Phone Dev Center](http://dev.windowsphone.com/en-us/publish) account if you want to install your app on a real device and/or submit it to Market Place.
-
-__NOTE:__ Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for [Windows Phone on a Mac](http://aka.ms/BuildaWP8apponaMac).
-
-2. Install SDK + Cordova
-----------------------------
-
-- Download and install [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
-- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-phone-8` subfolder.
-- Copy the file CordovaWP8_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
-
-2.1. Building the template
------------------------------
-
-__NOTE:__ this step may not be required. If the lib\windows-phone directory already contains a file CordovaWP8_x_x_x.zip then you may skip this step.
-
-In order to simplify the development process, Cordova comes with a Visual Studio template that allows creating a Cordova application rapidly. This template can be modified if needed and the below steps indicate how to proceed if you want to modify and re-generate the template.
-
-- Open the `lib\windows-phone\templates\standalone\CordovaSolution.sln` file in Visual Studio Express for Windows Phone.
-- Select __Export Template...__ from the __File__ menu.
-- Choose template type __Project template__
-- Give the exported template a name, such as `CordovaStarter-2.1.0`, which produces a `CordovaStarter-2.1.0.zip` archive.
-- Optionally, you may add a description, icon image, and preview image. These display in Visual Studio's __New Project__ dialog.
-- __NOTE:__ If you select __Automatically import the template...__, then you don't need to copy the `.zip` file over as outlined in step 2.
-- Press __Finish__
-
-2.2 About the different templates
----------------------------------
-
-Apache Cordova for Windows Phone 8 only supports the standalone template.
-
-The 'Stand-Alone' template includes _all_ the source code for Apache
-Cordova. This project is easier to fine-tune to use just the features
-you need, thereby working around the permissions issues of the 'Full'
-template, however this type of project is more difficult to update, as
-you update individual files within your project and manage any
-dependancies yourself. In order to exclude an unused API, simply
-right-click-select the __Command__ class file in Visual Studio and
-choose __do not include in project__.
-
-3. Set up New Project
---------------------
-
-- Open Visual Studio Express for Windows Phone and choose **New Project**.
-- Select **CordovaWP8**. (The version number is displayed in the template description.)
-- Give the project a name, and select __OK__.
-
-
-
-4. Review the project structure
--------------------------------
-
-- The 'www' folder contains your Cordova html/js/css and any other resources included in your app.
-- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
-- Note: This screen capture was from the cordova-2.3.0 download, your listing will vary based on the actual version installed.
-
-
-
-5. Build and Deploy to Emulator
--------------------------------
-
-- Make sure **Windows Phone Emulator** is selected in the main drop-down menu.
-- Press the green **play** button next to the drop-down menu to start debugging, or type __F5__.
-
-
-
-6. Build your project for the device
-------------------------------------
-
-In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 8.
-
-- Make sure your phone is connected, and the screen is unlocked.
-- In Visual Studio, select 'Device' from the top drop-down menu.
-- Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
-
-
-
-Done!
------
-
-Further Reading
--------
-
-For more details on the specific differences between IE10 and WebKit browsers, and how to support both MS has a helpful [guide here](http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx)
-
-[register-url]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/windows-phone-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-phone-8/tools.md b/docs/en/edge/guide/platforms/windows-phone-8/tools.md
deleted file mode 100644
index df821e2..0000000
--- a/docs/en/edge/guide/platforms/windows-phone-8/tools.md
+++ /dev/null
@@ -1,77 +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.
----
-
-# Windows Phone Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-## Windows Phone
-
-The Windows Phone command-line tools support creating, building, and
-running new projects. Commands must be run from a cmd or powershell
-prompt.
-
-The WP8 repo now includes code for building both WP7 + WP8 apps. The
-repo has subfolders for each: wp7/ and wp8/
-
-## 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 Windows Phone 7 and 8:
-
- $ C:\path\to\cordova-wp8\wp7\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
- $ C:\path\to\cordova-wp8\wp8\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
-
-## Building your project (cleans then builds)
-
-* Debug
-
- $ C:\path\to\my_new_project\cordova\build --debug
-
-* Release
-
- $ C:\path\to\my_new_project\cordova\build --release
-
-## Running your application
-
-Run the 'run' command with the following *optional* parameters
-
-* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
-* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
-
- $ C:\path\to\my_new_project\cordova\run [Target] [Build]
-
-By default the `run` command will look for a connected device, if no
-device is found it will look for any started emulators. If you have
-multiple emulators, you can specify a target ID.
-
-## Cleaning
-
- $ C:\path\to\my_new_project\cordova\clean
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp7/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp7/config.md b/docs/en/edge/guide/platforms/wp7/config.md
new file mode 100644
index 0000000..23c8304
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp7/config.md
@@ -0,0 +1,25 @@
+<!--
+#
+# 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.
+#
+-->
+
+Windows Phone 7 Configuration
+===================================
+
+Windows Phone 7 does not currently have any additional configurable features.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp7/index.md b/docs/en/edge/guide/platforms/wp7/index.md
new file mode 100644
index 0000000..a227130
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp7/index.md
@@ -0,0 +1,95 @@
+---
+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.
+---
+
+Windows Phone 7 Platform Guide
+==================================
+
+## Requirements and Support
+
+Requires Windows 7, Windows 8 or Windows Vista with SP2. Running
+Windows as a virtual machine does not work well, so Mac users should
+set up a Bootcamp partition to run Windows 7 or Vista.
+
+To install the app onto a device or submit it to the market place, you
+need to become an
+[App Hub member](http://create.msdn.com/en-US/home/membership).
+
+Developers should use the the `cordova` utility in conjunction with
+the Windows Phone SDK. Before installing it on Windows, open a
+command line and type `git` to make sure it is installed. If not,
+download it from [mysysgit.github.io](http://mysysgit.github.io). When
+prompted to configure your PATH, choose the option: __Run Git and
+included Unix tools from the Windows Command Prompt__. Once git is
+available, follow the instructions in The Cordova Command-line
+Interface for information how to install it, add projects, then build
+and deploy a project.
+
+## Install the SDK
+
+Download and install the
+[Windows Phone SDK](http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27570/)
+
+## Open a Project in the SDK
+
+After installing the `cordova` utility, use the following to create a
+new project, then add and build the Windows Phone 7 project.
+
+ $ cordova create hello com.example.hello "Hello World"
+ $ cd hello
+ $ cordova platform add wp7
+ $ cordova build
+
+Open Visual Studio and choose __Open Project__. Navigate to the
+`hello/platforms/wp7` directory and choose the `Hello_World.sln` file.
+The SDK displays the directory's contents:
+
+
+
+At this point you can modify the app within the SDK, but running the
+`build` or `prepare` commands again wipes out local changes. If Visual
+Studio is open, it alerts you about modified files and offers you the
+option to reload them. See The Cordova Command-line Interface for
+more information.
+
+## Deploy to Emulator
+
+Within the SDK, select the __Windows Phone Emulator__ target from the
+popup menu in the main menu bar, and press the green button to run the
+emulator:
+
+
+
+The app displays on the emulator's home screen as it would on a real
+device:
+
+
+
+## Deploy to Device
+
+To test your application on a device, the device must be registered.
+MSDN provides
+[documentation][http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx]
+to help deploy and test your Windows Phone.
+
+Once registered, you need to make sure the phone is connected via USB
+with its screen unlocked. In Visual Studio, choose the __Windows Phone
+Device__ target and press the green button to run it:
+
+
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp8/config.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/config.md b/docs/en/edge/guide/platforms/wp8/config.md
new file mode 100644
index 0000000..de0e54b
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp8/config.md
@@ -0,0 +1,25 @@
+<!--
+#
+# 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.
+#
+-->
+
+Windows Phone 8 Configuration
+===================================
+
+Windows Phone 8 does not currently have any additional configurable features.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/index.md b/docs/en/edge/guide/platforms/wp8/index.md
new file mode 100644
index 0000000..85a02ae
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp8/index.md
@@ -0,0 +1,135 @@
+---
+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.
+---
+
+Windows Phone 8 Platform Guide
+==================================
+
+This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
+
+__NOTE:__ Applications built with Apache Cordova for Windows Phone 8 run only on Windows Phone 8 devices. If you want to target both 7.5 'and' 8 devices, then use Apache Cordova for Windows Phone 7, which does not have all the advanced features included in IE10, but implements the same APIs.
+
+1. System Requirements
+---------------
+
+- Operating System:
+ - Windows 8 or Windows 8 Pro
+ - The 64-bit version (x64) of Windows is required for the SDK.
+ - The Pro version is recommended so you can run a device emulator.
+
+- Hardware:
+ - 6.5 GB of free hard disk space
+ - 4 GB RAM
+ - 64-bit (x64) CPU
+
+- Windows Phone 8 Emulator
+ - The phone emulator uses Hyper-V, so this list includes those pre-requisites.
+ - Windows 8 Pro 64-bit edition or greater
+ - Requires a processor that supports virtualization and [Second Level Address Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation)
+ - See the [list of Intel processors that support VT-x (virtualization) and EPT (SLAT)](http://ark.intel.com/Products/VirtualizationTechnology)
+ - Enable the virtualization capability (i.e., VT-x on Intel) in your BIOS settings, as usually this is disabled by default.
+
+- SDK + IDE ( Visual Studio )
+ - Visual Studio 2012 Professional, Premium, or Ultimate. Note that Visual Studio Express for Windows Phone (included in the SDK) is not recommended because you can not build the template (see below) with VS Express, as it does not have the __Export Template__ functionality, which is only in VS Pro or higher.
+
+- Register and pay for a [Windows Phone Dev Center](http://dev.windowsphone.com/en-us/publish) account if you want to install your app on a real device and/or submit it to Market Place.
+
+__NOTE:__ Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for [Windows Phone on a Mac](http://aka.ms/BuildaWP8apponaMac).
+
+2. Install SDK + Cordova
+----------------------------
+
+- Download and install [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
+- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-phone-8` subfolder.
+- Copy the file CordovaWP8_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
+
+2.1. Building the template
+-----------------------------
+
+__NOTE:__ this step may not be required. If the lib\windows-phone directory already contains a file CordovaWP8_x_x_x.zip then you may skip this step.
+
+In order to simplify the development process, Cordova comes with a Visual Studio template that allows creating a Cordova application rapidly. This template can be modified if needed and the below steps indicate how to proceed if you want to modify and re-generate the template.
+
+- Open the `lib\windows-phone\templates\standalone\CordovaSolution.sln` file in Visual Studio Express for Windows Phone.
+- Select __Export Template...__ from the __File__ menu.
+- Choose template type __Project template__
+- Give the exported template a name, such as `CordovaStarter-2.1.0`, which produces a `CordovaStarter-2.1.0.zip` archive.
+- Optionally, you may add a description, icon image, and preview image. These display in Visual Studio's __New Project__ dialog.
+- __NOTE:__ If you select __Automatically import the template...__, then you don't need to copy the `.zip` file over as outlined in step 2.
+- Press __Finish__
+
+2.2 About the different templates
+---------------------------------
+
+Apache Cordova for Windows Phone 8 only supports the standalone template.
+
+The 'Stand-Alone' template includes _all_ the source code for Apache
+Cordova. This project is easier to fine-tune to use just the features
+you need, thereby working around the permissions issues of the 'Full'
+template, however this type of project is more difficult to update, as
+you update individual files within your project and manage any
+dependancies yourself. In order to exclude an unused API, simply
+right-click-select the __Command__ class file in Visual Studio and
+choose __do not include in project__.
+
+3. Set up New Project
+--------------------
+
+- Open Visual Studio Express for Windows Phone and choose **New Project**.
+- Select **CordovaWP8**. (The version number is displayed in the template description.)
+- Give the project a name, and select __OK__.
+
+
+
+4. Review the project structure
+-------------------------------
+
+- The 'www' folder contains your Cordova html/js/css and any other resources included in your app.
+- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
+- Note: This screen capture was from the cordova-2.3.0 download, your listing will vary based on the actual version installed.
+
+
+
+5. Build and Deploy to Emulator
+-------------------------------
+
+- Make sure **Windows Phone Emulator** is selected in the main drop-down menu.
+- Press the green **play** button next to the drop-down menu to start debugging, or type __F5__.
+
+
+
+6. Build your project for the device
+------------------------------------
+
+In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 8.
+
+- Make sure your phone is connected, and the screen is unlocked.
+- In Visual Studio, select 'Device' from the top drop-down menu.
+- Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
+
+
+
+Done!
+-----
+
+Further Reading
+-------
+
+For more details on the specific differences between IE10 and WebKit browsers, and how to support both MS has a helpful [guide here](http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx)
+
+[register-url]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp8/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/plugin.md b/docs/en/edge/guide/platforms/wp8/plugin.md
new file mode 100644
index 0000000..ed89361
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp8/plugin.md
@@ -0,0 +1,194 @@
+---
+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.
+---
+
+Windows Phone Plugins
+====================================
+
+Writing a plugin for Cordova on Windows Phone requires a basic understanding of
+the architecture of Cordova. Cordova-WP7 consists of a WebBrowser which hosts the
+application JavaScript code and manages native API calls. There is a BaseCommand
+(`WP7CordovaClassLib.Cordova.Commands.BaseCommand`) class in C# which you can extend,
+and it comes with the majority of the 'plumbing' built for you already.
+
+1. Select your project, and right-click to choose __Add → New Item...__
+ - Preferably add it to the 'Plugins' folder, but it is up to you
+2. Select 'Class' and name it `Echo.cs`
+ - The name of this class must _exactly_ match what you call into `cordova.exec(win, fail, "Echo", ...)`
+3. Include the base classes implementation
+
+ using WPCordovaClassLib.Cordova;
+ using WPCordovaClassLib.Cordova.Commands;
+ using WPCordovaClassLib.Cordova.JSON;
+
+4. Extend your class from BaseCommand
+
+ public class Echo : BaseCommand
+ {
+ // ...
+ }
+
+5. Add a method that is callable from JS
+
+ public class Echo : BaseCommand
+ {
+ public void echo(string options)
+ {
+ // all JS callable plugin methods MUST have this signature!
+ // public, returning void, 1 argument that is a string
+ }
+ }
+
+Namespaces
+----------
+
+The default namespace for unqualified commands is:
+
+ namespace Cordova.Extension.Commands
+ {
+ // ...
+ }
+
+If you want to use your own namespace, you need to make a fully
+qualified call to `cordova.exec`. For example, if you want to define
+your C# class like this:
+
+ namespace com.mydomain.cordovaExtensions
+ {
+ public class Echo : BaseCommand
+ {
+ // ...
+ }
+ }
+
+Then, in JS you need to call `exec` like this:
+
+ cordova.exec(win, fail, "com.mydomain.cordovaExtensions.Echo", ...);
+
+Interpreting your arguments in C#
+----------------------------------
+
+The data received by your plugin method is a string value, but in actuality
+looking at our JavaScript code, we see our intention was to pass an array of strings.
+Looking back at our JS call to `cordova.exec`, we see we passed `[str]`:
+
+ cordova.exec(win, fail, "Echo", "echo", ["input string"]);
+
+If we inspect the options string passed in to our `Echo.echo` method,
+we see that the value is actually:
+
+ "[\"input string\"]"
+
+All JavaScript exec arguments are JSON encoded before being passed into C#.
+
+If we want to treat this as the string we were expecting, we need to decode it.
+We can use simple JSON deserialization.
+
+ string optVal = JsonHelper.Deserialize<string[]>(options)[0];
+ // optVal now has the value of "input string"
+
+Passing results from C# to JS
+-----------------------------
+
+The base class BaseCommand provides methods for passing data to your JS callback handlers.
+To simply signal that the command has succeeded, when no additional result info is needed,
+you can can simply call:
+
+ DispatchCommandResult(); // calls back with an empty plugin result, considered a success callback
+
+To pass data back, you need to call a different version of `DispatchCommandResult`:
+
+ DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "Everything went as planned, this is a result that is passed to the success handler."));
+
+To pass structured object data back to JS, it should be encoded as a JSON string:
+
+ DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "{result:\"super awesome!\"}"));
+
+If you need to signal that an error has occurred, you can call `DispatchCommandResult` with a `PluginResult` object:
+
+ DispatchCommandResult(new PluginResult(PluginResult.Status.ERROR, "Echo signaled an error"));
+
+Handling serialization errors in your plugin's C# method
+--------------------------------------------------------
+
+When interpreting your arguments, it is a good idea to use a try/catch block
+in case we have bad input. This is a pattern used throughout the Cordova C# code:
+
+ string optVal = null;
+
+ try
+ {
+ optVal = JsonHelper.Deserialize<string[]>(options)[0];
+ }
+ catch(Exception)
+ {
+ // simply catch the exception, we handle null values and exceptions together
+ }
+
+ if (optVal == null)
+ {
+ DispatchCommandResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION));
+ }
+ else
+ {
+ // ... continue on to do our work
+ }
+
+Advanced Plugin Functionality
+-----------------------------
+
+See other methods that you can override in:
+
+1. [BaseCommand.cs](https://github.com/apache/cordova-wp7/blob/master/templates/standalone/cordovalib/Commands/BaseCommand.cs)
+
+For example, you can hook into the 'pause' and 'resume' application events.
+
+### Debugging Plugins
+
+To debug the C# side, you can use Visual Studio's debugger, just set a break point
+at any of the methods exposed by your class.
+
+JavaScript is a little more difficult to debug on Windows Phone. You
+need to use `console.log` to output the state of your plugin, or
+inform yourself of errors.
+
+Common Pitfalls
+---------------
+
+- Be careful when deciding on the arguments you pass to native in your JavaScript
+ implementation. Most device platforms expect the args passed to cordova.exec
+ to be an array, but if you have different types of objects in this array, it
+ becomes difficult or impossible to deserialize.
+
+ cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", 54, {literal:'trouble'}]);
+
+ - This means that your C# code receives a difficult to decode string value, such as:
+
+ "[\"this is a string\", 54, { literal:'trouble' }]"
+
+ - Consider converting ALL parameters to strings before calling exec:
+
+ cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", "54", "{literal:'trouble'}"]) ;
+
+ string[] optValues = JsonHelper.Deserialize<string[]>(options);
+
+- It is usually a good idea to do parameter checking in your
+ JavaScript code, before you call `exec`. This allows you to re-use
+ more JavaScript code among your plug-in's various native
+ implementations.
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/tools.md b/docs/en/edge/guide/platforms/wp8/tools.md
new file mode 100644
index 0000000..df821e2
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp8/tools.md
@@ -0,0 +1,77 @@
+---
+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.
+---
+
+# Windows Phone Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## Windows Phone
+
+The Windows Phone command-line tools support creating, building, and
+running new projects. Commands must be run from a cmd or powershell
+prompt.
+
+The WP8 repo now includes code for building both WP7 + WP8 apps. The
+repo has subfolders for each: wp7/ and wp8/
+
+## 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 Windows Phone 7 and 8:
+
+ $ C:\path\to\cordova-wp8\wp7\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
+ $ C:\path\to\cordova-wp8\wp8\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
+
+## Building your project (cleans then builds)
+
+* Debug
+
+ $ C:\path\to\my_new_project\cordova\build --debug
+
+* Release
+
+ $ C:\path\to\my_new_project\cordova\build --release
+
+## Running your application
+
+Run the 'run' command with the following *optional* parameters
+
+* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
+* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
+
+ $ C:\path\to\my_new_project\cordova\run [Target] [Build]
+
+By default the `run` command will look for a connected device, if no
+device is found it will look for any started emulators. If you have
+multiple emulators, you can specify a target ID.
+
+## Cleaning
+
+ $ C:\path\to\my_new_project\cordova\clean
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/platforms/wp8/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/upgrading.md b/docs/en/edge/guide/platforms/wp8/upgrading.md
new file mode 100644
index 0000000..7d65b24
--- /dev/null
+++ b/docs/en/edge/guide/platforms/wp8/upgrading.md
@@ -0,0 +1,236 @@
+---
+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 Windows Phone
+===============================
+
+This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to both WP7 and WP8.
+
+## Upgrade to 2.8.0 from 2.9.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 or WP8 2.9.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update the name of cordova.js in the HTML tag if it's still using cordova-VERSION.js (should be just cordova.js).
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the .csproj file.
+6. Build and test.
+
+## Upgrade to 2.8.0 from 2.7.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 or WP8 2.8.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova.js file. ( note that there is no longer a version number in the name )
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.7.0 from 2.6.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 or WP8 2.7.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.7.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.6.0 from 2.5.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 or WP8 2.6.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.6.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.5.0 from 2.4.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 or WP8 2.5.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.5.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.4.0 from 2.3.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 or WP8 2.4.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.4.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.3.0 from 2.2.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 2.3.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.3.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.2.0 from 2.1.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 2.2.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.2.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 2.1.0 from 2.0.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 2.1.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.1.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+
+## Upgrade to 2.0.0 from 1.9.0 ##
+
+There have been considerable changes to the WP7 project structure in Apache Cordova 2.0.0 which make this upgrade a little more involved that the others. Essentially this is not an upgrade but creation of a new project and copy over of existing source files.
+
+### In Visual Studio's Solution Explorer window:
+1. Create a new Apache Cordova WP7 2.0 Project
+2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
+3. Update your HTML to use the new cordova-2.0.0.js file.
+4. Copy and overwrite any splash screen, or icon images.
+5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
+6. Build and test.
+
+## Upgrade to 1.9.0 from 1.8.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.9.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.9.0.js file.
+
+## Upgrade to 1.8.0 from 1.7.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.8.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.8.0.js file.
+
+## Upgrade to 1.7.0 from 1.6.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.7.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.7.0.js file.
+
+## Upgrade to 1.6.1 from 1.6.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.6.1.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.6.1.js file.
+
+## Upgrade to 1.6.0 from 1.5.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.6.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.6.0.js file.
+
+## Upgrade to 1.5.0 from 1.4.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.5.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.5.0.js file.
+
+## Upgrade to 1.4.0 from 1.3.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.4.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.4.0.js file.
+
+## Upgrade to 1.3.0 from 1.2.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.3.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.3.0.js file.
+
+## Upgrade to 1.2.0 from 1.1.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.2.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.2.0.js file.
+
+## Upgrade to 1.1.0 from 1.0.0 ##
+
+### In Visual Studio's Solution Explorer window:
+1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
+2. Remove the reference to WP7CordovaClassLib in the References folder.
+3. Right-Click on References and Select 'Add Reference'
+4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+ - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
+5. Copy the new cordova-1.1.0.js into your project ( be sure it is marked as Content )
+6. Update your HTML to use the new cordova-1.1.0.js file.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugin-development/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/android/index.md b/docs/en/edge/guide/plugin-development/android/index.md
deleted file mode 100644
index 39a79d7..0000000
--- a/docs/en/edge/guide/plugin-development/android/index.md
+++ /dev/null
@@ -1,192 +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
-
-Writing a plugin requires an understanding of the architecture of Cordova-Android. Cordova-Android consists
-of an Android WebView with hooks attached to it. These 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. A plugin must override one
-of the `execute` methods from `CordovaPlugin`.
-As best practice, the plugin should handle `pause` and `resume` events, and any message passing between plugins.
-Plugins with long-running requests, background activity such as media payback, listeners, or internal state should implement the `onReset()` method as well. This method is run when the `WebView` navigates to a new page or refreshes, which reloads the JavaScript.
-
-## Plugin Class Mapping
-
-The JavaScript portion of a plugin always 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,
-more or less boiling down to calling the `action` method on the
-`service` class, with the arguments passed in the `args` Array.
-
-Whether you distribute your plugin as Java file or as a JAR of its own, the plugin must be added to the `config.xml` file in your Cordova-Android application's `res/xml/` folder.
-
- <plugin name="<service_name>" value="<full_name_including_namespace>"/>
-
-The service name should match the one used in the JavaScript `exec`
-call, and the value is the Java classes full name, including the
-namespace. Otherwise the plugin may compile but still be unreachable
-by Cordova.
-
-## Writing an Android Java Plugin
-
-We have JavaScript to fire off a plugin request to the native side. We
-have the Android Java plugin mapped properly via the `config.xml` file.
-So what does the final Android Java Plugin class look like?
-
-What gets dispatched to the plugin via JavaScript's `exec` function gets
-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.
- }
-
-We compare the value of the `action` parameter, and dispatch the
-request off to a (private) method in the class, optionally passing
-some of the parameters to the method.
-
-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
-
-JavaScript in the WebView does *not* run on the UI thread. It runs on
-the WebCore thread. The `execute` method also runs on the WebCore thread.
-
-If you need to interact with the UI, you should use the following:
-
- @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;
- }
-
-If you do not need to run on the UI thread, but do not want to block the WebCore thread:
-
- @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
-
-We would add the following to our config.xml:
-
- <plugin name="Echo" value="org.apache.cordova.plugin.Echo" />
-
-Then we would add the following file to
-`src/org/apache/cordova/plugin/Echo.java` inside our Cordova-Android
-application:
-
- package org.apache.cordova.plugin;
-
- import org.apache.cordova.api.CordovaPlugin;
- import org.apache.cordova.api.PluginResult;
- 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.");
- }
- }
- }
-
-Let's take a look at the code. The necessary `imports` are at
-the top. Our class extends from `CordovaPlugin`. We override the
-execute() method in order to recieve messages from exec(). Our method
-first compares against `action`: this plugin only supports one action,
-the `echo` action. Any other action returns false, which results in an
-error of type `INVALID_ACTION`, which translates into an error
-callback invocation on the JavaScript side. Next, we grab the echo
-string using the `getString` method on our `args`, telling it we want
-to get the 0th parameter in the parameter array. We do a bit of
-parameter checking: make sure it is not `null`, and make sure it is
-not a zero-length string. If it is, we call `callbackContext.error()`
-(which, by now, you should know invokes the error callback). If all of
-those checks pass, then we call `callbackContext.success()` and pass
-in the `message` string we received as a parameter. This finally
-translates into a success callback invocation on the JavaScript
-side. It also passes the `message` parameter as a parameter into the
-JavaScript success callback function.
-
-## Debugging Plugins
-
-Eclipse can be used to debug an Android project, and the plugins can be debugged if the Java source is included in the project. Only the latest version of the Android Developer Tools is known to allow source code attachment to JAR dependencies, so this is not fully supported at this time.
-
-## Common Pitfalls
-
-* Plugins have access to a `CordovaInterface` object. This object has access to the Android `Activity` that is running 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` comes back to the application. This is important, since the
-`Intent`s system is how Android communicates between processes.
-* Plugins do not have direct access to the `Context` as they have in the past. The legacy `ctx` member is deprecated, and will be removed six months after 2.0 is released. All of `ctx` methods exist on the `Context`, so both `getContext()` and `getActivity()` are capable of returning the proper object required.
-
-## Use the Source
-
-One of the best ways to prepare yourself to write your own plugin is to
-[look over existing plugins](https://github.com/apache/cordova-android/tree/master/framework/src/org/apache/cordova).
-
-You should also read through the comments in [CordovaPlugin.java](https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/api/CordovaPlugin.java).
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugin-development/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/blackberry/index.md b/docs/en/edge/guide/plugin-development/blackberry/index.md
deleted file mode 100644
index ebdb780..0000000
--- a/docs/en/edge/guide/plugin-development/blackberry/index.md
+++ /dev/null
@@ -1,153 +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 Plugins
-=================================
-
-## How to make the Echo plugin on Blackberry
-
-This guide explores how to develop the Echo plugin on BlackBerry.
-If you haven't read the top-level guide about the JavaScript part of
-the plugin, it would be best if you read that first and then this
-guide. In addition, please download the [Cordova Blackberry
-repo](https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry-webworks.git;a=summary).
-
-The Cordova-BlackBerry project allows you to deploy to BlackBerry
-devices such a the Torch and Bold, as well as the Playbook. There's a
-difference between deploying to normal BlackBerry handheld devices and
-the Playbook. They use two different code bases, so when you develop
-for one, you have to duplicate your efforts for the other! This guide
-focuses on the handheld devices rather than the tablet. (In the future,
-this guide should cover both platforms.)
-
-Continuing on from the previous guide, the Echo plugin essentially
-returns whatever message a user provides to the `window.echo`
-function.
-
-The Echo function:
-
- window.echo = function(str, callback) {
- cordova.exec(callback, function(err) {
- callback('Nothing to echo.');
- }, "Echo", "echo", [str]);
- };
-
-## Modifying plugins.xml
-
-Your project's `www/plugins.xml` folder contains all of the necessary
-references to your Cordova project's plugins. Add an
-additional reference so that when `cordova.exec` is called, Cordova
-knows how to map the `Echo` argument of `cordova.exec` to the `Echo`
-class that we want to write natively:
-
- <plugins>
- ...
- <plugin name="Echo" value="org.apache.cordova.echo.Echo"/>
- ...
- </plugins>
-
-## Adding Echo.java
-
-If you notice the structure of the value attribute, you'll see a
-defined path that leads to the Echo plugin. In the root folder of the
-Cordova BlackBerry WebWorks repo, look for a folder called framework.
-This folder contains all of the source code that runs natively on the
-BlackBerry. Navigate to `framework/ext/src/org/apache/cordova`. At
-this point, you'll see all of the plugin folders, inside of which is
-the source code. So add the folder echo to
-`framework/ext/src/org/apache/cordova/echo` and create a file called
-`Echo.java` at `framework/ext/src/org/apache/cordova/echo/Echo.java`.
-
-## Writing Echo.java
-
-The basic idea behind writing a plugin is to create a class that
-extends the Plugin class and have a method called `execute` to return
-a `PluginResult` class. Any call to `cordova.exec` passes in the
-action to execute within the class, as well as the arguments. In this
-case, "echo" is the action we want to execute within the class "Echo"
-and [str] are the arguments we are passing in.
-
- package org.apache.cordova.echo;
-
- import org.apache.cordova.api.Plugin;
- import org.apache.cordova.api.PluginResult;
- import org.apache.cordova.json4j.JSONArray;
- import org.apache.cordova.json4j.JSONException;
- import org.apache.cordova.json4j.JSONObject;
- /**
- * A simple plugin to demonstrate how to build a plugin for Blackberry
- * Basically echos back the msg that a user calls to this plugin
- */
- public final class Echo extends Plugin {
-
- public static final String echo = "echo";
-
- public PluginResult execute(String action, JSONArray args, String callbackId) {
- PluginResult result = new PluginResult(PluginResult.Status.INVALID_ACTION, "Echo: Invalid action:" + action);
- if(action.equals(echo)){
- try {
- String theMsg = args.getString(0);
- if(theMsg!= null || theMsg.length()>0){
- result = new PluginResult(PluginResult.Status.OK, theMsg);
- }else{
- result = new PluginResult(PluginResult.Status.ERROR, "Nothing to echo.");
- }
- } catch (JSONException e) {
- result = new PluginResult(PluginResult.Status.JSON_EXCEPTION, e.getMessage());
- }
- }
-
- return result;
- }
-
- }
-
-So if we look at the code above, we can see that within the execute
-method, we are first looking for what actions are coming in. The Echo
-plugin has only one action, `echo`, so we will be only checking for
-that. If our plugin had more actions, it's simply a matter of adding
-more conditional tests to check for those actions.
-
-We are then going to grab the message coming in from the arguments
-which is supplied by the args parameter. We can grab the first
-argument by simply doing `String theMsg = args.getString(0);`.
-
-We will do some error checking and if the message looks okay, we will
-instantiate a new PluginResult with an ok status:
-`PluginResult.Status.OK` and return the message: `theMsg`. After this,
-we return the result which to be passed back to JavaScript to be fired
-in the success callback. If something fails, we can return various
-status exceptions like `PluginResult.Status.ERROR`,
-`PluginResult.Status.JSON_EXCEPTION`, or
-`PluginResult.Status.INVALID_ACTION`. When passed back, these types of
-results fire the fail callback in JavaScript.
-
-## Updating the .jar in your project's www folder
-
-The added `Echo.java` needs to be updated in your project. To build
-the `.jar` file, Navigate to the BlackBerry WebWorks repo's root
-directory and run the `ant` command:
-
- ant update -Dproject.path="~/path_to_my_project"
-
-This builds a new `.jar` file in the `build/ext` directory. Copy the
-`build/ext/cordova.jar` file into your `project/www/ext` directory.
-
-If all goes well, that allows you to use the Echo plugin in
-BlackBerry.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugin-development/blackberry10/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/blackberry10/index.md b/docs/en/edge/guide/plugin-development/blackberry10/index.md
deleted file mode 100644
index 5eb1401..0000000
--- a/docs/en/edge/guide/plugin-development/blackberry10/index.md
+++ /dev/null
@@ -1,191 +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 Plugins
-
-This is a continuation of the Plugin Development Guide for Cordova. Once you have reviewed that content, now let's look at things we need to have the Echo plugin for the BlackBerry 10 platform. Recall that the Echo plugin basically returns whatever string a user provides to the `window.echo` function:
-
- window.echo = function(str, callback) {
- cordova.exec(callback, function(err) {
- callback('Nothing to echo.');
- }, "Echo", "echo", [str]);
- };
-
-A native BlackBerry 10 plugin for Cordova contains JavaScript code and may also contain native code. The Echo plugin example demonstrates how to invoke native functionality from JavaScript. The native and JavaScript code communicate with each other through a framework provided by JNEXT. Every plugin must also include a plugin.xml file.
-
-
-## Creating the native part of your plugin ##
-
-To create the native portion of your plugin, open the BlackBerry 10 NDK IDE and select File > New > BlackBerry Project > Native Extension > BlackBerry WebWorks. Enter your desired project name / location and click finish.
-
-The project created by the IDE contains sample code for a memory plugin. You may replace or modify these files to include your own functionality.
-
-- ***name*_js.hpp** - C++ header for the JNEXT code.
-- ***name*_js.cpp** - C++ code for JNEXT.
-
-The native interface for the JNEXT extension can be viewed in the plugin header file located in the public folder of your project. It also contains constants and utility functions that can be used in your native code. Your plugin must be derived from JSExt which is defined in plugin.h. That is, you must implement the following class:
-
- class JSExt
- {
- public:
- virtual ~JSExt() {};
- virtual string InvokeMethod( const string& strCommand ) = 0;
- virtual bool CanDelete( void ) = 0;
- private:
- std::string m_id;
- };
-
-Therefore, your extension should include the plugin.h header file. In the Echo example, you use JSExt as follows in the echo_js.hpp file:
-
- #include "../public/plugin.h"
- #include <string>
-
- #ifndef ECHO_JS_H_
- #define ECHO_JS_H_
-
- class Echo : public JSExt
- {
- public:
- explicit Echo(const std::string& id);
- virtual ~Echo();
- virtual std::string InvokeMethod(const std::string& command);
- virtual bool CanDelete();
- private:
- std::string m_id;
- };
-
- #endif // ECHO_JS_H_
-
-The `m_id` is an attribute that contains the JNEXT id for this object. The id is passed to the class as an argument to the constructor. It is needed to trigger events on the JavaScript side from native.
-The CanDelete method is used by JNEXT to determine whether your native object can be deleted.
-The InvokeMethod function is called as a result from a request from JavaScript to invoke a method of this particular object. The only argument to this function is a string passed from JavaScript that this method should parse in order to determine which method of the native object should be executed.
-Now we implement these functions in echo_js.cpp. For the Echo example, we implement InvokeMethod function as follows:
-
- string Echo::InvokeMethod(const string& command) {
-
- //parse command and args from string
- int index = command.find_first_of(" ");
- string strCommand = command.substr(0, index);
- string strValue = command.substr(index + 1, command.length());
-
- // Determine which function should be executed
- if (strCommand == "echo") {
- return strValue;
- } else {
- return "Unsupported Method";
- }
- }
-
-Your native plugin must also implement the following callback functions:
-
-- `extern char* onGetObjList( void );`
-- `extern JSExt* onCreateObject( const string& strClassName, const string& strObjId );`
-
-The `onGetObjList` function returns a comma separated list of classes supported by JNEXT. JNEXT uses this function to determine the set of classes that JNEXT can instantiate. In our Echo plugin, we have the following in `echo_js.cpp`:
-
- char* onGetObjList() {
- static char name[] = "Echo";
- return name;
- }
-
-The `onCreateObject ` function takes two parameters. The first parameter is the name of the class requested to be created from the JavaScript side. Valid names are those that are returned in `onGetObjList`. The second parameter is the unique object id for the class. This method returns a pointer to the created plugin object. In our Echo plugin, we have the following in `echo_js.cpp`:
-
- JSExt* onCreateObject(const string& className, const string& id) {
- if (className == "Echo") {
- return new Echo(id);
- }
- return NULL;
- }
-
-##Creating the JavaScript part of your plugin##
-
-The JavaScript portion of your plugin must contain the following files:
-
-- **client.js** – This is considered the client side and contains the API that a Cordova application can call. The API in client.js calls makes calls to index.js. The API in client.js also connects callback functions to the events that fire the callbacks.
-
-- **index.js** – Cordova loads index.js and makes it accessible through the cordova.exec bridge. The client.js file makes calls to the API in the index.js file, which in turn makes call to JNEXT to communicate with the native side.
-
-The client and server side (client.js and index.js) interacts through the `Cordova.exec `function. So, in client.js you invoke the exec function and provide the necessary arguments. In the Echo plugin, we have the following in the client.js file:
-
- var service = "org.apache.cordova.blackberry.echo",
- exec = cordova.require("cordova/exec");
-
- module.exports = {
- echo: function (data, success, fail) {
- exec(success, fail, service, "echo", { data: data });
- }
- };
-
-Now, index.js interacts with the native side using JNEXT. So you attach a constructor function named Echo to JNEXT. Within the constructor you perform the following key operations using the init function:
-
-- Specify the required module exported by the native side. The name of the required module must match the name of a shared library file (.so file).
-
-`JNEXT.require("libecho")`
-
-- Create an object by using an acquired module and save the ID that's returned by the call.
-self.m_id = JNEXT.createObject("libecho.Echo");
-When your application calls the echo function in client.js, that call in turn calls the echo function in index.js, where the PluginResult object sends a response (data) back to client.js. Since the args argument passed into the functions was converted by JSON.stringfy() and encoded as a URIcomponent, you must call the following:
-
-`data = JSON.parse(decodeURIComponent(args.data));`
-
-You can now send the data back. Let’s put it all together:
-
- module.exports = {
-
- echo: function (success, fail, args, env) {
-
- var result = new PluginResult(args, env),
- data = JSON.parse(decodeURIComponent(args.data)),
- response = echo.getInstance().echo(data);
- result.ok(response, false);
- }
- };
-
-## Architecture of the plugin ##
-
-You can place the artifacts of the plugin, which includes the plugin.xml file, the source files (JavaScript, C++), and the binary files (.so) within any directory structure, as long as you correctly specify the file locations in the plugin.xml file. Below we show a typical structure that you can follow:
-
-***your_project_folder*** (>plugin.xml)
-
-- **www** (>client.js)
-- **src**
- - **blackberry10** (>index.js, **native** >*.cpp, *.hpp)
- - **device** (>*biary file* *.so)
- - **simulator** (>*binary file* *.so)
-
-(The list shows the hierarchical relationship among the top level folders. The parenthesis shows the contents of a given folder. All folder names appear in bold text. File names are preceded by the '>' sign.)
-
-## Contents of the plugin.xml file##
-The plugin.xml file contains the namespace of the extension and other metadata. Define the namespace and specify other metadata for the Echo plugin as follows:
-
- <plugin xmlns="http://www.phonegap.com/ns/plugins/1.0"
- id="org.apache.cordova.blackberry.echo"
- version="1.0.0">
- <js-module src="www/client.js">
- <merges target="navigator" />
- </js-module>
- <platform name="blackberry10">
- <source-file src="src/blackberry10/index.js" />
- <lib-file src="src/blackberry10/native/device/libecho.so" arch="device" />
- <lib-file src="src/blackberry10/native/simulator/libecho.so" arch="simulator" />
- <config-file target="www/config.xml" parent="/widget">
- <feature name="org.apache.cordova.blackberry.echo" value="org.apache.cordova.blackberry.echo" />
- </config-file>
- </platform>
- </plugin>
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugin-development/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/index.md b/docs/en/edge/guide/plugin-development/index.md
deleted file mode 100644
index e90c415..0000000
--- a/docs/en/edge/guide/plugin-development/index.md
+++ /dev/null
@@ -1,110 +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.
----
-
-# Plugin Development Guide
-
-A Cordova plugin bridges a bit of functionality between the WebView
-powering a Cordova application and the native platform the Cordova
-application is running on. Plugins are composed of a single JavaScript
-interface used across all platforms, and native implementations
-following platform-specific Plugin interfaces that the JavaScript
-calls into. All of the core Cordova APIs are implemented using this
-architecture.
-
-This guide steps the process of writing a simple Echo Plugin that
-passes a string from JavaScript and sends it into the native
-environment for the supported platforms. The native code then returns
-the same string back to the callbacks inside the plugin's JavaScript.
-
-This guide provides enough overview on which you can build to write
-more complex plugins.
-
-## JavaScript
-
-The entry point for any plugin is JavaScript. The reason developers use
-Cordova is so they can use and write JavaScript, not Objective-C,
-not Java, not C#. The JavaScript interface for your plugin is the
-front-facing and arguably most important part of your Cordova plugin.
-
-You can structure your plugin's JavaScript however you like. The one
-thing you _must_ use to communicate between the Cordova JavaScript
- and native environments is the `cordova.exec` function. Here is an example:
-
- cordova.exec(function(winParam) {}, function(error) {}, "service",
- "action", ["firstArgument", "secondArgument", 42,
- false]);
-
-The parameters are detailed below:
-
-1. `function(winParam) {}` - Success function callback. Assuming your
- `exec` call completes successfully, this function is invoked
- (optionally with any parameters you pass back to it).
-2. `function(error) {}` - Error function callback. If the operation does
- not complete successfully, this function is invoked (optionally
- with an error parameter).
-3. `"service"` - The service name to call into on the native side. This
- is mapped to a native class, about which more information is
- available in the native guides listed below.
-4. `"action"` - The action name to call into. This is picked up by the
- native class receiving the `exec` call, and, depending on the
- platform, essentially maps to a class's method.
- The native guides listed below provide details.
-5. `[/* arguments */]` - Arguments to pass into the native environment.
-
-### Echo Plugin JavaScript Example
-
- window.echo = function(str, callback) {
- cordova.exec(callback, function(err) {
- callback('Nothing to echo.');
- }, "Echo", "echo", [str]);
- };
-
-Let's dive into this. The plugin attaches itself to `window`,
-specifically to the `echo` function. Plugin users would then use it as
-follows:
-
- window.echo("echome", function(echoValue) {
- alert(echoValue == "echome"); // should alert true.
- });
-
-First, let's take a look at the last three arguments to the `exec`
-function. We will be calling the `Echo` "service", requesting the `echo`
-"action", and passing an array of arguments containing the echo string,
-which is the first parameter into the `window.echo` function.
-
-The success callback passed into `exec` is simply a reference to the
-callback function that `window.echo` takes. We do a bit more for the
-error callback: if the native side fires off the error callback, we
-simply invoke the success callback and pass into it a "default"
-string.
-
-## Native
-
-Once you define JavaScript for your plugin, you need to complement it
-with at least one native implementation. Details to do so for each
-platform are listed below. These guides continue to build on the
-simple Echo Plugin example discussed above.
-
-- Android Plugins
-- BlackBerry Plugins
-- BlackBerry 10 Plugins
-- iOS Plugins
-- Windows Phone Plugins
-
-The webOS and Tizen platforms currently do not support plugins.
[16/20] docs commit: [CB-3827] fixed problem where supposed '.md'
file actually became directory
Posted by mw...@apache.org.
[CB-3827] fixed problem where supposed '.md' file actually became directory
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/96d79d83
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/96d79d83
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/96d79d83
Branch: refs/heads/master
Commit: 96d79d83a3c65ee91650b652845e8db32ef26e6a
Parents: 610314b
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 13:28:44 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 13:28:44 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/platforms/win8/upgrading.md | 39 ++++++++++++++++++++
.../guide/platforms/win8/upgrading.md/index.md | 39 --------------------
2 files changed, 39 insertions(+), 39 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/96d79d83/docs/en/edge/guide/platforms/win8/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/upgrading.md b/docs/en/edge/guide/platforms/win8/upgrading.md
new file mode 100644
index 0000000..f5c3bea
--- /dev/null
+++ b/docs/en/edge/guide/platforms/win8/upgrading.md
@@ -0,0 +1,39 @@
+---
+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 Windows 8
+===============================
+
+This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to applications targetting Windows 8 and the Windows Store.
+
+## Upgrade to 2.9.0 from 2.8.0 ##
+
+The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
+
+1. Remove cordova-2.8.0.js from the www directory in your project.
+2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
+3. Build and test!
+
+## Upgrade to 2.8.0 from 2.7.0 ##
+
+The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
+
+1. Remove cordova-2.7.0.js from the www directory in your project.
+2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
+3. Build and test!
diff --git a/docs/en/edge/guide/platforms/win8/upgrading.md/index.md b/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
deleted file mode 100644
index f5c3bea..0000000
--- a/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
+++ /dev/null
@@ -1,39 +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 Windows 8
-===============================
-
-This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to applications targetting Windows 8 and the Windows Store.
-
-## Upgrade to 2.9.0 from 2.8.0 ##
-
-The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
-
-1. Remove cordova-2.8.0.js from the www directory in your project.
-2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
-3. Build and test!
-
-## Upgrade to 2.8.0 from 2.7.0 ##
-
-The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
-
-1. Remove cordova-2.7.0.js from the www directory in your project.
-2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
-3. Build and test!
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/96d79d83/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/upgrading.md/index.md b/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
deleted file mode 100644
index f5c3bea..0000000
--- a/docs/en/edge/guide/platforms/win8/upgrading.md/index.md
+++ /dev/null
@@ -1,39 +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 Windows 8
-===============================
-
-This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to applications targetting Windows 8 and the Windows Store.
-
-## Upgrade to 2.9.0 from 2.8.0 ##
-
-The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
-
-1. Remove cordova-2.8.0.js from the www directory in your project.
-2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
-3. Build and test!
-
-## Upgrade to 2.8.0 from 2.7.0 ##
-
-The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
-
-1. Remove cordova-2.7.0.js from the www directory in your project.
-2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
-3. Build and test!
[11/20] [CB-3827] move platform-specific files within platforms dir;
rename dirs within platforms
Posted by mw...@apache.org.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/upgrading/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/ios/index.md b/docs/en/edge/guide/upgrading/ios/index.md
deleted file mode 100644
index 4009bc2..0000000
--- a/docs/en/edge/guide/upgrading/ios/index.md
+++ /dev/null
@@ -1,438 +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 iOS
-=====================
-
-Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, you must use the latest shipped version of the iOS SDK, which is iOS 6. The iOS 6 SDK requires Xcode 4.5.
-
-## Upgrading 2.8.0 projects to 2.9.0 ##
-
-1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.9.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova.js** (note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your **www** folder, and delete your **www/cordova.js** file
-6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
-7. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
-
-## Upgrading 2.7.0 projects to 2.8.0 ##
-
-1. **Download and extract the Cordova 2.8.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.8.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova.js** (note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your **www** folder, and delete your **www/cordova-2.7.0.js** file
-6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
-7. Update any <plugin> tags that are in your **config.xml** to <feature> tags. Note that existing <plugin> tags will still work, but are deprecated. You can copy this information in the **config.xml** for a new project. For example:
-
- <plugins>
- <plugin name="LocalStorage" value="CDVLocalStorage" />
- <!-- other plugins -->
- </plugins>
-
- <!-- change to: (note that a <feature> tag is on the same level as <plugins> -->
- <feature name="LocalStorage">
- <param name="ios-package" value="CDVLocalStorage" />
- </feature>
- <!-- other <feature> tags -->
-
-8. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
-9. Add these two frameworks to your project:
-
- OpenAL
- ImageIO
-
-10. Update your project's target **Build Settings**. Under **Linking** -> **Other Linker Flags**, edit **"-Obj-C"** to be **"-ObjC"**
-
-11. Update your project's target **Build Settings**. Under **Linking** -> **Other Linker Flags**, change **"-all\_load"** to be **"-force\_load ${TARGET\_BUILD\_DIR}/libCordova.a"**. You would only need to do this if you have the problem defined in [this issue.](https://issues.apache.org/jira/browse/CB-3458)
-
-## Upgrading 2.6.0 projects to 2.7.0 ##
-
-1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.7.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. you need the assets from this new project.
-5. **Copy** the **www/cordova-2.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.6.0.js** file
-6. **Update** the Cordova script reference in your **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. Update (or replace, if you never changed the file) your **AppDelegate.m** file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=5c05ac80e056753c0e8736f887ba9f28d5b0774c;hp=623ad8ec3c46f656ea18c6c3a190d650dd64e479;hb=c6e71147386d4ad94b07428952d1aae0a9cbf3f5;hpb=c017fda8af00375a453cf27cfc488647972e9a23))
-8. In your **config.xml** file, [remove this line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=537705d76a5ef6bc5e57a8ebfcab78c02bb4110b;hp=8889726d9a8f8c530fe1371c56d858c34552992a;hb=064239b7b5fa9a867144cf1ee8b2fb798ce1f988;hpb=c9f233250d4b800f3412eeded811daaafb17b2cc).
-9. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
-
-
-## Upgrading 2.5.0 projects to 2.6.0 ##
-
-1. **Download and extract the Cordova 2.6.0 source** to a **permanent folder location** on your hard drive (say to `~/Documents/Cordova-2.6.0`)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the project's `www/cordova-2.6.0.js` file into your `www` folder, and delete your `www/cordova-2.5.0.js` file.
-6. **Update** the Cordova script reference in your `www/index.html` file (along with any other files that reference the script) to refer to the new `cordova-2.6.0.js` file.
-7. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=124a56bb4f361e95616f44d6d6f5a96ffa439b60;hp=318f79326176be8f16ebc93bad85dd745f4205b6;hb=a28c7712810a63396e9f32fa4eb94fe3f8b93985;hpb=36acdf55e4cab52802d73764c8a4b5b42cf18ef9))
-8. In your `config.xml` file, [add this new line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=1555b5e81de326a07efe0bccaa5f5e2326b07a9a;hp=0652d60f8d35ac13c825c572dca6ed01fea4a540;hb=95f16a6dc252db0299b8e2bb53797995b1e39aa1;hpb=a2de90b8f5f5f68bd9520bcbbb9afa3ac409b96d).
-9. In your `config.xml` file, [add this new line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=d307827b7e67301171a913417fb10003d43ce39d;hp=04260aa9786d6d74ab20a07c86d7e8b34e31968c;hb=97b89edfae3527828c0ca6bb2f6d58d9ded95188;hpb=942d33c8e7174a5766029ea1232ba2e0df745c3f).
-10. In your `config.xml` file, [UIWebViewBounce has ben changed to DisallowOverscroll - and default values are different](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=8889726d9a8f8c530fe1371c56d858c34552992a;hp=d307827b7e67301171a913417fb10003d43ce39d;hb=57982de638a4dce6ae130a26662591741b065f00;hpb=ec411f18309d577b4debefd9a2f085ba719701d5).
-10. In your `config.xml` file, the **EnableLocation** preference has been **deprecated**.
-11. Delete your `CordovaLib` folder, and copy the `CordovaLib` folder from the new project into your project's root folder.
-
-## Upgrading 2.4.0 projects to 2.5.0 ##
-
-1. **Download and extract the Cordova 2.5.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.5.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova-2.5.0.js** file from the new project into your **www** folder and delete your **www/cordova-2.4.0.js** file
-6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.5.0.js** file
-7. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=318f79326176be8f16ebc93bad85dd745f4205b6;hp=6dc7bfc84f0ecede4cc43d2a3256ef7c5383b9fe;hb=4001ae13fcb1fcbe73168327630fbc0ce44703d0;hpb=299a324e8c30065fc4511c1fe59c6515d4842f09))
-8. In your `config.xml` file, [add these new lines](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=903944c4b1e58575295c820e154be2f5f09e6314;hp=721c734120b13004a4a543ee25f4287e541f34be;hb=ae467249b4a256bd31ee89aea7a06f4f2316b8ac;hpb=9e39f7ef8096fb15b38121ab0e245a3a958d9cbb).
-9. In your `config.xml` file, [edit the root element, change it from cordova to widget](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=64e71636f5dd79fa0978a97b9ff5aa3860a493f5;hp=d8579352dfb21c14e5748e09b2cf3f4396450163;hb=0e711f8d09377a7ac10ff6be4ec17d22cdbee88d;hpb=57c3c082ed9be41c0588d0d63a1d2bfcd2ed878c).
-10. In your `config.xml` file, [remove the OpenAllWhitelistURLsInWebView preference](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=721c734120b13004a4a543ee25f4287e541f34be;hp=7d67508b70914aa921a16e79f79c00512502a8b6;hb=187bf21b308551bfb4b98b1a5e11edf04f699791;hpb=03b8854bdf039bcefbe0212db937abd81ac675e4).
-11. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.5.0, this has updated scripts)**
-12. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
-
-## Upgrading 2.3.0 projects to 2.4.0 ##
-
-1. **Download and extract the Cordova 2.4.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.4.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova-2.4.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.3.0.js** file
-6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.4.0.js** file
-7. Update (or replace, if you never changed the files) your `MainViewController.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/MainViewController.m;h=5f9eeac15c2437cd02a6eb5835b48374e9b94100;hp=89da1082d06ba5e5d0dffc5b2e75a3a06d5c2aa6;hb=b4a2e4ae0445ba7aec788090dce9b822d67edfd8;hpb=a484850f4610e73c7b20cd429a7794ba829ec997)).
-8. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=6dc7bfc84f0ecede4cc43d2a3256ef7c5383b9fe;hp=1ca3dafeb354c4442b7e149da4f281675aa6b740;hb=6749c17640c5fed8a7d3a0b9cca204b89a855baa;hpb=deabeeb6fcb35bac9360b053c8bf902b45e6de4d))
-9. In your `config.xml` file, [add this new line](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/config.xml;h=7d67508b70914aa921a16e79f79c00512502a8b6;hp=337d38da6f40c7432b0bce05aa3281d797eec40a;hb=6749c17640c5fed8a7d3a0b9cca204b89a855baa;hpb=deabeeb6fcb35bac9360b053c8bf902b45e6de4d).
-10. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.4.0, this has fixed scripts)**
-11. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
-12. Add AssetsLibrary.framework as a resource to your project. (Go [here](https://developer.apple.com/library/ios/#recipes/xcode_help-project_editor/Articles/AddingaLibrarytoaTarget.html) for instructions on how to do so.)
-
-## Upgrading 2.2.0 projects to 2.3.0 ##
-
-1. **Download and extract the Cordova 2.3.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.3.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova-2.3.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.2.0.js** file
-6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.3.0.js** file
-7. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project.
-8. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.3.0, this has new scripts)**
-9. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
-10. Convert your `Cordova.plist` file to `config.xml`, by running the script **bin/cordova\_plist\_to\_config\_xml** on your project file.
-11. Add the InAppBrowser plugin to your `config.xml`, by adding this tag under **<cordova><plugins>**:
-
- <plugin name="InAppBrowser" value="CDVInAppBrowser" />
-12. Note that Objective-C plugins are **not** whitelisted anymore. To whitelist your connections with the app whitelist, you will need to set the “User-Agent” header of the connection to the same user-agent as the main Cordova WebView.
-You can get this by accessing the **userAgent** property off the main view-controller. The main view-controller (CDVViewController) also has a **URLisAllowed** method for you to check whether a URL will pass the whitelist.
-13. Device API changes:
- * For iOS, device.platform used to return “iPhone”, “iPad” or “iPod Touch” — now it returns (correctly) “iOS”.
- * For iOS, device.name (now deprecated for all platforms) used to return the name of the user’s device (e.g ‘Shazron’s iPhone 5′) — now it returns what device.platform used to return: ”iPhone”, “iPad” or “iPod Touch”.
- * For all platforms, there is a new property called device.model — this returns the specific device model, e.g “iPad2,5″ (for other platforms, this returns what device.name used to return).
-
-## Upgrading 2.1.0 projects to 2.2.0 ##
-
-1. **Download and extract the Cordova 2.2.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.2.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova-2.2.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.1.0.js** file
-6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.2.0.js** file
-7. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project:
- - Updated → viewWillAppear
-8. Copy the **cordova** folder from the new project into your project's root folder **(in 2.2.0, this has an updated 'emulate' script)**
-9. Next, update your CordovaLib sub-project reference. Beginning with Cordova 2.1.0, we are not using the CORDOVALIB Xcode variable anymore when referencing where CordovaLib resides, the reference is an absolute file reference now.
- 1. Launch **Terminal.app**
- 2. Go to the location where you installed Cordova (see Step 1), in the **bin** sub-folder
- 3. Run the script below where the first parameter is the path to your project's **.xcodeproj** file:
-
- `update_cordova_subproject path/to/your/project/xcodeproj`
-
-__NOTE:__ In 2.2.0, the `bin/create` script copy in the CordovaLib sub-project into your project. To have the same kind of setup, just copy in the right CordovaLib into your project folder, and update the CordovaLib sub-project location (relative to the project) in the Xcode File Inspector.
-
-## Upgrading 2.0.0 projects to 2.1.0 ##
-
-With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Reference Counting (ARC)**. You don't need to upgrade to **ARC** to use CordovaLib, but if you want to upgrade your project to use **ARC**, please use the Xcode migration wizard from the menu: **Edit → Refactor → Convert to Objective-C ARC...**, **de-select libCordova.a**, then run the wizard to completion.
-
-1. **Download and extract the Cordova 2.1.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.1.0)
-2. **Quit Xcode** if it is running.
-3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-5. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-6. **Copy** the **www/cordova-2.1.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.0.0.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.1.0.js** file
-8. Update (or replace, if you never changed the file) your `AppDelegate.m` according to the one from the new project:
- - Edited -> application:didFinishLaunchingWithOptions:
- - Added -> application:supportedInterfaceOrientationsForWindow:
-9. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project:
- - Added -> viewWillAppear
-10. Copy the **cordova** folder from the new project into your project's root folder **(in 2.1.0, this has the updated scripts to support paths with spaces)**
-11. Remove the **VERSION** file reference from your **project** (_not_ the one in CordovaLib)
-12. Next, update your CordovaLib sub-project reference. Beginning with Cordova 2.1.0, we are not using the CORDOVALIB Xcode variable anymore when referencing where CordovaLib resides, the reference is an absolute file reference now.
- 1. Launch **Terminal.app**
- 2. Go to the location where you installed Cordova **(see Step 1)**, in the **bin** sub-folder
- 3. Run the script below where the first parameter is the path to your project's **.xcodeproj** file:
-
- `update_cordova_subproject path/to/your/project/xcodeproj`
-
-## Upgrading 1.9.0 projects to 2.0.0 ##
-
-1. **Install** Cordova 2.0.0
-2. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
-3. **Copy** the **www/cordova-2.0.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.9.0.js** file
-4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.0.0.js** file
-5. Copy the **cordova** folder from the new project into your project's root folder (if you want the project command-line tools)
-6. **Add** a new entry under **Plugins** in your `Cordova.plist` file (under the **Supporting Files** group) - the key is **Device** and the value is **CDVDevice**
-7. Remove `Cordova.framework`
-8. Remove `verify.sh` from the **Supporting Files** group
-9. Select the **project icon** in the Project Navigator, select your project **Target**, then select the **Build Settings** tab
-10. Search for **Preprocessor Macros**, then remove all **CORDOVA_FRAMEWORK=1** values
-11. Locate the **CordovaLib** folder that was installed in your hard-drive under your home folder's **Documents** sub-folder.
-12. Locate the `CordovaLib.xcodeproj` file in the **CordovaLib** folder, then **drag and drop** the file into your project - it should appear as a **sub-project**.
-13. **Build** your project, you should get some **errors** relating to **#import** directives
-14. For the **#import errors**, change any **quote-based** imports in this style:
-
- #import "CDV.h"
-
- to this **brackets-based** style:
-
- #import <Cordova/CDV.h>
-
- and remove any **#ifdef** wrappers around any Cordova imports, they are not needed anymore (the imports are **unified** now)
-15. **Build** your project again, and it should not have any **#import** errors.
-16. Select the **project icon** in the Project Navigator, select your project **Target**, then select the **Build Phases** tab
-17. Expand the **Target Dependencies** phase, then select the **+** button
-18. Select the **CordovaLib** target, then select the **Add** button
-19. Expand the **first** **Link Binary with Libraries** phase (it should already contain a bunch of frameworks), then select the **+** button
-20. Select the `libCordova.a` static library, then select the **Add** button
-21. Delete the **Run Script** phase.
-22. Select the **project icon** in the Project Navigator, select your project **Target**, then select the **Build Settings** tab
-23. Search for **Other Linker Flags**, and add the values **-all_load** and **-Obj-C**
-24. Expand the **CordovaLib** sub-project.
-25. Locate the **VERSION** file, drag it into your main project (we want to create a link to it, not a copy)
-26. Select the **Create groups for any added folders** radiobutton, then select the **Finish** button
-27. Select the **VERSION** file that you just dragged in a previous step
-28. Type the **Option-Command-1** key combination to show the **File Inspector** (or menuitem **View -> Utilities -> Show File Inspector**)
-29. Choose **Relative to CORDOVALIB** in the **File Inspector** for the drop-down menu for **Location**
-30. Set the Xcode preference **Xcode Preferences -> Locations -> Derived Data -> Advanced...** to **Unique** (this is so the unified headers can be found)
-31. Select the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
-32. Search for **Header Search Paths**. For that setting, add these three values below (with quotes):
-
- "$(TARGET_BUILD_DIR)/usr/local/lib/include"
-
- "$(OBJROOT)/UninstalledProducts/include"
-
- "$(BUILT_PRODUCTS_DIR)"
-
-33. Search for **Other Linker Flags**. For that setting, add this value below:
-
- -weak_framework CoreFoundation
-
-34. **Build** your project, it should compile and link with **no issues**.
-35. **Select your project** from the **Scheme** drop-down, and then select **iPhone 5.1 Simulator**
-36. Select the **Run** button
-
-__NOTE:__ If your project is **not working** as expected in the Simulator, please **take a note of any errors** in the **console log in Xcode** for clues.
-
-## Upgrading 1.8.x projects to 1.9.0 ##
-
-1. **Install** Cordova 1.9.0
-2. **Create a new project** - you will have to grab assets from this new project
-3. **Copy** the **www/cordova-1.9.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.8.x.js** file
-4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.9.0.js** file
-
-__NOTE:__ 1.9.0 supports the new **BackupWebStorage** boolean `Cordova.plist` setting. It's enabled by default, so set it to
-`false` to disable it, especially on iOS 6. See [Release Notes - Safari and UIKit Section](https://developer.apple.com/library/prerelease/ios/#releasenotes/General/RN-iOSSDK-6_0/_index.html)
-
-## Upgrading 1.7.0 projects to 1.8.x ##
-
-1. **Install** Cordova 1.8.0
-2. **Create a new project** - you will have to grab assets from this new project
-3. **Copy** the **www/cordova-1.8.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.7.x.js** file
-4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.8.0.js** file
-
-If you intend on using the **Capture API**, you will need the new **iPad retina-display** assets:
-
-1. **Copy** the `Resources/Capture.bundle` item from the new project into your project folder, over-writing your existing `Resources/Capture.bundle` item
-2. In your project, select the `Capture.bundle` item into your Project Navigator in Xcode, type the **Delete** key, then select **Remove Reference** from the resulting dialog.
-3. Drag the new `Capture.bundle` from Step 1 above into your Project Navigator in Xcode, then select the **Create groups for any added folders** radio button
-
-## Upgrading 1.6.x projects to 1.7.0 ##
-
-1. **Install** Cordova 1.7.0
-2. **Create a new project** - you will have to grab assets from this new project
-3. **Copy** the **www/cordova-1.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.6.0.js** file
-4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.7.0.js** file
-
-## Upgrading 1.5.0 projects to 1.6.x ##
-
-1. **Install** Cordova 1.6.1
-2. **Make a backup** of `AppDelegate.m`, `AppDelegate.h`, `MainViewController.m`, `MainViewController.h`, and `Cordova.plist` in your project
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** these files from the **new** project into your 1.5.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
-
- AppDelegate.h
- AppDelegate.m
- MainViewController.h
- MainViewController.m
- Cordova.plist
-5. **Add** all the new **MainViewController** and **AppDelegate** files into your Xcode project
-6. **Copy** the **www/cordova-1.6.1.js** file from the new project into your **www** folder, and delete your **www/cordova-1.5.0.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.6.1.js** file
-8. **Add** the new `Cordova.plist` file into your project - this is because the core plugin service names needed to be changed to match the ones from Android and Blackberry, for a unified Cordova JavaScript file (cordova-js).
-9. **Integrate** any settings, **Plugins** and **ExternalHosts** entries that you had in your **backed-up Cordova.plist** into the new `Cordova.plist`
-10. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files. Any **UIWebViewDelegate** or **CDVCommandDelegate** code in `AppDelegate.m` will need to go into MainViewController.m now (see commented out sections in that file)
-11. **Integrate** any project-specific code that you have in your **backed-up MainViewController.h and MainViewController.m** into the new MainViewController files
-12. Click on the **project icon** in the Project Navigator, select your **Project**, then select the **Build Settings** tab
-13. Enter **Compiler for C/C++/Objective-C** in the search field
-14. Select the **Apple LLVM Compiler 3.1** value
-
-## Upgrading 1.4.x projects to 1.5.0 ##
-
-1. **Install** Cordova 1.5.0
-2. **Create a new project** and run it once - you will have to grab assets from this new project
-3. **Copy** the **www/cordova-1.5.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.4.x.js** file
-4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new Cordova **cordova-1.5.0.js** file
-5. Find `PhoneGap.framework` in your Project Navigator, select it
-6. Type the **Delete** key and delete the `PhoneGap.framework` reference in the Project Navigator
-7. Type the **Option-Command-A** key combination, which should drop down a sheet to add files to your project (the **Add Files...** sheet). Make sure the **Created groups for any added folders** radio button is selected
-8. Type the **Shift-Command-G** key combination, which should drop down another sheet for you to go to a folder (the **Go to the folder:** sheet)
-9. Enter **/Users/Shared/Cordova/Frameworks/Cordova.framework** in the **Go to the folder:** sheet and then press the **Go** button
-10. Press the **Add** button in the **Add Files...** sheet
-11. Select `Cordova.framework` in the Project Navigator
-12. Type the **Option-Command-1** key combination to show the **File Inspector**
-13. Choose **Absolute Path** in the **File Inspector** for the drop-down menu for **Location**
-14. Type the **Option-Command-A** key combination, which should drop down a sheet to add files to your project (the **Add Files...** sheet). Make sure the **Created groups for any added folders** radio button is selected
-15. Type the **Shift-Command-G** key combination, which should drop down another sheet for you to go to a folder (the **Go to the folder:** sheet)
-16. Enter **~/Documents/CordovaLib/Classes/deprecated** in the **Go to the folder:** sheet and then press the **Go** button
-17. Press the **Add** button in the **Add Files...** sheet
-18. In your **AppDelegate.h, AppDelegate.m, and MainViewController.h** files - replace the whole **#ifdef PHONEGAP_FRAMEWORK** block with:
-
- #import "CDVDeprecated.h"
-19. Click on the **project icon** in the Project Navigator, select your **Target**, then select the **Build Settings** tab
-20. Search for **Framework Search Paths**
-21. Replace the existing value with **/Users/Shared/Cordova/Frameworks**
-22. Search for **Preprocessor Macros**
-23. For the first (combined) value, replace the value with **CORDOVA_FRAMEWORK=YES**
-24. Select the **Build Phases** tab
-25. Expand **Run Script**
-26. Replace any occurrences of **PhoneGap** with **Cordova**
-27. Find your `PhoneGap.plist` file in the Project Navigator, and click on the filename once to enter name edit mode
-28. Rename `PhoneGap.plist` to `Cordova.plist`
-29. Right-click on `Cordova.plist` and choose **Open As --> Source Code**
-30. Press **Option-Command-F**, choose **Replace** from the drop-down on the top left of the Source window
-31. Enter `com.phonegap` for the Find string, and `org.apache.cordova` for the Replace string - then press the **Replace All** button
-32. Enter **PG** for the Find string, and **CDV** for the Replace string - then press the **Replace All** button
-33. Press **Command-B** to build, you will still have deprecations that you can get rid of in the future (see `CDVDeprecated.h` - replace classes in your code that use PG* to CDV*, for example)
-
-## Upgrading 1.4.0 projects to 1.4.1 ##
-
-1. **Install** Cordova 1.4.1
-2. **Make a backup** of `MainViewController.m`
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** the `MainViewController.m` file from the **new** project into your 1.4.0-based project folder on disk, **replacing** the old file (**backup** your files first from step 2 above).
-5. **Add** the `MainViewController.m` file into your Xcode project
-6. **Integrate** any project-specific code that you have in your backed-up `MainViewController.m` into the new file
-7. Updating the `phonegap-1.4.0.js` file is optional, nothing has changed in the JavaScript between 1.4.0 and 1.4.1
-
-## Upgrading 1.3.0 projects to 1.4.0 ##
-
-1. **Install** Cordova 1.4.0
-2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** these files from the **new** project into your 1.3.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
-
- AppDelegate.h
- AppDelegate.m
- MainViewController.h
- MainViewController.m
- MainViewController.xib
-5. **Add** all the **MainViewController** files into your Xcode project
-6. **Copy** the **www/phonegap-1.4.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.3.0.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.4.0.js** file
-8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
-9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-
-## Upgrading 1.2.0 projects to 1.3.0 ##
-
-1. **Install** Cordova 1.3.0
-2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** these files from the **new** project into your 1.2.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
-
- AppDelegate.h
- AppDelegate.m
- MainViewController.h
- MainViewController.m
- MainViewController.xib
-5. **Add** all the **MainViewController** files into your Xcode project
-6. **Copy** the **www/phonegap-1.3.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.2.0.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.3.0.js** file
-8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
-9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-
-## Upgrading 1.1.0 projects to 1.2.0 ##
-
-1. **Install** Cordova 1.2.0
-2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** these files from the **new** project into your 1.1.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
-
- AppDelegate.h
- AppDelegate.m
- MainViewController.h
- MainViewController.m
- MainViewController.xib
-5. **Add** all the **MainViewController** files into your Xcode project
-6. **Copy** the **www/phonegap-1.2.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.1.0.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.2.0.js** file
-8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
-9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-
-## Upgrading 1.0.0 projects to 1.1.0 ##
-
-1. **Install** Cordova 1.1.0
-2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** these files from the **new** project into your 1.0.0-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
-
- AppDelegate.h
- AppDelegate.m
- MainViewController.h
- MainViewController.m
- MainViewController.xib
-5. **Add** all the **MainViewController** files into your Xcode project
-6. **Copy** the **www/phonegap-1.1.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-1.0.0.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.1.0.js** file
-8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
-9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-
-## Upgrading 0.9.6 projects to 1.0.0 ##
-
-1. **Install** Cordova 1.0.0
-2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
-3. **Create a new project** - you will have to grab assets from this new project
-4. **Copy** these files from the **new** project into your 0.9.6-based project folder on disk, **replacing** any old files (**backup** your files first from step 2 above):
-
- AppDelegate.h
- AppDelegate.m
- MainViewController.h
- MainViewController.m
- MainViewController.xib
-5. **Add** all the **MainViewController** files into your Xcode project
-6. **Copy** the **www/phonegap-1.0.0.js** file from the new project into your **www** folder, and delete your **www/phonegap-0.9.6.js** file
-7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **phonegap-1.0.0.js** file
-8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
-9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/upgrading/windows-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/windows-8/index.md b/docs/en/edge/guide/upgrading/windows-8/index.md
deleted file mode 100644
index f5c3bea..0000000
--- a/docs/en/edge/guide/upgrading/windows-8/index.md
+++ /dev/null
@@ -1,39 +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 Windows 8
-===============================
-
-This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to applications targetting Windows 8 and the Windows Store.
-
-## Upgrade to 2.9.0 from 2.8.0 ##
-
-The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
-
-1. Remove cordova-2.8.0.js from the www directory in your project.
-2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
-3. Build and test!
-
-## Upgrade to 2.8.0 from 2.7.0 ##
-
-The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
-
-1. Remove cordova-2.7.0.js from the www directory in your project.
-2. Add cordova.js file from the source to the www directory in your project. ( note that the file no longer contains a version number in the file name )
-3. Build and test!
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/upgrading/windows-phone/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/windows-phone/index.md b/docs/en/edge/guide/upgrading/windows-phone/index.md
deleted file mode 100644
index 7d65b24..0000000
--- a/docs/en/edge/guide/upgrading/windows-phone/index.md
+++ /dev/null
@@ -1,236 +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 Windows Phone
-===============================
-
-This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to both WP7 and WP8.
-
-## Upgrade to 2.8.0 from 2.9.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.9.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update the name of cordova.js in the HTML tag if it's still using cordova-VERSION.js (should be just cordova.js).
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the .csproj file.
-6. Build and test.
-
-## Upgrade to 2.8.0 from 2.7.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.8.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova.js file. ( note that there is no longer a version number in the name )
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.7.0 from 2.6.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.7.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.7.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.6.0 from 2.5.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.6.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.6.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.5.0 from 2.4.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.5.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.5.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.4.0 from 2.3.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.4.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.4.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.3.0 from 2.2.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.3.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.3.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.2.0 from 2.1.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.2.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.2.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 2.1.0 from 2.0.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.1.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.1.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-
-## Upgrade to 2.0.0 from 1.9.0 ##
-
-There have been considerable changes to the WP7 project structure in Apache Cordova 2.0.0 which make this upgrade a little more involved that the others. Essentially this is not an upgrade but creation of a new project and copy over of existing source files.
-
-### In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.0 Project
-2. Copy the contents of your 'www' folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova-2.0.0.js file.
-4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the plugins folder to the new project and ensure that they are also added to the VS project.
-6. Build and test.
-
-## Upgrade to 1.9.0 from 1.8.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.9.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.9.0.js file.
-
-## Upgrade to 1.8.0 from 1.7.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.8.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.8.0.js file.
-
-## Upgrade to 1.7.0 from 1.6.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.7.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.7.0.js file.
-
-## Upgrade to 1.6.1 from 1.6.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.6.1.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.6.1.js file.
-
-## Upgrade to 1.6.0 from 1.5.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.6.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.6.0.js file.
-
-## Upgrade to 1.5.0 from 1.4.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.5.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.5.0.js file.
-
-## Upgrade to 1.4.0 from 1.3.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.4.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.4.0.js file.
-
-## Upgrade to 1.3.0 from 1.2.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.3.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.3.0.js file.
-
-## Upgrade to 1.2.0 from 1.1.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.2.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.2.0.js file.
-
-## Upgrade to 1.1.0 from 1.0.0 ##
-
-### In Visual Studio's Solution Explorer window:
-1. Delete the file GapLib/WP7CordovaClassLib.dll from your project.
-2. Remove the reference to WP7CordovaClassLib in the References folder.
-3. Right-Click on References and Select 'Add Reference'
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
- - note: you can view the version of the DLL by right-clicking on the reference, and selecting Properties.
-5. Copy the new cordova-1.1.0.js into your project ( be sure it is marked as Content )
-6. Update your HTML to use the new cordova-1.1.0.js file.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/webviews/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/webviews/index.md b/docs/en/edge/guide/webviews/index.md
new file mode 100644
index 0000000..649a5e8
--- /dev/null
+++ b/docs/en/edge/guide/webviews/index.md
@@ -0,0 +1,27 @@
+---
+license: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+---
+
+Embedding WebViews
+=================
+
+> Implement the Cordova WebView in your own project.
+
+- Android WebViews
+- iOS WebViews
+
[10/20] docs commit: [CB-3827] rename 'getting-started' dirs as
'platforms'
Posted by mw...@apache.org.
[CB-3827] rename 'getting-started' dirs as 'platforms'
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/cfebdc34
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/cfebdc34
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/cfebdc34
Branch: refs/heads/master
Commit: cfebdc341560432abadba6abcbcb94b1f2f592d0
Parents: f50e593
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 13:02:26 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 13:02:26 2013 -0400
----------------------------------------------------------------------
.../edge/guide/getting-started/android/index.md | 190 -----------------
.../edge/guide/getting-started/android/tools.md | 80 -------
.../guide/getting-started/blackberry/index.md | 181 ----------------
.../guide/getting-started/blackberry/tools.md | 84 --------
.../guide/getting-started/blackberry10/index.md | 185 ----------------
.../guide/getting-started/blackberry10/tools.md | 179 ----------------
docs/en/edge/guide/getting-started/index.md | 95 ---------
docs/en/edge/guide/getting-started/ios/index.md | 210 -------------------
docs/en/edge/guide/getting-started/ios/tools.md | 59 ------
.../edge/guide/getting-started/tizen/index.md | 112 ----------
.../guide/getting-started/windows-8/index.md | 111 ----------
.../guide/getting-started/windows-8/tools.md | 44 ----
.../getting-started/windows-phone-7/index.md | 95 ---------
.../getting-started/windows-phone-8/index.md | 135 ------------
.../getting-started/windows-phone-8/tools.md | 77 -------
docs/en/edge/guide/overview/index.md | 16 +-
docs/en/edge/guide/platforms/android/index.md | 190 +++++++++++++++++
docs/en/edge/guide/platforms/android/tools.md | 80 +++++++
.../en/edge/guide/platforms/blackberry/index.md | 181 ++++++++++++++++
.../en/edge/guide/platforms/blackberry/tools.md | 84 ++++++++
.../edge/guide/platforms/blackberry10/index.md | 185 ++++++++++++++++
.../edge/guide/platforms/blackberry10/tools.md | 179 ++++++++++++++++
docs/en/edge/guide/platforms/index.md | 95 +++++++++
docs/en/edge/guide/platforms/ios/index.md | 210 +++++++++++++++++++
docs/en/edge/guide/platforms/ios/tools.md | 59 ++++++
docs/en/edge/guide/platforms/tizen/index.md | 112 ++++++++++
docs/en/edge/guide/platforms/windows-8/index.md | 111 ++++++++++
docs/en/edge/guide/platforms/windows-8/tools.md | 44 ++++
.../guide/platforms/windows-phone-7/index.md | 95 +++++++++
.../guide/platforms/windows-phone-8/index.md | 135 ++++++++++++
.../guide/platforms/windows-phone-8/tools.md | 77 +++++++
.../getting-started/android/AndroidFlow.png | Bin 198941 -> 0 bytes
.../guide/getting-started/android/asdk_avds.png | Bin 76048 -> 0 bytes
.../getting-started/android/asdk_device.png | Bin 109682 -> 0 bytes
.../getting-started/android/asdk_emulator.png | Bin 198297 -> 0 bytes
.../getting-started/android/asdk_newAVD.png | Bin 89084 -> 0 bytes
.../getting-started/android/asdk_window.png | Bin 244311 -> 0 bytes
.../guide/getting-started/android/buildPath.jpg | Bin 80516 -> 0 bytes
.../android/eclipse_android_sdk_button.png | Bin 9350 -> 0 bytes
.../android/eclipse_new_project.png | Bin 57193 -> 0 bytes
.../guide/getting-started/android/javaSrc.jpg | Bin 141340 -> 0 bytes
.../guide/getting-started/android/manifest.jpg | Bin 268212 -> 0 bytes
.../guide/getting-started/android/manifest.png | Bin 210586 -> 0 bytes
.../android/new_android_project.jpeg | Bin 62485 -> 0 bytes
.../guide/getting-started/android/step_1.png | Bin 59002 -> 0 bytes
.../guide/getting-started/android/step_2.png | Bin 67435 -> 0 bytes
.../guide/getting-started/android/step_3.png | Bin 71747 -> 0 bytes
.../guide/getting-started/android/step_4.png | Bin 48027 -> 0 bytes
.../guide/getting-started/android/step_5.png | Bin 52899 -> 0 bytes
.../guide/getting-started/bada/bada_1_run.png | Bin 84838 -> 0 bytes
.../guide/getting-started/bada/bada_2_run.png | Bin 115395 -> 0 bytes
.../guide/getting-started/bada/bada_project.png | Bin 56201 -> 0 bytes
.../getting-started/bada/bada_set_target.png | Bin 89656 -> 0 bytes
.../bada/import_bada_project.png | Bin 53647 -> 0 bytes
.../bada/import_bada_project_2.png | Bin 73479 -> 0 bytes
.../getting-started/ios/HelloWorldStandard.png | Bin 102066 -> 0 bytes
.../getting-started/ios/HelloWorldiPhone4.png | Bin 120055 -> 0 bytes
.../getting-started/ios/XCode4-templates.png | Bin 169771 -> 0 bytes
.../ios/active_scheme_device.png | Bin 21345 -> 0 bytes
.../ios/active_scheme_simulator.png | Bin 31070 -> 0 bytes
.../getting-started/ios/bin_create_project.png | Bin 36146 -> 0 bytes
.../getting-started/ios/bin_dir_listing.png | Bin 204942 -> 0 bytes
.../guide/getting-started/ios/bin_folder.png | Bin 55499 -> 0 bytes
.../ios/create-folder-reference.png | Bin 190649 -> 0 bytes
.../img/guide/getting-started/ios/create.png | Bin 38196 -> 0 bytes
.../getting-started/ios/helloworld_project.png | Bin 220325 -> 0 bytes
.../getting-started/ios/index-not-found.png | Bin 95265 -> 0 bytes
.../img/guide/getting-started/ios/make.png | Bin 53793 -> 0 bytes
.../img/guide/getting-started/ios/project.jpg | Bin 43884 -> 0 bytes
.../getting-started/ios/select_xcode_scheme.png | Bin 132314 -> 0 bytes
.../guide/getting-started/ios/www-folder.png | Bin 17844 -> 0 bytes
.../ios/xcode4-name_your_app.png | Bin 181444 -> 0 bytes
.../ios/xcode_build_location.png | Bin 129533 -> 0 bytes
.../getting-started/tizen/build_project.png | Bin 115912 -> 0 bytes
.../tizen/connection_explorer.png | Bin 14972 -> 0 bytes
.../getting-started/tizen/import_project.png | Bin 39736 -> 0 bytes
.../getting-started/tizen/import_widget.png | Bin 63293 -> 0 bytes
.../getting-started/tizen/project_explorer.png | Bin 54026 -> 0 bytes
.../getting-started/tizen/project_template.png | Bin 135765 -> 0 bytes
.../getting-started/tizen/runas_web_app.png | Bin 131463 -> 0 bytes
.../getting-started/tizen/runas_web_sim_app.png | Bin 130830 -> 0 bytes
.../guide/getting-started/windows-8/wsalert.png | Bin 44166 -> 0 bytes
.../windows-8/wschangemanifest.png | Bin 112224 -> 0 bytes
.../getting-started/windows-8/wsnewproject.png | Bin 189370 -> 0 bytes
.../windows-phone-7/wp7emulator.png | Bin 41379 -> 0 bytes
.../windows-phone-7/wp7projectstructure.png | Bin 22436 -> 0 bytes
.../getting-started/windows-phone-7/wp7vs.png | Bin 29416 -> 0 bytes
.../getting-started/windows-phone-7/wpd.png | Bin 1964 -> 0 bytes
.../windows-phone-7/wpfirstrun.png | Bin 114030 -> 0 bytes
.../windows-phone-7/wpnewproj.png | Bin 87470 -> 0 bytes
.../getting-started/windows-phone-7/wprun.png | Bin 63091 -> 0 bytes
.../windows-phone-8/BuidDevice.png | Bin 9935 -> 0 bytes
.../windows-phone-8/BuildEmulator.png | Bin 15667 -> 0 bytes
.../windows-phone-8/FullTemplate.png | Bin 77781 -> 0 bytes
.../windows-phone-8/StandAloneTemplate.png | Bin 78237 -> 0 bytes
.../windows-phone-8/projectStructure.png | Bin 9225 -> 0 bytes
.../img/guide/platforms/android/AndroidFlow.png | Bin 0 -> 198941 bytes
.../img/guide/platforms/android/asdk_avds.png | Bin 0 -> 76048 bytes
.../img/guide/platforms/android/asdk_device.png | Bin 0 -> 109682 bytes
.../guide/platforms/android/asdk_emulator.png | Bin 0 -> 198297 bytes
.../img/guide/platforms/android/asdk_newAVD.png | Bin 0 -> 89084 bytes
.../img/guide/platforms/android/asdk_window.png | Bin 0 -> 244311 bytes
.../img/guide/platforms/android/buildPath.jpg | Bin 0 -> 80516 bytes
.../android/eclipse_android_sdk_button.png | Bin 0 -> 9350 bytes
.../platforms/android/eclipse_new_project.png | Bin 0 -> 57193 bytes
.../img/guide/platforms/android/javaSrc.jpg | Bin 0 -> 141340 bytes
.../img/guide/platforms/android/manifest.jpg | Bin 0 -> 268212 bytes
.../img/guide/platforms/android/manifest.png | Bin 0 -> 210586 bytes
.../platforms/android/new_android_project.jpeg | Bin 0 -> 62485 bytes
.../img/guide/platforms/android/step_1.png | Bin 0 -> 59002 bytes
.../img/guide/platforms/android/step_2.png | Bin 0 -> 67435 bytes
.../img/guide/platforms/android/step_3.png | Bin 0 -> 71747 bytes
.../img/guide/platforms/android/step_4.png | Bin 0 -> 48027 bytes
.../img/guide/platforms/android/step_5.png | Bin 0 -> 52899 bytes
.../img/guide/platforms/bada/bada_1_run.png | Bin 0 -> 84838 bytes
.../img/guide/platforms/bada/bada_2_run.png | Bin 0 -> 115395 bytes
.../img/guide/platforms/bada/bada_project.png | Bin 0 -> 56201 bytes
.../guide/platforms/bada/bada_set_target.png | Bin 0 -> 89656 bytes
.../platforms/bada/import_bada_project.png | Bin 0 -> 53647 bytes
.../platforms/bada/import_bada_project_2.png | Bin 0 -> 73479 bytes
.../guide/platforms/ios/HelloWorldStandard.png | Bin 0 -> 102066 bytes
.../guide/platforms/ios/HelloWorldiPhone4.png | Bin 0 -> 120055 bytes
.../guide/platforms/ios/XCode4-templates.png | Bin 0 -> 169771 bytes
.../platforms/ios/active_scheme_device.png | Bin 0 -> 21345 bytes
.../platforms/ios/active_scheme_simulator.png | Bin 0 -> 31070 bytes
.../guide/platforms/ios/bin_create_project.png | Bin 0 -> 36146 bytes
.../img/guide/platforms/ios/bin_dir_listing.png | Bin 0 -> 204942 bytes
.../img/guide/platforms/ios/bin_folder.png | Bin 0 -> 55499 bytes
.../platforms/ios/create-folder-reference.png | Bin 0 -> 190649 bytes
.../default/img/guide/platforms/ios/create.png | Bin 0 -> 38196 bytes
.../guide/platforms/ios/helloworld_project.png | Bin 0 -> 220325 bytes
.../img/guide/platforms/ios/index-not-found.png | Bin 0 -> 95265 bytes
.../default/img/guide/platforms/ios/make.png | Bin 0 -> 53793 bytes
.../default/img/guide/platforms/ios/project.jpg | Bin 0 -> 43884 bytes
.../guide/platforms/ios/select_xcode_scheme.png | Bin 0 -> 132314 bytes
.../img/guide/platforms/ios/www-folder.png | Bin 0 -> 17844 bytes
.../platforms/ios/xcode4-name_your_app.png | Bin 0 -> 181444 bytes
.../platforms/ios/xcode_build_location.png | Bin 0 -> 129533 bytes
.../img/guide/platforms/tizen/build_project.png | Bin 0 -> 115912 bytes
.../platforms/tizen/connection_explorer.png | Bin 0 -> 14972 bytes
.../guide/platforms/tizen/import_project.png | Bin 0 -> 39736 bytes
.../img/guide/platforms/tizen/import_widget.png | Bin 0 -> 63293 bytes
.../guide/platforms/tizen/project_explorer.png | Bin 0 -> 54026 bytes
.../guide/platforms/tizen/project_template.png | Bin 0 -> 135765 bytes
.../img/guide/platforms/tizen/runas_web_app.png | Bin 0 -> 131463 bytes
.../guide/platforms/tizen/runas_web_sim_app.png | Bin 0 -> 130830 bytes
.../img/guide/platforms/windows-8/wsalert.png | Bin 0 -> 44166 bytes
.../platforms/windows-8/wschangemanifest.png | Bin 0 -> 112224 bytes
.../guide/platforms/windows-8/wsnewproject.png | Bin 0 -> 189370 bytes
.../platforms/windows-phone-7/wp7emulator.png | Bin 0 -> 41379 bytes
.../windows-phone-7/wp7projectstructure.png | Bin 0 -> 22436 bytes
.../guide/platforms/windows-phone-7/wp7vs.png | Bin 0 -> 29416 bytes
.../img/guide/platforms/windows-phone-7/wpd.png | Bin 0 -> 1964 bytes
.../platforms/windows-phone-7/wpfirstrun.png | Bin 0 -> 114030 bytes
.../platforms/windows-phone-7/wpnewproj.png | Bin 0 -> 87470 bytes
.../guide/platforms/windows-phone-7/wprun.png | Bin 0 -> 63091 bytes
.../platforms/windows-phone-8/BuidDevice.png | Bin 0 -> 9935 bytes
.../platforms/windows-phone-8/BuildEmulator.png | Bin 0 -> 15667 bytes
.../platforms/windows-phone-8/FullTemplate.png | Bin 0 -> 77781 bytes
.../windows-phone-8/StandAloneTemplate.png | Bin 0 -> 78237 bytes
.../windows-phone-8/projectStructure.png | Bin 0 -> 9225 bytes
161 files changed, 1845 insertions(+), 1845 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/android/index.md b/docs/en/edge/guide/getting-started/android/index.md
deleted file mode 100644
index 95a72f6..0000000
--- a/docs/en/edge/guide/getting-started/android/index.md
+++ /dev/null
@@ -1,190 +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 describes how to set up your SDK development environment to
-deploy Cordova apps for Android devices.
-
-## 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 the `cordova` utility in conjunction with
-the Android SDK. See The Cordova 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 Command-line Interface. For example, in a source-code directory:
-
- $ cordova create hello com.example.hello "Hello World"
- $ 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 folder.
-* 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/cfebdc34/docs/en/edge/guide/getting-started/android/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/android/tools.md b/docs/en/edge/guide/getting-started/android/tools.md
deleted file mode 100644
index 09fcfdc..0000000
--- a/docs/en/edge/guide/getting-started/android/tools.md
+++ /dev/null
@@ -1,80 +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 Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-## 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 and Windows:
-
- $ /path/to/cordova-android/bin/create /path/to/project com.example.project_name ProjectName
- $ C:\path\to\cordova-android\bin\create.bat C:\path\to\project com.example.project_name ProjectName
-
-## Build
-
-This cleans then builds a project.
-
-Debug, on Mac or Windows:
-
- $ /path/to/project/cordova/build --debug
- $ C:\path\to\project\cordova\build.bat --debug
-
-Release, on Mac 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
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry/index.md b/docs/en/edge/guide/getting-started/blackberry/index.md
deleted file mode 100644
index e17416d..0000000
--- a/docs/en/edge/guide/getting-started/blackberry/index.md
+++ /dev/null
@@ -1,181 +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 Platform Guide
-============================
-
-Cordova for BlackBerry makes use of the [BlackBerry WebWorks framework](https://bdsc.webapps.blackberry.com/html5). BlackBerry WebWorks tooling is available for Windows or Mac environments.
-
-WebWorks applications can ONLY be deployed to the following BlackBerry platforms:
-
-* BlackBerry OS 5.0 and higher
-* BlackBerry PlayBook
-* BlackBerry 10 (QNX)
-
-1. Requirements
----------------
-
-- Windows XP (32-bit) or Windows 7 (32-bit and 64-bit) or Mac OSX 10.6.4+
-- Java Development Kit (JDK)
- - Windows: [Oracle JDK](http://www.oracle.com/technetwork/java/javase/downloads/index.html#jdk) (32-Bit Version)
- - Mac OS X: Versions prior to Mac OS X 10.7 provided Java by default. OS X 10.7+ requires installation of [Java](http://support.apple.com/kb/DL1421).
-- Apache Ant
- - Windows: [Apache Ant](http://ant.apache.org/bindownload.cgi).
- - Mac OS X: Apache Ant is bundled with Java install.
-
-2. Install the WebWorks SDK
--------------------------
-Download and install the appropriate WebWorks SDKs for your development. BlackBerry 10, BlackBerry PlayBook, and BlackBerry Smartphone WebWorks SDKs can all be downloaded from the following locations. Please note that BlackBerry PlayBook development requires the Adobe Air SDK as well.
-
-- [BlackBerry 10 (QNX) SDK] (https://developer.blackberry.com/html5/download/#blackberry10)
-- [BlackBerry PlayBook SDK] (https://developer.blackberry.com/html5/download/#playbook) & [Adobe Air SDK](http://www.adobe.com/devnet/air/air-sdk-download.html)
-- [BlackBerry Smartphones SDK] (https://developer.blackberry.com/html5/download/#smartphones)
-
-3. Register for Signing Keys
--------------------------
-If you wish to publish your application on BlackBerry App World, or deploy on an actual device you’ll need to register for a set of free Code Signing Keys.
-
-To register for Signing Keys visit, and complete the [BlackBerry Keys Order Form](https://www.blackberry.com/SignedKeys).
-
-Once you receive your Signing Keys, they'll need to be setup. To learn how to setup your Signing Keys visit the [BlackBerry HTML5/WebWorks website](https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html).
-
-4. Install Cordova
--------------------------
-
-Download and extract the latest copy of [Cordova](http://cordova.apache.org/#download).
-
-5. Set up New Project
---------------------
-
-- Open up a command prompt/terminal and navigate to where you extracted Cordova.
-- There is a directory for each platform that Cordova supports. CD into the blackberry directory.
-- The blackberry directory contains several directories. The `example` folder contains a complete Cordova project. Copy the `example` folder to another location on your computer.
-- Change to the newly created directory.
-- Open up the project.properties file with your favorite editor and edit the entries for the WebWorks SDKs you are using. For example...
-
-BlackBerry 10 (QNX)
-- `qnx.bbwp.dir=C:\\Program Files (x86)\\Research In Motion\\BlackBerry 10 WebWorks SDK 1.0.2.9`
-
-BlackBerry PlayBook
-- `playbook.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks SDK for TabletOS 2.1.0.6\\bbwp`
-
-BlackBerry Smartphone (OS5-7)
-- `blackberry.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks Packager`
-
-6. Hello World
---------------
-
-Build the Cordova sample project by typing `./cordova/build <target>` in your command prompt/terminal while you are in your project's directory. Replace `<target>` with either `qnx` `playbook` or `blackberry`. For example...
-
-BlackBerry 10 (QNX)
-- `./cordova/build qnx`
-
-BlackBerry PlayBook
-- `./cordova/build playbook`
-
-BlackBerry Smartphone (OS5-7)
-- `./cordova/build blackberry`
-
-7A. Deploy to Simulator
---------------------------------------
-
-BlackBerry smartphone simulators are only available on Windows. BlackBerry 10, and PlayBook simulators require VMWare Player (Windows) or VMWare Fusion (Mac OS X). The WebWorks SDK provides a default simulator. Additional simulators are [available](http://us.blackberry.com/developers/resources/simulators.jsp).
-
-For instructions on installing simulators, please visit the following link(s):
-- [BlackBerry 10](https://developer.blackberry.com/html5/documentation/using_the_bb10_simulator_2008466_11.html)
-- [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)
-
-- Open the project.properties file with your favorite editor and customize the following properties.
-
-BlackBerry 10
-- `qnx.sim.ip`
-- `qnx.sim.password`
-- __NOTE:__ IP address of simulator obtained when placing the simulator in developer mode through simulator security settings. Simulator password can be set through simulator security settings.
-
-Playbook
-- `playbook.sim.ip` :
-- `playbook.sim.password`
-- __NOTE:__ IP address of simulator obtained when placing the simulator in developer mode through simulator security settings. Simulator password can be set through simulator security settings.
-
-Smartphone (Optional)
-- `blackberry.sim.dir`
-- `blackberry.sim.bin`
-- __NOTE:__ On windows file separator '\' must be escaped when specifying directories. For example `C:\\Program Files\\BlackBerry\\Simulator`.
-
-While in your project directory, in command prompt/terminal type `./cordova/run <target>`. Replace `<target>` with either `qnx`, `playbook`, or `blackberry`. Note, for BlackBerry 10 and PlayBook, the simulator virtual image must already be started. For example...
-
-BlackBerry 10 (QNX)
-- `./cordova/run qnx`
-
-BlackBerry PlayBook
-- `./cordova/run playbook`
-
-BlackBerry Smartphone (OS5-7)
-- `./cordova/run blackberry`
-
-When prompted __Do you have a BlackBerry device connected to your computer? (y/n)__, answer __n__.
-
-The application is installed to the simulator's home screen. Note that on BlackBerry OS 5, it is installed in the `Downloads` folder.
-
-7B. Deploy to Device (Windows and Mac)
---------------------------------------
-
-To deploy your app to a device you must have registered for, and setup BlackBerry Code Signing Keys. See section 3 for details. Also, to deploy apps on BlackBerry 10 or PlayBook, the device must be set to Development Mode which can be enabled from the __Settings → Security__ menu.
-
-- Open the project.properties file with your favorite editor and customize the following properties:
-
-BlackBerry 10 (QNX)
-- `qnx.sigtool.password`
-- `qnx.device.ip`
-- `qnx.device.password`
-
-BlackBerry PlayBook
-- `playbook.sigtool.csk.password`
-- `playbook.sigtool.p12.password`
-- `playbook.device.ip`
-- `playbook.device.password`
-
-BlackBerry Smartphone (OS5-7)
-- Smartphone (Optional)
-- `blackberry.sigtool.password`
-
-While in your project directory, in command prompt/terminal type `./cordova/run <target>`. Replace `<target>` with either `qnx`, `playbook`, or `blackberry`. For example...
-
-BlackBerry 10 (QNX)
-- `./cordova/run qnx`
-
-BlackBerry PlayBook
-- `./cordova/run playbook`
-
-BlackBerry Smartphone (OS5-7)
-- `./cordova/run blackberry`
-
-When prompted __Do you have a BlackBerry device connected to your computer? (y/n)__, answer __y__.
-
-The application is installed to the device's home screen. Note, on BlackBerry OS 5 the application is installed in the Downloads folder.
-
-Additional Information
-----------------------
-
-The following articles provide help to issues you may encounter when developing a Cordova application which is based on 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/cfebdc34/docs/en/edge/guide/getting-started/blackberry/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry/tools.md b/docs/en/edge/guide/getting-started/blackberry/tools.md
deleted file mode 100644
index 8bd2987..0000000
--- a/docs/en/edge/guide/getting-started/blackberry/tools.md
+++ /dev/null
@@ -1,84 +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 Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-## 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 and Windows:
-
- $ /path/to/cordova-blackberry-webworks/bin/create /path/to/my_new_project com.example.project_name ProjectName
- $ /path/to/cordova-blackberry-webworks/bin/create.bat /path/to/my_new_project com.example.project_name ProjectName
-
-__NOTE:__ The Blackberry platform ignores the package name placeholder
-(`com.example.project_name`), but it's still required for use by
-cross-platform tools.
-
-## Build a project
-
-For BlackBerry projects, please make sure you customize the
-`project.properties` file in your Cordova project's root directory.
-You need to do so to supply your BlackBerry signing key password, and
-specify locations for the BlackBerry WebWorks SDK and BlackBerry
-simulator executables.
-
- $ /path/to/my_new_project/cordova/build <platform>
- $ /path/to/my_new_project/cordova/build.bat <platform>
-
-## Launch simulator
-
-For BlackBerry projects, please make sure you customize the
-`project.properties` file in the root of your Cordova project folder.
-You need to do so to supply your BlackBerry signing key password, and
-specify locations for the BlackBerry WebWorks SDK and BlackBerry
-simulator executables.
-
- $ /path/to/my_new_project/cordova/run <platform>
-
-and then choose 'no' when prompted with:
-
- Do you have a BlackBerry device connected to your computer? (y/n)
- $ /path/to/my_new_project/cordova/run <platform>
-
-and then choose 'no' when prompted with:
-
- Do you have a BlackBerry device connected to your computer? (y/n)
-
-## Logging
-
-Unfortunately, streaming logs directly from the device is currently
-unsupported. However, BlackBerry offers built-in Web Inspector support
-for Playbook and BlackBerry smartphone devices running BlackBerry OS
-7.0 and above. You can also access your application's logs (including
-any calls to `console.log`) on your device by holding down the ''ALT''
-key from the home screen and typing ''lglg'' keys.
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/blackberry10/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry10/index.md b/docs/en/edge/guide/getting-started/blackberry10/index.md
deleted file mode 100644
index 9902522..0000000
--- a/docs/en/edge/guide/getting-started/blackberry10/index.md
+++ /dev/null
@@ -1,185 +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 Platform Guide
-==================================
-
-Apache Cordova is an application development platform that allows you to use common web technologies, primarily HTML5, JavaScript, and CSS, to create applications for mobile devices. Cordova uses a standard set of APIs to access common device features. Additional plugins allow you to access BlackBerry specific APIs, so that you can extend your application to tightly integrate with the BlackBerry 10 OS.
-
-Requirements
-------------
-
-Cordova for BlackBerry has the following software requirements:
-
-- Windows XP (32-bit) or Windows 7 (32-bit and 64-bit) or Mac OSX 10.6.4+
-- node.js (> 0.9.9) [Download node.js now](http://nodejs.org/)
-- BlackBerry 10 Native SDK. [Download the BlackBerry 10 Native SDK now.](http://developer.blackberry.com/native/download/)
-
-Setting up your signing keys
-----------------------------
-
-Before starting development, you'll need to register for your code signing key and debug token. The signing key allows you to sign your completed app so that you can distribute it through BlackBerry World. The debug token allows you to test an unsigned app on a BlackBerry 10 device. You do not need to create and install the debug token yourself; if you supply the keystore password, the build script will create and install the debug token for you.
-
-- [Register for your code signing key now.](https://www.blackberry.com/SignedKeys/codesigning.html)
-- [Set your computer up for code signing. ](http://developer.blackberry.com/html5/documentation/set_up_for_signing.html)
-- [Learn more about debug tokens.](http://developer.blackberry.com/html5/documentation/running_your_bb10_app_2008471_11.html)
-
-Creating your project
--------------------------
-
-To create a new project, you use the `create` command to set up the folder structure for your app.
-
-1. On the command line, navigate to the folder where you extracted Cordova.
-2. Run the `create` command using the following syntax:
- ```
- bin/create <path-to-project>
- ```
-
-This command creates the folder structure for your project at the specified location. All of your project resource files should be stored in the *<path-to-project>*/www folder, or in a subfolder within it.
-
-Adding and managing targets
----------------------------
-
-A target refers to a BlackBerry device or simulator that you will use to test your app. Targets are added directly to your project; you can add multiple targets to your project, each with a unique name. Then, when you want to deploy your app to a particular target, you can simply refer to that target by name when you run your script.
-
-###Add a target
-
-To add a target, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/target add <name> <ip-address> [-t <device | simulator>] [-p | --password <password>] [--pin <device-pin>]
-```
-
-where
-
-- `<name>` specifies a unique name for the target.
-- `<ip-address>` specifies the ip address of the BlackBerry device or simulator.
-- `-t <device | simulator>` specifies the target type. If not provided, the default value is device.
-- `-p|--password <password>` specifies the password for the device or simulator. This is required only if the device or simulator is password protected.
-- `--pin <device-pin>` specifies the PIN of the BlackBerry device, which identifies that device as a valid host for the debug token. This argument is required only if you are creating a debug token.
-
-###Remove a target
-
-To remove a target, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/target remove <name>
-```
-
-###Set a target as the default
-
-To specify a specific target as the default, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/target default <name>
-```
-
-Building your app
------------------
-
-To build your app, run the build script. You can build the app in either release mode or in debug mode.
-
-- When you build the app in release mode, you are preparing it for distribution through BlackBerry World. The script packages your app resources and plugins together in a .bar file, then signs the app.
-- When you build the app in debug mode, you are preparing it to be tested. The script packages your app resources and plugins together in a .bar file, but does not sign it. The script can also deploy the app onto a previously defined target. If you have not already created and installed a debug token, you can supply the keystore password, and the build script will create and install the debug token for you as well.
-
- Debug mode also enables Web Inspector for the app, which allows you to remotely inspect the source code. A prompt displays the URL that you can use to connect to and inspect your app. For more information on using Web Inspector, see [Debugging using Web Inspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
-
-###Build your app in release mode
-
-To build your app in release mode, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/build release -k|--keystorepass <password> [-b|--buildId <number>] [-p|--params <params-JSON-file>]
-```
-
-where
-
-- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications.
-- `-b|--buildId <number>` specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
-- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
-
-###Build your app in debug mode
-
-To build your app in release mode, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params <params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
-```
-
-where
-
-- `<target>` specifies the name of a previously added target. If `<target>` is not specified, the default target is used, if one has been created. This argument is only required if you want the script to deploy your app to a BlackBerry device or simulator and you have not created a default target. Additionally, if `<target>` is a device, then that device must be connected to your computer by USB connection or be connected to the same Wi-Fi network as your computer.
-- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications. This password is also used to create your debug token. This argument is only required if you want the script to create and install the debug token for you.
-- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools.
-- `-ll|--loglevel <level>` specifies the log level. The log level may be one of `error`, `warn`, or `verbose`.
-
-Note that all of these parameters are optional. If you have previously defined a default target (and installed a debug token, if that target is a BlackBerry device), you can run the script with no arguments, and the script will package your app and deploy it to the default target. For example:
-
-```
-<path-to-project>/cordova/build debug
-```
-
-Deploying an app
--------------------------
-
-You can test your app using either a BlackBerry device or a simulator. Before deploying your app, you must first create a target for the device or simulator you want to deploy your app to.
-
-The run script will first build your app. If you intend to deploy an app to a physical device for testing, you must first install a debug token on that device. If you specify the `--keystorepass <password>` argument when running the run script, the script will create and install the debug token for you. You do not need a debug token to test your app on a simulator, even if that app is unsigned.
-
-To deploy your app to a device or simulator, on a command line type the following command:
-
-```
-<path-to-project>/cordova/run <target> [--no-build]
-```
-
-where
-- `<target>` specifies the name of a previously added target. If `<target>` is a device, then that device must be connected to your computer by USB connection or be connected to the same Wi-Fi network as your computer.
-
-- `-no--build` will use the most recently built version of the application rather than re-building. This is useful to test an application in release mode.
-
-Adding and managing plugins
----------------------------
-
-To add additional functionality that is outside of the core features of Cordova, you'll need to add plugins. A plugin represents a set of APIs that provide access to additional features of the platform.
-
-In order to use a plugin, you must first add it into your project. Once added into your project, the plugin will be bundled with your project during the build process, to ensure that your app has access to all the APIs it needs.
-
-###Add a plugin
-
-To add a plugin, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/plugin add <path to plugin>
-```
-
-###Remove a plugin
-
-To remove a plugin, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/plugin rm <name>
-```
-
-###View a list of installed plugins
-
-To view a list of installed plugins, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/plugin ls
-```
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/blackberry10/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry10/tools.md b/docs/en/edge/guide/getting-started/blackberry10/tools.md
deleted file mode 100644
index 07ac1c6..0000000
--- a/docs/en/edge/guide/getting-started/blackberry10/tools.md
+++ /dev/null
@@ -1,179 +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 Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-If you need help with any command listed below, type the command along
-with the `-h` or `-help` arguments, which are supported by all
-commands and which provide descriptions for each of the available
-arguments.
-
-## create
-
-The 'create' command creates a new project:
-
-```
-bin/create <path-to-project>
-```
-
-## target
-
-The `target` command allows you to manage the BlackBerry device(s) or
-simulator that you will use to test your app. You can add or remove a
-target, or set a target as the default target.
-
-### Add a target
-
-```
-<path-to-project>/cordova/target add <name> <ip-address> <device | simulator> [-p | --password <password>] [--pin <device-pin>]
-```
-
-where
-
-- `<name>` specifies a unique name for the target.
-- `<ip-address>` specifies the ip address of the BlackBerry device or
- simulator.
-- `-p|--password <password>` specifies the password for the device or
- simulator. This is required only if the device or simulator is
- password protected.
-- `--pin <device-pin>` specifies the PIN of the BlackBerry device,
- which identifies that device as a valid host for the debug
- token. This argument is required only if you are creating a debug
- token.
-
-### Remove a target
-
-```
-<path-to-project>/cordova/target remove <name>
-```
-
-### Set a target as the default
-
-```
-<path-to-project>/cordova/target default <name>
-```
-
-## build
-
-The `build` command builds the project as a .bar file. You can build
-your app in either release mode (which produces a signed .bar file) or
-in debug mode (which produces an unsigned .bar file).
-
-### Build your project in release mode
-
-```
-<path-to-project>/cordova/build release -k|--keystorepass <password> [-b|--buildId <number>] [-p|--params <params-JSON-file>]
-```
-where
-
-- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications.
-- `-b|--buildId <number>` specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
-- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
-
-### Build your project in debug mode
-
-```
-<path-to-project>/cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params <params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
-```
-
-where
-
-- `<target>` specifies the name of a previously added target. If
- `<target>` is not specified, the default target is used, if one has
- been created. This argument is only required if you want the script
- to deploy your app to a BlackBerry device or simulator and you have
- not created a default target. Additionally, if `<target>` is a
- device, then that device must be connected to your computer by USB
- connection or be connected to the same Wi-Fi network as your
- computer.
-- `-k|--keystorepass <password>` specifies the password you defined
- when you configured your computer to sign applications. This
- password is also used to create your debug token. This argument is
- only required if you want the script to create and install the debug
- token for you.
-- `-p|--params <params-JSON-file>` specifies a JSON file containing
- additional parameters to pass to downstream tools.
-- `-ll|--loglevel <level>` specifies the log level. The log level may
- be one of `error`, `warn`, or `verbose`.
-
-If you have previously defined a default target (and previously
-installed a debug token, if that target is a BlackBerry device), you
-can run the script with no arguments, and the script will package your
-app and deploy it to the default target. For example:
-
-```
-<path-to-project>/cordova/build debug
-```
-
-## run
-
-The `run` command deploys the app on the specified BlackBerry device
-or a simulator. Before deploying your app, you must first create a
-target for the device or simulator you want to deploy your app to. The
-deploy script will deploy the most recent build of your app.
-
-```
-<path-to-project>/cordova/run <target>
-```
-
-where
-
-- `<target> `specifies the name of a previously added target. If
- `<target> `is a device, then that device must be connected to your
- computer by USB connection or be connected to the same Wi-Fi network
- as your computer.
-
-## plugin
-
-The `target` command allows you to add and remove plugins
-
-### Fetch a locally-hosted plugin
-
-```
-<path-to-project>/cordova/plugin fetch <path-to-plugin>
-```
-
-### View a list of installed plugins
-
-```
-<path-to-project>/cordova/plugin ls
-```
-
-### Add a plugin
-
-```
-<path-to-project>/cordova/plugin add <name>
-```
-
-### Remove a plugin
-
-```
-<path-to-project>/cordova/plugin rm <name>
-```
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/index.md b/docs/en/edge/guide/getting-started/index.md
deleted file mode 100644
index b26e5f1..0000000
--- a/docs/en/edge/guide/getting-started/index.md
+++ /dev/null
@@ -1,95 +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.
----
-
-Platform Guides
-======================
-
-Before developing for any of the platforms listed below, install
-cordova's command-line interface (CLI).
-(For details, see The Cordova Command-line Interface.)
-
-To develop Cordova applications, you must install SDKs for each mobile
-platform you are targeting. This installation is necessary regardless
-of whether you do the majority of your work in the SDK or use the CLI
-for your build cycle.
-
-Each _Platform Guide_ listed below tells you what you need to know to
-set up each platform's development environment: where to obtain the
-SDK, how to set up device emulators, how to connect devices for direct
-testing, and how to manage signing key requirements. Additional
-guides provide information on each platform's unique set of
-configuration options, instructions to add plugins, how to upgrade
-each platform, and platform-specific command-line tools that serve as
-a lower-level alternative to the `cordova` command-line utility.
-
-## Android
-
-* Android Platform Guide
-* Android Configuration
-* Android WebViews
-* Android Plugins
-* Android Command-line Tools
-* Upgrading Android
-
-## BlackBerry
-
-* BlackBerry Platform Guide
-* BlackBerry Configuration
-* Blackberry Command-line Tools
-* Upgrading BlackBerry
-
-## BlackBerry 10
-
-<!-- if "BlackBerry 10 Plugins" are available, how about WebViews? -->
-* BlackBerry 10 Platform Guide
-* BlackBerry 10 Plugins
-* Blackberry 10 Command-line Tools
-
-## iOS
-
-* iOS Platform Guide
-* iOS Configuration
-* iOS WebViews
-* iOS Plugins
-* iOS Command-line Tools
-* Upgrading iOS
-
-## Windows Phone
-
-* Windows Phone 8 Platform Guide
-* Windows Phone 8 Configuration
-* Windows Phone 7 Platform Guide
-* Windows Phone 7 Configuration
-* Windows Phone Command-line Tools
-* Upgrading Windows Phone
-
-## Windows 8
-
-* Windows 8 Platform Guide
-* Windows 8 Configuration
-* Windows 8 Command-line Tools
-* Upgrading Windows 8
-
-## Tizen
-
-* Tizen Platform Guide
-
-## FirefoxOS
-
-* FirefoxOS Configuration
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/ios/index.md b/docs/en/edge/guide/getting-started/ios/index.md
deleted file mode 100644
index b326712..0000000
--- a/docs/en/edge/guide/getting-started/ios/index.md
+++ /dev/null
@@ -1,210 +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 Platform 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 simulator
-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 simulator, 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. 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 Command-line Interface. For example, in a source-code directory:
-
- $ cordova create hello com.example.hello "Hello World"
- $ cd hello
- $ cordova platform add android
- $ 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:
-
- 
-
-## 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/cfebdc34/docs/en/edge/guide/getting-started/ios/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/ios/tools.md b/docs/en/edge/guide/getting-started/ios/tools.md
deleted file mode 100644
index c37dbcd..0000000
--- a/docs/en/edge/guide/getting-started/ios/tools.md
+++ /dev/null
@@ -1,59 +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 Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-The iOS command-line tools are built upon shell scripts and rely on
-Xcode command-line tools such as `xcode-select` and `xcodebuild`.
-
-## 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.
-
- $ ./path/to/cordova-ios/bin/create /path/to/my_new_project com.example.project_name ProjectName
-
-## Build a project
-
- $ /path/to/my_new_project/cordova/build
-
-## Run app on emulator
-
- $ /path/to/my_new_project/cordova/run
-
-## Releasing
-
- $ /path/to/my_new_project/cordova/release
-
-## Logging
-
- $ /path/to/my_new_project/cordova/log
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/tizen/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/tizen/index.md b/docs/en/edge/guide/getting-started/tizen/index.md
deleted file mode 100644
index 7e7c913..0000000
--- a/docs/en/edge/guide/getting-started/tizen/index.md
+++ /dev/null
@@ -1,112 +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 Platform Guide
-=========================
-
-## 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 the `cordova` utility in conjunction with
-the Tizen SDK. See The Cordova 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 you 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 & rarr; Tizen Web Application__:
-
- 
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/windows-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-8/index.md b/docs/en/edge/guide/getting-started/windows-8/index.md
deleted file mode 100644
index b663d3a..0000000
--- a/docs/en/edge/guide/getting-started/windows-8/index.md
+++ /dev/null
@@ -1,111 +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.
----
-
-Windows 8 Platform Guide
-==================================
-
-This guide describes how to set up your Cordova development
-environment and run a sample application. Note that Cordova used to
-be called PhoneGap, so some of the sites still use the old PhoneGap
-name.
-
-Microsoft deprecated the name _Metro-style apps_ in Windows 8 and
-Windows RT. MSDN now refers to this type of app as a _Windows Store_
-app, and this guide follows that convention. Also, in this guide
-_Windows 8_ signifies both Windows 8 and Windows RT.
-
-1. Requirements
----------------
-
-- Windows 8
-
-- Visual Studio 2012 Professional or better, or Visual Studio 2012 Express for Windows 8
-
-Follow the instructions [here](http://www.windowsstore.com/) to submit your apps Windows Store.
-
-2. Install SDK + Cordova
-----------------------------
-
-- Set up your preferred variant of Visual Studio 2012. All of the product's paid versions (Professional, etc.) let you build Windows Store apps. You need **Express for Windows 8** to build Windows Store apps using the [Express editions](http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products).
-- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-8` subfolder.
-
-3. Set up New Project
---------------------
-
-You can already build Windows 8 apps using the _HTML/JavaScript track_
-available in Windows Store apps. Use Cordova in Windows Store apps to
-expose the same APIs as on other Cordova-supported platforms.
-
-- Open Visual Studio 2012 and choose **New Project**.
-- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as **CordovaWin8Foo** as in this example.
-
- 
-
-- Microsoft continues to use `default.html` as the default home page, but most web developers use `index.html`. (Plus it's likely that in the other platform variants of your project you are using `index.html` as the name of your default page.) To fix this, in Solution Explorer rename the `default.html` file to `index.html`. Then double-click the `package.appxmanifest` file and change the **Start page** value to `index.html`.
-
- 
-
-- To include `cordova.js` in your project, right-click on the **js** folder in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the **lib\windows-8** folder noted above.
-
-- Edit the code for `index.html`. Add a reference to `cordova.js`. You can do this manually, or by dragging the file from Solution Explorer.
-
-### Adding the reference...
- <!-- WinJS references -->
- <link href="//Microsoft.WinJS.1.0/css/ui-dark.css" rel="stylesheet" />
- <script src="//Microsoft.WinJS.1.0/js/base.js"></script>
- <script src="//Microsoft.WinJS.1.0/js/ui.js"></script>
-
- <!-- Cordova -->
- <script src="/js/cordova.js"></script>
-
- <!-- CordovaWin8Foo references -->
- <link href="/css/default.css" rel="stylesheet" />
- <script src="/js/default.js"></script>
-
-- Next, add some code that demonstrates Cordova is working.
-
-### Adding a 'deviceready' handler...
- <body>
- <p>Content goes here</p>
-
- <script type="text/javascript">
-
- console.log("Subscribing...");
- document.addEventListener("deviceready", function () {
-
- navigator.notification.alert("The device is ready!");
-
- });
-
- </script>
-
- </body>
-
-5. Test the Project
--------------------------------
-
-- Run the project from Visual Studio. You'll see the message box appear:
-
- 
-
-Done!
------
-
-That's it! You're now ready to build Windows Store apps with Cordova.
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/windows-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-8/tools.md b/docs/en/edge/guide/getting-started/windows-8/tools.md
deleted file mode 100644
index 9fbb26d..0000000
--- a/docs/en/edge/guide/getting-started/windows-8/tools.md
+++ /dev/null
@@ -1,44 +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.
----
-
-# Windows 8 Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-## Windows 8
-
-The Windows 8 command-line tools only support creating new projects.
-Commands must be run from a cmd or powershell prompt.
-
-## Create a project
-
-Run the `create` command with the following parameters:
-
-* Path to your new Cordova Windows 8 project
-* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
-* Project name
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/windows-phone-7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-phone-7/index.md b/docs/en/edge/guide/getting-started/windows-phone-7/index.md
deleted file mode 100644
index ca9f08f..0000000
--- a/docs/en/edge/guide/getting-started/windows-phone-7/index.md
+++ /dev/null
@@ -1,95 +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.
----
-
-Windows Phone 7 Platform Guide
-==================================
-
-## Requirements and Support
-
-Requires Windows 7, Windows 8 or Windows Vista with SP2. Running
-Windows as a virtual machine does not work well, so Mac users should
-set up a Bootcamp partition to run Windows 7 or Vista.
-
-To install the app onto a device or submit it to the market place, you
-need to become an
-[App Hub member](http://create.msdn.com/en-US/home/membership).
-
-Developers should use the the `cordova` utility in conjunction with
-the Windows Phone SDK. Before installing it on Windows, open a
-command line and type `git` to make sure it is installed. If not,
-download it from [mysysgit.github.io](http://mysysgit.github.io). When
-prompted to configure your PATH, choose the option: __Run Git and
-included Unix tools from the Windows Command Prompt__. Once git is
-available, follow the instructions in The Cordova Command-line
-Interface for information how to install it, add projects, then build
-and deploy a project.
-
-## Install the SDK
-
-Download and install the
-[Windows Phone SDK](http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27570/)
-
-## Open a Project in the SDK
-
-After installing the `cordova` utility, use the following to create a
-new project, then add and build the Windows Phone 7 project.
-
- $ cordova create hello com.example.hello "Hello World"
- $ cd hello
- $ cordova platform add wp7
- $ cordova build
-
-Open Visual Studio and choose __Open Project__. Navigate to the
-`hello/platforms/wp7` directory and choose the `Hello_World.sln` file.
-The SDK displays the directory's contents:
-
-
-
-At this point you can modify the app within the SDK, but running the
-`build` or `prepare` commands again wipes out local changes. If Visual
-Studio is open, it alerts you about modified files and offers you the
-option to reload them. See The Cordova Command-line Interface for
-more information.
-
-## Deploy to Emulator
-
-Within the SDK, select the __Windows Phone Emulator__ target from the
-popup menu in the main menu bar, and press the green button to run the
-emulator:
-
-
-
-The app displays on the emulator's home screen as it would on a real
-device:
-
-
-
-## Deploy to Device
-
-To test your application on a device, the device must be registered.
-MSDN provides
-[documentation][http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx]
-to help deploy and test your Windows Phone.
-
-Once registered, you need to make sure the phone is connected via USB
-with its screen unlocked. In Visual Studio, choose the __Windows Phone
-Device__ target and press the green button to run it:
-
-
-
[09/20] [CB-3827] rename 'getting-started' dirs as 'platforms'
Posted by mw...@apache.org.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/windows-phone-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-phone-8/index.md b/docs/en/edge/guide/getting-started/windows-phone-8/index.md
deleted file mode 100644
index 9829038..0000000
--- a/docs/en/edge/guide/getting-started/windows-phone-8/index.md
+++ /dev/null
@@ -1,135 +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.
----
-
-Windows Phone 8 Platform Guide
-==================================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-__NOTE:__ Applications built with Apache Cordova for Windows Phone 8 run only on Windows Phone 8 devices. If you want to target both 7.5 'and' 8 devices, then use Apache Cordova for Windows Phone 7, which does not have all the advanced features included in IE10, but implements the same APIs.
-
-1. System Requirements
----------------
-
-- Operating System:
- - Windows 8 or Windows 8 Pro
- - The 64-bit version (x64) of Windows is required for the SDK.
- - The Pro version is recommended so you can run a device emulator.
-
-- Hardware:
- - 6.5 GB of free hard disk space
- - 4 GB RAM
- - 64-bit (x64) CPU
-
-- Windows Phone 8 Emulator
- - The phone emulator uses Hyper-V, so this list includes those pre-requisites.
- - Windows 8 Pro 64-bit edition or greater
- - Requires a processor that supports virtualization and [Second Level Address Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation)
- - See the [list of Intel processors that support VT-x (virtualization) and EPT (SLAT)](http://ark.intel.com/Products/VirtualizationTechnology)
- - Enable the virtualization capability (i.e., VT-x on Intel) in your BIOS settings, as usually this is disabled by default.
-
-- SDK + IDE ( Visual Studio )
- - Visual Studio 2012 Professional, Premium, or Ultimate. Note that Visual Studio Express for Windows Phone (included in the SDK) is not recommended because you can not build the template (see below) with VS Express, as it does not have the __Export Template__ functionality, which is only in VS Pro or higher.
-
-- Register and pay for a [Windows Phone Dev Center](http://dev.windowsphone.com/en-us/publish) account if you want to install your app on a real device and/or submit it to Market Place.
-
-__NOTE:__ Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for [Windows Phone on a Mac](http://aka.ms/BuildaWP8apponaMac).
-
-2. Install SDK + Cordova
-----------------------------
-
-- Download and install [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
-- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-phone-8` subfolder.
-- Copy the file CordovaWP8_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
-
-2.1. Building the template
------------------------------
-
-__NOTE:__ this step may not be required. If the lib\windows-phone directory already contains a file CordovaWP8_x_x_x.zip then you may skip this step.
-
-In order to simplify the development process, Cordova comes with a Visual Studio template that allows creating a Cordova application rapidly. This template can be modified if needed and the below steps indicate how to proceed if you want to modify and re-generate the template.
-
-- Open the `lib\windows-phone\templates\standalone\CordovaSolution.sln` file in Visual Studio Express for Windows Phone.
-- Select __Export Template...__ from the __File__ menu.
-- Choose template type __Project template__
-- Give the exported template a name, such as `CordovaStarter-2.1.0`, which produces a `CordovaStarter-2.1.0.zip` archive.
-- Optionally, you may add a description, icon image, and preview image. These display in Visual Studio's __New Project__ dialog.
-- __NOTE:__ If you select __Automatically import the template...__, then you don't need to copy the `.zip` file over as outlined in step 2.
-- Press __Finish__
-
-2.2 About the different templates
----------------------------------
-
-Apache Cordova for Windows Phone 8 only supports the standalone template.
-
-The 'Stand-Alone' template includes _all_ the source code for Apache
-Cordova. This project is easier to fine-tune to use just the features
-you need, thereby working around the permissions issues of the 'Full'
-template, however this type of project is more difficult to update, as
-you update individual files within your project and manage any
-dependancies yourself. In order to exclude an unused API, simply
-right-click-select the __Command__ class file in Visual Studio and
-choose __do not include in project__.
-
-3. Set up New Project
---------------------
-
-- Open Visual Studio Express for Windows Phone and choose **New Project**.
-- Select **CordovaWP8**. (The version number is displayed in the template description.)
-- Give the project a name, and select __OK__.
-
-
-
-4. Review the project structure
--------------------------------
-
-- The 'www' folder contains your Cordova html/js/css and any other resources included in your app.
-- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
-- Note: This screen capture was from the cordova-2.3.0 download, your listing will vary based on the actual version installed.
-
-
-
-5. Build and Deploy to Emulator
--------------------------------
-
-- Make sure **Windows Phone Emulator** is selected in the main drop-down menu.
-- Press the green **play** button next to the drop-down menu to start debugging, or type __F5__.
-
-
-
-6. Build your project for the device
-------------------------------------
-
-In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 8.
-
-- Make sure your phone is connected, and the screen is unlocked.
-- In Visual Studio, select 'Device' from the top drop-down menu.
-- Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
-
-
-
-Done!
------
-
-Further Reading
--------
-
-For more details on the specific differences between IE10 and WebKit browsers, and how to support both MS has a helpful [guide here](http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx)
-
-[register-url]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-phone-8/tools.md b/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
deleted file mode 100644
index df821e2..0000000
--- a/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
+++ /dev/null
@@ -1,77 +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.
----
-
-# Windows Phone Command-line Tools
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-## Windows Phone
-
-The Windows Phone command-line tools support creating, building, and
-running new projects. Commands must be run from a cmd or powershell
-prompt.
-
-The WP8 repo now includes code for building both WP7 + WP8 apps. The
-repo has subfolders for each: wp7/ and wp8/
-
-## 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 Windows Phone 7 and 8:
-
- $ C:\path\to\cordova-wp8\wp7\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
- $ C:\path\to\cordova-wp8\wp8\bin\create C:\path\to\my_new_project com.example.project_name ProjectName
-
-## Building your project (cleans then builds)
-
-* Debug
-
- $ C:\path\to\my_new_project\cordova\build --debug
-
-* Release
-
- $ C:\path\to\my_new_project\cordova\build --release
-
-## Running your application
-
-Run the 'run' command with the following *optional* parameters
-
-* Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
-* Build specification. This includes `--debug`, `--release`, or `--nobuild`.
-
- $ C:\path\to\my_new_project\cordova\run [Target] [Build]
-
-By default the `run` command will look for a connected device, if no
-device is found it will look for any started emulators. If you have
-multiple emulators, you can specify a target ID.
-
-## Cleaning
-
- $ C:\path\to\my_new_project\cordova\clean
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/overview/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/overview/index.md b/docs/en/edge/guide/overview/index.md
index a94de23..4dcbb7b 100644
--- a/docs/en/edge/guide/overview/index.md
+++ b/docs/en/edge/guide/overview/index.md
@@ -169,14 +169,14 @@ available for each mobile platform:
</tr>
<tr>
- <th><a href="guide_getting-started_index.md.html">IDE platform support</a></th>
- <td data-col="android" class="y"><a href="guide_getting-started_android_index.md.html"> </a></td>
- <td data-col="blackberry" class="y"><a href="guide_getting-started_blackberry_index.md.html"> </a></td>
- <td data-col="blackberry10" class="y"><a href="guide_getting-started_blackberry10_index.md.html"> </a></td>
- <td data-col="ios" class="y"><a href="guide_getting-started_ios_index.md.html"> </a></td>
- <td data-col="winphone7" class="y"><a href="guide_getting-started_windows-phone-7_index.md.html"> </a></td>
- <td data-col="winphone8" class="y"><a href="guide_getting-started_windows-phone-8_index.md.html"> </a></td>
- <td data-col="win8" class="y"><a href="guide_getting-started_windows-8_index.md.html"> </a></td>
+ <th><a href="guide_platforms_index.md.html">IDE platform support</a></th>
+ <td data-col="android" class="y"><a href="guide_platforms_android_index.md.html"> </a></td>
+ <td data-col="blackberry" class="y"><a href="guide_platforms_blackberry_index.md.html"> </a></td>
+ <td data-col="blackberry10" class="y"><a href="guide_platforms_blackberry10_index.md.html"> </a></td>
+ <td data-col="ios" class="y"><a href="guide_platforms_ios_index.md.html"> </a></td>
+ <td data-col="winphone7" class="y"><a href="guide_platforms_windows-phone-7_index.md.html"> </a></td>
+ <td data-col="winphone8" class="y"><a href="guide_platforms_windows-phone-8_index.md.html"> </a></td>
+ <td data-col="win8" class="y"><a href="guide_platforms_windows-8_index.md.html"> </a></td>
</tr>
<tr>
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/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
new file mode 100644
index 0000000..ed21185
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/index.md
@@ -0,0 +1,190 @@
+---
+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 describes how to set up your SDK development environment to
+deploy Cordova apps for Android devices.
+
+## 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 the `cordova` utility in conjunction with
+the Android SDK. See The Cordova 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 Command-line Interface. For example, in a source-code directory:
+
+ $ cordova create hello com.example.hello "Hello World"
+ $ 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 folder.
+* 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/cfebdc34/docs/en/edge/guide/platforms/android/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/tools.md b/docs/en/edge/guide/platforms/android/tools.md
new file mode 100644
index 0000000..09fcfdc
--- /dev/null
+++ b/docs/en/edge/guide/platforms/android/tools.md
@@ -0,0 +1,80 @@
+---
+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 Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## 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 and Windows:
+
+ $ /path/to/cordova-android/bin/create /path/to/project com.example.project_name ProjectName
+ $ C:\path\to\cordova-android\bin\create.bat C:\path\to\project com.example.project_name ProjectName
+
+## Build
+
+This cleans then builds a project.
+
+Debug, on Mac or Windows:
+
+ $ /path/to/project/cordova/build --debug
+ $ C:\path\to\project\cordova\build.bat --debug
+
+Release, on Mac 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
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/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
new file mode 100644
index 0000000..e17416d
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry/index.md
@@ -0,0 +1,181 @@
+---
+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 Platform Guide
+============================
+
+Cordova for BlackBerry makes use of the [BlackBerry WebWorks framework](https://bdsc.webapps.blackberry.com/html5). BlackBerry WebWorks tooling is available for Windows or Mac environments.
+
+WebWorks applications can ONLY be deployed to the following BlackBerry platforms:
+
+* BlackBerry OS 5.0 and higher
+* BlackBerry PlayBook
+* BlackBerry 10 (QNX)
+
+1. Requirements
+---------------
+
+- Windows XP (32-bit) or Windows 7 (32-bit and 64-bit) or Mac OSX 10.6.4+
+- Java Development Kit (JDK)
+ - Windows: [Oracle JDK](http://www.oracle.com/technetwork/java/javase/downloads/index.html#jdk) (32-Bit Version)
+ - Mac OS X: Versions prior to Mac OS X 10.7 provided Java by default. OS X 10.7+ requires installation of [Java](http://support.apple.com/kb/DL1421).
+- Apache Ant
+ - Windows: [Apache Ant](http://ant.apache.org/bindownload.cgi).
+ - Mac OS X: Apache Ant is bundled with Java install.
+
+2. Install the WebWorks SDK
+-------------------------
+Download and install the appropriate WebWorks SDKs for your development. BlackBerry 10, BlackBerry PlayBook, and BlackBerry Smartphone WebWorks SDKs can all be downloaded from the following locations. Please note that BlackBerry PlayBook development requires the Adobe Air SDK as well.
+
+- [BlackBerry 10 (QNX) SDK] (https://developer.blackberry.com/html5/download/#blackberry10)
+- [BlackBerry PlayBook SDK] (https://developer.blackberry.com/html5/download/#playbook) & [Adobe Air SDK](http://www.adobe.com/devnet/air/air-sdk-download.html)
+- [BlackBerry Smartphones SDK] (https://developer.blackberry.com/html5/download/#smartphones)
+
+3. Register for Signing Keys
+-------------------------
+If you wish to publish your application on BlackBerry App World, or deploy on an actual device you’ll need to register for a set of free Code Signing Keys.
+
+To register for Signing Keys visit, and complete the [BlackBerry Keys Order Form](https://www.blackberry.com/SignedKeys).
+
+Once you receive your Signing Keys, they'll need to be setup. To learn how to setup your Signing Keys visit the [BlackBerry HTML5/WebWorks website](https://developer.blackberry.com/html5/documentation/signing_setup_bb10_apps_2008396_11.html).
+
+4. Install Cordova
+-------------------------
+
+Download and extract the latest copy of [Cordova](http://cordova.apache.org/#download).
+
+5. Set up New Project
+--------------------
+
+- Open up a command prompt/terminal and navigate to where you extracted Cordova.
+- There is a directory for each platform that Cordova supports. CD into the blackberry directory.
+- The blackberry directory contains several directories. The `example` folder contains a complete Cordova project. Copy the `example` folder to another location on your computer.
+- Change to the newly created directory.
+- Open up the project.properties file with your favorite editor and edit the entries for the WebWorks SDKs you are using. For example...
+
+BlackBerry 10 (QNX)
+- `qnx.bbwp.dir=C:\\Program Files (x86)\\Research In Motion\\BlackBerry 10 WebWorks SDK 1.0.2.9`
+
+BlackBerry PlayBook
+- `playbook.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks SDK for TabletOS 2.1.0.6\\bbwp`
+
+BlackBerry Smartphone (OS5-7)
+- `blackberry.bbwp.dir=C:\\Program Files\\Research In Motion\\BlackBerry WebWorks Packager`
+
+6. Hello World
+--------------
+
+Build the Cordova sample project by typing `./cordova/build <target>` in your command prompt/terminal while you are in your project's directory. Replace `<target>` with either `qnx` `playbook` or `blackberry`. For example...
+
+BlackBerry 10 (QNX)
+- `./cordova/build qnx`
+
+BlackBerry PlayBook
+- `./cordova/build playbook`
+
+BlackBerry Smartphone (OS5-7)
+- `./cordova/build blackberry`
+
+7A. Deploy to Simulator
+--------------------------------------
+
+BlackBerry smartphone simulators are only available on Windows. BlackBerry 10, and PlayBook simulators require VMWare Player (Windows) or VMWare Fusion (Mac OS X). The WebWorks SDK provides a default simulator. Additional simulators are [available](http://us.blackberry.com/developers/resources/simulators.jsp).
+
+For instructions on installing simulators, please visit the following link(s):
+- [BlackBerry 10](https://developer.blackberry.com/html5/documentation/using_the_bb10_simulator_2008466_11.html)
+- [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)
+
+- Open the project.properties file with your favorite editor and customize the following properties.
+
+BlackBerry 10
+- `qnx.sim.ip`
+- `qnx.sim.password`
+- __NOTE:__ IP address of simulator obtained when placing the simulator in developer mode through simulator security settings. Simulator password can be set through simulator security settings.
+
+Playbook
+- `playbook.sim.ip` :
+- `playbook.sim.password`
+- __NOTE:__ IP address of simulator obtained when placing the simulator in developer mode through simulator security settings. Simulator password can be set through simulator security settings.
+
+Smartphone (Optional)
+- `blackberry.sim.dir`
+- `blackberry.sim.bin`
+- __NOTE:__ On windows file separator '\' must be escaped when specifying directories. For example `C:\\Program Files\\BlackBerry\\Simulator`.
+
+While in your project directory, in command prompt/terminal type `./cordova/run <target>`. Replace `<target>` with either `qnx`, `playbook`, or `blackberry`. Note, for BlackBerry 10 and PlayBook, the simulator virtual image must already be started. For example...
+
+BlackBerry 10 (QNX)
+- `./cordova/run qnx`
+
+BlackBerry PlayBook
+- `./cordova/run playbook`
+
+BlackBerry Smartphone (OS5-7)
+- `./cordova/run blackberry`
+
+When prompted __Do you have a BlackBerry device connected to your computer? (y/n)__, answer __n__.
+
+The application is installed to the simulator's home screen. Note that on BlackBerry OS 5, it is installed in the `Downloads` folder.
+
+7B. Deploy to Device (Windows and Mac)
+--------------------------------------
+
+To deploy your app to a device you must have registered for, and setup BlackBerry Code Signing Keys. See section 3 for details. Also, to deploy apps on BlackBerry 10 or PlayBook, the device must be set to Development Mode which can be enabled from the __Settings → Security__ menu.
+
+- Open the project.properties file with your favorite editor and customize the following properties:
+
+BlackBerry 10 (QNX)
+- `qnx.sigtool.password`
+- `qnx.device.ip`
+- `qnx.device.password`
+
+BlackBerry PlayBook
+- `playbook.sigtool.csk.password`
+- `playbook.sigtool.p12.password`
+- `playbook.device.ip`
+- `playbook.device.password`
+
+BlackBerry Smartphone (OS5-7)
+- Smartphone (Optional)
+- `blackberry.sigtool.password`
+
+While in your project directory, in command prompt/terminal type `./cordova/run <target>`. Replace `<target>` with either `qnx`, `playbook`, or `blackberry`. For example...
+
+BlackBerry 10 (QNX)
+- `./cordova/run qnx`
+
+BlackBerry PlayBook
+- `./cordova/run playbook`
+
+BlackBerry Smartphone (OS5-7)
+- `./cordova/run blackberry`
+
+When prompted __Do you have a BlackBerry device connected to your computer? (y/n)__, answer __y__.
+
+The application is installed to the device's home screen. Note, on BlackBerry OS 5 the application is installed in the Downloads folder.
+
+Additional Information
+----------------------
+
+The following articles provide help to issues you may encounter when developing a Cordova application which is based on 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/cfebdc34/docs/en/edge/guide/platforms/blackberry/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/tools.md b/docs/en/edge/guide/platforms/blackberry/tools.md
new file mode 100644
index 0000000..8bd2987
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry/tools.md
@@ -0,0 +1,84 @@
+---
+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 Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## 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 and Windows:
+
+ $ /path/to/cordova-blackberry-webworks/bin/create /path/to/my_new_project com.example.project_name ProjectName
+ $ /path/to/cordova-blackberry-webworks/bin/create.bat /path/to/my_new_project com.example.project_name ProjectName
+
+__NOTE:__ The Blackberry platform ignores the package name placeholder
+(`com.example.project_name`), but it's still required for use by
+cross-platform tools.
+
+## Build a project
+
+For BlackBerry projects, please make sure you customize the
+`project.properties` file in your Cordova project's root directory.
+You need to do so to supply your BlackBerry signing key password, and
+specify locations for the BlackBerry WebWorks SDK and BlackBerry
+simulator executables.
+
+ $ /path/to/my_new_project/cordova/build <platform>
+ $ /path/to/my_new_project/cordova/build.bat <platform>
+
+## Launch simulator
+
+For BlackBerry projects, please make sure you customize the
+`project.properties` file in the root of your Cordova project folder.
+You need to do so to supply your BlackBerry signing key password, and
+specify locations for the BlackBerry WebWorks SDK and BlackBerry
+simulator executables.
+
+ $ /path/to/my_new_project/cordova/run <platform>
+
+and then choose 'no' when prompted with:
+
+ Do you have a BlackBerry device connected to your computer? (y/n)
+ $ /path/to/my_new_project/cordova/run <platform>
+
+and then choose 'no' when prompted with:
+
+ Do you have a BlackBerry device connected to your computer? (y/n)
+
+## Logging
+
+Unfortunately, streaming logs directly from the device is currently
+unsupported. However, BlackBerry offers built-in Web Inspector support
+for Playbook and BlackBerry smartphone devices running BlackBerry OS
+7.0 and above. You can also access your application's logs (including
+any calls to `console.log`) on your device by holding down the ''ALT''
+key from the home screen and typing ''lglg'' keys.
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/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
new file mode 100644
index 0000000..9902522
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry10/index.md
@@ -0,0 +1,185 @@
+---
+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 Platform Guide
+==================================
+
+Apache Cordova is an application development platform that allows you to use common web technologies, primarily HTML5, JavaScript, and CSS, to create applications for mobile devices. Cordova uses a standard set of APIs to access common device features. Additional plugins allow you to access BlackBerry specific APIs, so that you can extend your application to tightly integrate with the BlackBerry 10 OS.
+
+Requirements
+------------
+
+Cordova for BlackBerry has the following software requirements:
+
+- Windows XP (32-bit) or Windows 7 (32-bit and 64-bit) or Mac OSX 10.6.4+
+- node.js (> 0.9.9) [Download node.js now](http://nodejs.org/)
+- BlackBerry 10 Native SDK. [Download the BlackBerry 10 Native SDK now.](http://developer.blackberry.com/native/download/)
+
+Setting up your signing keys
+----------------------------
+
+Before starting development, you'll need to register for your code signing key and debug token. The signing key allows you to sign your completed app so that you can distribute it through BlackBerry World. The debug token allows you to test an unsigned app on a BlackBerry 10 device. You do not need to create and install the debug token yourself; if you supply the keystore password, the build script will create and install the debug token for you.
+
+- [Register for your code signing key now.](https://www.blackberry.com/SignedKeys/codesigning.html)
+- [Set your computer up for code signing. ](http://developer.blackberry.com/html5/documentation/set_up_for_signing.html)
+- [Learn more about debug tokens.](http://developer.blackberry.com/html5/documentation/running_your_bb10_app_2008471_11.html)
+
+Creating your project
+-------------------------
+
+To create a new project, you use the `create` command to set up the folder structure for your app.
+
+1. On the command line, navigate to the folder where you extracted Cordova.
+2. Run the `create` command using the following syntax:
+ ```
+ bin/create <path-to-project>
+ ```
+
+This command creates the folder structure for your project at the specified location. All of your project resource files should be stored in the *<path-to-project>*/www folder, or in a subfolder within it.
+
+Adding and managing targets
+---------------------------
+
+A target refers to a BlackBerry device or simulator that you will use to test your app. Targets are added directly to your project; you can add multiple targets to your project, each with a unique name. Then, when you want to deploy your app to a particular target, you can simply refer to that target by name when you run your script.
+
+###Add a target
+
+To add a target, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/target add <name> <ip-address> [-t <device | simulator>] [-p | --password <password>] [--pin <device-pin>]
+```
+
+where
+
+- `<name>` specifies a unique name for the target.
+- `<ip-address>` specifies the ip address of the BlackBerry device or simulator.
+- `-t <device | simulator>` specifies the target type. If not provided, the default value is device.
+- `-p|--password <password>` specifies the password for the device or simulator. This is required only if the device or simulator is password protected.
+- `--pin <device-pin>` specifies the PIN of the BlackBerry device, which identifies that device as a valid host for the debug token. This argument is required only if you are creating a debug token.
+
+###Remove a target
+
+To remove a target, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/target remove <name>
+```
+
+###Set a target as the default
+
+To specify a specific target as the default, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/target default <name>
+```
+
+Building your app
+-----------------
+
+To build your app, run the build script. You can build the app in either release mode or in debug mode.
+
+- When you build the app in release mode, you are preparing it for distribution through BlackBerry World. The script packages your app resources and plugins together in a .bar file, then signs the app.
+- When you build the app in debug mode, you are preparing it to be tested. The script packages your app resources and plugins together in a .bar file, but does not sign it. The script can also deploy the app onto a previously defined target. If you have not already created and installed a debug token, you can supply the keystore password, and the build script will create and install the debug token for you as well.
+
+ Debug mode also enables Web Inspector for the app, which allows you to remotely inspect the source code. A prompt displays the URL that you can use to connect to and inspect your app. For more information on using Web Inspector, see [Debugging using Web Inspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
+
+###Build your app in release mode
+
+To build your app in release mode, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/build release -k|--keystorepass <password> [-b|--buildId <number>] [-p|--params <params-JSON-file>]
+```
+
+where
+
+- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications.
+- `-b|--buildId <number>` specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
+- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
+
+###Build your app in debug mode
+
+To build your app in release mode, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params <params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
+```
+
+where
+
+- `<target>` specifies the name of a previously added target. If `<target>` is not specified, the default target is used, if one has been created. This argument is only required if you want the script to deploy your app to a BlackBerry device or simulator and you have not created a default target. Additionally, if `<target>` is a device, then that device must be connected to your computer by USB connection or be connected to the same Wi-Fi network as your computer.
+- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications. This password is also used to create your debug token. This argument is only required if you want the script to create and install the debug token for you.
+- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools.
+- `-ll|--loglevel <level>` specifies the log level. The log level may be one of `error`, `warn`, or `verbose`.
+
+Note that all of these parameters are optional. If you have previously defined a default target (and installed a debug token, if that target is a BlackBerry device), you can run the script with no arguments, and the script will package your app and deploy it to the default target. For example:
+
+```
+<path-to-project>/cordova/build debug
+```
+
+Deploying an app
+-------------------------
+
+You can test your app using either a BlackBerry device or a simulator. Before deploying your app, you must first create a target for the device or simulator you want to deploy your app to.
+
+The run script will first build your app. If you intend to deploy an app to a physical device for testing, you must first install a debug token on that device. If you specify the `--keystorepass <password>` argument when running the run script, the script will create and install the debug token for you. You do not need a debug token to test your app on a simulator, even if that app is unsigned.
+
+To deploy your app to a device or simulator, on a command line type the following command:
+
+```
+<path-to-project>/cordova/run <target> [--no-build]
+```
+
+where
+- `<target>` specifies the name of a previously added target. If `<target>` is a device, then that device must be connected to your computer by USB connection or be connected to the same Wi-Fi network as your computer.
+
+- `-no--build` will use the most recently built version of the application rather than re-building. This is useful to test an application in release mode.
+
+Adding and managing plugins
+---------------------------
+
+To add additional functionality that is outside of the core features of Cordova, you'll need to add plugins. A plugin represents a set of APIs that provide access to additional features of the platform.
+
+In order to use a plugin, you must first add it into your project. Once added into your project, the plugin will be bundled with your project during the build process, to ensure that your app has access to all the APIs it needs.
+
+###Add a plugin
+
+To add a plugin, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/plugin add <path to plugin>
+```
+
+###Remove a plugin
+
+To remove a plugin, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/plugin rm <name>
+```
+
+###View a list of installed plugins
+
+To view a list of installed plugins, on the command line, type the following command:
+
+```
+<path-to-project>/cordova/plugin ls
+```
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/blackberry10/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry10/tools.md b/docs/en/edge/guide/platforms/blackberry10/tools.md
new file mode 100644
index 0000000..07ac1c6
--- /dev/null
+++ b/docs/en/edge/guide/platforms/blackberry10/tools.md
@@ -0,0 +1,179 @@
+---
+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 Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+If you need help with any command listed below, type the command along
+with the `-h` or `-help` arguments, which are supported by all
+commands and which provide descriptions for each of the available
+arguments.
+
+## create
+
+The 'create' command creates a new project:
+
+```
+bin/create <path-to-project>
+```
+
+## target
+
+The `target` command allows you to manage the BlackBerry device(s) or
+simulator that you will use to test your app. You can add or remove a
+target, or set a target as the default target.
+
+### Add a target
+
+```
+<path-to-project>/cordova/target add <name> <ip-address> <device | simulator> [-p | --password <password>] [--pin <device-pin>]
+```
+
+where
+
+- `<name>` specifies a unique name for the target.
+- `<ip-address>` specifies the ip address of the BlackBerry device or
+ simulator.
+- `-p|--password <password>` specifies the password for the device or
+ simulator. This is required only if the device or simulator is
+ password protected.
+- `--pin <device-pin>` specifies the PIN of the BlackBerry device,
+ which identifies that device as a valid host for the debug
+ token. This argument is required only if you are creating a debug
+ token.
+
+### Remove a target
+
+```
+<path-to-project>/cordova/target remove <name>
+```
+
+### Set a target as the default
+
+```
+<path-to-project>/cordova/target default <name>
+```
+
+## build
+
+The `build` command builds the project as a .bar file. You can build
+your app in either release mode (which produces a signed .bar file) or
+in debug mode (which produces an unsigned .bar file).
+
+### Build your project in release mode
+
+```
+<path-to-project>/cordova/build release -k|--keystorepass <password> [-b|--buildId <number>] [-p|--params <params-JSON-file>]
+```
+where
+
+- `-k|--keystorepass <password>` specifies the password you defined when you configured your computer to sign applications.
+- `-b|--buildId <number>` specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
+- `-p|--params <params-JSON-file>` specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
+
+### Build your project in debug mode
+
+```
+<path-to-project>/cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params <params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
+```
+
+where
+
+- `<target>` specifies the name of a previously added target. If
+ `<target>` is not specified, the default target is used, if one has
+ been created. This argument is only required if you want the script
+ to deploy your app to a BlackBerry device or simulator and you have
+ not created a default target. Additionally, if `<target>` is a
+ device, then that device must be connected to your computer by USB
+ connection or be connected to the same Wi-Fi network as your
+ computer.
+- `-k|--keystorepass <password>` specifies the password you defined
+ when you configured your computer to sign applications. This
+ password is also used to create your debug token. This argument is
+ only required if you want the script to create and install the debug
+ token for you.
+- `-p|--params <params-JSON-file>` specifies a JSON file containing
+ additional parameters to pass to downstream tools.
+- `-ll|--loglevel <level>` specifies the log level. The log level may
+ be one of `error`, `warn`, or `verbose`.
+
+If you have previously defined a default target (and previously
+installed a debug token, if that target is a BlackBerry device), you
+can run the script with no arguments, and the script will package your
+app and deploy it to the default target. For example:
+
+```
+<path-to-project>/cordova/build debug
+```
+
+## run
+
+The `run` command deploys the app on the specified BlackBerry device
+or a simulator. Before deploying your app, you must first create a
+target for the device or simulator you want to deploy your app to. The
+deploy script will deploy the most recent build of your app.
+
+```
+<path-to-project>/cordova/run <target>
+```
+
+where
+
+- `<target> `specifies the name of a previously added target. If
+ `<target> `is a device, then that device must be connected to your
+ computer by USB connection or be connected to the same Wi-Fi network
+ as your computer.
+
+## plugin
+
+The `target` command allows you to add and remove plugins
+
+### Fetch a locally-hosted plugin
+
+```
+<path-to-project>/cordova/plugin fetch <path-to-plugin>
+```
+
+### View a list of installed plugins
+
+```
+<path-to-project>/cordova/plugin ls
+```
+
+### Add a plugin
+
+```
+<path-to-project>/cordova/plugin add <name>
+```
+
+### Remove a plugin
+
+```
+<path-to-project>/cordova/plugin rm <name>
+```
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/index.md b/docs/en/edge/guide/platforms/index.md
new file mode 100644
index 0000000..b26e5f1
--- /dev/null
+++ b/docs/en/edge/guide/platforms/index.md
@@ -0,0 +1,95 @@
+---
+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.
+---
+
+Platform Guides
+======================
+
+Before developing for any of the platforms listed below, install
+cordova's command-line interface (CLI).
+(For details, see The Cordova Command-line Interface.)
+
+To develop Cordova applications, you must install SDKs for each mobile
+platform you are targeting. This installation is necessary regardless
+of whether you do the majority of your work in the SDK or use the CLI
+for your build cycle.
+
+Each _Platform Guide_ listed below tells you what you need to know to
+set up each platform's development environment: where to obtain the
+SDK, how to set up device emulators, how to connect devices for direct
+testing, and how to manage signing key requirements. Additional
+guides provide information on each platform's unique set of
+configuration options, instructions to add plugins, how to upgrade
+each platform, and platform-specific command-line tools that serve as
+a lower-level alternative to the `cordova` command-line utility.
+
+## Android
+
+* Android Platform Guide
+* Android Configuration
+* Android WebViews
+* Android Plugins
+* Android Command-line Tools
+* Upgrading Android
+
+## BlackBerry
+
+* BlackBerry Platform Guide
+* BlackBerry Configuration
+* Blackberry Command-line Tools
+* Upgrading BlackBerry
+
+## BlackBerry 10
+
+<!-- if "BlackBerry 10 Plugins" are available, how about WebViews? -->
+* BlackBerry 10 Platform Guide
+* BlackBerry 10 Plugins
+* Blackberry 10 Command-line Tools
+
+## iOS
+
+* iOS Platform Guide
+* iOS Configuration
+* iOS WebViews
+* iOS Plugins
+* iOS Command-line Tools
+* Upgrading iOS
+
+## Windows Phone
+
+* Windows Phone 8 Platform Guide
+* Windows Phone 8 Configuration
+* Windows Phone 7 Platform Guide
+* Windows Phone 7 Configuration
+* Windows Phone Command-line Tools
+* Upgrading Windows Phone
+
+## Windows 8
+
+* Windows 8 Platform Guide
+* Windows 8 Configuration
+* Windows 8 Command-line Tools
+* Upgrading Windows 8
+
+## Tizen
+
+* Tizen Platform Guide
+
+## FirefoxOS
+
+* FirefoxOS Configuration
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/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
new file mode 100644
index 0000000..a3398dc
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/index.md
@@ -0,0 +1,210 @@
+---
+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 Platform 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 simulator
+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 simulator, 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. 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 Command-line Interface. For example, in a source-code directory:
+
+ $ cordova create hello com.example.hello "Hello World"
+ $ cd hello
+ $ cordova platform add android
+ $ 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:
+
+ 
+
+## 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/cfebdc34/docs/en/edge/guide/platforms/ios/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/ios/tools.md b/docs/en/edge/guide/platforms/ios/tools.md
new file mode 100644
index 0000000..c37dbcd
--- /dev/null
+++ b/docs/en/edge/guide/platforms/ios/tools.md
@@ -0,0 +1,59 @@
+---
+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 Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+The iOS command-line tools are built upon shell scripts and rely on
+Xcode command-line tools such as `xcode-select` and `xcodebuild`.
+
+## 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.
+
+ $ ./path/to/cordova-ios/bin/create /path/to/my_new_project com.example.project_name ProjectName
+
+## Build a project
+
+ $ /path/to/my_new_project/cordova/build
+
+## Run app on emulator
+
+ $ /path/to/my_new_project/cordova/run
+
+## Releasing
+
+ $ /path/to/my_new_project/cordova/release
+
+## Logging
+
+ $ /path/to/my_new_project/cordova/log
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/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
new file mode 100644
index 0000000..32dff75
--- /dev/null
+++ b/docs/en/edge/guide/platforms/tizen/index.md
@@ -0,0 +1,112 @@
+---
+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 Platform Guide
+=========================
+
+## 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 the `cordova` utility in conjunction with
+the Tizen SDK. See The Cordova 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 you 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 & rarr; Tizen Web Application__:
+
+ 
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/windows-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-8/index.md b/docs/en/edge/guide/platforms/windows-8/index.md
new file mode 100644
index 0000000..3372889
--- /dev/null
+++ b/docs/en/edge/guide/platforms/windows-8/index.md
@@ -0,0 +1,111 @@
+---
+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.
+---
+
+Windows 8 Platform Guide
+==================================
+
+This guide describes how to set up your Cordova development
+environment and run a sample application. Note that Cordova used to
+be called PhoneGap, so some of the sites still use the old PhoneGap
+name.
+
+Microsoft deprecated the name _Metro-style apps_ in Windows 8 and
+Windows RT. MSDN now refers to this type of app as a _Windows Store_
+app, and this guide follows that convention. Also, in this guide
+_Windows 8_ signifies both Windows 8 and Windows RT.
+
+1. Requirements
+---------------
+
+- Windows 8
+
+- Visual Studio 2012 Professional or better, or Visual Studio 2012 Express for Windows 8
+
+Follow the instructions [here](http://www.windowsstore.com/) to submit your apps Windows Store.
+
+2. Install SDK + Cordova
+----------------------------
+
+- Set up your preferred variant of Visual Studio 2012. All of the product's paid versions (Professional, etc.) let you build Windows Store apps. You need **Express for Windows 8** to build Windows Store apps using the [Express editions](http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products).
+- Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-8` subfolder.
+
+3. Set up New Project
+--------------------
+
+You can already build Windows 8 apps using the _HTML/JavaScript track_
+available in Windows Store apps. Use Cordova in Windows Store apps to
+expose the same APIs as on other Cordova-supported platforms.
+
+- Open Visual Studio 2012 and choose **New Project**.
+- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as **CordovaWin8Foo** as in this example.
+
+ 
+
+- Microsoft continues to use `default.html` as the default home page, but most web developers use `index.html`. (Plus it's likely that in the other platform variants of your project you are using `index.html` as the name of your default page.) To fix this, in Solution Explorer rename the `default.html` file to `index.html`. Then double-click the `package.appxmanifest` file and change the **Start page** value to `index.html`.
+
+ 
+
+- To include `cordova.js` in your project, right-click on the **js** folder in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the **lib\windows-8** folder noted above.
+
+- Edit the code for `index.html`. Add a reference to `cordova.js`. You can do this manually, or by dragging the file from Solution Explorer.
+
+### Adding the reference...
+ <!-- WinJS references -->
+ <link href="//Microsoft.WinJS.1.0/css/ui-dark.css" rel="stylesheet" />
+ <script src="//Microsoft.WinJS.1.0/js/base.js"></script>
+ <script src="//Microsoft.WinJS.1.0/js/ui.js"></script>
+
+ <!-- Cordova -->
+ <script src="/js/cordova.js"></script>
+
+ <!-- CordovaWin8Foo references -->
+ <link href="/css/default.css" rel="stylesheet" />
+ <script src="/js/default.js"></script>
+
+- Next, add some code that demonstrates Cordova is working.
+
+### Adding a 'deviceready' handler...
+ <body>
+ <p>Content goes here</p>
+
+ <script type="text/javascript">
+
+ console.log("Subscribing...");
+ document.addEventListener("deviceready", function () {
+
+ navigator.notification.alert("The device is ready!");
+
+ });
+
+ </script>
+
+ </body>
+
+5. Test the Project
+-------------------------------
+
+- Run the project from Visual Studio. You'll see the message box appear:
+
+ 
+
+Done!
+-----
+
+That's it! You're now ready to build Windows Store apps with Cordova.
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/windows-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-8/tools.md b/docs/en/edge/guide/platforms/windows-8/tools.md
new file mode 100644
index 0000000..9fbb26d
--- /dev/null
+++ b/docs/en/edge/guide/platforms/windows-8/tools.md
@@ -0,0 +1,44 @@
+---
+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.
+---
+
+# Windows 8 Command-line Tools
+
+The `cordova` command-line utility is a high-level tool that allows
+you to build applications across several platforms at once. An older
+version of the Cordova framework provides sets of command-line tools
+specific to each platform. To use them as an alternative to the CLI,
+you need to download this version of Cordova from
+[cordova.apache.org](http://cordova.apache.org). The download contains
+separate archives for each platform. Expand the platform you wish to
+target. The tools described here are typically available in the
+top-level `bin` directory, otherwise consult the __README__ file for
+more detailed directions.
+
+## Windows 8
+
+The Windows 8 command-line tools only support creating new projects.
+Commands must be run from a cmd or powershell prompt.
+
+## Create a project
+
+Run the `create` command with the following parameters:
+
+* Path to your new Cordova Windows 8 project
+* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
+* Project name
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cfebdc34/docs/en/edge/guide/platforms/windows-phone-7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/windows-phone-7/index.md b/docs/en/edge/guide/platforms/windows-phone-7/index.md
new file mode 100644
index 0000000..a227130
--- /dev/null
+++ b/docs/en/edge/guide/platforms/windows-phone-7/index.md
@@ -0,0 +1,95 @@
+---
+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.
+---
+
+Windows Phone 7 Platform Guide
+==================================
+
+## Requirements and Support
+
+Requires Windows 7, Windows 8 or Windows Vista with SP2. Running
+Windows as a virtual machine does not work well, so Mac users should
+set up a Bootcamp partition to run Windows 7 or Vista.
+
+To install the app onto a device or submit it to the market place, you
+need to become an
+[App Hub member](http://create.msdn.com/en-US/home/membership).
+
+Developers should use the the `cordova` utility in conjunction with
+the Windows Phone SDK. Before installing it on Windows, open a
+command line and type `git` to make sure it is installed. If not,
+download it from [mysysgit.github.io](http://mysysgit.github.io). When
+prompted to configure your PATH, choose the option: __Run Git and
+included Unix tools from the Windows Command Prompt__. Once git is
+available, follow the instructions in The Cordova Command-line
+Interface for information how to install it, add projects, then build
+and deploy a project.
+
+## Install the SDK
+
+Download and install the
+[Windows Phone SDK](http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27570/)
+
+## Open a Project in the SDK
+
+After installing the `cordova` utility, use the following to create a
+new project, then add and build the Windows Phone 7 project.
+
+ $ cordova create hello com.example.hello "Hello World"
+ $ cd hello
+ $ cordova platform add wp7
+ $ cordova build
+
+Open Visual Studio and choose __Open Project__. Navigate to the
+`hello/platforms/wp7` directory and choose the `Hello_World.sln` file.
+The SDK displays the directory's contents:
+
+
+
+At this point you can modify the app within the SDK, but running the
+`build` or `prepare` commands again wipes out local changes. If Visual
+Studio is open, it alerts you about modified files and offers you the
+option to reload them. See The Cordova Command-line Interface for
+more information.
+
+## Deploy to Emulator
+
+Within the SDK, select the __Windows Phone Emulator__ target from the
+popup menu in the main menu bar, and press the green button to run the
+emulator:
+
+
+
+The app displays on the emulator's home screen as it would on a real
+device:
+
+
+
+## Deploy to Device
+
+To test your application on a device, the device must be registered.
+MSDN provides
+[documentation][http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx]
+to help deploy and test your Windows Phone.
+
+Once registered, you need to make sure the phone is connected via USB
+with its screen unlocked. In Visual Studio, choose the __Windows Phone
+Device__ target and press the green button to run it:
+
+
+
[03/20] docs commit: [CB-3827] separate platform-specific CL tool
guides; still needs cleanup
Posted by mw...@apache.org.
[CB-3827] separate platform-specific CL tool guides; still needs cleanup
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/4db1732c
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/4db1732c
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/4db1732c
Branch: refs/heads/master
Commit: 4db1732c651abe3b86deeefbd4f1debc6a73180a
Parents: f488410
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 11:40:05 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 11:40:05 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/getting-started/index.md | 21 +++++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/4db1732c/docs/en/edge/guide/getting-started/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/index.md b/docs/en/edge/guide/getting-started/index.md
index e2367d4..9c080f9 100644
--- a/docs/en/edge/guide/getting-started/index.md
+++ b/docs/en/edge/guide/getting-started/index.md
@@ -43,34 +43,44 @@ a lower-level alternative to the `cordova` command-line utility.
* Android Platform Guide
* Android Configuration
* Android Plugins
+* Android Command-Line Tools
* Upgrading Android
## BlackBerry (Windows, Mac)
* BlackBerry Platform Guide
-* BlackBerry 10 Platform Guide
* BlackBerry Configuration
-* BlackBerry 10 Plugins
+* Blackberry Command-Line Tools
* Upgrading BlackBerry
+## BlackBerry 10 (Windows, Mac)
+
+* BlackBerry 10 Platform Guide
+* BlackBerry 10 Plugins
+* Blackberry 10 Command-Line Tools
+
## iOS (Mac)
* iOS Platform Guide
* iOS Configuration
* iOS Plugins
+* iOS Command-Line Tools
* Upgrading iOS
## Windows Phone
-* Windows Phone 7 Platform Guide (Windows 7 or 8)
-* Windows Phone 7 Configuration
-
* Windows Phone 8 Platform Guide (Windows 8)
* Windows Phone 8 Configuration
+* Windows Phone 7 Platform Guide (Windows 7 or 8)
+* Windows Phone 7 Configuration
+* Windows Phone Command-Line Tools
* Upgrading Windows Phone
+## Windows 8
+
* Windows 8 Platform Guide (Windows 8)
* Windows 8 Configuration
+* Windows 8 Command-Line Tools
* Upgrading Windows 8
## Tizen
@@ -80,4 +90,3 @@ a lower-level alternative to the `cordova` command-line utility.
## FirefoxOS
* FirefoxOS Configuration
-
[12/20] [CB-3827] move platform-specific files within platforms dir;
rename dirs within platforms
Posted by mw...@apache.org.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugin-development/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/ios/index.md b/docs/en/edge/guide/plugin-development/ios/index.md
deleted file mode 100644
index 61bc117..0000000
--- a/docs/en/edge/guide/plugin-development/ios/index.md
+++ /dev/null
@@ -1,230 +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 Plugins
-
-A plugin is an Objective-C class that extends the `CDVPlugin` class.
-
-Each plugin class must be registered using the config.xml file, as a <plugin> tag under the <plugins> key.
-
-## Plugin Class Mapping
-
-The JavaScript portion of a plugin always uses the `cordova.exec` method as follows:
-
- exec(<successFunction>, <failFunction>, <service>, <action>, [<args>]);
-
-This marshals a request from the `UIWebView` to the iOS native side,
-more or less boiling down to calling the `action` method on the
-`service` class, with the arguments passed in the `args` array.
-
-The plugin must be added under the `<plugins>` tag of your Cordova-iOS
-application's project's `config.xml` file.
-
- <feature name="LocalStorage">
- <param name="ios-package" value="CDVLocalStorage" />
- </feature>
-
-The feature name='name' should match what you use in the JavaScript
-`exec` call, and the value matches the name of the plugin's
-Objective-C class. param name should always be "ios-package".
-Otherwise the plugin may compile but would not be
-reachable by Cordova.
-
-## Plugin Initialization and Lifetime
-
-There is one instance of a plugin object that is created per-UIWebView, and the lifetime of the instance is tied to the UIWebView. Plugins are not instantiated until they are first referenced by a call from JS, unless the `onload` attribute set within config.xml. E.g.:
-
- <plugin name="Echo" value="Echo" onload="true" />
-
-There is *no* designated initializer for plugins. Instead, plugins should use the `pluginInitialize` method for their start-up logic.
-
-Plugins with long-running requests, background activity (e.g. playing media), listeners or internal state should implement the `onReset` method and stop or clean up those activities. This method is run when the `UIWebView` navigates to a new page or refreshes, which reloads the JavaScript.
-
-## Writing an iOS Cordova Plugin
-
-We have JavaScript fire off a plugin request to the native side. We have the iOS Objective-C plugin mapped properly via the `config.xml` file. So what does the final iOS Objective-C Plugin class look like?
-
-What gets dispatched to the plugin via JavaScript's `exec` function gets passed into the corresponding Plugin class's `action` method. A plugin method has this signature:
-
- - (void)myMethod:(CDVInvokedUrlCommand*)command
- {
- CDVPluginResult* pluginResult = nil;
- NSString* myarg = [command.arguments objectAtIndex:0];
-
- if (myarg != nil) {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK];
- } else {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR messageAsString:@"Arg was null"];
- }
- [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
- }
-
-1. [CDVInvokedUrlCommand.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVInvokedUrlCommand.h)
-2. [CDVPluginResult.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPluginResult.h)
-3. [CDVCommandDelegate.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVCommandDelegate.h)
-
-## iOS CDVPluginResult message types
-
-Using CDVPluginResult you can return a variety of result types back to your JavaScript callbacks, using class methods that look like:
-
- + (CDVPluginResult*)resultWithStatus:(CDVCommandStatus)statusOrdinal messageAs...
-
-You can create `String`, `Int`, `Double`, `Bool`, `Array`,
-`Dictionary`, `ArrayBuffer`, and `Multipart` types. Or, don't attach
-any arguments (just send a status). Or, return an Error. You can
-even choose to not send any plugin result at all, in which case the
-callback does not fire.
-
-### Notes
-
- * `messageAsArrayBuffer` expects `NSData*` and converts to an `ArrayBuffer` for your JavaScript callback (and `ArrayBuffers` sent to a plugin from JavaScript are converted to `NSData*`).
- * `messageAsMultipart` expects an `NSArray*` containing any of the other supported types, and sends the whole array as the `arguments` to your JavaScript callback.
- * Quirk: this is not just syntactic sugar (though it is sweet). This way, all of the arguments are serialized/deserialized as necessary. e.g. it is safe to return `NSData*` as multipart, but not as `Array`/`Dictionary`.
-
-## Plugin Signatures
-
-The **new signature** supported beginning in **Cordova 2.1.0** is:
-
- - (void)myMethod:(CDVInvokedUrlCommand*)command;
-
-The **old (deprecated)** signature is:
-
- - (void)myMethod:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
-
-Basically, the options dictionary has been removed for the new signature, and the callbackId is not the 0th index item for the arguments array, but it is now in a separate property.
-
-## Echo Plugin iOS Plugin
-
-We would add the following to the `<plugins>` tag of the project's `config.xml` file:
-
- <plugin name="Echo" value="Echo" />
-
-Then we would add the following files (`Echo.h` and `Echo.m`) to the Plugins folder inside our Cordova-iOS
-application folder:
-
- /********* Echo.h Cordova Plugin Header *******/
-
- #import <Cordova/CDV.h>
-
- @interface Echo : CDVPlugin
-
- - (void)echo:(CDVInvokedUrlCommand*)command;
-
- @end
-
- /********* Echo.m Cordova Plugin Implementation *******/
-
- #import "Echo.h"
- #import <Cordova/CDV.h>
-
- @implementation Echo
-
- - (void)echo:(CDVInvokedUrlCommand*)command
- {
- CDVPluginResult* pluginResult = nil;
- NSString* echo = [command.arguments objectAtIndex:0];
-
- if (echo != nil && [echo length] > 0) {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:echo];
- } else {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR];
- }
-
- [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
- }
-
- @end
-
-Let's take a look at the code. At the top we have all of the necessary
-Cordova imports. Our class extends from `CDVPlugin` - very important.
-
-This plugin only supports one action, the `echo` action. First, we
-grab the echo string using the `objectAtIndex` method on our `args`,
-telling it we want to get the 0th parameter in the arguments array. We
-do a bit of parameter checking: make sure it is not `nil`, and make
-sure it is not a zero-length string.
-
-If it is, we return a `PluginResult` with an `ERROR` status. If all of
-those checks pass, then we return a `PluginResult` with an `OK`
-status, and pass in the `echo` string we received in the first place
-as a parameter.
-
-Finally, we send the result to `self.commandDelegate`, which executes
-the `exec` method's success or failure callbacks on the JavaScript
-side. If the success callback is called, it passes in the `echo`
-parameter.
-
-## Threading
-
-Plugin methods are executed in the same thread as the UI. If your
-plugin requires a great deal of processing or requires a blocking
-call, you should use a background thread. For example:
-
- - (void)myPluginMethod:(CDVInvokedUrlCommand*)command
- {
- // Check command.arguments here.
- [self.commandDelegate runInBackground:^{
- NSString* payload = nil;
- // Some blocking logic...
- CDVPluginResult* pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:payload];
- // The sendPluginResult method is thread-safe.
- [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
- }];
- }
-
-## Advanced Plugin Functionality
-
-See other methods that you can override in:
-
-1. [CDVPlugin.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.h)
-2. [CDVPlugin.m](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.m)
-
-For example, you can hook into the `pause`, `resume`, app terminate and `handleOpenURL` events.
-
-## Debugging Plugins
-
-To debug the Objective-C side, you would use Xcode's built-in debugger.
-For JavaScript, on iOS 5.0 you can use
-[Weinre, an Apache Cordova Project](https://github.com/apache/cordova-weinre) or
-[iWebInspector, a third-party utility](http://www.iwebinspector.com/)
-
-For iOS 6, you would use Safari 6.0 to simply attach to your app
-running in the iOS 6 Simulator.
-
-## Common Pitfalls
-
-* Don't forget to add your plugin's mapping to config.xml. If you forget, an error is logged in the Xcode console.
-* Don't forget to add any hosts you connect to in the whitelist, as described in Domain Whitelist Guide. If you forget, an error is logged in the Xcode console.
-
-## Deprecated Plugin Signature Note
-
-The **old (deprecated)** signature is:
-
- - (void) myMethod:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
-
-The Objective-C plugin method's `options` parameter is deprecated, and
-should not be used. For legacy reasons, the last JavaScript object
-passed in the `args` array is passed in as the `options` dictionary of
-the Objective-C method. You must make sure that any JavaScript object
-that is passed in as an element in the `args` appears as the last item
-in the array. Otherwise it throws off the array index for all
-subsequent parameters of the Objective-C array. Only one JavaScript
-object is supported for the options dictionary, and only the last one
-encountered will be passed to the native method. Errors stemming from
-this problem are the reason `options` has been deprecated.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugin-development/windows-phone/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/windows-phone/index.md b/docs/en/edge/guide/plugin-development/windows-phone/index.md
deleted file mode 100644
index ed89361..0000000
--- a/docs/en/edge/guide/plugin-development/windows-phone/index.md
+++ /dev/null
@@ -1,194 +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.
----
-
-Windows Phone Plugins
-====================================
-
-Writing a plugin for Cordova on Windows Phone requires a basic understanding of
-the architecture of Cordova. Cordova-WP7 consists of a WebBrowser which hosts the
-application JavaScript code and manages native API calls. There is a BaseCommand
-(`WP7CordovaClassLib.Cordova.Commands.BaseCommand`) class in C# which you can extend,
-and it comes with the majority of the 'plumbing' built for you already.
-
-1. Select your project, and right-click to choose __Add → New Item...__
- - Preferably add it to the 'Plugins' folder, but it is up to you
-2. Select 'Class' and name it `Echo.cs`
- - The name of this class must _exactly_ match what you call into `cordova.exec(win, fail, "Echo", ...)`
-3. Include the base classes implementation
-
- using WPCordovaClassLib.Cordova;
- using WPCordovaClassLib.Cordova.Commands;
- using WPCordovaClassLib.Cordova.JSON;
-
-4. Extend your class from BaseCommand
-
- public class Echo : BaseCommand
- {
- // ...
- }
-
-5. Add a method that is callable from JS
-
- public class Echo : BaseCommand
- {
- public void echo(string options)
- {
- // all JS callable plugin methods MUST have this signature!
- // public, returning void, 1 argument that is a string
- }
- }
-
-Namespaces
-----------
-
-The default namespace for unqualified commands is:
-
- namespace Cordova.Extension.Commands
- {
- // ...
- }
-
-If you want to use your own namespace, you need to make a fully
-qualified call to `cordova.exec`. For example, if you want to define
-your C# class like this:
-
- namespace com.mydomain.cordovaExtensions
- {
- public class Echo : BaseCommand
- {
- // ...
- }
- }
-
-Then, in JS you need to call `exec` like this:
-
- cordova.exec(win, fail, "com.mydomain.cordovaExtensions.Echo", ...);
-
-Interpreting your arguments in C#
-----------------------------------
-
-The data received by your plugin method is a string value, but in actuality
-looking at our JavaScript code, we see our intention was to pass an array of strings.
-Looking back at our JS call to `cordova.exec`, we see we passed `[str]`:
-
- cordova.exec(win, fail, "Echo", "echo", ["input string"]);
-
-If we inspect the options string passed in to our `Echo.echo` method,
-we see that the value is actually:
-
- "[\"input string\"]"
-
-All JavaScript exec arguments are JSON encoded before being passed into C#.
-
-If we want to treat this as the string we were expecting, we need to decode it.
-We can use simple JSON deserialization.
-
- string optVal = JsonHelper.Deserialize<string[]>(options)[0];
- // optVal now has the value of "input string"
-
-Passing results from C# to JS
------------------------------
-
-The base class BaseCommand provides methods for passing data to your JS callback handlers.
-To simply signal that the command has succeeded, when no additional result info is needed,
-you can can simply call:
-
- DispatchCommandResult(); // calls back with an empty plugin result, considered a success callback
-
-To pass data back, you need to call a different version of `DispatchCommandResult`:
-
- DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "Everything went as planned, this is a result that is passed to the success handler."));
-
-To pass structured object data back to JS, it should be encoded as a JSON string:
-
- DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "{result:\"super awesome!\"}"));
-
-If you need to signal that an error has occurred, you can call `DispatchCommandResult` with a `PluginResult` object:
-
- DispatchCommandResult(new PluginResult(PluginResult.Status.ERROR, "Echo signaled an error"));
-
-Handling serialization errors in your plugin's C# method
---------------------------------------------------------
-
-When interpreting your arguments, it is a good idea to use a try/catch block
-in case we have bad input. This is a pattern used throughout the Cordova C# code:
-
- string optVal = null;
-
- try
- {
- optVal = JsonHelper.Deserialize<string[]>(options)[0];
- }
- catch(Exception)
- {
- // simply catch the exception, we handle null values and exceptions together
- }
-
- if (optVal == null)
- {
- DispatchCommandResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION));
- }
- else
- {
- // ... continue on to do our work
- }
-
-Advanced Plugin Functionality
------------------------------
-
-See other methods that you can override in:
-
-1. [BaseCommand.cs](https://github.com/apache/cordova-wp7/blob/master/templates/standalone/cordovalib/Commands/BaseCommand.cs)
-
-For example, you can hook into the 'pause' and 'resume' application events.
-
-### Debugging Plugins
-
-To debug the C# side, you can use Visual Studio's debugger, just set a break point
-at any of the methods exposed by your class.
-
-JavaScript is a little more difficult to debug on Windows Phone. You
-need to use `console.log` to output the state of your plugin, or
-inform yourself of errors.
-
-Common Pitfalls
----------------
-
-- Be careful when deciding on the arguments you pass to native in your JavaScript
- implementation. Most device platforms expect the args passed to cordova.exec
- to be an array, but if you have different types of objects in this array, it
- becomes difficult or impossible to deserialize.
-
- cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", 54, {literal:'trouble'}]);
-
- - This means that your C# code receives a difficult to decode string value, such as:
-
- "[\"this is a string\", 54, { literal:'trouble' }]"
-
- - Consider converting ALL parameters to strings before calling exec:
-
- cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", "54", "{literal:'trouble'}"]) ;
-
- string[] optValues = JsonHelper.Deserialize<string[]>(options);
-
-- It is usually a good idea to do parameter checking in your
- JavaScript code, before you call `exec`. This allows you to re-use
- more JavaScript code among your plug-in's various native
- implementations.
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/plugins/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugins/index.md b/docs/en/edge/guide/plugins/index.md
new file mode 100644
index 0000000..bebe2a8
--- /dev/null
+++ b/docs/en/edge/guide/plugins/index.md
@@ -0,0 +1,110 @@
+---
+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.
+---
+
+# Plugin Development Guide
+
+A Cordova plugin bridges a bit of functionality between the WebView
+powering a Cordova application and the native platform the Cordova
+application is running on. Plugins are composed of a single JavaScript
+interface used across all platforms, and native implementations
+following platform-specific Plugin interfaces that the JavaScript
+calls into. All of the core Cordova APIs are implemented using this
+architecture.
+
+This guide steps the process of writing a simple Echo Plugin that
+passes a string from JavaScript and sends it into the native
+environment for the supported platforms. The native code then returns
+the same string back to the callbacks inside the plugin's JavaScript.
+
+This guide provides enough overview on which you can build to write
+more complex plugins.
+
+## JavaScript
+
+The entry point for any plugin is JavaScript. The reason developers use
+Cordova is so they can use and write JavaScript, not Objective-C,
+not Java, not C#. The JavaScript interface for your plugin is the
+front-facing and arguably most important part of your Cordova plugin.
+
+You can structure your plugin's JavaScript however you like. The one
+thing you _must_ use to communicate between the Cordova JavaScript
+ and native environments is the `cordova.exec` function. Here is an example:
+
+ cordova.exec(function(winParam) {}, function(error) {}, "service",
+ "action", ["firstArgument", "secondArgument", 42,
+ false]);
+
+The parameters are detailed below:
+
+1. `function(winParam) {}` - Success function callback. Assuming your
+ `exec` call completes successfully, this function is invoked
+ (optionally with any parameters you pass back to it).
+2. `function(error) {}` - Error function callback. If the operation does
+ not complete successfully, this function is invoked (optionally
+ with an error parameter).
+3. `"service"` - The service name to call into on the native side. This
+ is mapped to a native class, about which more information is
+ available in the native guides listed below.
+4. `"action"` - The action name to call into. This is picked up by the
+ native class receiving the `exec` call, and, depending on the
+ platform, essentially maps to a class's method.
+ The native guides listed below provide details.
+5. `[/* arguments */]` - Arguments to pass into the native environment.
+
+### Echo Plugin JavaScript Example
+
+ window.echo = function(str, callback) {
+ cordova.exec(callback, function(err) {
+ callback('Nothing to echo.');
+ }, "Echo", "echo", [str]);
+ };
+
+Let's dive into this. The plugin attaches itself to `window`,
+specifically to the `echo` function. Plugin users would then use it as
+follows:
+
+ window.echo("echome", function(echoValue) {
+ alert(echoValue == "echome"); // should alert true.
+ });
+
+First, let's take a look at the last three arguments to the `exec`
+function. We will be calling the `Echo` "service", requesting the `echo`
+"action", and passing an array of arguments containing the echo string,
+which is the first parameter into the `window.echo` function.
+
+The success callback passed into `exec` is simply a reference to the
+callback function that `window.echo` takes. We do a bit more for the
+error callback: if the native side fires off the error callback, we
+simply invoke the success callback and pass into it a "default"
+string.
+
+## Native
+
+Once you define JavaScript for your plugin, you need to complement it
+with at least one native implementation. Details to do so for each
+platform are listed below. These guides continue to build on the
+simple Echo Plugin example discussed above.
+
+- Android Plugins
+- BlackBerry Plugins
+- BlackBerry 10 Plugins
+- iOS Plugins
+- Windows Phone Plugins
+
+The Tizen platform currently does not support plugins.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/android/index.md b/docs/en/edge/guide/project-settings/android/index.md
deleted file mode 100644
index b3c02b5..0000000
--- a/docs/en/edge/guide/project-settings/android/index.md
+++ /dev/null
@@ -1,43 +0,0 @@
-<!--
-#
-# 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` settings file controls various settings of Cordova. This is application wide, and not set per CordovaWebView Instance.
-
-## <preference>
-
-Various **other** preferences (as **<preference>** tags) default on not breaking existing apps. The available preferences are:
-
-1. **useBrowserHistory (boolean, defaults to true)** - set to false if you want to use the history shim that was used to work around the hashtag error present in Android 3.x prior to the history fix. (Note: This setting will be deprecated in April 2013)
-2. **loadingDialog** - Display a native loading dialog when loading the app. The value's format is _Title, Message_
-3. **loadingPageDialog** - Display a native loading dialog when loading sub-pages. The value's format is _Title, Message_
-4. **errorUrl** - Set the error page for your application. Should be located in your Android project in file://android_asset/www/
-5. **backgroundColor** - Set the background color for your application. Supports a four-byte hex value, with the first byte representing alpha value, and the following three bytes with standard RGB values. (i.e. 0x00000000 = Black)
-6. **loadUrlTimeoutValue** - How much time Cordova should wait before throwing a timeout error on the application.
-7. **keepRunning (boolean, defaults to true)** - Determines whether Cordova will keep running in the background or not
-8. **splashscreen** - The name of the file minus its extension in the res/drawable directory. If you have multiple assets, they all must share this common name in their respective directories.
-9. **disallowOverscroll (boolean, defaults to false)** - set to true if you want to disable the glow when a user scrolls beyond the edge of the webview.
-
-## <plugin>
-
-Android supports using <feature> as analogues to <plugin> elements.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/blackberry/index.md b/docs/en/edge/guide/project-settings/blackberry/index.md
deleted file mode 100644
index ab266ad..0000000
--- a/docs/en/edge/guide/project-settings/blackberry/index.md
+++ /dev/null
@@ -1,29 +0,0 @@
-<!--
-#
-# 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 Configuration
-===================================
-
-BlackBerry fully supports the
-[W3C Widget Specification](http://www.w3.org/TR/widgets/)
-as well as proprietary RIM extensions. Please see the full
-[BlackBerry WebWorks documentation regarding config.xml](https://developer.blackberry.com/html5/documentation/working_with_config_xml_file_1866970_11.html)
-for details.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/firefoxos/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/firefoxos/index.md b/docs/en/edge/guide/project-settings/firefoxos/index.md
deleted file mode 100644
index 2806083..0000000
--- a/docs/en/edge/guide/project-settings/firefoxos/index.md
+++ /dev/null
@@ -1,24 +0,0 @@
-<!--
-#
-# 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.
-#
--->
-
-FirefoxOS Configuration
-===================================
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/ios/index.md b/docs/en/edge/guide/project-settings/ios/index.md
deleted file mode 100644
index ccb0ec4..0000000
--- a/docs/en/edge/guide/project-settings/ios/index.md
+++ /dev/null
@@ -1,60 +0,0 @@
-<!--
-#
-# 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 Configuration
-========================
-
-The `config.xml` settings file controls various settings of Cordova. This is application wide, and not set per CDVViewController instance.
-The `config.xml` file is located in your `<project folder>/<appname>` directory.
-
-## <preference>
-
-Various preferences (as **<preference>** tags) default on not breaking existing apps. The available preferences are:
-
-1. **DisallowOverscroll (boolean, defaults to false)** - set to true if you don't want the WebView to rubber-band
-
-2. **TopActivityIndicator (string, defaults to 'gray')** - this is the top spinning throbber in the status/battery bar, valid values are `whiteLarge`, `white`, and `gray`
-
-3. **EnableLocation (boolean, defaults to false)** - set to true, to initialize the Geolocation plugin at start-up (so the fix on your location can be more accurate) **DEPRECATED**: please set the **onload** attribute of the **Geolocation** plugin to **true** instead.
-
-4. **EnableViewportScale (boolean, defaults to false)** - set to true to prevent viewport scaling through a meta tag
-
-5. **AutoHideSplashScreen (boolean, defaults to true)** - set to false to control when the splashscreen is hidden through a JavaScript API
-
-6. **FadeSplashScreen (boolean, defaults to true)** - set to false to prevent the splash-screen to fade in and out when showing/hiding it.
-
-7. **FadeSplashScreenDuration (float, defaults to 2)** - The splash-screen Fade duration in seconds.
-
-8. **ShowSplashScreenSpinner (boolean, defaults to true)** - set to false to hide the splash-screen spinner
-
-9. **MediaPlaybackRequiresUserAction (boolean, defaults to false)** - set to true to not allow autoplayed HTML5 video
-
-10. **AllowInlineMediaPlayback (boolean, defaults to false)** - set to true to allow inline HTML5 media playback, also, the video element in the HTML document must also include the webkit-playsinline attribute
-
-11. **BackupWebStorage (string, defaults to 'cloud')** - valid values are 'none', 'cloud' and 'local'. Set to 'cloud' to allow the web storage data to be backed up to iCloud, and set to 'local' to only allow local backups (iTunes sync). Set to 'none' to not allow any backups of web storage.
-
-12. **KeyboardDisplayRequiresUserAction (boolean, defaults to true)** - set to false to open the keyboard when form elements get focus via the JavaScript focus() call.
-
-13. **SuppressesIncrementalRendering (boolean, defaults to false)** - set to true to wait until all new view content has been received before it is rendered.
-
-14. **HideKeyboardFormAccessoryBar (boolean, defaults to false)** - set to true to hide the additional toolbar that is on top of the keyboard (this is the toolbar that has the Prev, Next and Done buttons)
-
-15. **KeyboardShrinksView (boolean, defaults to false)** - set to true to shrink the WebView when the keyboard comes up. The WebView shrinks instead of the viewport shrinking and the page scrollable. This applies to apps that position their elements relative to the bottom of the WebView. This is the default behaviour on Android, and makes a lot of sense when building apps as opposed to webpages.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/windows8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/windows8/index.md b/docs/en/edge/guide/project-settings/windows8/index.md
deleted file mode 100644
index dfeb618..0000000
--- a/docs/en/edge/guide/project-settings/windows8/index.md
+++ /dev/null
@@ -1,26 +0,0 @@
-<!--
-#
-# 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.
-#
--->
-
-Windows 8 Configuration
-===================================
-
-Windows 8 does not currently support this feature.
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/wp7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/wp7/index.md b/docs/en/edge/guide/project-settings/wp7/index.md
deleted file mode 100644
index 23c8304..0000000
--- a/docs/en/edge/guide/project-settings/wp7/index.md
+++ /dev/null
@@ -1,25 +0,0 @@
-<!--
-#
-# 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.
-#
--->
-
-Windows Phone 7 Configuration
-===================================
-
-Windows Phone 7 does not currently have any additional configurable features.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/project-settings/wp8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/project-settings/wp8/index.md b/docs/en/edge/guide/project-settings/wp8/index.md
deleted file mode 100644
index de0e54b..0000000
--- a/docs/en/edge/guide/project-settings/wp8/index.md
+++ /dev/null
@@ -1,25 +0,0 @@
-<!--
-#
-# 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.
-#
--->
-
-Windows Phone 8 Configuration
-===================================
-
-Windows Phone 8 does not currently have any additional configurable features.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/upgrading/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/android/index.md b/docs/en/edge/guide/upgrading/android/index.md
deleted file mode 100644
index 63019d3..0000000
--- a/docs/en/edge/guide/upgrading/android/index.md
+++ /dev/null
@@ -1,242 +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 document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova.
-
-## 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 libs directory in your project
-2. Add cordova-2.8.0.jar to the libs directory in your project
-3. If you are using Eclipse, please refresh your eclipse project and do a clean
-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 to be the same as the one found in 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 cordova directory in your project
-
-## Upgrade to 2.7.0 from 2.6.0 ##
-1. Remove cordova-2.6.0.jar from the libs directory in your project
-2. Add cordova-2.7.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in 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 cordova directory in your project
-
-
-## Upgrade to 2.6.0 from 2.5.0 ##
-1. Remove cordova-2.5.0.jar from the libs directory in your project
-2. Add cordova-2.6.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in 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 cordova directory in your project
-
-. 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 libs directory in your project
-2. Add cordova-2.5.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in 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 cordova directory in your project
-
-## Upgrade to 2.4.0 from 2.3.0 ##
-
-1. Remove cordova-2.3.0.jar from the libs directory in your project
-2. Add cordova-2.4.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
-7. Copy files from bin/templates/cordova to the cordova directory in your project
-
-## Upgrade to 2.3.0 from 2.2.0 ##
-
-1. Remove cordova-2.2.0.jar from the libs directory in your project
-2. Add cordova-2.3.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
-7. Copy files from bin/templates/cordova to the cordova directory in your project
-
-## Upgrade to 2.2.0 from 2.1.0 ##
-
-1. Remove cordova-2.1.0.jar from the libs directory in your project
-2. Add cordova-2.2.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
-7. Copy files from bin/templates/cordova to the cordova directory in your project
-
-## Upgrade to 2.1.0 from 2.0.0 ##
-
-1. Remove cordova-2.0.0.jar from the libs directory in your project
-2. Add cordova-2.1.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
-7. Copy files from bin/templates/cordova to the cordova directory in your project
-
-## Upgrade to 2.0.0 from 1.9.0 ##
-
-1. Remove cordova-1.9.0.jar from the libs directory in your project
-2. Add cordova-2.0.0.jar to the libs directory in your project
-3. If you are using 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 be the same as the one found in framework/res/xml/config.xml
-
-### Notes about 2.0.0 release
-config.xml will be replacing cordova.xml and plugins.xml. This new file is a combination of the previous two. However, the
-old files are deprecated, and and while currently still work, will cease working in a future release.
-
-## Upgrade to 1.9.0 from 1.8.1 ##
-
-1. Remove cordova-1.8.0.jar from the libs directory in your project
-2. Add cordova-1.9.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
-
-### Notes about 1.9.0 release
-
-- Third-Party plugins may or may not work. This is because of the introduction of the CordovaWebView. 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 libs directory in your project
-2. Add cordova-1.8.1.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
-
-## Upgrade to 1.8.0 from 1.7.0 ##
-
-1. Remove cordova-1.7.0.jar from the libs directory in your project
-2. Add cordova-1.8.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
-
-## Upgrade to 1.8.0 from 1.7.0 ##
-
-1. Remove cordova-1.7.0.jar from the libs directory in your project
-2. Add cordova-1.8.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
-
-## Upgrade to 1.7.0 from 1.6.1 ##
-
-1. Remove cordova-1.6.1.jar from the libs directory in your project
-2. Add cordova-1.7.0.jar to the libs directory in your project
-3. If you are using Eclipse, please refresh your eclipse project and do a clean
-4. Copy the new cordova-1.7.0.js into your project
-5. Update the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
-
-## Upgrade to 1.6.1 from 1.6.0 ##
-
-1. Remove cordova-1.6.0.jar from the libs directory in your project
-2. Add cordova-1.6.1.jar to the libs directory in your project
-3. If you are using Eclipse, please refresh your eclipse project and do a clean
-4. Copy the new cordova-1.6.1.js into your project
-5. Update the res/xml/plugins.xml to be the same as the one found in framework/res/xml/plugins.xml
-
-## Upgrade to 1.6.0 from 1.5.0 ##
-1. Remove cordova-1.5.0.jar from the libs directory in your project
-2. Add cordova-1.6.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
-7. Replace the res/xml/phonegap.xml with res/xml/cordova.xml so that it is the same as the one found in framework/res/xml/cordova.xml
-
-## Upgrade to 1.5.0 from 1.4.0##
-1. Remove phonegap-1.4.0.jar from the libs directory in your project
-2. Add cordova-1.5.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
-7. Replace the res/xml/phonegap.xml with res/xml/cordova.xml so that it is the same as the one found in framework/res/xml/cordova.xml
-
-## Upgrade to 1.4.0 from 1.3.0 ##
-1. Remove phonegap-1.3.0.jar from the libs directory in your project
-2. Add phonegap-1.4.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
-7. Update the res/xml/phonegap.xml so that it is the same as the one found in framework/res/xml/phonegap.xml
-
-## Upgrade to 1.3.0 from 1.2.0 ##
-1. Remove phonegap-1.2.0.jar from the libs directory in your project
-2. Add phonegap-1.3.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
-7. Update the res/xml/phonegap.xml so that it is the same as the one found in framework/res/xml/phonegap.xml
-
-## Upgrade to 1.2.0 from 1.1.0 ##
-1. Remove phonegap-1.1.0.jar from the libs directory in your project
-2. Add phonegap-1.2.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
-7. Update the res/xml/phonegap.xml so that it is the same as the one found in framework/res/xml/phonegap.xml
-
-## Upgrade to 1.1.0 from 1.0.0 ##
-1. Remove phonegap-1.0.0.jar from the libs directory in your project
-2. Add phonegap-1.1.0.jar to the libs directory in your project
-3. If you are using 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 the res/xml/plugins.xml so that it is the same as the one found in framework/res/xml/plugins.xml
-
-## Upgrade to 1.0.0 from 0.9.6 ##
-1. Remove phonegap-0.9.6.jar from the libs directory in your project
-2. Add phonegap-1.0.0.jar to the libs directory in your project
-3. If you are using 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 so that it is the same as the one found in framework/res/xml/plugins.xml
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/610314b2/docs/en/edge/guide/upgrading/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/blackberry/index.md b/docs/en/edge/guide/upgrading/blackberry/index.md
deleted file mode 100644
index a50cddb..0000000
--- a/docs/en/edge/guide/upgrading/blackberry/index.md
+++ /dev/null
@@ -1,311 +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 document describes the process of upgrading Cordova projects to the latest released version
-
-## Upgrading 2.8.0 projects to 2.9.0 ##
-
-### BlackBerry10 ###
-
-1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.9.0)
-2. **Quit any running IDE's** Eclipse, Momentics and the lik
-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 Command-line Tools. This becomes the home of your updated project.
-5. **Copy** your projects source from the old project's /www folder to the new project's /www folder
-6. **Update** the Cordova script reference in your **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 folder location** on your hard drive (say to ~/Cordova-2.9.0)
-2. **Quit any running IDE's** 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 Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova.js** file from the new project into your **www** folder, and delete your **www/cordova.js** file
-6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
-8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
-9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
-
-## Upgrading 2.7.0 projects to 2.8.0 ##
-
-### BlackBerry10 ###
-
-BlackBerry10 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 folder location** on your hard drive (say to ~/Cordova-2.8.0)
-2. **Quit any running IDE's** 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 Command-line Tools. This becomes the home of your updated project.
-5. **Copy** your projects source from the old project's /www folder to the new project's /www folder
-6. **Update** the Cordova script reference in your **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 folder location** on your hard drive (say to ~/Cordova-2.8.0)
-2. **Quit any running IDE's** 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 Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova.js** file from the new project into your **www** folder, and delete your **www/cordova.js** file
-6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
-8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
-9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
-
-## Upgrading 2.6.0 projects to 2.7.0 ##
-
-1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.7.0)
-2. **Quit any running IDE's** 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 Command-line Tools. You need the assets from this new project.
-5. **Copy** the **www/cordova-2.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.6.0.js** file
-6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
-8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
-9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
-
-## Upgrade to 2.6.0 from 2.5.0 ##
-
-Updating the PhoneGap download folder:
-
-It is recommended that you download a fresh copy of the entire folder.
-
-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’ folder
-2. Update the ‘ext’, ‘ext-air’, and ‘ext-qnx’ in the ‘Phonegap-2.6.0/lib/blackberry/framework’ folder
-3. Update the ‘build.xml’ file in the ‘Phonegap-2.6.0/lib/blackberry’ folder
-4. Update the the ‘Phonegap-2.6.0/lib/blackberry/bin’ folder
-5. Update the ‘VERSION’ file in the ‘Phonegap-2.6.0/lib/blackberry’ folder
-
-Updating the example/ folder or migrating an existing project:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Update the contents of the `ext-qnx/` folder.
-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 folder:
-
-It is recommended that you download a fresh copy of the entire folder.
-
-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’ folder
-2. Update the ‘ext’, ‘ext-air’, and ‘ext-qnx’ in the ‘Phonegap-2.5.0/lib/blackberry/framework’ folder
-3. Update the ‘build.xml’ file in the ‘Phonegap-2.5.0/lib/blackberry’ folder
-4. Update the the ‘Phonegap-2.5.0/lib/blackberry/bin’ folder
-5. Update the ‘VERSION’ file in the ‘Phonegap-2.5.0/lib/blackberry’ folder
-
-Updating the example/ folder or migrating an existing project:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Update the contents of the `ext-qnx/` folder.
-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 folder:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Copy the new `cordova-2.4.0.js` into your project.
- - If playbook, then update the .js file in the `playbook/` folder.
- - If BlackBerry10, then update the .js file in the `qnx/` folder.
-5. Update your HTML to use the new `cordova-2.4.0.js` file.
-
-
-Updating the sample folder (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` folder.
-2. Update the .jar file in the `cordova.2.3.0/ext/` folder.
-3. Update the contents of the `cordova.2.3.0/ext-air/` folder.
-4. Update the contents of the `cordova.2.3.0/ext-qnx/` folder.
-5. Update the .js file in the `cordova.2.3.0/javascript/` folder.
-6. Open the `sample/lib/` folder and rename the `cordova.2.3.0/` folder to `cordova.2.4.0/`.
-7. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
-8. Open the `www/` folder 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` folder:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Copy the new `cordova-2.3.0.js` into your project.
- - If playbook, then update the .js file in the `playbook/` folder.
- - If BlackBerry10, then update the .js file in the `qnx/` folder.
-5. Update your HTML to use the new `cordova-2.3.0.js` file.
-
-
-Updating the sample folder (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` folder.
-2. Update the .jar file in the `cordova.2.2.0/ext/` folder.
-3. Update the contents of the `cordova.2.2.0/ext-air/` folder.
-4. Update the contents of the `cordova.2.2.0/ext-qnx/` folder.
-5. Update the .js file in the `cordova.2.2.0/javascript/` folder.
-6. Open the `sample/lib/` folder and rename the `cordova.2.2.0/` folder to `cordova.2.3.0/`.
-7. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
-8. Open the `www/` folder 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 folder:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Copy the new `cordova-2.2.0.js` into your project.
- - If playbook, then update the .js file in the `playbook/` folder.
- - If BlackBerry10, then update the .js file in the `qnx/` folder.
-5. Update your HTML to use the new `cordova-2.2.0.js` file.
-
-
-Updating the sample folder (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` folder.
-2. Update the .jar file in the `cordova.2.1.0/ext/` folder.
-3. Update the contents of the `cordova.2.1.0/ext-air/` folder.
-4. Update the contents of the `cordova.2.1.0/ext-qnx/` folder.
-5. Update the .js file in the `cordova.2.1.0/javascript/` folder.
-6. Open the `sample/lib/` folder and rename the `cordova.2.1.0/` folder to `cordova.2.2.0/`.
-7. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
-8. Open the `www/` folder 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 folder:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Copy the new `cordova-2.1.0.js` into your project.
- - If playbook, then update the .js file in the `playbook/` folder.
-5. Update your HTML to use the new `cordova-2.1.0.js` file.
-
-
-Updating the sample folder (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` folder.
-2. Update the .jar file in the `cordova.2.0.0/ext/` folder.
-3. Update the contents of the `cordova.2.0.0/ext-air/` folder.
-4. Update the .js file in the `cordova.2.0.0/javascript/` folder.
-5. Open the `sample/lib/` folder and rename the `cordova.2.0.0/` folder to `cordova.2.1.0/`.
-6. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
-7. Open the `www/` folder 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` folder:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Copy the new `cordova-2.0.0.js` into your project.
- - If playbook, then update the .js file in the `playbook/` folder.
-5. Update your HTML to use the new `cordova-2.0.0.js` file.
-6. Update your `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 folder (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` folder.
-2. Update the .jar file in the `cordova.1.9.0/ext/` folder.
-3. Update the contents of the `cordova.1.9.0/ext-air/` folder.
-4. Update the .js file in the `cordova.1.9.0/javascript/` folder.
-5. Open the `sample/lib/` folder and rename the `cordova.1.9.0/` folder to `cordova.2.0.0/`.
-6. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
-7. Open the `www/` folder and update your HTML to use the new `cordova-2.0.0.js` file.
-8. Open the `www/` folder 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` folder:
-
-1. Open your `www/` folder, which contains your app.
-2. Remove and update the .jar file in the `ext/` folder.
-3. Update the contents of the `ext-air/` folder.
-4. Copy the new `cordova-1.8.0.js` into your project.
- - If playbook, then update the .js file in the `playbook/` folder.
-5. Update your HTML to use the new `cordova-1.8.0.js` file.
-6. Update your `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 folder (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` folder.
-2. Update the .jar file in the `cordova.1.7.0/ext/` folder.
-3. Update the contents of the `cordova.1.7.0/ext-air/` folder.
-4. Update the .js file in the `cordova.1.7.0/javascript/` folder.
-5. Open the `sample/lib/` folder and rename the `cordova.1.7.0/` folder to `cordova.1.8.0/`.
-6. Type `ant blackberry build` or `ant playbook build` to update the `www/` folder with updated Cordova.
-7. Open the `www/` folder and update your HTML to use the new `cordova-1.8.0.js` file.
-8. Open the `www/` folder 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"/>
-
[06/20] docs commit: [CB-3827] Remove other hard-coded HTML links
Posted by mw...@apache.org.
[CB-3827] Remove other hard-coded HTML links
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/a0baad9c
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/a0baad9c
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/a0baad9c
Branch: refs/heads/master
Commit: a0baad9c6b0132696b4e4567f5fabaad24c6f910
Parents: 08f3a01
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 12:37:14 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 12:37:14 2013 -0400
----------------------------------------------------------------------
docs/en/edge/cordova/splashscreen/splashscreen.hide.md | 7 +++----
docs/en/edge/guide/plugin-development/ios/index.md | 2 +-
2 files changed, 4 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/a0baad9c/docs/en/edge/cordova/splashscreen/splashscreen.hide.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/cordova/splashscreen/splashscreen.hide.md b/docs/en/edge/cordova/splashscreen/splashscreen.hide.md
index 50824cd..ea07cd8 100644
--- a/docs/en/edge/cordova/splashscreen/splashscreen.hide.md
+++ b/docs/en/edge/cordova/splashscreen/splashscreen.hide.md
@@ -71,10 +71,9 @@ Full Example
iOS Quirk
------------
-The [`config.xml` file's setting](guide_project-settings_index.md.html#Project%20Settings) for
-`AutoHideSplashScreen` must be `false`. To delay hiding the splash
-screen for two seconds, add a timer such as the following in the
-`deviceready` event handler:
+The `config.xml` file's `AutoHideSplashScreen` setting must be
+`false`. To delay hiding the splash screen for two seconds, add a
+timer such as the following in the `deviceready` event handler:
setTimeout(function() {
navigator.splashscreen.hide();
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/a0baad9c/docs/en/edge/guide/plugin-development/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/plugin-development/ios/index.md b/docs/en/edge/guide/plugin-development/ios/index.md
index 2e311e2..61bc117 100644
--- a/docs/en/edge/guide/plugin-development/ios/index.md
+++ b/docs/en/edge/guide/plugin-development/ios/index.md
@@ -210,7 +210,7 @@ running in the iOS 6 Simulator.
## Common Pitfalls
* Don't forget to add your plugin's mapping to config.xml. If you forget, an error is logged in the Xcode console.
-* Don't forget to add any hosts you connect to in the [whitelist](guide_whitelist_index.md.html#Domain%20Whitelist%20Guide). If you forget, an error is logged in the Xcode console.
+* Don't forget to add any hosts you connect to in the whitelist, as described in Domain Whitelist Guide. If you forget, an error is logged in the Xcode console.
## Deprecated Plugin Signature Note
[05/20] docs commit: [CB-3827] Remove explicit HTML links to
Command-Line Usage section; fix other HTML links to privacy section
Posted by mw...@apache.org.
[CB-3827] Remove explicit HTML links to Command-Line Usage section; fix other HTML links to privacy section
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/08f3a019
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/08f3a019
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/08f3a019
Branch: refs/heads/master
Commit: 08f3a0192a7c742dddac0df6378cb87fe85f4125
Parents: 02c4420
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 12:32:38 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 12:32:38 2013 -0400
----------------------------------------------------------------------
docs/en/edge/cordova/camera/camera.md | 2 +-
docs/en/edge/cordova/contacts/contacts.md | 2 +-
docs/en/edge/cordova/geolocation/geolocation.md | 2 +-
docs/en/edge/cordova/media/capture/capture.md | 2 +-
docs/en/edge/guide/cordova-webview/ios.md | 2 +-
.../edge/guide/getting-started/android/tools.md | 2 +-
.../guide/getting-started/blackberry/tools.md | 2 +-
.../guide/getting-started/blackberry10/tools.md | 2 +-
docs/en/edge/guide/getting-started/index.md | 26 ++++++++++----------
docs/en/edge/guide/getting-started/ios/tools.md | 2 +-
.../guide/getting-started/windows-8/tools.md | 2 +-
.../getting-started/windows-phone-8/tools.md | 2 +-
.../en/edge/guide/upgrading/blackberry/index.md | 12 ++++-----
docs/en/edge/guide/upgrading/ios/index.md | 20 +++++++--------
14 files changed, 40 insertions(+), 40 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/cordova/camera/camera.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/cordova/camera/camera.md b/docs/en/edge/cordova/camera/camera.md
index 1fcc7e5..9b100e4 100644
--- a/docs/en/edge/cordova/camera/camera.md
+++ b/docs/en/edge/cordova/camera/camera.md
@@ -22,7 +22,7 @@ Camera
> The `camera` object provides access to the device's default camera application.
-**Important privacy note:** Collection and use of images from a device's camera raises important privacy issues. Your app's [privacy policy](guide_getting-started_index.md.html) should discuss how the app uses the camera and whether the images recorded are shared with any other parties. In addition, if the app's use of the camera is not apparent in the user interface, you should provide a just-in-time notice prior to your app accessing the camera (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). For more information, please see the Privacy Guide.
+**Important privacy note:** Collection and use of images from a device's camera raises important privacy issues. Your app's privacy policy should discuss how the app uses the camera and whether the images recorded are shared with any other parties. In addition, if the app's use of the camera is not apparent in the user interface, you should provide a just-in-time notice prior to your app accessing the camera (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). For more information, please see the Privacy Guide.
Methods
-------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/cordova/contacts/contacts.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/cordova/contacts/contacts.md b/docs/en/edge/cordova/contacts/contacts.md
index 05c4bc9..ec50fd7 100644
--- a/docs/en/edge/cordova/contacts/contacts.md
+++ b/docs/en/edge/cordova/contacts/contacts.md
@@ -22,7 +22,7 @@ Contacts
> The `contacts` object provides access to the device contacts database.
-**Important privacy note:** Collection and use of contact data raises important privacy issues. Your app's [privacy policy](guide_getting-started_index.md.html) should discuss how the app uses contact data and whether it is shared with any other parties. Contact information is considered sensitive because it reveals the people with whom a person communicates. Therefore, in addition to your app's privacy policy, you should strongly consider providing a just-in-time notice prior to your app accessing or using contact data (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). Note that some app marketplaces may require your app to provide just-in-time notice and obtain permission from the user prior to accessing contact data. A clear and easy to understand user experience surrounding the use of contact data will help avoi
d user confusion and perceived misuse of contact data. For more information, please see the Privacy Guide.
+**Important privacy note:** Collection and use of contact data raises important privacy issues. Your app's privacy policy should discuss how the app uses contact data and whether it is shared with any other parties. Contact information is considered sensitive because it reveals the people with whom a person communicates. Therefore, in addition to your app's privacy policy, you should strongly consider providing a just-in-time notice prior to your app accessing or using contact data (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). Note that some app marketplaces may require your app to provide just-in-time notice and obtain permission from the user prior to accessing contact data. A clear and easy to understand user experience surrounding the use of contact data will help avoid user confusion and perceived misuse o
f contact data. For more information, please see the Privacy Guide.
Methods
-------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/cordova/geolocation/geolocation.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/cordova/geolocation/geolocation.md b/docs/en/edge/cordova/geolocation/geolocation.md
index e771411..f2444c5 100644
--- a/docs/en/edge/cordova/geolocation/geolocation.md
+++ b/docs/en/edge/cordova/geolocation/geolocation.md
@@ -33,7 +33,7 @@ This API is based on the
[W3C Geolocation API Specification](http://dev.w3.org/geo/api/spec-source.html),
and only executes on devices that don't already provide an implementation.
-**Important privacy note:** Collection and use of geolocation data raises important privacy issues. Your app's [privacy policy](guide_getting-started_index.md.html) should discuss how the app uses geolocation data, whether it is shared with any other parties, and the level of precision of the data (for example, coarse, fine, ZIP code level, etc.). Geolocation data is generally considered sensitive because it can reveal a person's whereabouts and, if stored, the history of his or her travels. Therefore, in addition to your app's privacy policy, you should strongly consider providing a just-in-time notice prior to your app accessing geolocation data (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). For more information, please see the Privacy Guide.
+**Important privacy note:** Collection and use of geolocation data raises important privacy issues. Your app's privacy policy should discuss how the app uses geolocation data, whether it is shared with any other parties, and the level of precision of the data (for example, coarse, fine, ZIP code level, etc.). Geolocation data is generally considered sensitive because it can reveal a person's whereabouts and, if stored, the history of his or her travels. Therefore, in addition to your app's privacy policy, you should strongly consider providing a just-in-time notice prior to your app accessing geolocation data (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). For more information, please see the Privacy Guide.
Methods
-------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/cordova/media/capture/capture.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/cordova/media/capture/capture.md b/docs/en/edge/cordova/media/capture/capture.md
index 1e3ec56..ca184bb 100644
--- a/docs/en/edge/cordova/media/capture/capture.md
+++ b/docs/en/edge/cordova/media/capture/capture.md
@@ -22,7 +22,7 @@ Capture
> Provides access to the device's audio, image, and video capture capabilities.
-**Important privacy note:** Collection and use of images, video, or audio from the device's camera or microphone raises important privacy issues. Your app's [privacy policy](guide_getting-started_index.md.html) should discuss how the app uses such sensors and whether the data recorded is shared with any other parties. In addition, if the app's use of the camera or microphone is not apparent in the user interface, you should provide a just-in-time notice prior to your app accessing the camera or microphone (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). Note that some app marketplaces may require your app to provide just-in-time notice and obtain permission from the user prior to accessing the camera or microphone. For more information, please see the Privacy Guide.
+**Important privacy note:** Collection and use of images, video, or audio from the device's camera or microphone raises important privacy issues. Your app's privacy policy should discuss how the app uses such sensors and whether the data recorded is shared with any other parties. In addition, if the app's use of the camera or microphone is not apparent in the user interface, you should provide a just-in-time notice prior to your app accessing the camera or microphone (if the device operating system doesn't do so already). That notice should provide the same information noted above, as well as obtaining the user's permission (e.g., by presenting choices for "OK" and "No Thanks"). Note that some app marketplaces may require your app to provide just-in-time notice and obtain permission from the user prior to accessing the camera or microphone. For more information, please see the Privacy Guide.
Objects
-------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/cordova-webview/ios.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/cordova-webview/ios.md b/docs/en/edge/guide/cordova-webview/ios.md
index 4605368..5da6e36 100644
--- a/docs/en/edge/guide/cordova-webview/ios.md
+++ b/docs/en/edge/guide/cordova-webview/ios.md
@@ -35,7 +35,7 @@ Prerequisites
1. **Cordova 2.3.0** or greater
2. **Xcode 4.5** or greater
-3. `config.xml` file (from a [newly created](guide_command-line_index.md.html#Command-Line%20Usage_ios) Cordova project)
+3. `config.xml` file (from a newly created iOS project)
Adding Cleaver to your Xcode project (CordovaLib sub-project)
-------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/android/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/android/tools.md b/docs/en/edge/guide/getting-started/android/tools.md
index 03b0ac2..09fcfdc 100644
--- a/docs/en/edge/guide/getting-started/android/tools.md
+++ b/docs/en/edge/guide/getting-started/android/tools.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Android Command-Line Tools
+# Android Command-line Tools
The `cordova` command-line utility is a high-level tool that allows
you to build applications across several platforms at once. An older
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/blackberry/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry/tools.md b/docs/en/edge/guide/getting-started/blackberry/tools.md
index f7f7447..8bd2987 100644
--- a/docs/en/edge/guide/getting-started/blackberry/tools.md
+++ b/docs/en/edge/guide/getting-started/blackberry/tools.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Blackberry Command-Line Tools
+# Blackberry Command-line Tools
The `cordova` command-line utility is a high-level tool that allows
you to build applications across several platforms at once. An older
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/blackberry10/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/blackberry10/tools.md b/docs/en/edge/guide/getting-started/blackberry10/tools.md
index e759738..07ac1c6 100644
--- a/docs/en/edge/guide/getting-started/blackberry10/tools.md
+++ b/docs/en/edge/guide/getting-started/blackberry10/tools.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Blackberry 10 Command-Line Tools
+# Blackberry 10 Command-line Tools
The `cordova` command-line utility is a high-level tool that allows
you to build applications across several platforms at once. An older
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/index.md b/docs/en/edge/guide/getting-started/index.md
index 9c080f9..c58f0c7 100644
--- a/docs/en/edge/guide/getting-started/index.md
+++ b/docs/en/edge/guide/getting-started/index.md
@@ -38,49 +38,49 @@ configuration options, instructions to add plugins, how to upgrade
each platform, and platform-specific command-line tools that serve as
a lower-level alternative to the `cordova` command-line utility.
-## Android (Windows, Mac, Linux)
+## Android
* Android Platform Guide
* Android Configuration
* Android Plugins
-* Android Command-Line Tools
+* Android Command-line Tools
* Upgrading Android
-## BlackBerry (Windows, Mac)
+## BlackBerry
* BlackBerry Platform Guide
* BlackBerry Configuration
-* Blackberry Command-Line Tools
+* Blackberry Command-line Tools
* Upgrading BlackBerry
-## BlackBerry 10 (Windows, Mac)
+## BlackBerry 10
* BlackBerry 10 Platform Guide
* BlackBerry 10 Plugins
-* Blackberry 10 Command-Line Tools
+* Blackberry 10 Command-line Tools
-## iOS (Mac)
+## iOS
* iOS Platform Guide
* iOS Configuration
* iOS Plugins
-* iOS Command-Line Tools
+* iOS Command-line Tools
* Upgrading iOS
## Windows Phone
-* Windows Phone 8 Platform Guide (Windows 8)
+* Windows Phone 8 Platform Guide
* Windows Phone 8 Configuration
-* Windows Phone 7 Platform Guide (Windows 7 or 8)
+* Windows Phone 7 Platform Guide
* Windows Phone 7 Configuration
-* Windows Phone Command-Line Tools
+* Windows Phone Command-line Tools
* Upgrading Windows Phone
## Windows 8
-* Windows 8 Platform Guide (Windows 8)
+* Windows 8 Platform Guide
* Windows 8 Configuration
-* Windows 8 Command-Line Tools
+* Windows 8 Command-line Tools
* Upgrading Windows 8
## Tizen
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/ios/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/ios/tools.md b/docs/en/edge/guide/getting-started/ios/tools.md
index ea7cdee..c37dbcd 100644
--- a/docs/en/edge/guide/getting-started/ios/tools.md
+++ b/docs/en/edge/guide/getting-started/ios/tools.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# iOS Command-Line Tools
+# iOS Command-line Tools
The `cordova` command-line utility is a high-level tool that allows
you to build applications across several platforms at once. An older
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/windows-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-8/tools.md b/docs/en/edge/guide/getting-started/windows-8/tools.md
index 355016a..9fbb26d 100644
--- a/docs/en/edge/guide/getting-started/windows-8/tools.md
+++ b/docs/en/edge/guide/getting-started/windows-8/tools.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Windows 8 Command-Line Tools
+# Windows 8 Command-line Tools
The `cordova` command-line utility is a high-level tool that allows
you to build applications across several platforms at once. An older
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/windows-phone-8/tools.md b/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
index b096671..df821e2 100644
--- a/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
+++ b/docs/en/edge/guide/getting-started/windows-phone-8/tools.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-# Windows Phone Command-Line Tools
+# Windows Phone Command-line Tools
The `cordova` command-line utility is a high-level tool that allows
you to build applications across several platforms at once. An older
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/upgrading/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/blackberry/index.md b/docs/en/edge/guide/upgrading/blackberry/index.md
index 0b91c77..a50cddb 100644
--- a/docs/en/edge/guide/upgrading/blackberry/index.md
+++ b/docs/en/edge/guide/upgrading/blackberry/index.md
@@ -29,7 +29,7 @@ This document describes the process of upgrading Cordova projects to the latest
1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.9.0)
2. **Quit any running IDE's** Eclipse, Momentics and the lik
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**](guide_command-line_index.md.html#Command-Line%20Usage_blackberry) from the command-line tools - this will be the home of your updated project
+4. **Create a new project**, as described in Blackberry Command-line Tools. This becomes the home of your updated project.
5. **Copy** your projects source from the old project's /www folder to the new project's /www folder
6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
@@ -38,7 +38,7 @@ This document describes the process of upgrading Cordova projects to the latest
1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.9.0)
2. **Quit any running IDE's** 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**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools - you will have to grab the assets from this new project
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova.js** file from the new project into your **www** folder, and delete your **www/cordova.js** file
6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
@@ -49,13 +49,13 @@ This document describes the process of upgrading Cordova projects to the latest
### BlackBerry10 ###
-BlackBerry10 uses the new CLI tooling and manages core api's 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.
+BlackBerry10 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 folder location** on your hard drive (say to ~/Cordova-2.8.0)
2. **Quit any running IDE's** 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**](guide_command-line_index.md.html#Command-Line%20Usage_blackberry) from the command-line tools - this will be the home of your updated project
+4. **Create a new project**, as described in Blackberry Command-line Tools. This becomes the home of your updated project.
5. **Copy** your projects source from the old project's /www folder to the new project's /www folder
6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
@@ -64,7 +64,7 @@ Also note that the cordova js script file is now called 'cordova.js' and no long
1. **Download and extract the Cordova 2.8.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.8.0)
2. **Quit any running IDE's** 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**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools - you will have to grab the assets from this new project
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova.js** file from the new project into your **www** folder, and delete your **www/cordova.js** file
6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
@@ -76,7 +76,7 @@ Also note that the cordova js script file is now called 'cordova.js' and no long
1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.7.0)
2. **Quit any running IDE's** 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**](guide_command-line_index.md.html#Command-Line%20Usage_blackberry) from the command-line tools - you will have to grab the assets from this new project
+4. **Create a new project**, as described in Blackberry Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova-2.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.6.0.js** file
6. **Update** the Cordova script reference in your **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** folder from the new project into the existing project, overwriting the old **native** folder
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/08f3a019/docs/en/edge/guide/upgrading/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/ios/index.md b/docs/en/edge/guide/upgrading/ios/index.md
index 72313b1..4009bc2 100644
--- a/docs/en/edge/guide/upgrading/ios/index.md
+++ b/docs/en/edge/guide/upgrading/ios/index.md
@@ -27,7 +27,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.9.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools - you will have to grab the assets from this new project
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova.js** (note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your **www** folder, and delete your **www/cordova.js** file
6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
7. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
@@ -37,7 +37,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.8.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.8.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools - you will have to grab the assets from this new project
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova.js** (note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your **www** folder, and delete your **www/cordova-2.7.0.js** file
6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
7. Update any <plugin> tags that are in your **config.xml** to <feature> tags. Note that existing <plugin> tags will still work, but are deprecated. You can copy this information in the **config.xml** for a new project. For example:
@@ -68,7 +68,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.7.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools - you will have to grab the assets from this new project
+4. **Create a new project**, as described in iOS Command-line Tools. you need the assets from this new project.
5. **Copy** the **www/cordova-2.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.6.0.js** file
6. **Update** the Cordova script reference in your **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. Update (or replace, if you never changed the file) your **AppDelegate.m** file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=5c05ac80e056753c0e8736f887ba9f28d5b0774c;hp=623ad8ec3c46f656ea18c6c3a190d650dd64e479;hb=c6e71147386d4ad94b07428952d1aae0a9cbf3f5;hpb=c017fda8af00375a453cf27cfc488647972e9a23))
@@ -81,7 +81,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.6.0 source** to a **permanent folder location** on your hard drive (say to `~/Documents/Cordova-2.6.0`)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the project's `www/cordova-2.6.0.js` file into your `www` folder, and delete your `www/cordova-2.5.0.js` file.
6. **Update** the Cordova script reference in your `www/index.html` file (along with any other files that reference the script) to refer to the new `cordova-2.6.0.js` file.
7. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=124a56bb4f361e95616f44d6d6f5a96ffa439b60;hp=318f79326176be8f16ebc93bad85dd745f4205b6;hb=a28c7712810a63396e9f32fa4eb94fe3f8b93985;hpb=36acdf55e4cab52802d73764c8a4b5b42cf18ef9))
@@ -96,7 +96,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.5.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.5.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova-2.5.0.js** file from the new project into your **www** folder and delete your **www/cordova-2.4.0.js** file
6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.5.0.js** file
7. Update (or replace, if you never changed the file) your `AppDelegate.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/AppDelegate.m;h=318f79326176be8f16ebc93bad85dd745f4205b6;hp=6dc7bfc84f0ecede4cc43d2a3256ef7c5383b9fe;hb=4001ae13fcb1fcbe73168327630fbc0ce44703d0;hpb=299a324e8c30065fc4511c1fe59c6515d4842f09))
@@ -111,7 +111,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.4.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.4.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova-2.4.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.3.0.js** file
6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.4.0.js** file
7. Update (or replace, if you never changed the files) your `MainViewController.m` file according to the one from the new project (see [this diff](https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__/Classes/MainViewController.m;h=5f9eeac15c2437cd02a6eb5835b48374e9b94100;hp=89da1082d06ba5e5d0dffc5b2e75a3a06d5c2aa6;hb=b4a2e4ae0445ba7aec788090dce9b822d67edfd8;hpb=a484850f4610e73c7b20cd429a7794ba829ec997)).
@@ -126,7 +126,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
1. **Download and extract the Cordova 2.3.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.3.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova-2.3.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.2.0.js** file
6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.3.0.js** file
7. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project.
@@ -148,7 +148,7 @@ You can get this by accessing the **userAgent** property off the main view-contr
1. **Download and extract the Cordova 2.2.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.2.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-4. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+4. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
5. **Copy** the **www/cordova-2.2.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.1.0.js** file
6. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.2.0.js** file
7. Update (or replace, if you never changed the file) your `MainViewController.m` according to the one from the new project:
@@ -170,7 +170,7 @@ With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Referenc
1. **Download and extract the Cordova 2.1.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.1.0)
2. **Quit Xcode** if it is running.
3. **Navigate** to the directory where you put the downloaded source above, using **Terminal.app**.
-5. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+5. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
6. **Copy** the **www/cordova-2.1.0.js** file from the new project into your **www** folder, and delete your **www/cordova-2.0.0.js** file
7. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.1.0.js** file
8. Update (or replace, if you never changed the file) your `AppDelegate.m` according to the one from the new project:
@@ -190,7 +190,7 @@ With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Referenc
## Upgrading 1.9.0 projects to 2.0.0 ##
1. **Install** Cordova 2.0.0
-2. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
+2. **Create a new project**, as described in iOS Command-line Tools. You need the assets from this new project.
3. **Copy** the **www/cordova-2.0.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.9.0.js** file
4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-2.0.0.js** file
5. Copy the **cordova** folder from the new project into your project's root folder (if you want the project command-line tools)
[19/20] docs commit: [CB-3827] suppress display of firefoxos content
Posted by mw...@apache.org.
[CB-3827] suppress display of firefoxos content
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/1cfcb959
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/1cfcb959
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/1cfcb959
Branch: refs/heads/master
Commit: 1cfcb959469fa7024cf104774f1e6ff77a4317b5
Parents: 5a8c2cc
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 14:09:10 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 14:09:10 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/platforms/index.md | 2 ++
1 file changed, 2 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/1cfcb959/docs/en/edge/guide/platforms/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/index.md b/docs/en/edge/guide/platforms/index.md
index b26e5f1..77b010f 100644
--- a/docs/en/edge/guide/platforms/index.md
+++ b/docs/en/edge/guide/platforms/index.md
@@ -90,6 +90,8 @@ a lower-level alternative to the `cordova` command-line utility.
* Tizen Platform Guide
+<!--
## FirefoxOS
* FirefoxOS Configuration
+-->
[17/20] docs commit: [CB-3827] redirect hard-coded HTML links based
on new dir structure
Posted by mw...@apache.org.
[CB-3827] redirect hard-coded HTML links based on new dir structure
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/cf9a3c3a
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/cf9a3c3a
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/cf9a3c3a
Branch: refs/heads/master
Commit: cf9a3c3a2778d22cb72137747a758d7f16b6f14c
Parents: 96d79d8
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 13:34:12 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 13:34:12 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/overview/index.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/cf9a3c3a/docs/en/edge/guide/overview/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/overview/index.md b/docs/en/edge/guide/overview/index.md
index 4dcbb7b..0da9f96 100644
--- a/docs/en/edge/guide/overview/index.md
+++ b/docs/en/edge/guide/overview/index.md
@@ -174,17 +174,17 @@ available for each mobile platform:
<td data-col="blackberry" class="y"><a href="guide_platforms_blackberry_index.md.html"> </a></td>
<td data-col="blackberry10" class="y"><a href="guide_platforms_blackberry10_index.md.html"> </a></td>
<td data-col="ios" class="y"><a href="guide_platforms_ios_index.md.html"> </a></td>
- <td data-col="winphone7" class="y"><a href="guide_platforms_windows-phone-7_index.md.html"> </a></td>
+ <td data-col="winphone7" class="y"><a href="guide_platforms_wp7_index.md.html"> </a></td>
<td data-col="winphone8" class="y"><a href="guide_platforms_windows-phone-8_index.md.html"> </a></td>
<td data-col="win8" class="y"><a href="guide_platforms_windows-8_index.md.html"> </a></td>
</tr>
<tr>
<th><a href="#">Embedded<br/>WebView</a></th>
- <td data-col="android" class="y"><a href="guide_cordova-webview_android.md.html"></a></td>
+ <td data-col="android" class="y"><a href="guide_platforms_android_webview.md.html"></a></td>
<td data-col="blackberry" class="n"></td>
<td data-col="blackberry10" class="n"></td>
- <td data-col="ios" class="y"><a href="guide_cordova-webview_ios.md.html"></a></td>
+ <td data-col="ios" class="y"><a href="guide_platforms_ios_webview.md.html"></a></td>
<td data-col="winphone7" class="n"></td>
<td data-col="winphone8" class="n"></td>
<td data-col="win8" class="n"></td>
@@ -192,11 +192,11 @@ available for each mobile platform:
<tr>
<th><a href="guide_plugin-development_index.md.html">Plug-in<br/>Interface</a></th>
- <td data-col="android" class="y"><a href="guide_plugin-development_android_index.md.html"></a></td>
- <td data-col="blackberry" class="y"><a href="guide_plugin-development_blackberry_index.md.html"></a></td>
- <td data-col="blackberry10" class="y"><a href="guide_plugin-development_blackberry10_index.md.html"></a></td>
- <td data-col="ios" class="y"><a href="guide_plugin-development_ios_index.md.html"></a></td>
- <td data-col="winphone7" class="y"><a href="guide_plugin-development_windows-phone_index.md.html"></a></td>
+ <td data-col="android" class="y"><a href="guide_guide_platforms_android_plugin.md.html"></a></td>
+ <td data-col="blackberry" class="y"><a href="guide_guide_platforms_blackberry_plugin.md.html"></a></td>
+ <td data-col="blackberry10" class="y"><a href="guide_guide_platforms_blackberry10_plugin.md.html"></a></td>
+ <td data-col="ios" class="y"><a href="guide_guide_platforms_ios_plugin.md.html"></a></td>
+ <td data-col="winphone7" class="y"><a href="guide_guide_platforms_wp8_plugin.md.html"></a></td>
<td data-col="winphone8" class="n"></td>
<td data-col="win8" class="n"></td>
</tr>
[18/20] docs commit: [CB-3827] rename img dirs & redirect links
Posted by mw...@apache.org.
[CB-3827] rename img dirs & redirect links
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/5a8c2ccd
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/5a8c2ccd
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/5a8c2ccd
Branch: refs/heads/master
Commit: 5a8c2ccdfa41f2cdc5e2aab6e163599f4469206b
Parents: cf9a3c3
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 13:44:17 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 13:44:17 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/platforms/win8/index.md | 6 +++---
docs/en/edge/guide/platforms/wp7/index.md | 8 ++++----
docs/en/edge/guide/platforms/wp8/index.md | 8 ++++----
.../default/img/guide/platforms/win8/wsalert.png | Bin 0 -> 44166 bytes
.../img/guide/platforms/win8/wschangemanifest.png | Bin 0 -> 112224 bytes
.../img/guide/platforms/win8/wsnewproject.png | Bin 0 -> 189370 bytes
.../img/guide/platforms/windows-8/wsalert.png | Bin 44166 -> 0 bytes
.../platforms/windows-8/wschangemanifest.png | Bin 112224 -> 0 bytes
.../guide/platforms/windows-8/wsnewproject.png | Bin 189370 -> 0 bytes
.../platforms/windows-phone-7/wp7emulator.png | Bin 41379 -> 0 bytes
.../windows-phone-7/wp7projectstructure.png | Bin 22436 -> 0 bytes
.../img/guide/platforms/windows-phone-7/wp7vs.png | Bin 29416 -> 0 bytes
.../img/guide/platforms/windows-phone-7/wpd.png | Bin 1964 -> 0 bytes
.../platforms/windows-phone-7/wpfirstrun.png | Bin 114030 -> 0 bytes
.../guide/platforms/windows-phone-7/wpnewproj.png | Bin 87470 -> 0 bytes
.../img/guide/platforms/windows-phone-7/wprun.png | Bin 63091 -> 0 bytes
.../platforms/windows-phone-8/BuidDevice.png | Bin 9935 -> 0 bytes
.../platforms/windows-phone-8/BuildEmulator.png | Bin 15667 -> 0 bytes
.../platforms/windows-phone-8/FullTemplate.png | Bin 77781 -> 0 bytes
.../windows-phone-8/StandAloneTemplate.png | Bin 78237 -> 0 bytes
.../windows-phone-8/projectStructure.png | Bin 9225 -> 0 bytes
.../img/guide/platforms/wp7/wp7emulator.png | Bin 0 -> 41379 bytes
.../guide/platforms/wp7/wp7projectstructure.png | Bin 0 -> 22436 bytes
.../default/img/guide/platforms/wp7/wp7vs.png | Bin 0 -> 29416 bytes
.../docs/default/img/guide/platforms/wp7/wpd.png | Bin 0 -> 1964 bytes
.../img/guide/platforms/wp7/wpfirstrun.png | Bin 0 -> 114030 bytes
.../default/img/guide/platforms/wp7/wpnewproj.png | Bin 0 -> 87470 bytes
.../default/img/guide/platforms/wp7/wprun.png | Bin 0 -> 63091 bytes
.../img/guide/platforms/wp8/BuidDevice.png | Bin 0 -> 9935 bytes
.../img/guide/platforms/wp8/BuildEmulator.png | Bin 0 -> 15667 bytes
.../img/guide/platforms/wp8/FullTemplate.png | Bin 0 -> 77781 bytes
.../guide/platforms/wp8/StandAloneTemplate.png | Bin 0 -> 78237 bytes
.../img/guide/platforms/wp8/projectStructure.png | Bin 0 -> 9225 bytes
33 files changed, 11 insertions(+), 11 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/docs/en/edge/guide/platforms/win8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/win8/index.md b/docs/en/edge/guide/platforms/win8/index.md
index 3372889..658ca32 100644
--- a/docs/en/edge/guide/platforms/win8/index.md
+++ b/docs/en/edge/guide/platforms/win8/index.md
@@ -55,11 +55,11 @@ expose the same APIs as on other Cordova-supported platforms.
- Open Visual Studio 2012 and choose **New Project**.
- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as **CordovaWin8Foo** as in this example.
- 
+ 
- Microsoft continues to use `default.html` as the default home page, but most web developers use `index.html`. (Plus it's likely that in the other platform variants of your project you are using `index.html` as the name of your default page.) To fix this, in Solution Explorer rename the `default.html` file to `index.html`. Then double-click the `package.appxmanifest` file and change the **Start page** value to `index.html`.
- 
+ 
- To include `cordova.js` in your project, right-click on the **js** folder in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the **lib\windows-8** folder noted above.
@@ -102,7 +102,7 @@ expose the same APIs as on other Cordova-supported platforms.
- Run the project from Visual Studio. You'll see the message box appear:
- 
+ 
Done!
-----
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/docs/en/edge/guide/platforms/wp7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp7/index.md b/docs/en/edge/guide/platforms/wp7/index.md
index a227130..beeb37c 100644
--- a/docs/en/edge/guide/platforms/wp7/index.md
+++ b/docs/en/edge/guide/platforms/wp7/index.md
@@ -59,7 +59,7 @@ Open Visual Studio and choose __Open Project__. Navigate to the
`hello/platforms/wp7` directory and choose the `Hello_World.sln` file.
The SDK displays the directory's contents:
-
+
At this point you can modify the app within the SDK, but running the
`build` or `prepare` commands again wipes out local changes. If Visual
@@ -73,12 +73,12 @@ Within the SDK, select the __Windows Phone Emulator__ target from the
popup menu in the main menu bar, and press the green button to run the
emulator:
-
+
The app displays on the emulator's home screen as it would on a real
device:
-
+
## Deploy to Device
@@ -91,5 +91,5 @@ Once registered, you need to make sure the phone is connected via USB
with its screen unlocked. In Visual Studio, choose the __Windows Phone
Device__ target and press the green button to run it:
-
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/docs/en/edge/guide/platforms/wp8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/index.md b/docs/en/edge/guide/platforms/wp8/index.md
index 85a02ae..fac477b 100644
--- a/docs/en/edge/guide/platforms/wp8/index.md
+++ b/docs/en/edge/guide/platforms/wp8/index.md
@@ -94,7 +94,7 @@ choose __do not include in project__.
- Select **CordovaWP8**. (The version number is displayed in the template description.)
- Give the project a name, and select __OK__.
-
+
4. Review the project structure
-------------------------------
@@ -103,7 +103,7 @@ choose __do not include in project__.
- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
- Note: This screen capture was from the cordova-2.3.0 download, your listing will vary based on the actual version installed.
-
+
5. Build and Deploy to Emulator
-------------------------------
@@ -111,7 +111,7 @@ choose __do not include in project__.
- Make sure **Windows Phone Emulator** is selected in the main drop-down menu.
- Press the green **play** button next to the drop-down menu to start debugging, or type __F5__.
-
+
6. Build your project for the device
------------------------------------
@@ -122,7 +122,7 @@ In order to test your application on a device, the device must be registered. Cl
- In Visual Studio, select 'Device' from the top drop-down menu.
- Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
-
+
Done!
-----
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/win8/wsalert.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/win8/wsalert.png b/template/docs/default/img/guide/platforms/win8/wsalert.png
new file mode 100755
index 0000000..9680e53
Binary files /dev/null and b/template/docs/default/img/guide/platforms/win8/wsalert.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/win8/wschangemanifest.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/win8/wschangemanifest.png b/template/docs/default/img/guide/platforms/win8/wschangemanifest.png
new file mode 100755
index 0000000..1dd67da
Binary files /dev/null and b/template/docs/default/img/guide/platforms/win8/wschangemanifest.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/win8/wsnewproject.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/win8/wsnewproject.png b/template/docs/default/img/guide/platforms/win8/wsnewproject.png
new file mode 100755
index 0000000..8e1df69
Binary files /dev/null and b/template/docs/default/img/guide/platforms/win8/wsnewproject.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-8/wsalert.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-8/wsalert.png b/template/docs/default/img/guide/platforms/windows-8/wsalert.png
deleted file mode 100755
index 9680e53..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-8/wsalert.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png b/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png
deleted file mode 100755
index 1dd67da..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-8/wschangemanifest.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png b/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png
deleted file mode 100755
index 8e1df69..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-8/wsnewproject.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png b/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png
deleted file mode 100644
index e3de172..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wp7emulator.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png b/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png
deleted file mode 100644
index 0c7d42d..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wp7projectstructure.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png b/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png
deleted file mode 100644
index 4e14c2f..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wp7vs.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png b/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png
deleted file mode 100644
index 0a0b2db..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wpd.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png b/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png
deleted file mode 100644
index 8a82ec6..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wpfirstrun.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png b/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png
deleted file mode 100644
index ed2f143..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wpnewproj.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png b/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png
deleted file mode 100644
index ce67de9..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-7/wprun.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png b/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png
deleted file mode 100644
index 92ea56d..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-8/BuidDevice.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png b/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png
deleted file mode 100644
index 5893f64..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-8/BuildEmulator.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png b/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png
deleted file mode 100644
index 85f49cf..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-8/FullTemplate.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png b/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png
deleted file mode 100644
index 62a98c4..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-8/StandAloneTemplate.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png b/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png
deleted file mode 100644
index 9956094..0000000
Binary files a/template/docs/default/img/guide/platforms/windows-phone-8/projectStructure.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wp7emulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wp7emulator.png b/template/docs/default/img/guide/platforms/wp7/wp7emulator.png
new file mode 100644
index 0000000..e3de172
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wp7emulator.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wp7projectstructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wp7projectstructure.png b/template/docs/default/img/guide/platforms/wp7/wp7projectstructure.png
new file mode 100644
index 0000000..0c7d42d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wp7projectstructure.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wp7vs.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wp7vs.png b/template/docs/default/img/guide/platforms/wp7/wp7vs.png
new file mode 100644
index 0000000..4e14c2f
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wp7vs.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wpd.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wpd.png b/template/docs/default/img/guide/platforms/wp7/wpd.png
new file mode 100644
index 0000000..0a0b2db
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wpd.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wpfirstrun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wpfirstrun.png b/template/docs/default/img/guide/platforms/wp7/wpfirstrun.png
new file mode 100644
index 0000000..8a82ec6
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wpfirstrun.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wpnewproj.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wpnewproj.png b/template/docs/default/img/guide/platforms/wp7/wpnewproj.png
new file mode 100644
index 0000000..ed2f143
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wpnewproj.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp7/wprun.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp7/wprun.png b/template/docs/default/img/guide/platforms/wp7/wprun.png
new file mode 100644
index 0000000..ce67de9
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp7/wprun.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp8/BuidDevice.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp8/BuidDevice.png b/template/docs/default/img/guide/platforms/wp8/BuidDevice.png
new file mode 100644
index 0000000..92ea56d
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp8/BuidDevice.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp8/BuildEmulator.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp8/BuildEmulator.png b/template/docs/default/img/guide/platforms/wp8/BuildEmulator.png
new file mode 100644
index 0000000..5893f64
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp8/BuildEmulator.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp8/FullTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp8/FullTemplate.png b/template/docs/default/img/guide/platforms/wp8/FullTemplate.png
new file mode 100644
index 0000000..85f49cf
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp8/FullTemplate.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp8/StandAloneTemplate.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp8/StandAloneTemplate.png b/template/docs/default/img/guide/platforms/wp8/StandAloneTemplate.png
new file mode 100644
index 0000000..62a98c4
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp8/StandAloneTemplate.png differ
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/5a8c2ccd/template/docs/default/img/guide/platforms/wp8/projectStructure.png
----------------------------------------------------------------------
diff --git a/template/docs/default/img/guide/platforms/wp8/projectStructure.png b/template/docs/default/img/guide/platforms/wp8/projectStructure.png
new file mode 100644
index 0000000..9956094
Binary files /dev/null and b/template/docs/default/img/guide/platforms/wp8/projectStructure.png differ
[02/20] docs commit: [CB-3827] list Upgrading guides within Platform
Guides; rm redundant "Cordova"
Posted by mw...@apache.org.
[CB-3827] list Upgrading guides within Platform Guides; rm redundant "Cordova"
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/f488410b
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/f488410b
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/f488410b
Branch: refs/heads/master
Commit: f488410bcbe9af774de273ef6d98e9407242ba6e
Parents: 6ac5f0c
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 10:32:11 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 10:32:11 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/getting-started/index.md | 22 ++++++----
docs/en/edge/guide/upgrading/android/index.md | 2 +-
.../en/edge/guide/upgrading/blackberry/index.md | 8 ++--
docs/en/edge/guide/upgrading/index.md | 10 ++---
docs/en/edge/guide/upgrading/ios/index.md | 44 ++++++++++----------
docs/en/edge/guide/upgrading/windows-8/index.md | 2 +-
.../edge/guide/upgrading/windows-phone/index.md | 2 +-
7 files changed, 48 insertions(+), 42 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/getting-started/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/getting-started/index.md b/docs/en/edge/guide/getting-started/index.md
index 28461fb..e2367d4 100644
--- a/docs/en/edge/guide/getting-started/index.md
+++ b/docs/en/edge/guide/getting-started/index.md
@@ -29,20 +29,21 @@ platform you are targeting. This installation is necessary regardless
of whether you do the majority of your work in the SDK or use the CLI
for your build cycle.
-Each platform guide listed below tells you what you need to know to
-set up each development environment: where to obtain the SDK, how to
-set up device emulators, how to connect devices for direct testing,
-and managing signing key requirements. Additional guides provide
-information on each platform's available configuration settings,
-instructions to add plugins, how to upgrade each platform, and
-platform-specific command-line tools that serve as an alternative to
-the `cordova` command-line tool.
+Each _Platform Guide_ listed below tells you what you need to know to
+set up each platform's development environment: where to obtain the
+SDK, how to set up device emulators, how to connect devices for direct
+testing, and how to manage signing key requirements. Additional
+guides provide information on each platform's unique set of
+configuration options, instructions to add plugins, how to upgrade
+each platform, and platform-specific command-line tools that serve as
+a lower-level alternative to the `cordova` command-line utility.
## Android (Windows, Mac, Linux)
* Android Platform Guide
* Android Configuration
* Android Plugins
+* Upgrading Android
## BlackBerry (Windows, Mac)
@@ -50,12 +51,14 @@ the `cordova` command-line tool.
* BlackBerry 10 Platform Guide
* BlackBerry Configuration
* BlackBerry 10 Plugins
+* Upgrading BlackBerry
## iOS (Mac)
* iOS Platform Guide
* iOS Configuration
* iOS Plugins
+* Upgrading iOS
## Windows Phone
@@ -64,9 +67,11 @@ the `cordova` command-line tool.
* Windows Phone 8 Platform Guide (Windows 8)
* Windows Phone 8 Configuration
+* Upgrading Windows Phone
* Windows 8 Platform Guide (Windows 8)
* Windows 8 Configuration
+* Upgrading Windows 8
## Tizen
@@ -75,3 +80,4 @@ the `cordova` command-line tool.
## FirefoxOS
* FirefoxOS Configuration
+
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/upgrading/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/android/index.md b/docs/en/edge/guide/upgrading/android/index.md
index 4ab9b0e..63019d3 100644
--- a/docs/en/edge/guide/upgrading/android/index.md
+++ b/docs/en/edge/guide/upgrading/android/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Upgrading Cordova Android
+Upgrading Android
=========================
This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/upgrading/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/blackberry/index.md b/docs/en/edge/guide/upgrading/blackberry/index.md
index 3242da6..0b91c77 100644
--- a/docs/en/edge/guide/upgrading/blackberry/index.md
+++ b/docs/en/edge/guide/upgrading/blackberry/index.md
@@ -17,12 +17,12 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Upgrading Cordova BlackBerry
+Upgrading BlackBerry
============================
This document describes the process of upgrading Cordova projects to the latest released version
-## Upgrading Cordova 2.8.0 projects to 2.9.0 ##
+## Upgrading 2.8.0 projects to 2.9.0 ##
### BlackBerry10 ###
@@ -45,7 +45,7 @@ This document describes the process of upgrading Cordova projects to the latest
8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
-## Upgrading Cordova 2.7.0 projects to 2.8.0 ##
+## Upgrading 2.7.0 projects to 2.8.0 ##
### BlackBerry10 ###
@@ -71,7 +71,7 @@ Also note that the cordova js script file is now called 'cordova.js' and no long
8. **Copy** the **lib** folder from the new project into the existing project, overwriting the old **lib** folder
9. **Copy** the **cordova** folder from the new project into the existing project, overwriting the old **cordova** folder
-## Upgrading Cordova 2.6.0 projects to 2.7.0 ##
+## Upgrading 2.6.0 projects to 2.7.0 ##
1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Cordova-2.7.0)
2. **Quit any running IDE's** Eclipse, Momentics and the like.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/upgrading/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/index.md b/docs/en/edge/guide/upgrading/index.md
index ecac766..ac4b96f 100644
--- a/docs/en/edge/guide/upgrading/index.md
+++ b/docs/en/edge/guide/upgrading/index.md
@@ -22,9 +22,9 @@ Upgrading Guides
> Learn how to upgrade an application to the latest Apache Cordova release.
-- Upgrading Cordova Android
-- Upgrading Cordova BlackBerry
-- Upgrading Cordova iOS
-- Upgrading Cordova Windows Phone
-- Upgrading Cordova Windows 8
+- Upgrading Android
+- Upgrading BlackBerry
+- Upgrading iOS
+- Upgrading Windows Phone
+- Upgrading Windows 8
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/upgrading/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/ios/index.md b/docs/en/edge/guide/upgrading/ios/index.md
index 6130d05..72313b1 100644
--- a/docs/en/edge/guide/upgrading/ios/index.md
+++ b/docs/en/edge/guide/upgrading/ios/index.md
@@ -17,12 +17,12 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Upgrading Cordova iOS
+Upgrading iOS
=====================
Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, you must use the latest shipped version of the iOS SDK, which is iOS 6. The iOS 6 SDK requires Xcode 4.5.
-## Upgrading Cordova 2.8.0 projects to 2.9.0 ##
+## Upgrading 2.8.0 projects to 2.9.0 ##
1. **Download and extract the Cordova 2.9.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.9.0)
2. **Quit Xcode** if it is running.
@@ -32,7 +32,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
6. **Update** the Cordova script reference in your **www/index.html** file (and any other files that contain the script reference) to point to the new **cordova.js** file
7. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
-## Upgrading Cordova 2.7.0 projects to 2.8.0 ##
+## Upgrading 2.7.0 projects to 2.8.0 ##
1. **Download and extract the Cordova 2.8.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.8.0)
2. **Quit Xcode** if it is running.
@@ -63,7 +63,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
11. Update your project's target **Build Settings**. Under **Linking** -> **Other Linker Flags**, change **"-all\_load"** to be **"-force\_load ${TARGET\_BUILD\_DIR}/libCordova.a"**. You would only need to do this if you have the problem defined in [this issue.](https://issues.apache.org/jira/browse/CB-3458)
-## Upgrading Cordova 2.6.0 projects to 2.7.0 ##
+## Upgrading 2.6.0 projects to 2.7.0 ##
1. **Download and extract the Cordova 2.7.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.7.0)
2. **Quit Xcode** if it is running.
@@ -76,7 +76,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
9. Delete your **"CordovaLib"** folder, and copy the **"CordovaLib"** folder from the new project into your project's root folder
-## Upgrading Cordova 2.5.0 projects to 2.6.0 ##
+## Upgrading 2.5.0 projects to 2.6.0 ##
1. **Download and extract the Cordova 2.6.0 source** to a **permanent folder location** on your hard drive (say to `~/Documents/Cordova-2.6.0`)
2. **Quit Xcode** if it is running.
@@ -91,7 +91,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
10. In your `config.xml` file, the **EnableLocation** preference has been **deprecated**.
11. Delete your `CordovaLib` folder, and copy the `CordovaLib` folder from the new project into your project's root folder.
-## Upgrading Cordova 2.4.0 projects to 2.5.0 ##
+## Upgrading 2.4.0 projects to 2.5.0 ##
1. **Download and extract the Cordova 2.5.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.5.0)
2. **Quit Xcode** if it is running.
@@ -106,7 +106,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
11. Delete your **cordova** folder, and copy the **cordova** folder from the new project into your project's root folder **(in 2.5.0, this has updated scripts)**
12. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
-## Upgrading Cordova 2.3.0 projects to 2.4.0 ##
+## Upgrading 2.3.0 projects to 2.4.0 ##
1. **Download and extract the Cordova 2.4.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.4.0)
2. **Quit Xcode** if it is running.
@@ -121,7 +121,7 @@ Please note that **Xcode 4.5 is required**. To submit to the Apple App Store, yo
11. Delete your **CordovaLib** folder, and copy the **CordovaLib** folder from the new project into your project's root folder
12. Add AssetsLibrary.framework as a resource to your project. (Go [here](https://developer.apple.com/library/ios/#recipes/xcode_help-project_editor/Articles/AddingaLibrarytoaTarget.html) for instructions on how to do so.)
-## Upgrading Cordova 2.2.0 projects to 2.3.0 ##
+## Upgrading 2.2.0 projects to 2.3.0 ##
1. **Download and extract the Cordova 2.3.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.3.0)
2. **Quit Xcode** if it is running.
@@ -143,7 +143,7 @@ You can get this by accessing the **userAgent** property off the main view-contr
* For iOS, device.name (now deprecated for all platforms) used to return the name of the user’s device (e.g ‘Shazron’s iPhone 5′) — now it returns what device.platform used to return: ”iPhone”, “iPad” or “iPod Touch”.
* For all platforms, there is a new property called device.model — this returns the specific device model, e.g “iPad2,5″ (for other platforms, this returns what device.name used to return).
-## Upgrading Cordova 2.1.0 projects to 2.2.0 ##
+## Upgrading 2.1.0 projects to 2.2.0 ##
1. **Download and extract the Cordova 2.2.0 source** to a **permanent folder location** on your hard drive (say to ~/Documents/Cordova-2.2.0)
2. **Quit Xcode** if it is running.
@@ -163,7 +163,7 @@ You can get this by accessing the **userAgent** property off the main view-contr
__NOTE:__ In 2.2.0, the `bin/create` script copy in the CordovaLib sub-project into your project. To have the same kind of setup, just copy in the right CordovaLib into your project folder, and update the CordovaLib sub-project location (relative to the project) in the Xcode File Inspector.
-## Upgrading Cordova 2.0.0 projects to 2.1.0 ##
+## Upgrading 2.0.0 projects to 2.1.0 ##
With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Reference Counting (ARC)**. You don't need to upgrade to **ARC** to use CordovaLib, but if you want to upgrade your project to use **ARC**, please use the Xcode migration wizard from the menu: **Edit → Refactor → Convert to Objective-C ARC...**, **de-select libCordova.a**, then run the wizard to completion.
@@ -187,7 +187,7 @@ With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Referenc
`update_cordova_subproject path/to/your/project/xcodeproj`
-## Upgrading Cordova 1.9.0 projects to 2.0.0 ##
+## Upgrading 1.9.0 projects to 2.0.0 ##
1. **Install** Cordova 2.0.0
2. [**Create a new project**](guide_command-line_index.md.html#Command-Line%20Usage_ios) from the command-line tools. You need to use the assets from this new project.
@@ -246,7 +246,7 @@ With **Cordova 2.1.0**, CordovaLib has been upgraded to use **Automatic Referenc
__NOTE:__ If your project is **not working** as expected in the Simulator, please **take a note of any errors** in the **console log in Xcode** for clues.
-## Upgrading Cordova 1.8.x projects to 1.9.0 ##
+## Upgrading 1.8.x projects to 1.9.0 ##
1. **Install** Cordova 1.9.0
2. **Create a new project** - you will have to grab assets from this new project
@@ -256,7 +256,7 @@ __NOTE:__ If your project is **not working** as expected in the Simulator, pleas
__NOTE:__ 1.9.0 supports the new **BackupWebStorage** boolean `Cordova.plist` setting. It's enabled by default, so set it to
`false` to disable it, especially on iOS 6. See [Release Notes - Safari and UIKit Section](https://developer.apple.com/library/prerelease/ios/#releasenotes/General/RN-iOSSDK-6_0/_index.html)
-## Upgrading Cordova 1.7.0 projects to 1.8.x ##
+## Upgrading 1.7.0 projects to 1.8.x ##
1. **Install** Cordova 1.8.0
2. **Create a new project** - you will have to grab assets from this new project
@@ -269,14 +269,14 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
2. In your project, select the `Capture.bundle` item into your Project Navigator in Xcode, type the **Delete** key, then select **Remove Reference** from the resulting dialog.
3. Drag the new `Capture.bundle` from Step 1 above into your Project Navigator in Xcode, then select the **Create groups for any added folders** radio button
-## Upgrading Cordova 1.6.x projects to 1.7.0 ##
+## Upgrading 1.6.x projects to 1.7.0 ##
1. **Install** Cordova 1.7.0
2. **Create a new project** - you will have to grab assets from this new project
3. **Copy** the **www/cordova-1.7.0.js** file from the new project into your **www** folder, and delete your **www/cordova-1.6.0.js** file
4. **Update** the Cordova script reference in your `www/index.html` file (and any other files that contain the script reference) to point to the new **cordova-1.7.0.js** file
-## Upgrading Cordova 1.5.0 projects to 1.6.x ##
+## Upgrading 1.5.0 projects to 1.6.x ##
1. **Install** Cordova 1.6.1
2. **Make a backup** of `AppDelegate.m`, `AppDelegate.h`, `MainViewController.m`, `MainViewController.h`, and `Cordova.plist` in your project
@@ -299,7 +299,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
13. Enter **Compiler for C/C++/Objective-C** in the search field
14. Select the **Apple LLVM Compiler 3.1** value
-## Upgrading Cordova 1.4.x projects to 1.5.0 ##
+## Upgrading 1.4.x projects to 1.5.0 ##
1. **Install** Cordova 1.5.0
2. **Create a new project** and run it once - you will have to grab assets from this new project
@@ -337,7 +337,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
32. Enter **PG** for the Find string, and **CDV** for the Replace string - then press the **Replace All** button
33. Press **Command-B** to build, you will still have deprecations that you can get rid of in the future (see `CDVDeprecated.h` - replace classes in your code that use PG* to CDV*, for example)
-## Upgrading Cordova 1.4.0 projects to 1.4.1 ##
+## Upgrading 1.4.0 projects to 1.4.1 ##
1. **Install** Cordova 1.4.1
2. **Make a backup** of `MainViewController.m`
@@ -347,7 +347,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
6. **Integrate** any project-specific code that you have in your backed-up `MainViewController.m` into the new file
7. Updating the `phonegap-1.4.0.js` file is optional, nothing has changed in the JavaScript between 1.4.0 and 1.4.1
-## Upgrading Cordova 1.3.0 projects to 1.4.0 ##
+## Upgrading 1.3.0 projects to 1.4.0 ##
1. **Install** Cordova 1.4.0
2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
@@ -365,7 +365,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-## Upgrading Cordova 1.2.0 projects to 1.3.0 ##
+## Upgrading 1.2.0 projects to 1.3.0 ##
1. **Install** Cordova 1.3.0
2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
@@ -383,7 +383,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-## Upgrading Cordova 1.1.0 projects to 1.2.0 ##
+## Upgrading 1.1.0 projects to 1.2.0 ##
1. **Install** Cordova 1.2.0
2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
@@ -401,7 +401,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-## Upgrading Cordova 1.0.0 projects to 1.1.0 ##
+## Upgrading 1.0.0 projects to 1.1.0 ##
1. **Install** Cordova 1.1.0
2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
@@ -419,7 +419,7 @@ If you intend on using the **Capture API**, you will need the new **iPad retina-
8. **Add** a new entry under **Plugins** in your `PhoneGap.plist` file - key is `com.phonegap.battery` and the value is **PGBattery**
9. **Integrate** any project-specific code that you have in your **backed-up AppDelegate.h and AppDelegate.m** into the new AppDelegate files
-## Upgrading Cordova 0.9.6 projects to 1.0.0 ##
+## Upgrading 0.9.6 projects to 1.0.0 ##
1. **Install** Cordova 1.0.0
2. **Make a backup** of `AppDelegate.m` and `AppDelegate.h` in your project
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/upgrading/windows-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/windows-8/index.md b/docs/en/edge/guide/upgrading/windows-8/index.md
index 75611ed..f5c3bea 100644
--- a/docs/en/edge/guide/upgrading/windows-8/index.md
+++ b/docs/en/edge/guide/upgrading/windows-8/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Upgrading Cordova Windows 8
+Upgrading Windows 8
===============================
This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to applications targetting Windows 8 and the Windows Store.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/f488410b/docs/en/edge/guide/upgrading/windows-phone/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/upgrading/windows-phone/index.md b/docs/en/edge/guide/upgrading/windows-phone/index.md
index c475636..7d65b24 100644
--- a/docs/en/edge/guide/upgrading/windows-phone/index.md
+++ b/docs/en/edge/guide/upgrading/windows-phone/index.md
@@ -17,7 +17,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
under the License.
---
-Upgrading Cordova Windows Phone
+Upgrading Windows Phone
===============================
This document is for people who need to upgrade their Cordova versions from an older version to a current version of Cordova. This applies to both WP7 and WP8.
[20/20] docs commit: [CB-3827] remove comment that screws up Markdown
formatting
Posted by mw...@apache.org.
[CB-3827] remove comment that screws up Markdown formatting
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/2a1e9328
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/2a1e9328
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/2a1e9328
Branch: refs/heads/master
Commit: 2a1e9328343162edf0259a0078e5d1dd190c41fa
Parents: 1cfcb95
Author: Mike Sierra <le...@gmail.com>
Authored: Thu Jul 4 14:10:40 2013 -0400
Committer: Mike Sierra <le...@gmail.com>
Committed: Thu Jul 4 14:10:40 2013 -0400
----------------------------------------------------------------------
docs/en/edge/guide/platforms/index.md | 1 -
1 file changed, 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/2a1e9328/docs/en/edge/guide/platforms/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/index.md b/docs/en/edge/guide/platforms/index.md
index 77b010f..5c366b8 100644
--- a/docs/en/edge/guide/platforms/index.md
+++ b/docs/en/edge/guide/platforms/index.md
@@ -56,7 +56,6 @@ a lower-level alternative to the `cordova` command-line utility.
## BlackBerry 10
-<!-- if "BlackBerry 10 Plugins" are available, how about WebViews? -->
* BlackBerry 10 Platform Guide
* BlackBerry 10 Plugins
* Blackberry 10 Command-line Tools