cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From agri...@apache.org
Subject svn commit: r1673862 [4/15] - in /cordova/site: ./ public/docs/en/edge/
Date Wed, 15 Apr 2015 16:43:44 GMT
Modified: cordova/site/public/docs/en/edge/guide_hybrid_plugins_index.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_hybrid_plugins_index.md.html?rev=1673862&r1=1673861&r2=1673862&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_hybrid_plugins_index.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_hybrid_plugins_index.md.html Wed Apr 15 16:43:43 2015
@@ -1,4 +1,3 @@
-<!DOCTYPE html>
 <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
@@ -16,12 +15,14 @@
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
---><html lang="en">
+-->
+
+<!DOCTYPE html>
+<html lang="en">
     <head>
         <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
         <meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no, width=device-width">
-        <meta name="generator" content="joDoc">
-<meta name="robots" content="noindex">
+        <meta name="generator" content="joDoc"><meta name="robots" label="noindex">
 
         <title>Apache Cordova API Documentation</title>
 
@@ -40,7 +41,7 @@
 <option value="3.1.0">3.1.0</option>
 </optgroup>
 <optgroup label="English" value="en">
-<option selected value="edge">edge</option>
+<option selected="selected" value="edge">edge</option>
 <option value="4.0.0">4.0.0</option>
 <option value="3.6.0">3.6.0</option>
 <option value="3.5.0">3.5.0</option>
@@ -104,7 +105,9 @@
 <option value="3.1.0">3.1.0</option>
 <option value="2.0.0">2.0.0</option>
 </optgroup>
-<optgroup label="Polish" value="pl"><option value="edge">edge</option></optgroup>
+<optgroup label="Polish" value="pl">
+<option value="edge">edge</option>
+</optgroup>
 <optgroup label="Russian" value="ru">
 <option value="edge">edge</option>
 <option value="3.5.0">3.5.0</option>
@@ -121,18 +124,13 @@
 <option value="3.5.0">3.5.0</option>
 <option value="3.4.0">3.4.0</option>
 <option value="3.1.0">3.1.0</option>
-</optgroup></select>
+</optgroup>
+</select>
             </small>
         </div>
         <div id="subheader">
             <h1>Plugin Development Guide</h1>
-            <small><select><option value="Plugin%2520Development%2520Guide">Plugin Development Guide</option>
-<option value="Plugin%20Development%20Guide_building_a_plugin">      - Building a Plugin</option>
-<option value="Plugin%20Development%20Guide_validating_a_plugin">      - Validating a Plugin</option>
-<option value="Plugin%20Development%20Guide_the_javascript_interface">      - The JavaScript Interface</option>
-<option value="Plugin%20Development%20Guide_sample_javascript">      - Sample JavaScript</option>
-<option value="Plugin%20Development%20Guide_native_interfaces">      - Native Interfaces</option>
-<option value="Plugin%20Development%20Guide_publishing_plugins">      - Publishing Plugins</option></select></small>
+            <small><select><option value="Plugin%2520Development%2520Guide">Plugin Development Guide</option><option value="Plugin%20Development%20Guide_building_a_plugin">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Building a Plugin</option><option value="Plugin%20Development%20Guide_validating_a_plugin">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Validating a Plugin</option><option value="Plugin%20Development%20Guide_the_javascript_interface">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- The JavaScript Interface</option><option value="Plugin%20Development%20Guide_sample_javascript">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Sample JavaScript</option><option value="Plugin%20Development%20Guide_native_interfaces">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Native Interfaces</option><option value="Plugin%20Development%20Guide_publishing_plugins">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Publishing Plugins</option></select></small>
         </div>
 
         <div id="sidebar">
@@ -165,7 +163,6 @@
         <div id="scrollable">
             <div id="content">
                 <h1><a name="Plugin%20Development%20Guide">Plugin Development Guide</a></h1>
-
 <p>A <em>plugin</em> is a package of injected code that allows the Cordova webview within
 which the app renders to communicate with the native platform on
 which it runs.  Plugins provide access to device and platform
@@ -174,170 +171,135 @@ the main Cordova API features are implem
 others are available that enable features such as bar code scanners,
 NFC communication, or to tailor calendar interfaces. There is a
 <a class="external" href="http://plugins.cordova.io">registry</a> of available plugins.</p>
-
 <p>Plugins comprise a single JavaScript interface along with
 corresponding native code libraries for each supported platform.  In essence
 this hides the various native code implementations behind a common
 JavaScript interface.</p>
-
 <p>This section steps through a simple <em>echo</em> plugin that passes a string from
 JavaScript to the native platform and back, one that you can use as a
 model to build far more complex features.  This section discusses the
 basic plugin structure and the outward-facing JavaScript interface.
 For each corresponding native interface, see the list at the end of
 this section.</p>
-
 <p>In addition to these instructions, when preparing to write a plugin it
 is best to look over
 <a class="external" href="http://cordova.apache.org/#contribute">existing plugins</a>
 for guidance.</p>
-
-<h2><a name="Plugin%20Development%20Guide_building_a_plugin">Building a Plugin</a></h2>
-
-<p>Application developers use the CLI's <code>plugin add</code> command (discussed
+<h2 id="building-a-plugin"><a name="Plugin%20Development%20Guide_building_a_plugin">Building a Plugin</a></h2>
+<p>Application developers use the CLI&apos;s <code>plugin add</code> command (discussed
 in <a href="guide_cli_index.md.html#The%20Command-Line%20Interface">The Command-Line Interface</a>) to apply a plugin to a project. The
 argument to that command is the URL for a <em>git</em> repository containing
-the plugin code.  This example implements Cordova's Device API:</p>
-
+the plugin code.  This example implements Cordova&apos;s Device API:</p>
 <pre class="prettyprint"><code>    $ cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-device.git
-</code></pre>
-
-<p>The plugin repository must feature a top-level <code>plugin.xml</code> manifest
+</code></pre><p>The plugin repository must feature a top-level <code>plugin.xml</code> manifest
 file. There are many ways to configure this file, details for which
 are available in the <a href="plugin_ref_spec.md.html#Plugin%20Specification">Plugin Specification</a>. This abbreviated version of
 the <code>Device</code> plugin provides a simple example to use as a model:</p>
-
-<pre class="prettyprint"><code>    &lt;?xml version="1.0" encoding="UTF-8"?&gt;
-    &lt;plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
-            id="org.apache.cordova.device" version="0.2.3"&gt;
+<pre class="prettyprint"><code>    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+    &lt;plugin xmlns=&quot;http://apache.org/cordova/ns/plugins/1.0&quot;
+            id=&quot;org.apache.cordova.device&quot; version=&quot;0.2.3&quot;&gt;
         &lt;name&gt;Device&lt;/name&gt;
         &lt;description&gt;Cordova Device Plugin&lt;/description&gt;
         &lt;license&gt;Apache 2.0&lt;/license&gt;
         &lt;keywords&gt;cordova,device&lt;/keywords&gt;
-        &lt;js-module src="www/device.js" name="device"&gt;
-            &lt;clobbers target="device" /&gt;
+        &lt;js-module src=&quot;www/device.js&quot; name=&quot;device&quot;&gt;
+            &lt;clobbers target=&quot;device&quot; /&gt;
         &lt;/js-module&gt;
-        &lt;platform name="ios"&gt;
-            &lt;config-file target="config.xml" parent="/*"&gt;
-                &lt;feature name="Device"&gt;
-                    &lt;param name="ios-package" value="CDVDevice"/&gt;
+        &lt;platform name=&quot;ios&quot;&gt;
+            &lt;config-file target=&quot;config.xml&quot; parent=&quot;/*&quot;&gt;
+                &lt;feature name=&quot;Device&quot;&gt;
+                    &lt;param name=&quot;ios-package&quot; value=&quot;CDVDevice&quot;/&gt;
                 &lt;/feature&gt;
             &lt;/config-file&gt;
-            &lt;header-file src="src/ios/CDVDevice.h" /&gt;
-            &lt;source-file src="src/ios/CDVDevice.m" /&gt;
+            &lt;header-file src=&quot;src/ios/CDVDevice.h&quot; /&gt;
+            &lt;source-file src=&quot;src/ios/CDVDevice.m&quot; /&gt;
         &lt;/platform&gt;
     &lt;/plugin&gt;
-</code></pre>
-
-<p>The top-level <code>plugin</code> tag's <code>id</code> attribute uses the same
+</code></pre><p>The top-level <code>plugin</code> tag&apos;s <code>id</code> attribute uses the same
 reverse-domain format to identify the plugin package as the apps to
-they're added.  The <code>js-module</code> tag specifies the path to the common
+they&apos;re added.  The <code>js-module</code> tag specifies the path to the common
 JavaScript interface.  The <code>platform</code> tag specifies a corresponding
 set of native code, for the <code>ios</code> platform in this case.  The
 <code>config-file</code> tag encapsulates a <code>feature</code> tag that is injected into
 the platform-specific <code>config.xml</code> file to make the platform aware of
 the additional code library.  The <code>header-file</code> and <code>source-file</code> tags
-specify the path to the library's component files.</p>
-
-<h2><a name="Plugin%20Development%20Guide_validating_a_plugin">Validating a Plugin</a></h2>
-
+specify the path to the library&apos;s component files.</p>
+<h2 id="validating-a-plugin"><a name="Plugin%20Development%20Guide_validating_a_plugin">Validating a Plugin</a></h2>
 <p>You can use the <code>plugman</code> utility to check whether the plugin installs
 correctly for each platform.  Install <code>plugman</code> with the following
 <a class="external" href="http://nodejs.org/">node</a> command:</p>
-
 <pre class="prettyprint"><code>    $ npm install -g plugman
-</code></pre>
-
-<p>You need an valid app source directory, such as the top-level <code>www</code>
+</code></pre><p>You need an valid app source directory, such as the top-level <code>www</code>
 directory included in a default CLI-generated project as described in
-<a href="guide_cli_index.md.html#The%20Command-Line%20Interface">The Command-Line Interface</a>.  Make sure the app's <code>index.html</code> home
-page reference the name of the plugin's JavaScript interface, as if it
+<a href="guide_cli_index.md.html#The%20Command-Line%20Interface">The Command-Line Interface</a>.  Make sure the app&apos;s <code>index.html</code> home
+page reference the name of the plugin&apos;s JavaScript interface, as if it
 were in the same source directory:</p>
-
-<pre class="prettyprint"><code>    &lt;script src="myplugin.js"&gt;&lt;/script&gt;
-</code></pre>
-
-<p>Then run a command such as the following to test whether iOS
+<pre class="prettyprint"><code>    &lt;script src=&quot;myplugin.js&quot;&gt;&lt;/script&gt;
+</code></pre><p>Then run a command such as the following to test whether iOS
 dependencies load properly:</p>
-
 <pre class="prettyprint"><code>     $ plugman install --platform ios --project /path/to/my/project/www --plugin /path/to/my/plugin
-</code></pre>
-
-<p>For details on <code>plugman</code> options, see <a href="plugin_ref_plugman.md.html#Using%20Plugman%20to%20Manage%20Plugins">Using Plugman to Manage Plugins</a>.
+</code></pre><p>For details on <code>plugman</code> options, see <a href="plugin_ref_plugman.md.html#Using%20Plugman%20to%20Manage%20Plugins">Using Plugman to Manage Plugins</a>.
 For information on how to actually <em>debug</em> plugins, see each
-platform's native interface listed at the bottom of this page.</p>
-
-<h2><a name="Plugin%20Development%20Guide_the_javascript_interface">The JavaScript Interface</a></h2>
-
+platform&apos;s native interface listed at the bottom of this page.</p>
+<h2 id="the-javascript-interface"><a name="Plugin%20Development%20Guide_the_javascript_interface">The JavaScript Interface</a></h2>
 <p>The JavaScript provides the front-facing interface, making it perhaps
 the most important part of the plugin.  You can structure your
-plugin's JavaScript however you like, but you need to call
+plugin&apos;s JavaScript however you like, but you need to call
 <code>cordova.exec</code> to communicate with the native platform, using the
 following syntax:</p>
-
 <pre class="prettyprint"><code>    cordova.exec(function(winParam) {},
                  function(error) {},
-                 "service",
-                 "action",
-                 ["firstArgument", "secondArgument", 42, false]);
-</code></pre>
-
-<p>Here is how each parameter works:</p>
-
+                 &quot;service&quot;,
+                 &quot;action&quot;,
+                 [&quot;firstArgument&quot;, &quot;secondArgument&quot;, 42, false]);
+</code></pre><p>Here is how each parameter works:</p>
 <ul>
 <li><p><code>function(winParam) {}</code>: A success callback function. Assuming your
 <code>exec</code> call completes successfully, this function executes along
-with any parameters you pass to it.</p></li>
+with any parameters you pass to it.</p>
+</li>
 <li><p><code>function(error) {}</code>: An error callback function. If the operation
 does not complete successfully, this function executes with an
-optional error parameter.</p></li>
-<li><p><code>"service"</code>: The service name to call on the native side. This
+optional error parameter.</p>
+</li>
+<li><p><code>&quot;service&quot;</code>: The service name to call on the native side. This
 corresponds to a native class, for which more information is
-available in the native guides listed below.</p></li>
-<li><p><code>"action"</code>: The action name to call on the native side. This
+available in the native guides listed below.</p>
+</li>
+<li><p><code>&quot;action&quot;</code>: The action name to call on the native side. This
 generally corresponds to the native class method. See the native
-guides listed below.</p></li>
+guides listed below.</p>
+</li>
 <li><p><code>[/* arguments */]</code>: An array of arguments to pass into the native
-environment.</p></li>
+environment.</p>
+</li>
 </ul>
-
-<h2><a name="Plugin%20Development%20Guide_sample_javascript">Sample JavaScript</a></h2>
-
-<p>This example shows one way to implement the plugin's JavaScript
+<h2 id="sample-javascript"><a name="Plugin%20Development%20Guide_sample_javascript">Sample JavaScript</a></h2>
+<p>This example shows one way to implement the plugin&apos;s JavaScript
 interface:</p>
-
 <pre class="prettyprint"><code>    window.echo = function(str, callback) {
         cordova.exec(callback, function(err) {
-            callback('Nothing to echo.');
-        }, "Echo", "echo", [str]);
+            callback(&apos;Nothing to echo.&apos;);
+        }, &quot;Echo&quot;, &quot;echo&quot;, [str]);
     };
-</code></pre>
-
-<p>In this example, the plugin attaches itself to the <code>window</code> object as
+</code></pre><p>In this example, the plugin attaches itself to the <code>window</code> object as
 the <code>echo</code> function, which plugin users would call as follows:</p>
-
-<pre class="prettyprint"><code>    window.echo("echome", function(echoValue) {
-        alert(echoValue == "echome"); // should alert true.
+<pre class="prettyprint"><code>    window.echo(&quot;echome&quot;, function(echoValue) {
+        alert(echoValue == &quot;echome&quot;); // should alert true.
     });
-</code></pre>
-
-<p>Look at the last three arguments to the <code>cordova.exec</code> function. The
+</code></pre><p>Look at the last three arguments to the <code>cordova.exec</code> function. The
 first calls the <code>Echo</code> <em>service</em>, a class name. The second requests
 the <code>echo</code> <em>action</em>, a method within that class. The third is an array
 of arguments containing the echo string, which is the <code>window.echo</code>
-function's the first parameter.</p>
-
+function&apos;s the first parameter.</p>
 <p>The success callback passed into <code>exec</code> is simply a reference to the
 callback function <code>window.echo</code> takes. If the native platform fires
 the error callback, it simply calls the success callback and passes it
 a default string.</p>
-
-<h2><a name="Plugin%20Development%20Guide_native_interfaces">Native Interfaces</a></h2>
-
+<h2 id="native-interfaces"><a name="Plugin%20Development%20Guide_native_interfaces">Native Interfaces</a></h2>
 <p>Once you define JavaScript for your plugin, you need to complement it
 with at least one native implementation. Details for each platform are
 listed below, and each builds on the simple Echo Plugin example above:</p>
-
 <ul>
 <li><a href="guide_platforms_amazonfireos_plugin.md.html#Amazon%20Fire%20OS%20Plugins">Amazon Fire OS Plugins</a></li>
 <li><a href="guide_platforms_android_plugin.md.html#Android%20Plugins">Android Plugins</a></li>
@@ -346,28 +308,20 @@ listed below, and each builds on the sim
 <li><a href="guide_platforms_wp8_plugin.md.html#Windows%20Phone%208%20Plugins">Windows Phone 8 Plugins</a></li>
 <li><a href="guide_platforms_win8_plugin.md.html#Windows%20Plugins">Windows Plugins</a></li>
 </ul>
-
 <p>The Tizen platform does not support plugins.</p>
-
-<h2><a name="Plugin%20Development%20Guide_publishing_plugins">Publishing Plugins</a></h2>
-
+<h2 id="publishing-plugins"><a name="Plugin%20Development%20Guide_publishing_plugins">Publishing Plugins</a></h2>
 <p>Once you develop your plugin, you may want to publish and share it
 with the community. You can publish your plugin to the Cordova
 <a class="external" href="http://plugins.cordova.io">registry</a> (based on <a class="external" href="https://github.com/isaacs/npmjs.org"><code>npmjs</code></a>) or
 to any other <code>npmjs</code>-based registry. Other developers can install it
 automatically using either <code>plugman</code> or the Cordova CLI.  (For details
-on each development path, see <a href="plugin_ref_plugman.md.html#Using%20Plugman%20to%20Manage%20Plugins">Using Plugman to Manage Plugins</a> and <a href="#The%0ACommand-Line%20Interface">The
+on each development path, see <a href="plugin_ref_plugman.md.html#Using%20Plugman%20to%20Manage%20Plugins">Using Plugman to Manage Plugins</a> and <a href="guide_cli_index.md.html#The%0ACommand-Line%20Interface">The
 Command-Line Interface</a>.)</p>
-
 <p>To publish a plugin you need to use the <code>plugman</code> tool and go through
 the following steps:</p>
-
-<pre class="prettyprint"><code>$ plugman adduser # that is if you don't have an account yet
+<pre class="prettyprint"><code>$ plugman adduser # that is if you don&apos;t have an account yet
 $ plugman publish /path/to/your/plugin
-</code></pre>
-
-<p>That is it!</p>
-
+</code></pre><p>That is it!</p>
 <p>Running <code>plugman --help</code> lists other available registry-based
 commands.</p>
 

Modified: cordova/site/public/docs/en/edge/guide_hybrid_webviews_index.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_hybrid_webviews_index.md.html?rev=1673862&r1=1673861&r2=1673862&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_hybrid_webviews_index.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_hybrid_webviews_index.md.html Wed Apr 15 16:43:43 2015
@@ -1,4 +1,3 @@
-<!DOCTYPE html>
 <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
@@ -16,12 +15,14 @@
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
---><html lang="en">
+-->
+
+<!DOCTYPE html>
+<html lang="en">
     <head>
         <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
         <meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no, width=device-width">
-        <meta name="generator" content="joDoc">
-<meta name="robots" content="noindex">
+        <meta name="generator" content="joDoc"><meta name="robots" label="noindex">
 
         <title>Apache Cordova API Documentation</title>
 
@@ -40,7 +41,7 @@
 <option value="3.1.0">3.1.0</option>
 </optgroup>
 <optgroup label="English" value="en">
-<option selected value="edge">edge</option>
+<option selected="selected" value="edge">edge</option>
 <option value="4.0.0">4.0.0</option>
 <option value="3.6.0">3.6.0</option>
 <option value="3.5.0">3.5.0</option>
@@ -104,7 +105,9 @@
 <option value="3.1.0">3.1.0</option>
 <option value="2.0.0">2.0.0</option>
 </optgroup>
-<optgroup label="Polish" value="pl"><option value="edge">edge</option></optgroup>
+<optgroup label="Polish" value="pl">
+<option value="edge">edge</option>
+</optgroup>
 <optgroup label="Russian" value="ru">
 <option value="edge">edge</option>
 <option value="3.5.0">3.5.0</option>
@@ -121,7 +124,8 @@
 <option value="3.5.0">3.5.0</option>
 <option value="3.4.0">3.4.0</option>
 <option value="3.1.0">3.1.0</option>
-</optgroup></select>
+</optgroup>
+</select>
             </small>
         </div>
         <div id="subheader">
@@ -159,18 +163,15 @@
         <div id="scrollable">
             <div id="content">
                 <h1><a name="Embedding%20WebViews">Embedding WebViews</a></h1>
-
 <p>Cordova applications are ordinarily implemented as a browser-based
 <em>WebView</em> within the native mobile platform. This section shows how,
 for supporting platforms, to create your own WebView components that
 make full use of Cordova APIs. You can then deploy these Cordova
 application components along with native components in a hybrid
 application.</p>
-
 <p>To deploy a WebView, you need to be familiar with each native
 programming environment. The following provides instructions for
 supported platforms:</p>
-
 <ul>
 <li><a href="guide_platforms_amazonfireos_webview.md.html#Amazon%20Fire%20OS%20WebViews">Amazon Fire OS WebViews</a></li>
 <li><a href="guide_platforms_android_webview.md.html#Android%20WebViews">Android WebViews</a></li>

Modified: cordova/site/public/docs/en/edge/guide_next_index.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_next_index.md.html?rev=1673862&r1=1673861&r2=1673862&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_next_index.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_next_index.md.html Wed Apr 15 16:43:43 2015
@@ -1,4 +1,3 @@
-<!DOCTYPE html>
 <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
@@ -16,12 +15,14 @@
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
---><html lang="en">
+-->
+
+<!DOCTYPE html>
+<html lang="en">
     <head>
         <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
         <meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no, width=device-width">
-        <meta name="generator" content="joDoc">
-<meta name="robots" content="noindex">
+        <meta name="generator" content="joDoc"><meta name="robots" label="noindex">
 
         <title>Apache Cordova API Documentation</title>
 
@@ -40,7 +41,7 @@
 <option value="3.1.0">3.1.0</option>
 </optgroup>
 <optgroup label="English" value="en">
-<option selected value="edge">edge</option>
+<option selected="selected" value="edge">edge</option>
 <option value="4.0.0">4.0.0</option>
 <option value="3.6.0">3.6.0</option>
 <option value="3.5.0">3.5.0</option>
@@ -104,7 +105,9 @@
 <option value="3.1.0">3.1.0</option>
 <option value="2.0.0">2.0.0</option>
 </optgroup>
-<optgroup label="Polish" value="pl"><option value="edge">edge</option></optgroup>
+<optgroup label="Polish" value="pl">
+<option value="edge">edge</option>
+</optgroup>
 <optgroup label="Russian" value="ru">
 <option value="edge">edge</option>
 <option value="3.5.0">3.5.0</option>
@@ -121,37 +124,13 @@
 <option value="3.5.0">3.5.0</option>
 <option value="3.4.0">3.4.0</option>
 <option value="3.1.0">3.1.0</option>
-</optgroup></select>
+</optgroup>
+</select>
             </small>
         </div>
         <div id="subheader">
             <h1>Next Steps</h1>
-            <small><select><option value="Next%2520Steps">Next Steps</option>
-<option value="Best%2520Practices">Best Practices</option>
-<option value="Best%20Practices_1_spa_is_your_friend">      - 1) SPA Is Your Friend</option>
-<option value="Best%20Practices_2_performance_considerations">      - 2) Performance Considerations</option>
-<option value="Best%20Practices_3_recognize_and_handle_offline_status">      - 3) Recognize and Handle Offline Status</option>
-<option value="Handling%2520Upgrades">Handling Upgrades</option>
-<option value="Handling%20Upgrades_upgrading_cordova_projects">      - Upgrading Cordova Projects</option>
-<option value="Handling%20Upgrades_plugin_upgrades">      - Plugin Upgrades</option>
-<option value="Testing">Testing</option>
-<option value="Testing_testing_on_a_simulator_vs_on_a_real_device">      - 
-Testing on a simulator vs. on a real device</option>
-<option value="Debugging">Debugging</option>
-<option value="Debugging_ios_debugging">      - iOS Debugging
-</option>
-<option value="Debugging_chrome_remote_debugging">      - Chrome Remote Debugging
-</option>
-<option value="Debugging_ripple">      - Ripple</option>
-<option value="Debugging_weinre">      - Weinre</option>
-<option value="Debugging_other_options">      - Other Options</option>
-<option value="User%2520Interface">User Interface</option>
-<option value="User%20Interface_additional_ui_articles_and_resources">      - Additional UI Articles and Resources</option>
-<option value="Special%2520Considerations">Special Considerations</option>
-<option value="Special%20Considerations_platform_quirks">      - Platform Quirks</option>
-<option value="Special%20Considerations_loading_remote_content">      - Loading Remote Content</option>
-<option value="Keeping%2520Up">Keeping Up</option>
-<option value="Getting%2520Help">Getting Help</option></select></small>
+            <small><select><option value="Next%2520Steps">Next Steps</option><option value="Best%2520Practices">Best Practices</option><option value="Best%20Practices_1_spa_is_your_friend">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- 1) SPA Is Your Friend</option><option value="Best%20Practices_2_performance_considerations">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- 2) Performance Considerations</option><option value="Best%20Practices_3_recognize_and_handle_offline_status">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- 3) Recognize and Handle Offline Status</option><option value="Handling%2520Upgrades">Handling Upgrades</option><option value="Handling%20Upgrades_upgrading_cordova_projects">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Upgrading Cordova Projects</option><option value="Handling%20Upgrades_plugin_upgrades">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Plugin Upgrades</option><option value="Testing">Testing</option><option value="Testing_testing_on_a_simulator_vs_on_a_real_device">&#xA0;&#xA0;&#xA0;&#xA0;&
 #xA0;&#xA0;- Testing on a simulator vs. on a real device</option><option value="Debugging">Debugging</option><option value="Debugging_ios_debugging">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- iOS Debugging</option><option value="Debugging_chrome_remote_debugging">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Chrome Remote Debugging</option><option value="Debugging_ripple">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Ripple</option><option value="Debugging_weinre">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Weinre</option><option value="Debugging_other_options">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Other Options</option><option value="User%2520Interface">User Interface</option><option value="User%20Interface_additional_ui_articles_and_resources">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Additional UI Articles and Resources</option><option value="Special%2520Considerations">Special Considerations</option><option value="Special%20Considerations_platform_quirks">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Platform Quirks<
 /option><option value="Special%20Considerations_loading_remote_content">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Loading Remote Content</option><option value="Keeping%2520Up">Keeping Up</option><option value="Getting%2520Help">Getting Help</option></select></small>
         </div>
 
         <div id="sidebar">
@@ -184,11 +163,8 @@ Testing on a simulator vs. on a real dev
         <div id="scrollable">
             <div id="content">
                 <h1><a name="Next%20Steps">Next Steps</a></h1>
-
 <p>For developers who have an understanding of how to use the Cordova CLI and make use of plugins, there are a few things you may want to consider researching next to build better, more performant Cordova applications. The following document offers advice on various topics relating to best practices, testing, upgrades, and other topics, but is not meant to be prescriptive. Consider this your launching point for your growth as a Cordova developer. Also, if you see something that can be improved, please <a class="external" href="http://cordova.apache.org/#contribute">contribute</a>!</p>
-
 <p>This guide contains the following topics:</p>
-
 <ul>
 <li><a href="guide_next_index.md.html#Best%20Practices">Best Practices</a></li>
 <li><a href="guide_next_index.md.html#Handling%20Upgrades">Handling Upgrades</a></li>
@@ -197,22 +173,14 @@ Testing on a simulator vs. on a real dev
 <li><a href="guide_next_index.md.html#User%20Interface">User Interface</a></li>
 <li><a href="guide_next_index.md.html#Special%20Considerations">Special Considerations</a></li>
 <li><a href="guide_next_index.md.html#Keeping%20Up">Keeping Up</a></li>
-<li>
-<a href="guide_next_index.md.html#Getting%20Help">Getting Help</a> </li>
+<li><a href="guide_next_index.md.html#Getting%20Help">Getting Help</a> </li>
 </ul>
-
 <h1><a name="Best%20Practices">Best Practices</a></h1>
-
-<h2><a name="Best%20Practices_1_spa_is_your_friend">1) SPA Is Your Friend</a></h2>
-
+<h2 id="1-spa-is-your-friend"><a name="Best%20Practices_1_spa_is_your_friend">1) SPA Is Your Friend</a></h2>
 <p>First and foremost - your Cordova applications should adopt the SPA (Single Page Application) design. Loosely defined, a SPA is a client-side application that is run from one request of a web page. The user loads an initial set of resources (HTML, CSS, and JavaScript) and further updates (showing a new view, loading data) is done via AJAX. SPAs are commonly used for more complex client-side applications. GMail is a great example of this. After you load GMail, mail views, editing, and organization are all done by updating the DOM instead of actually leaving the current page to load a completely new one. </p>
-
 <p>Using a SPA can help you organize your application in a more efficient manner, but it also has specific benefits for Cordova applications. A Cordova application must wait for the <a href="cordova_events_events.md.html#deviceready">deviceready</a> event to fire before any plugins may be used. If you do not use a SPA, and your user clicks to go from one page to another, you will have to wait for <a href="cordova_events_events.md.html#deviceready">deviceready</a> to fire again before you make use of a plugin. This is easy to forget as your application gets larger. </p>
-
 <p>Even if you choose not to use Cordova, creating a mobile application without using a single page architecture will have serious performance implications. This is because navigating between pages will require scripts, assets, etc., to be reloaded. Even if these assets are cached, there will still be performance issues. </p>
-
 <p>Examples of SPA libraries you can use in your Cordova applications are:</p>
-
 <ul>
 <li><a class="external" href="http://angularjs.org">AngularJS</a></li>
 <li><a class="external" href="http://emberjs.com">EmberJS</a></li>
@@ -223,45 +191,27 @@ Testing on a simulator vs. on a real dev
 <li><a class="external" href="http://www.sencha.com/products/touch/">Sencha Touch</a></li>
 <li><a class="external" href="http://jquerymobile.com">jQuery Mobile</a></li>
 </ul>
-
 <p>And many, many, more.</p>
-
-<h2><a name="Best%20Practices_2_performance_considerations">2) Performance Considerations</a></h2>
-
+<h2 id="2-performance-considerations"><a name="Best%20Practices_2_performance_considerations">2) Performance Considerations</a></h2>
 <p>One of the biggest mistakes a new Cordova developer can make is to assume that the performance they get on a desktop machine is the same they will get on a mobile device. While our mobile devices have gotten more powerful every year, they still lack the power and performance of a desktop. Mobile devices typically have much less RAM and a GPU that is a far cry from their desktop (or even laptop) brethren. A full list of tips here would be too much, but here are a few things to keep in mind (with a list of longer resources at the end for further research).</p>
-
-<p><strong>Click versus Touch</strong> - The biggest and simplest mistake you can make is to use click events. While these "work" just fine on mobile, most devices impose a 300ms delay on them in order to distinguish between a touch and a touch "hold" event. Using <code>touchstart</code>, or <code>touchend</code>, will result in a dramatic improvement - 300ms doesn't sound like much, but it can result in jerky UI updates and behavior. You should also consider the fact that “touch” events are not supported on non-webkit browsers, see <a class="external" href="http://caniuse.com/#search=touch">CanIUse</a>. In order to deal with these limitations, you can checkout various libraries like HandJS and Fastouch.</p>
-
+<p><strong>Click versus Touch</strong> - The biggest and simplest mistake you can make is to use click events. While these &quot;work&quot; just fine on mobile, most devices impose a 300ms delay on them in order to distinguish between a touch and a touch &quot;hold&quot; event. Using <code>touchstart</code>, or <code>touchend</code>, will result in a dramatic improvement - 300ms doesn&apos;t sound like much, but it can result in jerky UI updates and behavior. You should also consider the fact that &#x201C;touch&#x201D; events are not supported on non-webkit browsers, see <a class="external" href="http://caniuse.com/#search=touch">CanIUse</a>. In order to deal with these limitations, you can checkout various libraries like HandJS and Fastouch.</p>
 <p><strong>CSS Transitions versus DOM Manipulation</strong> - Using hardware accelerated CSS transitions will be dramatically better than using JavaScript to create animations. See the list of resources at the end of this section for examples.</p>
-
-<p><strong>Networks Suck</strong> - Ok, networks don't always suck, but the latency of mobile networks, even good mobile networks, is far worse than you probably think. A desktop app that slurps down 500 rows of JSON data, every 30 seconds, will be both slower on a mobile device as well as a battery hog. Keep in mind that Cordova apps have multiple ways to persist data in the app (LocalStorage and the file system for example). Cache that data locally and be cognizant of the amount of data you are sending back and forth. This is an especially important consideration when your application is connected over a cellular network.</p>
-
+<p><strong>Networks Suck</strong> - Ok, networks don&apos;t always suck, but the latency of mobile networks, even good mobile networks, is far worse than you probably think. A desktop app that slurps down 500 rows of JSON data, every 30 seconds, will be both slower on a mobile device as well as a battery hog. Keep in mind that Cordova apps have multiple ways to persist data in the app (LocalStorage and the file system for example). Cache that data locally and be cognizant of the amount of data you are sending back and forth. This is an especially important consideration when your application is connected over a cellular network.</p>
 <p><strong>Additional Performance Articles and Resources</strong></p>
-
 <ul>
-<li><a class="external" href="http://sintaxi.com/you-half-assed-it">"You half assed it"</a></li>
-<li><a class="external" href="http://coenraets.org/blog/2013/10/top-10-performance-techniques-for-phonegap-and-hybrid-apps-slides-available/">"Top Ten Performance Tips for PhoneGap and Hybrid Apps"</a></li>
-<li>"Fast Apps and Sites with JavaScript": http://channel9.msdn.com/<a href="cordova_events_events.md.html#Events">Events</a>/Build/2013/4-313</li>
+<li><a class="external" href="http://sintaxi.com/you-half-assed-it">&quot;You half assed it&quot;</a></li>
+<li><a class="external" href="http://coenraets.org/blog/2013/10/top-10-performance-techniques-for-phonegap-and-hybrid-apps-slides-available/">&quot;Top Ten Performance Tips for PhoneGap and Hybrid Apps&quot;</a></li>
+<li>&quot;Fast Apps and Sites with JavaScript&quot;: <a class="external" href="http://channel9.msdn.com/&lt;a href=" cordova_events_events.md.html#events"="">Events</a>/Build/2013/4-313&quot;&gt;http://channel9.msdn.com/<a href="cordova_events_events.md.html#Events">Events</a>/Build/2013/4-313</li>
 </ul>
-
-<h2><a name="Best%20Practices_3_recognize_and_handle_offline_status">3) Recognize and Handle Offline Status</a></h2>
-
+<h2 id="3-recognize-and-handle-offline-status"><a name="Best%20Practices_3_recognize_and_handle_offline_status">3) Recognize and Handle Offline Status</a></h2>
 <p>See the previous tip about networks. Not only can you be on a slow network, it is entirely possible for your application to be completely offline. Your application should handle this in an intelligent manner. If your application does not, people will think your application is broken. Given how easy it is to handle (Cordova supports listening for both an offline and online event), there is absolutely no reason for your application to not respond well when run offline. Be sure to test (see the <a href="guide_next_index.md.html#Testing">Testing</a> section below) your application and be sure to test how your application handles when you start in one state and then switch to another.</p>
-
-<p>Note that the online and offline events, as well as the Network Connection API is not perfect. You may need to rely on using an XHR request to see if the device is truly offline or online. At the end of the day, be sure add some form of support for network issues - in fact, the Apple store (and probably other stores) will reject apps that don’t properly handle offline/online states. For more discussion on this topic, see 
-<a class="external" href="http://blogs.telerik.com/appbuilder/posts/13-04-23/is-this-thing-on-%28part-1%29">"Is This Thing On?"</a></p>
-
+<p>Note that the online and offline events, as well as the Network Connection API is not perfect. You may need to rely on using an XHR request to see if the device is truly offline or online. At the end of the day, be sure add some form of support for network issues - in fact, the Apple store (and probably other stores) will reject apps that don&#x2019;t properly handle offline/online states. For more discussion on this topic, see 
+<a class="external" href="http://blogs.telerik.com/appbuilder/posts/13-04-23/is-this-thing-on-%28part-1%29">&quot;Is This Thing On?&quot;</a></p>
 <h1><a name="Handling%20Upgrades">Handling Upgrades</a></h1>
-
-<h2><a name="Handling%20Upgrades_upgrading_cordova_projects">Upgrading Cordova Projects</a></h2>
-
+<h2 id="upgrading-cordova-projects"><a name="Handling%20Upgrades_upgrading_cordova_projects">Upgrading Cordova Projects</a></h2>
 <p>If your existing project was created using Cordova 3.x, you can upgrade the project by issuing the following:</p>
-
 <pre class="prettyprint"><code>cordova platform update platform-name ios, android, etc.
-</code></pre>
-
-<p>If your existing project was created under a version prior to Cordova 3.x, it would probably be best to create a new Cordova 3.x project, and then copy your existing project’s code and assets to the new project. Typical steps:</p>
-
+</code></pre><p>If your existing project was created under a version prior to Cordova 3.x, it would probably be best to create a new Cordova 3.x project, and then copy your existing project&#x2019;s code and assets to the new project. Typical steps:</p>
 <ul>
 <li>Create a new Cordova 3.x project (cordova create ...)</li>
 <li>Copy the www folder from your old project to the new project</li>
@@ -270,143 +220,85 @@ Testing on a simulator vs. on a real dev
 <li>Build your project</li>
 <li>Test, test, test!</li>
 </ul>
-
-<p>Regardless of the project's prior version, it is absolutely critical that you read up on what was changed in the updated version, as the update may break your code. The best place to find this information will be in the release notes published both in the repositories and on the Cordova blog. You will want to test your app thoroughly in order to verify that it is working correctly after you perform the update.</p>
-
+<p>Regardless of the project&apos;s prior version, it is absolutely critical that you read up on what was changed in the updated version, as the update may break your code. The best place to find this information will be in the release notes published both in the repositories and on the Cordova blog. You will want to test your app thoroughly in order to verify that it is working correctly after you perform the update.</p>
 <p>Note: some plugins may not be compatible with the new version of Cordova. If a plugin is not compatible, you may be able to find a replacement plugin that does what you need, or you may need to delay upgrading your project. Alternatively, alter the plugin so that it does work under the new version and contribute back to the community.</p>
-
-<h2><a name="Handling%20Upgrades_plugin_upgrades">Plugin Upgrades</a></h2>
-
+<h2 id="plugin-upgrades"><a name="Handling%20Upgrades_plugin_upgrades">Plugin Upgrades</a></h2>
 <p>As of Cordova 3.4, there is no mechanism for upgrading changed plugins using a single command. Instead, remove the plugin and add it back to your project, and the new version will be installed:</p>
-
 <pre class="prettyprint"><code>cordova plugin rm com.some.plugin
 cordova plugin add com.some.plugin
-</code></pre>
-
-<p>Be sure to check the updated plugin's documentation, as you may need to adjust your code to work with the new version. Also, double check that the new version of the plugin works with your project’s version of Cordova.</p>
-
+</code></pre><p>Be sure to check the updated plugin&apos;s documentation, as you may need to adjust your code to work with the new version. Also, double check that the new version of the plugin works with your project&#x2019;s version of Cordova.</p>
 <p>Always test your apps to ensure that installing the new plugin has not broken something that you did not anticipate.</p>
-
 <p>If your project has a lot of plugins that you need updated, it might save time to create a shell or batch script that removes and adds the plugins with one command. </p>
-
 <h1><a name="Testing">Testing</a></h1>
-
 <p><a href="guide_next_index.md.html#Testing">Testing</a> your applications is super important. The Cordova team uses Jasmine but any web friendly unit testing solution will do. </p>
-
-<h2><a name="Testing_testing_on_a_simulator_vs_on_a_real_device">
-Testing on a simulator vs. on a real device</a></h2>
-
-<p>It’s not uncommon to use desktop browsers and device simulators/emulators when developing a Cordova application. However, it is incredibly important that you test your app on as many physical devices as you possibly can:</p>
-
+<h2 id="testing-on-a-simulator-vs-on-a-real-device"><a name="Testing_testing_on_a_simulator_vs_on_a_real_device">Testing on a simulator vs. on a real device</a></h2>
+<p>It&#x2019;s not uncommon to use desktop browsers and device simulators/emulators when developing a Cordova application. However, it is incredibly important that you test your app on as many physical devices as you possibly can:</p>
 <ul>
 <li>Simulators are just that: simulators. For example, your app may work in the iOS simulator without a problem, but it may fail on a real device (especially in certain circumstances, such as a low memory state). Or, your app may actually fail on the simulator while it works just fine on a real device. </li>
 <li>Emulators are just that: emulators. They do not represent how well your app will run on a physical device. For example, some emulators may render your app with a garbled display, while a real device has no problem. (If you do encounter this problem, disable the host GPU in the emulator.)</li>
 <li>Simulators are generally faster than your physical device. Emulators, on the other hand, are generally slower. Do not judge the performance of your app by how it performs in a simulator or an emulator. Do judge the performance of your app by how it runs on a spectrum of real devices.</li>
-<li>It's impossible to get a good feel for how your app responds to your touch by using a simulator or an emulator. Instead, running the app on a real device can point out problems with the sizes of user interface elements, responsiveness, etc.</li>
+<li>It&apos;s impossible to get a good feel for how your app responds to your touch by using a simulator or an emulator. Instead, running the app on a real device can point out problems with the sizes of user interface elements, responsiveness, etc.</li>
 <li>Although it would be nice to be able to test only on one device per platform, it is best to test on many devices sporting many different OS versions. For example, what works on your particular Android smartphone may fail on another Android device. What works on an iOS 7 device may fail on an iOS 6 device.</li>
 </ul>
-
-<p>It is, of course, impossible to test on every possible device on the market. For this reason, it’s wise to recruit many testers who have different devices. Although they won’t catch every problem, chances are good that they will discover quirks and issues that you would never find alone.</p>
-
-<p>Tip: It is possible on Android Nexus devices to easily flash different versions of Android onto the device. This simple process will allow you to easily test your application on different levels of Android with a single device, without voiding your warranty or requiring you to “jailbreak” or “root” your device. The Google Android factory images and instructions are located at: https://developers.google.com/android/nexus/images#instructions</p>
-
+<p>It is, of course, impossible to test on every possible device on the market. For this reason, it&#x2019;s wise to recruit many testers who have different devices. Although they won&#x2019;t catch every problem, chances are good that they will discover quirks and issues that you would never find alone.</p>
+<p>Tip: It is possible on Android Nexus devices to easily flash different versions of Android onto the device. This simple process will allow you to easily test your application on different levels of Android with a single device, without voiding your warranty or requiring you to &#x201C;jailbreak&#x201D; or &#x201C;root&#x201D; your device. The Google Android factory images and instructions are located at: <a class="external" href="https://developers.google.com/android/nexus/images#instructions">https://developers.google.com/android/nexus/images#instructions</a></p>
 <h1><a name="Debugging">Debugging</a></h1>
-
-<p><a href="guide_next_index.md.html#Debugging">Debugging</a> Cordova requires some setup. Unlike a desktop application, you can't simply open dev tools on your mobile device and start debugging, luckily there are some great alternatives.</p>
-
-<h2><a name="Debugging_ios_debugging">iOS Debugging
-</a></h2>
-
-<h3>Xcode</h3>
-
-<p>With Xcode you can debug the iOS native side of your Cordova application. Make sure the Debug Area is showing (View -&gt; Debug Area). Once your app is running on the device (or simulator), you can view log output in the debug area. This is where any errors or warnings will print. You can also set breakpoints within the source files. This will allow you to step through the code one line at a time and view the state of the variables at that time. The state of the variables is shown in the debug area when a breakpoint is hit. Once your app is up and running on the device, you can bring up Safari's web inspector (as described below) to debug the webview and js side of your application. For more details and help, see the Xcode guide: <a class="external" href="https://developer.apple.com/library/mac/documentation/ToolsLanguages/Conceptual/Xcode_Overview/DebugYourApp/DebugYourApp.html#//apple_ref/doc/uid/TP40010215-CH18-SW1">Xcode </a><a href="guide_next_index.md.html#Debugging">Debugg
 ing</a> Guide</p>
-
-<h3>Safari Remote <a href="guide_next_index.md.html#Debugging">Debugging</a> with Web Inspector</h3>
-
-<p>With Safari's web inspector you can debug the webview and js code in your Cordova application. This works only on OSX and only with iOS 6 (and higher). It uses Safari to connect to your device (or the simulator) and will connect the browser's dev tools to the Cordova application. You get what you expect from dev tools - DOM inspection/manipulation, a JavaScript debugger, network inspection, the console, and more. Like Xcode, with Safari's web inspector you can set breakpoints in the JavaScript code and view the state of the variables at that time. You can view any errors, warnings or messages that are printed to the console. You can also run JavaScript commands directly from the console as your app is running. For more details on how to set it up and what you can do, see this excellent blog post: <a class="external" href="http://moduscreate.com/enable-remote-web-inspector-in-ios-6/">http://moduscreate.com/enable-remote-web-inspector-in-ios-6/</a> and this guide: <a class="externa
 l" href="https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html">Safari Web Inspector Guide</a></p>
-
-<h2><a name="Debugging_chrome_remote_debugging">Chrome Remote Debugging
-</a></h2>
-
+<p><a href="guide_next_index.md.html#Debugging">Debugging</a> Cordova requires some setup. Unlike a desktop application, you can&apos;t simply open dev tools on your mobile device and start debugging, luckily there are some great alternatives.</p>
+<h2 id="ios-debugging"><a name="Debugging_ios_debugging">iOS Debugging</a></h2>
+<h3 id="xcode">Xcode</h3>
+<p>With Xcode you can debug the iOS native side of your Cordova application. Make sure the Debug Area is showing (View -&gt; Debug Area). Once your app is running on the device (or simulator), you can view log output in the debug area. This is where any errors or warnings will print. You can also set breakpoints within the source files. This will allow you to step through the code one line at a time and view the state of the variables at that time. The state of the variables is shown in the debug area when a breakpoint is hit. Once your app is up and running on the device, you can bring up Safari&apos;s web inspector (as described below) to debug the webview and js side of your application. For more details and help, see the Xcode guide: <a class="external" href="https://developer.apple.com/library/mac/documentation/ToolsLanguages/Conceptual/Xcode_Overview/DebugYourApp/DebugYourApp.html#//apple_ref/doc/uid/TP40010215-CH18-SW1">Xcode <a href="guide_next_index.md.html#Debugging">Debug
 ging</a> Guide</a></p>
+<h3 id="safari-remote-debugging-with-web-inspector">Safari Remote <a href="guide_next_index.md.html#Debugging">Debugging</a> with Web Inspector</h3>
+<p>With Safari&apos;s web inspector you can debug the webview and js code in your Cordova application. This works only on OSX and only with iOS 6 (and higher). It uses Safari to connect to your device (or the simulator) and will connect the browser&apos;s dev tools to the Cordova application. You get what you expect from dev tools - DOM inspection/manipulation, a JavaScript debugger, network inspection, the console, and more. Like Xcode, with Safari&apos;s web inspector you can set breakpoints in the JavaScript code and view the state of the variables at that time. You can view any errors, warnings or messages that are printed to the console. You can also run JavaScript commands directly from the console as your app is running. For more details on how to set it up and what you can do, see this excellent blog post: <a class="external" href="http://moduscreate.com/enable-remote-web-inspector-in-ios-6/">http://moduscreate.com/enable-remote-web-inspector-in-ios-6/</a> and this guide: <a
  class="external" href="https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html">Safari Web Inspector Guide</a></p>
+<h2 id="chrome-remote-debugging"><a name="Debugging_chrome_remote_debugging">Chrome Remote Debugging</a></h2>
 <p>Virtually the same as the Safari version, this works with Android only but can be used from any desktop operating system. It requires a minimum of Android 4.4 (KitKat), minimum API level of 19, and Chrome 30+ (on the desktop). Once connected, you get the same Chrome Dev Tools experience for your mobile applications as you do with your desktop applications. Even better, the Chrome Dev Tools have a mirror option that shows your app running on the mobile device. This is more than just a view - you can scroll and click from dev tools and it updates on the mobile device. More details on Chrome Remote <a href="guide_next_index.md.html#Debugging">Debugging</a> may be found here: <a class="external" href="https://developers.google.com/chrome/mobile/docs/debugging">https://developers.google.com/chrome/mobile/docs/debugging</a></p>
-
 <p>It is possible to use Chrome Dev Tools to inspect iOS apps, through a WebKit proxy: <a class="external" href="https://github.com/google/ios-webkit-debug-proxy/">https://github.com/google/ios-webkit-debug-proxy/</a></p>
-
-<h2><a name="Debugging_ripple">Ripple</a></h2>
-
+<h2 id="ripple"><a name="Debugging_ripple">Ripple</a></h2>
 <p>Ripple is a desktop based emulator for Cordova projects. Essentially it lets you run a Cordova application in your desktop application and fake various Cordova features. For example, it lets you simulate the accelerometer to test shake events. It fakes the camera API by letting you select a picture from your hard drive. Ripple lets you focus more on your custom code rather than worrying about Cordova plugins. You can find out more about Ripple here: <a class="external" href="http://ripple.incubator.apache.org/">http://ripple.incubator.apache.org/</a></p>
-
-<h2><a name="Debugging_weinre">Weinre</a></h2>
-
-<p>Weinre creates a local server that can host a remote debug client for your Cordova applications. After you've installed and started it up, you copy a line of code into your Cordova application and then restart it. You can then open a dev tool panel on your desktop to work with the application. Weinre is not quite as fancy as Chrome and Safari Remote debugging but has the benefit of working with a much greater range of operating systems and platforms. More information may be found here: <a class="external" href="http://people.apache.org/~pmuellr/weinre/docs/latest/">http://people.apache.org/~pmuellr/weinre/docs/latest/</a></p>
-
-<h2><a name="Debugging_other_options">Other Options</a></h2>
-
+<h2 id="weinre"><a name="Debugging_weinre">Weinre</a></h2>
+<p>Weinre creates a local server that can host a remote debug client for your Cordova applications. After you&apos;ve installed and started it up, you copy a line of code into your Cordova application and then restart it. You can then open a dev tool panel on your desktop to work with the application. Weinre is not quite as fancy as Chrome and Safari Remote debugging but has the benefit of working with a much greater range of operating systems and platforms. More information may be found here: <a class="external" href="http://people.apache.org/~pmuellr/weinre/docs/latest/">http://people.apache.org/~pmuellr/weinre/docs/latest/</a></p>
+<h2 id="other-options"><a name="Debugging_other_options">Other Options</a></h2>
 <ul>
-<li>BlackBerry 10 supports debugging as well: <a class="external" href="https://developer.blackberry.com/html5/documentation/v2_0/debugging_using_web_inspector.html">Documentation</a>
-</li>
+<li>BlackBerry 10 supports debugging as well: <a class="external" href="https://developer.blackberry.com/html5/documentation/v2_0/debugging_using_web_inspector.html">Documentation</a></li>
 <li>You can debug using Firefox App Manager as well, see <a class="external" href="https://hacks.mozilla.org/2014/02/building-cordova-apps-for-firefox-os/">this blog post</a> and this 
 <a class="external" href="https://developer.mozilla.org/en-US/Apps/Tools_and_frameworks/Cordova_support_for_Firefox_OS#Testing_and_debugging">MDN article</a>.</li>
-<li>For more examples and explanation of the above debugging tips, see: <a class="external" href="http://developer.telerik.com/featured/a-concise-guide-to-remote-debugging-on-ios-android-and-windows-phone/">http://developer.telerik.com/featured/a-concise-guide-to-remote-debugging-on-ios-android-and-windows-phone/</a>
-</li>
+<li>For more examples and explanation of the above debugging tips, see: <a class="external" href="http://developer.telerik.com/featured/a-concise-guide-to-remote-debugging-on-ios-android-and-windows-phone/">http://developer.telerik.com/featured/a-concise-guide-to-remote-debugging-on-ios-android-and-windows-phone/</a></li>
 </ul>
-
 <h1><a name="User%20Interface">User Interface</a></h1>
-
 <p>Building a Cordova application that looks nice on mobile can be a challenge, especially for developers. Many people chose to use a UI framework to make this easier. Here is a short list of options you may want to consider.</p>
-
 <ul>
-<li>
-<a class="external" href="http://jquerymobile.com">jQuery Mobile</a> - jQuery Mobile automatically enhances your layout for mobile optimization. It also handles creating a SPA for you automatically.</li>
-<li>
-<a class="external" href="http://ionicframework.com/">ionic</a> - This powerful UI framework actually has its own CLI to handle project creation. </li>
-<li>
-<a class="external" href="http://goratchet.com/">Ratchet</a> - Brought to you by the people who created Bootstrap. </li>
-<li>
-<a class="external" href="http://www.telerik.com/kendo-ui">Kendo UI</a> - Open source UI and application framework from Telerik.</li>
+<li><a class="external" href="http://jquerymobile.com">jQuery Mobile</a> - jQuery Mobile automatically enhances your layout for mobile optimization. It also handles creating a SPA for you automatically.</li>
+<li><a class="external" href="http://ionicframework.com/">ionic</a> - This powerful UI framework actually has its own CLI to handle project creation. </li>
+<li><a class="external" href="http://goratchet.com/">Ratchet</a> - Brought to you by the people who created Bootstrap. </li>
+<li><a class="external" href="http://www.telerik.com/kendo-ui">Kendo UI</a> - Open source UI and application framework from Telerik.</li>
 <li><a class="external" href="http://topcoat.io">Topcoat</a></li>
 <li><a class="external" href="http://facebook.github.io/react/">ReactJS</a></li>
 </ul>
-
-<p>When building your user interface, it is important to think about all platforms that you are targeting and the differences between the user’s expectations. For example, an Android application that has an iOS-style UI will probably not go over well with users. This sometimes is even enforced by the various application stores. Because of this, it is important that you respect the conventions of each platform and therefore are familiar with the various Human Interface Guidelines: 
-* <a class="external" href="https://developer.apple.com/library/ios/documentation/userexperience/conceptual/MobileHIG/index.html">iOS</a>
-* <a class="external" href="https://developer.android.com/designWP8">Android</a>
-* <a class="external" href="http://dev.windowsphone.com/en-us/design/library">Windows Phone</a></p>
-
-<h2><a name="User%20Interface_additional_ui_articles_and_resources">Additional UI Articles and Resources</a></h2>
-
-<p>Although browser engines become more and more standards complaint, we still live in a prefixed world (-webkit and -ms.) The following article is valuable when developing UI’s in for cross browser apps: <a class="external" href="http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx">http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx</a></p>
-
+<p>When building your user interface, it is important to think about all platforms that you are targeting and the differences between the user&#x2019;s expectations. For example, an Android application that has an iOS-style UI will probably not go over well with users. This sometimes is even enforced by the various application stores. Because of this, it is important that you respect the conventions of each platform and therefore are familiar with the various Human Interface Guidelines: </p>
+<ul>
+<li><a class="external" href="https://developer.apple.com/library/ios/documentation/userexperience/conceptual/MobileHIG/index.html">iOS</a></li>
+<li><a class="external" href="https://developer.android.com/designWP8">Android</a></li>
+<li><a class="external" href="http://dev.windowsphone.com/en-us/design/library">Windows Phone</a></li>
+</ul>
+<h2 id="additional-ui-articles-and-resources"><a name="User%20Interface_additional_ui_articles_and_resources">Additional UI Articles and Resources</a></h2>
+<p>Although browser engines become more and more standards complaint, we still live in a prefixed world (-webkit and -ms.) The following article is valuable when developing UI&#x2019;s in for cross browser apps: <a class="external" href="http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx">http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx</a></p>
 <h1><a name="Special%20Considerations">Special Considerations</a></h1>
-
-<p>Although Cordova makes cross-platform development easier, it's just not possible to provide 100% isolation from the underlying native platform. So do be aware of restrictions.</p>
-
-<h2><a name="Special%20Considerations_platform_quirks">Platform Quirks</a></h2>
-
-<p>While reading the documentation, look for sections which outline different behaviors or requirements on multiple platforms. If present, these would be in a section titled "Android Quirks", "iOS Quirks", etc. Read through these quirks and be aware of them as you work with Cordova.</p>
-
-<h2><a name="Special%20Considerations_loading_remote_content">Loading Remote Content</a></h2>
-
+<p>Although Cordova makes cross-platform development easier, it&apos;s just not possible to provide 100% isolation from the underlying native platform. So do be aware of restrictions.</p>
+<h2 id="platform-quirks"><a name="Special%20Considerations_platform_quirks">Platform Quirks</a></h2>
+<p>While reading the documentation, look for sections which outline different behaviors or requirements on multiple platforms. If present, these would be in a section titled &quot;Android Quirks&quot;, &quot;iOS Quirks&quot;, etc. Read through these quirks and be aware of them as you work with Cordova.</p>
+<h2 id="loading-remote-content"><a name="Special%20Considerations_loading_remote_content">Loading Remote Content</a></h2>
 <p>Invoking Cordova JavaScript functions from a remotely-loaded HTML page (an HTML page not stored locally on the device) is an unsupported configuration. This is because Cordova was not designed for this, and the Apache Cordova community does no testing of this configuration. While it can work in some circumstances, it is not recommended nor supported. There are challenges with the same origin policy, keeping the JavaScript and native portions of Cordova synchronized at the same version (since they are coupled via private APIs which may change), the trustworthiness of remote content calling native local functions, and potential app store rejection.</p>
-
-<p>The display of remotely-loaded HTML content in a webview should be done using Cordova's InAppBrowser. The InAppBrowser is designed so that JavaScript running there does not have access to the Cordova JavaScript APIs for the reasons listed above. Please refer to the <a href="guide_appdev_security_index.md.html#Security%20Guide">Security Guide</a>.</p>
-
+<p>The display of remotely-loaded HTML content in a webview should be done using Cordova&apos;s InAppBrowser. The InAppBrowser is designed so that JavaScript running there does not have access to the Cordova JavaScript APIs for the reasons listed above. Please refer to the <a href="guide_appdev_security_index.md.html#Security%20Guide">Security Guide</a>.</p>
 <h1><a name="Keeping%20Up">Keeping Up</a></h1>
-
 <p>Here are a few ways to keep up to date with Cordova.</p>
-
 <ul>
 <li>Subscribe to the <a class="external" href="http://cordova.apache.org/#news">Cordova blog</a>.</li>
 <li>Subscribe to the <a class="external" href="http://cordova.apache.org/#mailing-list">developer list</a>. Note - this is not a support group! Rather this is a place where development of Cordova is discussed.</li>
 </ul>
-
 <h1><a name="Getting%20Help">Getting Help</a></h1>
-
 <p>The following links are the best places to get help for Cordova:</p>
-
 <ul>
 <li>StackOverflow: <a class="external" href="http://stackoverflow.com/questions/tagged/cordova">http://stackoverflow.com/questions/tagged/cordova</a>
-By using the Cordova tag, you can view and browse all Cordova questions. Note that StackOverflow automatically converts the "Phonegap" tag to "Cordova", so this way you will be able to access historical questions as well</li>
+By using the Cordova tag, you can view and browse all Cordova questions. Note that StackOverflow automatically converts the &quot;Phonegap&quot; tag to &quot;Cordova&quot;, so this way you will be able to access historical questions as well</li>
 <li>PhoneGap Google Group: <a class="external" href="https://groups.google.com/forum/#!forum/phonegap">https://groups.google.com/forum/#!forum/phonegap</a>
 This Google Group was the old support forum for when Cordova was still called PhoneGap. While there are still a lot of Cordova users that frequent this group, the Cordova community has expressed an interest in focusing less on this group and instead using StackOverflow for support</li>
 <li>Meetup: <a class="external" href="http://phonegap.meetup.com">http://phonegap.meetup.com</a> - 

Modified: cordova/site/public/docs/en/edge/guide_overview_index.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_overview_index.md.html?rev=1673862&r1=1673861&r2=1673862&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_overview_index.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_overview_index.md.html Wed Apr 15 16:43:43 2015
@@ -1,4 +1,3 @@
-<!DOCTYPE html>
 <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
@@ -16,12 +15,14 @@
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
---><html lang="en">
+-->
+
+<!DOCTYPE html>
+<html lang="en">
     <head>
         <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
         <meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no, width=device-width">
-        <meta name="generator" content="joDoc">
-<meta name="robots" content="noindex">
+        <meta name="generator" content="joDoc"><meta name="robots" label="noindex">
 
         <title>Apache Cordova API Documentation</title>
 
@@ -40,7 +41,7 @@
 <option value="3.1.0">3.1.0</option>
 </optgroup>
 <optgroup label="English" value="en">
-<option selected value="edge">edge</option>
+<option selected="selected" value="edge">edge</option>
 <option value="4.0.0">4.0.0</option>
 <option value="3.6.0">3.6.0</option>
 <option value="3.5.0">3.5.0</option>
@@ -104,7 +105,9 @@
 <option value="3.1.0">3.1.0</option>
 <option value="2.0.0">2.0.0</option>
 </optgroup>
-<optgroup label="Polish" value="pl"><option value="edge">edge</option></optgroup>
+<optgroup label="Polish" value="pl">
+<option value="edge">edge</option>
+</optgroup>
 <optgroup label="Russian" value="ru">
 <option value="edge">edge</option>
 <option value="3.5.0">3.5.0</option>
@@ -121,15 +124,13 @@
 <option value="3.5.0">3.5.0</option>
 <option value="3.4.0">3.4.0</option>
 <option value="3.1.0">3.1.0</option>
-</optgroup></select>
+</optgroup>
+</select>
             </small>
         </div>
         <div id="subheader">
             <h1>Overview</h1>
-            <small><select><option value="Overview">Overview</option>
-<option value="Overview_basic_components">      - Basic Components</option>
-<option value="Overview_development_paths">      - Development Paths</option>
-<option value="Overview_installing_cordova">      - Installing Cordova</option></select></small>
+            <small><select><option value="Overview">Overview</option><option value="Overview_basic_components">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Basic Components</option><option value="Overview_development_paths">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Development Paths</option><option value="Overview_installing_cordova">&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;- Installing Cordova</option></select></small>
         </div>
 
         <div id="sidebar">
@@ -162,50 +163,44 @@
         <div id="scrollable">
             <div id="content">
                 <h1><a name="Overview">Overview</a></h1>
-
 <p>Apache Cordova is an open-source mobile development framework. It allows you
 to use standard web technologies such as HTML5, CSS3, and JavaScript
-for cross-platform development, avoiding each mobile platforms' native
+for cross-platform development, avoiding each mobile platforms&apos; native
 development language.  Applications execute within wrappers targeted
 to each platform, and rely on standards-compliant API bindings to
-access each device's sensors, data, and network status. </p>
-
+access each device&apos;s sensors, data, and network status. </p>
 <p>Apache Cordova graduated in October 2012 as a top level project within the Apache Software Foundation (ASF). Through the ASF, future Cordova development will ensure open stewardship of the project. It will always remain free and open source under the Apache License, Version 2.0.  Visit <a class="external" href="http://cordova.apache.org">cordova.apache.org</a> for more information.</p>
-
 <p>Use Apache Cordova if you are:</p>
-
 <ul>
 <li><p>a mobile developer and want to extend an application across more
 than one platform, without having to re-implement it with each
-platform's language and tool set.</p></li>
-<li><p>a web developer and want to deploy a web app that's packaged for
-distribution in various app store portals.</p></li>
+platform&apos;s language and tool set.</p>
+</li>
+<li><p>a web developer and want to deploy a web app that&apos;s packaged for
+distribution in various app store portals.</p>
+</li>
 <li><p>a mobile developer interested in mixing native application
 components with a <em>WebView</em> (special browser window) that can access
 device-level APIs, or if you want to develop a plugin interface
-between native and WebView components.</p></li>
+between native and WebView components.</p>
+</li>
 </ul>
-
-<h2><a name="Overview_basic_components">Basic Components</a></h2>
-
+<h2 id="basic-components"><a name="Overview_basic_components">Basic Components</a></h2>
 <p>Apache Cordova applications rely on a common <code>config.xml</code> file that provides
 information about the app and specifies parameters affecting how it
 works, such as whether it responds to orientation shifts. This file
-adheres to the W3C's
+adheres to the W3C&apos;s
 <a class="external" href="http://www.w3.org/TR/widgets/">Packaged Web App</a>,
 or <em>widget</em>, specification.</p>
-
 <p>The application itself is implemented as a web page, by default a local
 file named <em>index.html</em>, that references whatever CSS, JavaScript,
 images, media files, or other resources are necessary for it to run.
 The app executes as a <em>WebView</em> within the native application wrapper,
 which you distribute to app stores.</p>
-
 <p>The Cordova-enabled WebView may provide the application with its
 entire user interface. On some platforms, it can also be a component
 within a larger, hybrid application that mixes the WebView with native
 application components. (See <a href="guide_hybrid_webviews_index.md.html#Embedding%20WebViews">Embedding WebViews</a> for details.)</p>
-
 <p>A <em>plugin</em> interface is available for Cordova and native components to
 communicate with each other. This enables you to invoke native code
 from JavaScript. Ideally, the JavaScript APIs to that native code are
@@ -217,22 +212,17 @@ platforms. You can find these third-part
 application. You can also develop your own plugins, as described in the
 <a href="guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide">Plugin Development Guide</a>. Plugins may be necessary, for example, to
 communicate between Cordova and custom native components.</p>
-
 <p><strong>NOTE</strong>: As of version 3.0, when you create a Cordova project it does not have
 any plugins present. This is the new default behavior. Any plugins you
 desire, even the core plugins, must be explicitly added.</p>
-
-<p>Cordova does not provide any UI widgets or MV* frameworks. Cordova provides
+<p>Cordova does not provide any UI widgets or MV<em> frameworks. Cordova provides
 only the runtime in which those can execute. If you wish to use UI widgets
-and/or an MV* framework, you will need to select those and include them in
+and/or an MV</em> framework, you will need to select those and include them in
 your application yourself as third-party material.</p>
-
-<h2><a name="Overview_development_paths">Development Paths</a></h2>
-
+<h2 id="development-paths"><a name="Overview_development_paths">Development Paths</a></h2>
 <p>As of version 3.0, you can use two basic workflows to create a mobile
 app. While you can often use either workflow to accomplish the same
 task, they each offer advantages:</p>
-
 <ul>
 <li><p><strong>Cross-platform (CLI) workflow</strong>: Use this workflow if you want your app
 to run on as many different mobile operating systems as possible,
@@ -245,9 +235,10 @@ scripts. The CLI copies a common set of
 subdirectories for each mobile platform, makes any necessary
 configuration changes for each, runs build scripts to generate
 application binaries. The CLI also provides a common interface to
-apply plugins to your app. For more details on the CLI, see <a href="#The%0ACommand-Line%20Interface">The
+apply plugins to your app. For more details on the CLI, see <a href="guide_cli_index.md.html#The%0ACommand-Line%20Interface">The
 Command-Line Interface</a>. Unless you have a need for the platform-centered
-workflow, the cross-platform workflow is recommended.</p></li>
+workflow, the cross-platform workflow is recommended.</p>
+</li>
 <li><p><strong>Platform-centered workflow</strong>: Use this workflow if you want to
 focus on building an app for a single platform and need to be able
 to modify it at a lower level. You need to use this approach, for
@@ -263,9 +254,9 @@ higher-level tool means separate build c
 modifications for each platform. Still, this workflow allows you
 greater access to development options provided by each SDK, and is
 essential for complex hybrid apps. See the various <a href="guide_platforms_index.md.html#Platform%20Guides">Platform Guides</a>
-for details on each platform's available shell utilities.</p></li>
+for details on each platform&apos;s available shell utilities.</p>
+</li>
 </ul>
-
 <p>When first starting out, it may be easiest to use the cross-platform
 workflow to create an app, as described in The Command-line Interface.
 You then have the option to switch to a platform-centered workflow if
@@ -273,28 +264,25 @@ you need the greater control the SDK pro
 utilities are available at
 <a class="external" href="http://cordova.apache.org">cordova.apache.org</a> in a separate
 distribution than the CLI. For projects initially generated by the
-CLI, these shell tools are also available in the project's various
+CLI, these shell tools are also available in the project&apos;s various
 <code>platforms/*/cordova</code> directories.</p>
-
 <p><strong>NOTE</strong>: Once you switch from the CLI-based workflow to one centered
-around the platform-specific SDKs and shell tools, you can't go back.
+around the platform-specific SDKs and shell tools, you can&apos;t go back.
 The CLI maintains a common set of cross-platform source code, which on
 each build it uses to write over platform-specific source code.  To
 preserve any modifications you make to the platform-specific assets,
 you need to switch to the platform-centered shell tools, which ignore
 the cross-platform source code, and instead relies on the
 platform-specific source code.</p>
-
-<h2><a name="Overview_installing_cordova">Installing Cordova</a></h2>
-
+<h2 id="installing-cordova"><a name="Overview_installing_cordova">Installing Cordova</a></h2>
 <p>The installation of Cordova will differ depending on the workflow above
 you choose:</p>
-
 <ul>
-<li><p>Cross-platform workflow: see <a href="guide_cli_index.md.html#The%20Command-Line%20Interface">The Command-Line Interface</a>.</p></li>
-<li><p>Platform-centered workflow: see the <a href="guide_platforms_index.md.html#Platform%20Guides">Platform Guides</a>.</p></li>
+<li><p>Cross-platform workflow: see <a href="guide_cli_index.md.html#The%20Command-Line%20Interface">The Command-Line Interface</a>.</p>
+</li>
+<li><p>Platform-centered workflow: see the <a href="guide_platforms_index.md.html#Platform%20Guides">Platform Guides</a>.</p>
+</li>
 </ul>
-
 <p>After installing Cordova, it is recommended that you review the <a href="guide_platforms_index.md.html#Platform%20Guides">Platform Guides</a>
 for the mobile platforms that you will be developing for. It is also
 recommended that you also review the <a href="guide_appdev_privacy_index.md.html#Privacy%20Guide">Privacy Guide</a>, <a href="guide_appdev_security_index.md.html#Security%20Guide">Security Guide</a>, and

Modified: cordova/site/public/docs/en/edge/guide_platforms_amazonfireos_config.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_amazonfireos_config.md.html?rev=1673862&r1=1673861&r2=1673862&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_platforms_amazonfireos_config.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_platforms_amazonfireos_config.md.html Wed Apr 15 16:43:43 2015
@@ -1,4 +1,3 @@
-<!DOCTYPE html>
 <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
@@ -16,12 +15,14 @@
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
---><html lang="en">
+-->
+
+<!DOCTYPE html>
+<html lang="en">
     <head>
         <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
         <meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no, width=device-width">
-        <meta name="generator" content="joDoc">
-<meta name="robots" content="noindex">
+        <meta name="generator" content="joDoc"><meta name="robots" label="noindex">
 
         <title>Apache Cordova API Documentation</title>
 
@@ -40,7 +41,7 @@
 <option value="3.1.0">3.1.0</option>
 </optgroup>
 <optgroup label="English" value="en">
-<option selected value="edge">edge</option>
+<option selected="selected" value="edge">edge</option>
 <option value="4.0.0">4.0.0</option>
 <option value="3.6.0">3.6.0</option>
 <option value="3.5.0">3.5.0</option>
@@ -104,7 +105,9 @@
 <option value="3.1.0">3.1.0</option>
 <option value="2.0.0">2.0.0</option>
 </optgroup>
-<optgroup label="Polish" value="pl"><option value="edge">edge</option></optgroup>
+<optgroup label="Polish" value="pl">
+<option value="edge">edge</option>
+</optgroup>
 <optgroup label="Russian" value="ru">
 <option value="edge">edge</option>
 <option value="3.5.0">3.5.0</option>
@@ -121,7 +124,8 @@
 <option value="3.5.0">3.5.0</option>
 <option value="3.4.0">3.4.0</option>
 <option value="3.1.0">3.1.0</option>
-</optgroup></select>
+</optgroup>
+</select>
             </small>
         </div>
         <div id="subheader">
@@ -159,86 +163,57 @@
         <div id="scrollable">
             <div id="content">
                 <h1><a name="Amazon%20Fire%20OS%20Configuration">Amazon Fire OS Configuration</a></h1>
-
-<p>The <code>config.xml</code> file controls an app's basic settings that apply
+<p>The <code>config.xml</code> file controls an app&apos;s basic settings that apply
 across each application and CordovaWebView instance. This section
-details preferences that only apply to  Amazon Fire OS builds. See <a href="#The%0Aconfig.xml%20File">The
-config.xml File</a> for information on global configuration options.</p>
-
+details preferences that only apply to  Amazon Fire OS builds. See <a href="config_ref_index.md.html#The%20config.xml%20File"><a href="config_ref_index.md.html#The%20config.xml%0AFile">The config.xml
+File</a></a> for information on global configuration options.</p>
 <ul>
-<li>
-<p><code>KeepRunning</code> (boolean, defaults to <code>true</code>): Determines whether the
+<li><p><code>KeepRunning</code> (boolean, defaults to <code>true</code>): Determines whether the
 application stays running in the background even after a <code><a href="cordova_events_events.md.html#pause">pause</a></code>
 event fires. Setting this to <code>false</code> does not kill the app after a
 <code><a href="cordova_events_events.md.html#pause">pause</a></code> event, but simply halts execution of code within the cordova
 webview while the app is in the background.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="KeepRunning" value="false"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>ErrorUrl</code> (URL, defaults to <code>null</code>):
+<pre class="prettyprint"><code>  &lt;preference name=&quot;KeepRunning&quot; value=&quot;false&quot;/&gt;
+</code></pre></li>
+<li><p><code>ErrorUrl</code> (URL, defaults to <code>null</code>):
 If set, will display the referenced page upon an error in the application
-instead of a dialog with the title "Application Error".</p>
-
-<pre class="prettyprint"><code>&lt;preference name="ErrorUrl" value="error.html"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>LoadingDialog</code> (string, defaults to <code>null</code>): If set, displays a dialog with
+instead of a dialog with the title &quot;Application Error&quot;.</p>
+<pre class="prettyprint"><code>  &lt;preference name=&quot;ErrorUrl&quot; value=&quot;error.html&quot;/&gt;
+</code></pre></li>
+<li><p><code>LoadingDialog</code> (string, defaults to <code>null</code>): If set, displays a dialog with
 the specified title and message, and a spinner, when loading the first
 page of an application. The title and message are separated by a comma
 in this value string, and that comma is removed before the dialog is
 displayed.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="LoadingDialog" value="Please wait, the app is loading"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>LoadingPageDialog</code> (string, defaults to <code>null</code>): The same as <code>LoadingDialog</code>,
+<pre class="prettyprint"><code>  &lt;preference name=&quot;LoadingDialog&quot; value=&quot;Please wait, the app is loading&quot;/&gt;
+</code></pre></li>
+<li><p><code>LoadingPageDialog</code> (string, defaults to <code>null</code>): The same as <code>LoadingDialog</code>,
 but for loading every page after the first page in the application.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="LoadingPageDialog" value="Please wait, the data is loading"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>LoadUrlTimeoutValue</code> (number, default is <code>20000</code>): When loading a
+<pre class="prettyprint"><code>  &lt;preference name=&quot;LoadingPageDialog&quot; value=&quot;Please wait, the data is loading&quot;/&gt;
+</code></pre></li>
+<li><p><code>LoadUrlTimeoutValue</code> (number, default is <code>20000</code>): When loading a
 page, the amount of time to wait before throwing a timeout error.
 This example specifies 10 seconds rather than 20:</p>
-
-<pre class="prettyprint"><code>&lt;preference name="LoadUrlTimeoutValue" value="10000"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>SplashScreen</code>: The name of the file minus its extension in the
+<pre class="prettyprint"><code>  &lt;preference name=&quot;LoadUrlTimeoutValue&quot; value=&quot;10000&quot;/&gt;
+</code></pre></li>
+<li><p><code>SplashScreen</code>: The name of the file minus its extension in the
 <code>res/drawable</code> directory.  Various assets must share this common
 name in various subdirectories.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="SplashScreen" value="splash"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>SplashScreenDelay</code> (number, defaults to <code>5000</code>): The amount of
+<pre class="prettyprint"><code>  &lt;preference name=&quot;SplashScreen&quot; value=&quot;splash&quot;/&gt;
+</code></pre></li>
+<li><p><code>SplashScreenDelay</code> (number, defaults to <code>5000</code>): The amount of
 time the splash screen image displays.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="SplashScreenDelay" value="10000"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>ShowTitle</code> (boolean, defaults to <code>false</code>): Show the title at the top
+<pre class="prettyprint"><code>  &lt;preference name=&quot;SplashScreenDelay&quot; value=&quot;10000&quot;/&gt;
+</code></pre></li>
+<li><p><code>ShowTitle</code> (boolean, defaults to <code>false</code>): Show the title at the top
 of the screen.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="ShowTitle" value="true"/&gt;
-</code></pre>
-</li>
-<li>
-<p><code>LogLevel</code> (string, defaults to <code>ERROR</code>): Sets the minimum log level
+<pre class="prettyprint"><code>  &lt;preference name=&quot;ShowTitle&quot; value=&quot;true&quot;/&gt;
+</code></pre></li>
+<li><p><code>LogLevel</code> (string, defaults to <code>ERROR</code>): Sets the minimum log level
 through which log messages from your application will be filtered. Valid
 values are <code>ERROR</code>, <code>WARN</code>, <code>INFO</code>, <code>DEBUG</code>, and <code>VERBOSE</code>.</p>
-
-<pre class="prettyprint"><code>&lt;preference name="LogLevel" value="VERBOSE"/&gt;
-</code></pre>
-</li>
+<pre class="prettyprint"><code>  &lt;preference name=&quot;LogLevel&quot; value=&quot;VERBOSE&quot;/&gt;
+</code></pre></li>
 </ul>
 
             </div>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org


Mime
View raw message