You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by st...@apache.org on 2016/01/28 18:36:53 UTC
svn commit: r1727412 [1/4] - in /cordova/site/public: ./
announcements/2016/01/24/ blog/ docs/en/dev/config_ref/
docs/en/dev/guide/platforms/android/ docs/en/dev/guide/platforms/ios/
news/2016/01/28/ static/js/
Author: steven
Date: Thu Jan 28 17:36:52 2016
New Revision: 1727412
URL: http://svn.apache.org/viewvc?rev=1727412&view=rev
Log:
added cordova 6 blog post
Added:
cordova/site/public/news/2016/01/28/
cordova/site/public/news/2016/01/28/tools-release.html
Modified:
cordova/site/public/announcements/2016/01/24/cordova-android-5.1.0.html
cordova/site/public/blog/index.html
cordova/site/public/docs/en/dev/config_ref/index.html
cordova/site/public/docs/en/dev/guide/platforms/android/lifecycle.html
cordova/site/public/docs/en/dev/guide/platforms/android/plugin.html
cordova/site/public/docs/en/dev/guide/platforms/ios/plugin.html
cordova/site/public/feed.xml
cordova/site/public/sitemap.xml
cordova/site/public/static/js/index.js
Modified: cordova/site/public/announcements/2016/01/24/cordova-android-5.1.0.html
URL: http://svn.apache.org/viewvc/cordova/site/public/announcements/2016/01/24/cordova-android-5.1.0.html?rev=1727412&r1=1727411&r2=1727412&view=diff
==============================================================================
--- cordova/site/public/announcements/2016/01/24/cordova-android-5.1.0.html (original)
+++ cordova/site/public/announcements/2016/01/24/cordova-android-5.1.0.html Thu Jan 28 17:36:52 2016
@@ -170,6 +170,26 @@ cordova platform update android@5.1.0
</div>
<div class="col-sm-6">
+ <a href="/news/2016/01/28/tools-release.html">Next</a>
+ <br>
+ <br>
+ <a class="title" href="/news/2016/01/28/tools-release.html">Cordova 6.0.0 Released!</a>
+ <div class="date"> 28 Jan 2016 - By Steve Gill </div>
+ <p class="content">
+ <!--
+ NOTE:
+ the markdownify filter is used here
+ because posts are rendered in sequence;
+ that is, the next post's content isn't
+ yet rendered at the time that this post
+ is being rendered, so page.next.excerpt
+ is still in Markdown and not HTML
+
+ Reference: https://github.com/jekyll/jekyll/issues/2860
+ -->
+ New versions of cordova tools are now live! cordova-lib@6.0.0 cordova@6.0.0 plugman@1.1.0 cordova-js@4.1.3...
+ </p>
+
</div>
</div>
</footer>
Modified: cordova/site/public/blog/index.html
URL: http://svn.apache.org/viewvc/cordova/site/public/blog/index.html?rev=1727412&r1=1727411&r2=1727412&view=diff
==============================================================================
--- cordova/site/public/blog/index.html (original)
+++ cordova/site/public/blog/index.html Thu Jan 28 17:36:52 2016
@@ -106,7 +106,65 @@
<li>
<header>
- <div class="adorner" blogTime="Sun, 24 Jan 2016 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Thu, 28 Jan 2016 00:00:00 -0700"></div>
+ <h2 class="title">
+ <a href="/news/2016/01/28/tools-release.html">Cordova 6.0.0 Released!</a>
+ </h2>
+ <div class="details">
+ <span class="date">28 Jan 2016</span>
+ - by
+ <span class="author">
+
+ <a href="https://twitter.com/stevesgill">Steve Gill</a>
+
+ </span>
+ <a class="comment" href="/news/2016/01/28/tools-release.html#disqus_thread"></a>
+ </div>
+ </header>
+ <section class="post-excerpt">
+ <p><p>New versions of cordova tools are now live!</p>
+
+<ul>
+<li><a href="https://www.npmjs.org/package/cordova-lib">cordova-lib@6.0.0</a></li>
+<li><a href="https://www.npmjs.org/package/cordova">cordova@6.0.0</a></li>
+<li><a href="https://www.npmjs.org/package/plugman">plugman@1.1.0</a></li>
+<li><a href="https://www.npmjs.org/package/cordova-js">cordova-js@4.1.3</a></li>
+</ul>
+
+<p>Release Highlights include:</p>
+
+<ul>
+<li>Updated default platform versions to <code class="prettyprint">cordova-android@5</code>, <code class="prettyprint">cordova-ios@4</code> and <code class="prettyprint">cordova-windows@4.3</code>.
+
+<ul>
+<li><code class="prettyprint">cordova-android@5.1</code> supports <strong>Android 6.X.X (Marshmallow)</strong> </li>
+<li><code class="prettyprint">cordova-ios@4.0</code> adds <strong>iOS9</strong> and <code class="prettyprint">WKWebView</code> support</li>
+<li><code class="prettyprint">cordova-windows@4.3</code> updated the platform to use the new Platform API.</li>
+</ul></li>
+<li>Added a new template feature to <code class="prettyprint">create</code> command. E.g. <code class="prettyprint">cordova create --template cordova-app-hello-world</code>. This can fetch templates via <strong>npm</strong>, <strong>git URL</strong> or local paths.</li>
+<li>Removed support for our old <strong>Cordova Plugins Registry</strong>. Now plugins can only be installed via <strong>npm</strong>, <strong>git URL</strong> or local paths.</li>
+<li>Added default plugin pinning to <code class="prettyprint">cordova</code>. This means that <code class="prettyprint">cordova plugin add cordova-plugin-camera</code> will fetch the pinned version of the plugin instead of the always grabbing the <code class="prettyprint">latest</code>. Users can still install any version of a plugin via <code class="prettyprint">cordova plugin add cordova-plugin-camera@VERSION</code>.</li>
+<li>Added deprecation notices for <strong>amazon-fireos</strong> and <strong>wp8</strong>. We are aiming to remove support for these platforms in 6 months. Target <strong>Android</strong> and <strong>Windows</strong> instead.</li>
+</ul>
+
+<p>To update your tools:</p>
+
+<ul>
+<li><p>If you have <code class="prettyprint">cordova</code> installed:</p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">npm install -g cordova@latest
+</code></pre></div></li>
+<li><p>If you have <code class="prettyprint">plugman</code> installed:</p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">npm install -g plugman@latest
+</code></pre></div></li>
+</ul>
+</p>
+ <div><a href="/news/2016/01/28/tools-release.html">More...</a></div>
+ </section>
+ </li>
+
+ <li>
+ <header>
+ <div class="adorner" blogTime="Sun, 24 Jan 2016 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2016/01/24/cordova-android-5.1.0.html">Cordova Android 5.1.0</a>
</h2>
@@ -149,7 +207,7 @@ cordova platform update android@5.1.0
<li>
<header>
- <div class="adorner" blogTime="Tue, 19 Jan 2016 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 19 Jan 2016 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2016/01/19/plugins-release.html">Plugins Release</a>
</h2>
@@ -201,7 +259,7 @@ cordova plugin add cordova-plugin-camera
<li>
<header>
- <div class="adorner" blogTime="Mon, 18 Jan 2016 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 18 Jan 2016 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2016/01/18/cordova-windows-4.3.0.html">Apache Cordova Windows 4.3.0</a>
</h2>
@@ -237,7 +295,7 @@ cordova platform update windows@4.3.0
<li>
<header>
- <div class="adorner" blogTime="Fri, 08 Jan 2016 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 08 Jan 2016 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2016/01/08/cordova-ubuntu-4.3.2.html">Cordova Ubuntu 4.3.2</a>
</h2>
@@ -269,7 +327,7 @@ cordova platform update ubuntu@4.3.2
<li>
<header>
- <div class="adorner" blogTime="Fri, 18 Dec 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 18 Dec 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/12/18/cordova-ios-4.0.1.html">Cordova iOS 4.0.1</a>
</h2>
@@ -301,7 +359,7 @@ cordova platform update ios@4.0.1
<li>
<header>
- <div class="adorner" blogTime="Mon, 14 Dec 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 14 Dec 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/12/14/plugins-release.html">Plugins Release</a>
</h2>
@@ -340,7 +398,7 @@ cordova plugin add cordova-plugin-wkwebv
<li>
<header>
- <div class="adorner" blogTime="Tue, 08 Dec 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 08 Dec 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/12/08/wkwebview-engine-plugin-release.html">Plugins Release</a>
</h2>
@@ -377,7 +435,7 @@ cordova plugin add cordova-plugin-wkwebv
<li>
<header>
- <div class="adorner" blogTime="Tue, 08 Dec 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 08 Dec 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/12/08/cordova-ios-4.0.0.html">Cordova iOS 4.0.0</a>
</h2>
@@ -432,7 +490,7 @@ cordova platform update ios@4.0.0
<li>
<header>
- <div class="adorner" blogTime="Tue, 24 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 24 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/11/24/tools-release.html">Tools Release</a>
</h2>
@@ -471,7 +529,7 @@ cordova platform update ios@4.0.0
<li>
<header>
- <div class="adorner" blogTime="Tue, 24 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 24 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/11/24/plugins-release.html">Plugins Release</a>
</h2>
@@ -549,7 +607,7 @@ cordova plugin add cordova-plugin-camera
<li>
<header>
- <div class="adorner" blogTime="Fri, 20 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 20 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/11/20/security.html">CVE annoucements for Cordova-Android</a>
</h2>
@@ -582,7 +640,7 @@ Cordova-Android 3.x due to security issu
<li>
<header>
- <div class="adorner" blogTime="Wed, 11 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Wed, 11 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/11/11/cordova-windows-4.2.0.html">Apache Cordova Windows 4.2.0</a>
</h2>
@@ -620,7 +678,7 @@ cordova platform update windows@4.2.0
<li>
<header>
- <div class="adorner" blogTime="Mon, 09 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 09 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/11/09/cordova-android-5.0.0.html">Cordova Android 5.0.0</a>
</h2>
@@ -667,7 +725,7 @@ cordova platform update android@5.0.0
<li>
<header>
- <div class="adorner" blogTime="Fri, 06 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 06 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/11/06/tools-release.html">Tools Release: November 6th, 2015</a>
</h2>
@@ -718,7 +776,7 @@ cordova platform update android@5.0.0
<li>
<header>
- <div class="adorner" blogTime="Mon, 02 Nov 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 02 Nov 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/11/02/cordova-ios-3.9.2.html">Apache Cordova iOS 3.9.2</a>
</h2>
@@ -749,7 +807,7 @@ cordova platform update ios@3.9.2
<li>
<header>
- <div class="adorner" blogTime="Tue, 22 Sep 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 22 Sep 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/09/22/tools-release.html">Tools Release 5.3.3</a>
</h2>
@@ -790,7 +848,7 @@ cordova platform update ios@3.9.2
<li>
<header>
- <div class="adorner" blogTime="Mon, 21 Sep 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 21 Sep 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/09/21/file-transfer-release.html">cordova-plugin-file-transfer release: September 21, 2015</a>
</h2>
@@ -826,7 +884,7 @@ cordova plugin add cordova-plugin-file-t
<li>
<header>
- <div class="adorner" blogTime="Wed, 09 Sep 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 09 Sep 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/09/09/tools-release.html">Tools Release: September 9th, 2015</a>
</h2>
@@ -868,7 +926,7 @@ cordova plugin add cordova-plugin-file-t
<li>
<header>
- <div class="adorner" blogTime="Tue, 08 Sep 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 08 Sep 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/09/08/cpr-readonly.html">Cordova Plugins Registry becomes immutable</a>
</h2>
@@ -899,7 +957,7 @@ cordova plugin add cordova-plugin-file-t
<li>
<header>
- <div class="adorner" blogTime="Sat, 05 Sep 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Sat, 05 Sep 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/09/05/cordova-blackberry-3.8.0.html">Apache Cordova BlackBerry 3.8.0</a>
</h2>
@@ -936,7 +994,7 @@ cordova platform update blackberry10@3.8
<li>
<header>
- <div class="adorner" blogTime="Tue, 18 Aug 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 18 Aug 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/08/18/cordova-windows-4.1.0.html">Apache Cordova Windows 4.1.0</a>
</h2>
@@ -980,7 +1038,7 @@ cordova platform update windows@4.1.0
<li>
<header>
- <div class="adorner" blogTime="Thu, 13 Aug 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Thu, 13 Aug 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/08/13/tools-release.html">Tools Release: August 13th, 2015</a>
</h2>
@@ -1033,7 +1091,7 @@ cordova platform update windows@4.1.0
<li>
<header>
- <div class="adorner" blogTime="Tue, 04 Aug 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 04 Aug 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/08/04/cordova-ios-3.9.0.html">Apache Cordova iOS 3.9.0</a>
</h2>
@@ -1080,7 +1138,7 @@ cordova platform update ios@3.9.0
<li>
<header>
- <div class="adorner" blogTime="Tue, 21 Jul 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 21 Jul 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/07/21/cordova-android-4.1.0.html">Apache Cordova Android 4.1.0</a>
</h2>
@@ -1123,7 +1181,7 @@ cordova platform update android@4.1.0
<li>
<header>
- <div class="adorner" blogTime="Mon, 22 Jun 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 22 Jun 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/06/22/plugins-release.html">Plugins Release: June 22, 2015</a>
</h2>
@@ -1164,7 +1222,7 @@ cordova platform update android@4.1.0
<li>
<header>
- <div class="adorner" blogTime="Wed, 10 Jun 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 10 Jun 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/06/10/tools-release.html">Tools Release: June 10, 2015</a>
</h2>
@@ -1214,7 +1272,7 @@ cordova platform update android@4.1.0
<li>
<header>
- <div class="adorner" blogTime="Thu, 04 Jun 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Thu, 04 Jun 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/06/04/tools-release.html">Tools Release 4.3.1</a>
</h2>
@@ -1260,7 +1318,7 @@ release:</p>
<li>
<header>
- <div class="adorner" blogTime="Wed, 03 Jun 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 03 Jun 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/06/03/windows-release.html">Apache Cordova Windows 4.0.0 release</a>
</h2>
@@ -1301,7 +1359,7 @@ release:</p>
<li>
<header>
- <div class="adorner" blogTime="Tue, 26 May 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 26 May 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/05/26/android-402.html">Apache Cordova Android 4.0.2 and 3.7.2 released</a>
</h2>
@@ -1335,7 +1393,7 @@ release:</p>
<li>
<header>
- <div class="adorner" blogTime="Tue, 21 Apr 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 21 Apr 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2015/04/21/tools-release.html">Tools Release: April 21, 2015</a>
</h2>
@@ -1387,7 +1445,7 @@ release:</p>
<li>
<header>
- <div class="adorner" blogTime="Tue, 21 Apr 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 21 Apr 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/04/21/plugins-release-and-move-to-npm.html">Plugins Release and Moving plugins to npm: April 21, 2015</a>
</h2>
@@ -1435,7 +1493,7 @@ We encourage all third party plugin deve
<li>
<header>
- <div class="adorner" blogTime="Wed, 15 Apr 2015 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 15 Apr 2015 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2015/04/15/cordova-android-4.0.0.html">Apache Cordova Android 4.0.0</a>
</h2>
@@ -1470,7 +1528,7 @@ cordova plugin add https://github.com/Mo
<li>
<header>
- <div class="adorner" blogTime="Mon, 02 Mar 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 02 Mar 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/03/02/tools-release.html">Tools Release: March 02, 2015</a>
</h2>
@@ -1525,7 +1583,7 @@ This should make it easier developing co
<li>
<header>
- <div class="adorner" blogTime="Fri, 27 Feb 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 27 Feb 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/02/27/cordova-windows-3.8.0.html">Apache Cordova Windows 3.8.0</a>
</h2>
@@ -1561,7 +1619,7 @@ cordova platform update windows
<li>
<header>
- <div class="adorner" blogTime="Wed, 25 Feb 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Wed, 25 Feb 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/02/25/cordova-ios-3.8.0.html">Apache Cordova iOS 3.8.0</a>
</h2>
@@ -1600,7 +1658,7 @@ cordova platform update ios
<li>
<header>
- <div class="adorner" blogTime="Tue, 10 Feb 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 10 Feb 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/02/10/plugins-release.html">Plugins Release: February 10, 2015</a>
</h2>
@@ -1660,7 +1718,7 @@ cordova plugin add org.apache.cordova.ca
<li>
<header>
- <div class="adorner" blogTime="Fri, 06 Feb 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 06 Feb 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2015/02/06/cordova-android-3.7.1.html">Apache Cordova Android 3.7.1</a>
</h2>
@@ -1696,7 +1754,7 @@ cordova platform update android@3.7.1
<li>
<header>
- <div class="adorner" blogTime="Fri, 09 Jan 2015 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 09 Jan 2015 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2015/01/09/tools-release.html">Tools Release: January 09, 2015</a>
</h2>
@@ -1738,7 +1796,7 @@ cordova platform update android@3.7.1
<li>
<header>
- <div class="adorner" blogTime="Tue, 09 Dec 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 09 Dec 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/12/09/plugins-release.html">Plugins Release: December 9, 2014</a>
</h2>
@@ -1794,7 +1852,7 @@ cordova plugin add org.apache.cordova.ca
<li>
<header>
- <div class="adorner" blogTime="Tue, 25 Nov 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 25 Nov 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2014/11/25/ios-64bit.html">iOS 64-bit apps in Cordova</a>
</h2>
@@ -1828,7 +1886,7 @@ version <strong>3.4.1</strong> of <stron
<li>
<header>
- <div class="adorner" blogTime="Tue, 18 Nov 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 18 Nov 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/blog/2014/11/18/cordova-perf.html">Automating Performance Audits for Cordova apps</a>
</h2>
@@ -1869,7 +1927,7 @@ Similar principles can be applied to app
<li>
<header>
- <div class="adorner" blogTime="Thu, 13 Nov 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Thu, 13 Nov 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/11/13/tools-release.html">Tools Release: November 13, 2014</a>
</h2>
@@ -1911,7 +1969,7 @@ Similar principles can be applied to app
<li>
<header>
- <div class="adorner" blogTime="Tue, 11 Nov 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Tue, 11 Nov 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/11/11/windows-cert.html">Critical Update: Windows 3.7.1. Release</a>
</h2>
@@ -1954,7 +2012,7 @@ C:\Program Files (x86)\MSBuild\Microsoft
<li>
<header>
- <div class="adorner" blogTime="Thu, 06 Nov 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Thu, 06 Nov 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2014/11/06/cordova-wp-windows-3.7.0.html">Apache Cordova Windows & Windows Phone 3.7.0</a>
</h2>
@@ -1993,7 +2051,7 @@ cordova platform add wp8@3.7.0
<li>
<header>
- <div class="adorner" blogTime="Thu, 06 Nov 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Thu, 06 Nov 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2014/11/06/cordova-ios-3.7.0.html">Apache Cordova iOS 3.7.0</a>
</h2>
@@ -2030,7 +2088,7 @@ cordova platform update ios
<li>
<header>
- <div class="adorner" blogTime="Fri, 17 Oct 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Fri, 17 Oct 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/10/17/plugins-release.html">Plugins Release: October 17, 2014</a>
</h2>
@@ -2086,7 +2144,7 @@ cordova plugin add org.apache.cordova.ca
<li>
<header>
- <div class="adorner" blogTime="Thu, 16 Oct 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Thu, 16 Oct 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2014/10/16/cordova-4.html">Apache Cordova CLI 4.0 Release</a>
</h2>
@@ -2132,7 +2190,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Mon, 22 Sep 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 22 Sep 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/09/22/plugins-release.html">Plugins Release: September 22, 2014</a>
</h2>
@@ -2189,7 +2247,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Mon, 08 Sep 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 08 Sep 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2014/09/08/cordova-361.html">Apache Cordova 3.6</a>
</h2>
@@ -2243,7 +2301,7 @@ Apologies for the confusion.</p>
<li>
<header>
- <div class="adorner" blogTime="Wed, 13 Aug 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 13 Aug 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/08/13/tools-update.html">Tools Release: August 13, 2014</a>
</h2>
@@ -2277,7 +2335,7 @@ Apologies for the confusion.</p>
<li>
<header>
- <div class="adorner" blogTime="Mon, 11 Aug 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 11 Aug 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/08/11/plugins-release.html">Plugins Release: August 11, 2014</a>
</h2>
@@ -2343,7 +2401,7 @@ cordova plugin add org.apache.cordova.fi
<li>
<header>
- <div class="adorner" blogTime="Wed, 06 Aug 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 06 Aug 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2014/08/06/android-351-update.html">Apache Cordova Android 3.5.1 Update</a>
</h2>
@@ -2371,7 +2429,7 @@ cordova plugin add org.apache.cordova.fi
<li>
<header>
- <div class="adorner" blogTime="Mon, 04 Aug 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 04 Aug 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2014/08/04/android-351.html">Apache Cordova Android 3.5.1</a>
</h2>
@@ -2405,7 +2463,7 @@ cordova plugin add org.apache.cordova.fi
<li>
<header>
- <div class="adorner" blogTime="Thu, 10 Jul 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Thu, 10 Jul 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/07/10/tools-release.html">Tools Release: July 10, 2014</a>
</h2>
@@ -2461,7 +2519,7 @@ npm install -g plugman
<li>
<header>
- <div class="adorner" blogTime="Tue, 08 Jul 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 08 Jul 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/07/08/plugins-release.html">Plugins Release: July 8, 2014</a>
</h2>
@@ -2509,7 +2567,7 @@ cordova plugin add org.apache.cordova.co
<li>
<header>
- <div class="adorner" blogTime="Thu, 12 Jun 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Thu, 12 Jun 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/06/12/plugins-release.html">Plugins Release: June 12, 2014</a>
</h2>
@@ -2577,7 +2635,7 @@ cordova plugin add org.apache.cordova.fi
<li>
<header>
- <div class="adorner" blogTime="Fri, 23 May 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Fri, 23 May 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/announcements/2014/05/23/cordova-350.html">Apache Cordova 3.5.0</a>
</h2>
@@ -2620,7 +2678,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Wed, 23 Apr 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 23 Apr 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/04/23/plugins.release.html">Plugins Release: April 23, 2014</a>
</h2>
@@ -2687,7 +2745,7 @@ cordova plugin add org.apache.cordova.fi
<li>
<header>
- <div class="adorner" blogTime="Wed, 09 Apr 2014 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 09 Apr 2014 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2014/04/09/tools-ios-release.html">Tools Release: April 9, 2014</a>
</h2>
@@ -2736,7 +2794,7 @@ npm update -g plugman
<li>
<header>
- <div class="adorner" blogTime="Wed, 05 Mar 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Wed, 05 Mar 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/03/05/tools-release.html">Tools Release: March 5, 2014</a>
</h2>
@@ -2780,7 +2838,7 @@ npm update -g plugman
<li>
<header>
- <div class="adorner" blogTime="Mon, 03 Mar 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 03 Mar 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/03/03/plugins-release.html">Plugins Release: March 3, 2014</a>
</h2>
@@ -2830,7 +2888,7 @@ cordova plugin add org.apache.cordova.fi
<li>
<header>
- <div class="adorner" blogTime="Thu, 20 Feb 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Thu, 20 Feb 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2014/02/20/cordova-340.html">Apache Cordova 3.4.0</a>
</h2>
@@ -2865,7 +2923,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Mon, 10 Feb 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 10 Feb 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/02/10/plugins-release.html">Plugins Release: Feb 10, 2014</a>
</h2>
@@ -2915,7 +2973,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Fri, 31 Jan 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 31 Jan 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/01/31/tools-release.html">Tools Release: Jan 31, 2014</a>
</h2>
@@ -2959,7 +3017,7 @@ npm update -g plugman
<li>
<header>
- <div class="adorner" blogTime="Thu, 02 Jan 2014 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Thu, 02 Jan 2014 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2014/01/02/plugins-release.html">Plugins Release: Jan 2, 2014</a>
</h2>
@@ -3010,7 +3068,7 @@ within plugins themselves. Eventually, d
<li>
<header>
- <div class="adorner" blogTime="Mon, 16 Dec 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Mon, 16 Dec 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2013/12/16/cordova-330.html">Apache Cordova 3.3.0</a>
</h2>
@@ -3044,7 +3102,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Fri, 06 Dec 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 06 Dec 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/releases/2013/12/06/cordova-330rc1.html">Apache Cordova 3.3.0 RC1</a>
</h2>
@@ -3084,7 +3142,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Wed, 04 Dec 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Wed, 04 Dec 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/news/2013/12/04/plugins-release.html">Plugins Release: Dec 4, 2013</a>
</h2>
@@ -3125,7 +3183,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Fri, 22 Nov 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 22 Nov 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2013/11/22/cordova-320.html">Apache Cordova 3.2.0</a>
</h2>
@@ -3162,7 +3220,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Fri, 15 Nov 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Fri, 15 Nov 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/2013/11/15/kitkat.html">Action Required: Android KitKat Compatibility</a>
</h2>
@@ -3201,7 +3259,7 @@ or to directly apply the fix to
<li>
<header>
- <div class="adorner" blogTime="Wed, 13 Nov 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Wed, 13 Nov 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/announcements/releases/2013/11/13/cordova-320rc1.html">Apache Cordova 3.2.0 RC1</a>
</h2>
@@ -3240,7 +3298,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Wed, 06 Nov 2013 00:00:00 -0800"></div>
+ <div class="adorner" blogTime="Wed, 06 Nov 2013 00:00:00 -0700"></div>
<h2 class="title">
<a href="/blog/releases/2013/11/06/cordova-291.html">Apache Cordova 2.9.1</a>
</h2>
@@ -3268,7 +3326,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Mon, 28 Oct 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 28 Oct 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2013/10/28/plugins-release.html">CLI, Plugman & Plugins Release: Oct 28, 2013</a>
</h2>
@@ -3304,7 +3362,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Mon, 21 Oct 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Mon, 21 Oct 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2013/10/21/cordova-registry.html">Cordova's Plugin Registry</a>
</h2>
@@ -3330,7 +3388,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Thu, 10 Oct 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Thu, 10 Oct 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2013/10/10/plugins-release.html">Plugins Release: October 10th, 2013</a>
</h2>
@@ -3381,7 +3439,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Wed, 02 Oct 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Wed, 02 Oct 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/blog/releases/2013/10/02/cordova-31.html">Apache Cordova 3.1</a>
</h2>
@@ -3426,7 +3484,7 @@ cordova platform update android
<li>
<header>
- <div class="adorner" blogTime="Tue, 01 Oct 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Tue, 01 Oct 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2013/10/01/plugins-release.html">Plugins Release: October 1st, 2013</a>
</h2>
@@ -3460,7 +3518,7 @@ cordova plugin add org.apache.cordova.ca
<li>
<header>
- <div class="adorner" blogTime="Fri, 13 Sep 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Fri, 13 Sep 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2013/09/13/last-week.html">Last Week in Cordova: FirefoxOS, Translations, bug fixes</a>
</h2>
@@ -3486,7 +3544,7 @@ translating docs, and fixing bugs.</p>
<li>
<header>
- <div class="adorner" blogTime="Fri, 06 Sep 2013 00:00:00 -0700"></div>
+ <div class="adorner" blogTime="Fri, 06 Sep 2013 00:00:00 -0600"></div>
<h2 class="title">
<a href="/news/2013/09/06/last-week.html">Last Week in Cordova</a>
</h2>
@@ -3515,7 +3573,7 @@ There was also good progress made toward
<li>
<header>
- <div class="adorner" blogTime="Mon, 12 Aug 2013 13:45:04 -0700"></div>
+ <div class="adorner" blogTime="Mon, 12 Aug 2013 14:45:04 -0600"></div>
<h2 class="title">
<a href="/blog/2013/08/12/crowdintranslation.html">Apache Cordova Is Looking for a Few Good Translators</a>
</h2>
@@ -3549,7 +3607,7 @@ like. If you know another language plea
<li>
<header>
- <div class="adorner" blogTime="Tue, 23 Jul 2013 11:45:04 -0700"></div>
+ <div class="adorner" blogTime="Tue, 23 Jul 2013 12:45:04 -0600"></div>
<h2 class="title">
<a href="/blog/releases/2013/07/23/cordova-3.html">Apache Cordova 3.0</a>
</h2>
@@ -3583,7 +3641,7 @@ like. If you know another language plea
<li>
<header>
- <div class="adorner" blogTime="Thu, 11 Jul 2013 13:45:04 -0700"></div>
+ <div class="adorner" blogTime="Thu, 11 Jul 2013 14:45:04 -0600"></div>
<h2 class="title">
<a href="/blog/2013/07/11/cordova-has-a-blog.html">Apache Cordova Gets an Official Blog</a>
</h2>
@@ -3640,7 +3698,7 @@ window.twttr = (function(d, s, id) {
<script>
window.onload = function(){
setTimeout(function(){
- var lastPostTime = new Date("Sun, 24 Jan 2016 00:00:00 -0800").getTime();
+ var lastPostTime = new Date("Thu, 28 Jan 2016 00:00:00 -0700").getTime();
setCookie("visitTime", lastPostTime, 365);
}, 2000);
};
Modified: cordova/site/public/docs/en/dev/config_ref/index.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/dev/config_ref/index.html?rev=1727412&r1=1727411&r2=1727412&view=diff
==============================================================================
--- cordova/site/public/docs/en/dev/config_ref/index.html (original)
+++ cordova/site/public/docs/en/dev/config_ref/index.html Thu Jan 28 17:36:52 2016
@@ -1747,6 +1747,13 @@ example specifies blue:</p>
</code></pre></div></li>
</ul>
+<p>Windows Quirk: CSS Color names are also supported:</p>
+<div class="highlight"><pre><code class="language-text" data-lang="text"> <platform name="windows">
+ <preference name="BackgroundColor" value="turquoise"/>
+ </platform>
+</code></pre></div>
+<p><strong>NOTE</strong>: <code class="prettyprint">transparent</code> value will cause black/white background color in case of Dark/Light theme accordingly.</p>
+
<p>Applies to Android and BlackBerry. Overrides CSS otherwise available
across <em>all</em> platforms, for example: <code class="prettyprint">body{background-color:blue}</code>.</p>
Modified: cordova/site/public/docs/en/dev/guide/platforms/android/lifecycle.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/dev/guide/platforms/android/lifecycle.html?rev=1727412&r1=1727411&r2=1727412&view=diff
==============================================================================
--- cordova/site/public/docs/en/dev/guide/platforms/android/lifecycle.html (original)
+++ cordova/site/public/docs/en/dev/guide/platforms/android/lifecycle.html Thu Jan 28 17:36:52 2016
@@ -1596,131 +1596,339 @@
<div id="page-toc-source">
<h1 id="android-lifecycle-guide">Android Lifecycle Guide</h1>
-<p>Native Android apps typically consist of a series of "activities" that the user interacts with. Activities can be thought of as the individual screens that make up an application; different tasks in an app will often have their own activity. Each activity has a lifecycle, and can be created and destroyed as the OS sees fit.</p>
+<h2 id="cordova-and-android">Cordova and Android</h2>
-<p>In contrast, Cordova applications on the Android platform are executed within a Webview that is embedded in a <em>single</em> Android activity. The lifecycle of this activity is exposed to your application through the document events that are fired. These events are not guaranteed to line up with Android's lifecycle, but they can provide guidelines for saving and restoring your state. These events roughly map to Android callbacks as follows:</p>
+<p>Native Android apps typically consist of a series of <a href="http://developer.android.com/reference/android/app/Activity.html">activities</a> that the user
+interacts with. Activities can be thought of as the individual screens that make
+up an application; different tasks in an app will often have their own activity.
+Each activity has its own lifecycle that is maintained as the activity enters
+and leaves the foreground of a user's device.</p>
+
+<p>In contrast, Cordova applications on the Android platform are executed within a
+Webview that is embedded in a <em>single</em> Android activity. The lifecycle of this
+activity is exposed to your application through the document events that are
+fired. The events are not guaranteed to line up with Android's lifecycle, but
+they can provide guidelines for saving and restoring your state. These events
+roughly map to Android callbacks as follows:</p>
<table><thead>
<tr>
<th>Cordova Event</th>
<th>Rough Android Equivalent</th>
+<th>Meaning</th>
</tr>
</thead><tbody>
<tr>
<td><code class="prettyprint">deviceready</code></td>
<td><code class="prettyprint">onCreate()</code></td>
+<td>Application is starting (not from background)</td>
</tr>
<tr>
<td><code class="prettyprint">pause</code></td>
<td><code class="prettyprint">onPause()</code></td>
+<td>Application is moving to the background</td>
</tr>
<tr>
<td><code class="prettyprint">resume</code></td>
<td><code class="prettyprint">onResume()</code></td>
+<td>Application is returning to the foreground</td>
</tr>
</tbody></table>
-<p>Often, Cordova applications are confined to the single activity that contains the Webview. However, there are instances in which other activities may be launched that push the Cordova activity to the background. It is important in these cases to be aware of the Android lifecycle and properly maintain your application's state by respecting it.</p>
-
-<h2 id="low-memory-and-the-activity-lifecycle">Low memory and the Activity lifecycle</h2>
-
-<p>Plugins have the ability to launch activities beyond the Cordova activity in order to perform some tasks. For example, the Apache camera plugin, cordova-plugin-camera, launches the device's camera activity in order to take photos.</p>
-
-<p>The flow of events in this case looks something like this:</p>
+<p>Most other Cordova platforms have a similar concept of lifecycles and should
+fire these same events when similar actions happen on a user's device. However,
+Android presents some unique challenges that can sometimes show up thanks to the
+native Activity lifecycle.</p>
+
+<h2 id="what-makes-android-different">What makes Android different?</h2>
+
+<p>In Android, the OS can choose to kill activities in the background in
+order to free up resources if the device running the application is low on
+memory. Unfortunately, when the activity holding your application is killed,
+the Webview in which your application lives will be destroyed as well. Any state
+that your application is maintaining will be lost in this case. When the user
+navigates back to your application, the Activity and Webview will be
+recreated by the OS, but state will not be automatically restored for your
+Cordova app. For this reason, it is imperative that your application be aware of
+the lifecycle events that are fired and maintain whatever state is appropriate
+to make sure a user's context in your app is not lost when they leave the
+application.</p>
+
+<h2 id="when-can-this-happen">When can this happen?</h2>
+
+<p>Your application is susceptible to being destroyed by the OS whenever it leaves
+the sight of the user. There are two main situations in which this can occur.
+The first and most obvious case is when the user presses the home button or
+switches to another application.</p>
+
+<p>However, there is a second (and much more subtle) case that certain plugins can
+introduce. As noted above, Cordova applications are usually confined to the
+single activity that contains the Webview. However, there are instances in which
+other activities may be launched by plugins and temporarily push the Cordova
+activity to the background. These other Activities are typically launched in
+order to perform a specific task using a native application installed on the
+device. For example, the Apache camera plugin launches whatever camera activity
+is natively installed on the device in order to take a photo. Reusing the
+installed camera application in this way makes your application feel much more
+like a native app when the user tries to take a photo. Unfortunately, when the
+native Activity pushes your app to the background there is a chance the OS
+will kill it.</p>
+
+<p>For a clearer understanding of this second case, let's walk through an example
+using the camera plugin. Imagine you have an application that requires the user
+to take a profile photo. The flow of events in the application when everything
+goes as planned will look something like this:</p>
<ol>
<li>The user is interacting with your app and needs to take a picture</li>
<li>The camera plugin launches the native camera activity
<ul>
-<li><em>The Cordova activity is pushed to the background (<code class="prettyprint">pause</code> event is fired)</em></li>
+<li><em>The Cordova activity is pushed to the background (pause event is fired)</em></li>
</ul></li>
<li>The user takes a photo</li>
<li>The camera activity finishes
<ul>
-<li><em>The Cordova activity is moved to the foreground (<code class="prettyprint">resume</code> event is fired)</em></li>
+<li><em>The Cordova activity is moved to the foreground (resume event is fired)</em></li>
</ul></li>
<li>The user is returned to your application where they left off</li>
</ol>
-<p>However, this flow of events can be disrupted if a device is low on memory. The Android OS will often kill background activities in order to free up memory if necessary. Unfortunately, when the activity holding your application is killed, the Webview in which your application lives will be destroyed as well. Any state that your application is maintaining will be lost in this case. When the user navigates back to your the application, the Activity and Webview will be recreated by the OS, but state will not be automatically restored.</p>
-
-<p>If state is not properly saved when the Activity is destroyed, the above sequence of events instead plays out as follows:</p>
+<p>However, this flow of events can be disrupted if a device is low on memory. If
+the Activity is killed by the OS, the above sequence of events instead plays out
+as follows:</p>
<ol>
<li>The user is interacting with your app and needs to take a picture</li>
<li>The camera plugin launches the native camera activity
<ul>
-<li><em>The OS destroys the Cordova activity (<code class="prettyprint">pause</code> event is fired)</em></li>
+<li><em>The OS destroys the Cordova activity (pause event is fired)</em></li>
</ul></li>
<li>The user takes a photo</li>
<li>The camera activity finishes
<ul>
-<li><em>The OS recreates the Cordova activity (<code class="prettyprint">deviceready</code> and <code class="prettyprint">resume</code> events are fired)</em></li>
+<li><em>The OS recreates the Cordova activity (deviceready and resume events are fired)</em></li>
</ul></li>
<li>The user is confused as to why they are suddenly back at your app's login screen</li>
</ol>
-<p>In this instance, the photo that was taken is lost and the user is given the confusing and frustrating experience of having your application appear to randomly restart. The key to preventing this experience is subscribing to events and properly maintaining state as part of the activity lifecycle.</p>
-
-<h2 id="maintaining-state">Maintaining state</h2>
-
-<p>In the examples above, the javascript events that are fired are noted in italics. These events are your opportunity to save and restore your application's state. You should register callbacks in your application's <code class="prettyprint">bindEvents</code> function that respond to the lifecycle events by saving state. What information you save and how you save it is left to your discretion, but you should be sure to save enough information so that you can restore the user to exactly where they left off when they return to your application.</p>
-
-<h2 id="testing-the-activity-lifecycle">Testing the Activity Lifecycle</h2>
-
-<p>Android provides a developer setting for debugging Activity destruction on low memory. Enable the "Don't keep activities" setting in the Developer Options menu on your device or emulator to simulate low memory scenarios. If your application launches external activities, you should always do some testing with this setting enabled to ensure that you are properly handling low memory scenarios.</p>
-
-<h2 id="retrieving-plugin-callback-results">Retrieving plugin callback results</h2>
-
-<p>When the OS destroys the Cordova activity in the above example, any pending callbacks are lost as well. This means that if you passed a callback to the plugin that launched the new activity (e.g. cordova-plugin-camera), that callback will NOT be fired when the application is recreated. However, there is a way for plugins to pass the result of this call to your application. The <code class="prettyprint">resume</code> event's payload will contain any pending plugin results from the plugin request that launched the external activity made prior to the activity being destroyed.</p>
+<p>In this instance, the OS killed the application in the background and the
+application did not maintain its state as part of the lifecycle. When the user
+returned to the app, the Webview was recreated and the app appeared to have
+restarted from scratch (hence the user's confusion). This sequence of events is
+equivalent to what happens when the home button is pressed or the user switches
+applications. The key to preventing the above experience is subscribing to
+events and properly maintaining state as part of the activity lifecycle.</p>
+
+<h2 id="respecting-the-lifecycle">Respecting the Lifecycle</h2>
+
+<p>In the examples above, the javascript events that are fired are noted in
+italics. These events are your opportunity to save and restore your
+application's state. You should register callbacks in your application's
+<code class="prettyprint">bindEvents</code> function that respond to the lifecycle events by saving state. What
+information you save and how you save it is left to your discretion, but you
+should be sure to save enough information so that you can restore the user to
+exactly where they left off when they return to your application.</p>
+
+<p>There is one additional factor in the example above that only applies in the
+second-discussed situation (i.e. when a plugin launches an external activity).
+Not only was the state of the application lost when the user finished taking a
+photo, but so was the photo that the user took. Normally, that photo would be
+delivered to your application through the callback that was registered with the
+camera plugin. However, when the Webview was destroyed that callback was lost
+forever. Luckily, cordova-android 5.1.0 and above provide a means for getting
+the result of that plugin call when your application resumes.</p>
+
+<h2 id="retrieving-plugin-callback-results-cordova-android-5-1-0">Retrieving plugin callback results (cordova-android 5.1.0+)</h2>
+
+<p>When the OS destroys the Cordova activity that was pushed into the background
+by a plugin, any pending callbacks are lost as well. This means that if you
+passed a callback to the plugin that launched the new activity (e.g. the camera
+plugin), that callback will NOT be fired when the application is recreated.
+However, starting in cordova-android <strong>5.1.0</strong>, the <code class="prettyprint">resume</code> event's payload will
+contain any pending plugin results from the plugin request that launched the
+external activity made prior to the activity being destroyed.</p>
<p>The payload for the <code class="prettyprint">resume</code> event adheres to the following format:</p>
<div class="highlight"><pre><code class="language-text" data-lang="text">{
action: "resume",
pendingResult: {
- pluginServiceName: <name of the plugin e.g. "Camera">,
- pluginStatus: <description of the result's status (see below)>,
- result: <argument(s) that would have been given to the callback>
+ pluginServiceName: string,
+ pluginStatus: string,
+ result: any
}
}
</code></pre></div>
-<p>The possible plugin statuses in the <code class="prettyprint">pendingResult</code> field include the following values:</p>
-<div class="highlight"><pre><code class="language-text" data-lang="text">"No result"
-"OK"
-"Class not found"
-"Illegal access"
-"Instantiation error"
-"Malformed url"
-"IO error"
-"Invalid action"
-"JSON error"
-"Error
-</code></pre></div>
-<blockquote>
-<p><strong>NOTE:</strong> It is up to the plugin to decide what is contained in the <code class="prettyprint">result</code> field and the meaning of the <code class="prettyprint">pluginStatus</code> that is returned. Reference the API of the plugin you are using to see what you should expect those fields to contain and how to use their values</p>
-</blockquote>
-
-<p>A <code class="prettyprint">resume</code> callback that makes use of the event payload might look something like this:</p>
-<div class="highlight"><pre><code class="language-javascript" data-lang="javascript"><span class="nx">onResume</span><span class="p">(</span><span class="nx">event</span><span class="p">)</span> <span class="p">{</span>
- <span class="c1">// Restore your application's state here. It's up to you to keep track of</span>
- <span class="c1">// where this plugin result is coming from (i.e. what part of your code made</span>
- <span class="c1">// the call) and what arguments you provided to the plugin</span>
-
- <span class="c1">// Next, check if there is a plugin result in the event object</span>
- <span class="k">if</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">pendingResult</span><span class="p">)</span> <span class="p">{</span>
- <span class="c1">// Figure out whether or not the plugin call was successful</span>
- <span class="k">if</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">pendingResult</span><span class="p">.</span><span class="nx">pluginStatus</span> <span class="o">===</span> <span class="s2">"OK"</span><span class="p">)</span> <span class="p">{</span>
- <span class="nx">successCallback</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">result</span><span class="p">);</span>
- <span class="p">}</span> <span class="k">else</span> <span class="p">{</span>
- <span class="nx">failCallback</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">result</span><span class="p">);</span>
+<p>The fields of that payload are defined as follows:</p>
+
+<ul>
+<li><code class="prettyprint">pluginServiceName</code>: The name of the plugin returning the result (e.g. "Camera"). This can be found in the <code class="prettyprint"><name></code> tag of a plugin's plugin.xml file</li>
+<li><code class="prettyprint">pluginStatus</code>: The status of the plugin call (see below)</li>
+<li><code class="prettyprint">result</code>: Whatever the result of the plugin call is</li>
+</ul>
+
+<p>The possible values for <code class="prettyprint">pluginStatus</code> in the <code class="prettyprint">pendingResult</code> field include the following:</p>
+
+<ul>
+<li><code class="prettyprint">"OK"</code> - The plugin call was successful</li>
+<li><code class="prettyprint">"No Result"</code> - The plugin call ended with no result</li>
+<li><code class="prettyprint">"Error"</code> - The plugin call resulted in some general error</li>
+<li>Other miscellaneous errors
+
+<ul>
+<li><code class="prettyprint">"Class not found"</code></li>
+<li><code class="prettyprint">"Illegal access"</code></li>
+<li><code class="prettyprint">"Instantiation error"</code></li>
+<li><code class="prettyprint">"Malformed url"</code></li>
+<li><code class="prettyprint">"IO error"</code></li>
+<li><code class="prettyprint">"Invalid action"</code></li>
+<li><code class="prettyprint">"JSON error"</code></li>
+</ul></li>
+</ul>
+
+<p>Please note that it is up to the plugin to decide what is contained in the
+<code class="prettyprint">result</code> field and the meaning of the <code class="prettyprint">pluginStatus</code> that is returned. Reference
+the API of the plugin you are using to see what you should expect those fields
+to contain and how to use their values.</p>
+
+<h3 id="example">Example</h3>
+
+<p>Below is a brief example application that uses the <code class="prettyprint">resume</code> and <code class="prettyprint">pause</code> events
+to manage state. It uses the Apache camera plugin as an example of how to
+retrieve the results of a plugin call from the <code class="prettyprint">resume</code> event payload. The
+portion of the code dealing with the <code class="prettyprint">resume</code>'s <code class="prettyprint">event.pendingResult</code> object
+requires cordova-android <strong>5.1.0+</strong></p>
+<div class="highlight"><pre><code class="language-javascript" data-lang="javascript"><span class="c1">// This state represents the state of our application and will be saved and</span>
+<span class="c1">// restored by onResume() and onPause()</span>
+<span class="kd">var</span> <span class="nx">appState</span> <span class="o">=</span> <span class="p">{</span>
+ <span class="nx">takingPicture</span><span class="o">:</span> <span class="kc">true</span><span class="p">,</span>
+ <span class="nx">imageUri</span><span class="o">:</span> <span class="s2">""</span>
+<span class="p">};</span>
+
+<span class="kd">var</span> <span class="nx">APP_STORAGE_KEY</span> <span class="o">=</span> <span class="s2">"exampleAppState"</span><span class="p">;</span>
+
+<span class="kd">var</span> <span class="nx">app</span> <span class="o">=</span> <span class="p">{</span>
+ <span class="nx">initialize</span><span class="o">:</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
+ <span class="k">this</span><span class="p">.</span><span class="nx">bindEvents</span><span class="p">();</span>
+ <span class="p">},</span>
+ <span class="nx">bindEvents</span><span class="o">:</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
+ <span class="c1">// Here we register our callbacks for the lifecycle events we care about</span>
+ <span class="nb">document</span><span class="p">.</span><span class="nx">addEventListener</span><span class="p">(</span><span class="s1">'deviceready'</span><span class="p">,</span> <span class="k">this</span><span class="p">.</span><span class="nx">onDeviceReady</span><span class="p">,</span> <span class="kc">false</span><span class="p">);</span>
+ <span class="nb">document</span><span class="p">.</span><span class="nx">addEventListener</span><span class="p">(</span><span class="s1">'pause'</span><span class="p">,</span> <span class="k">this</span><span class="p">.</span><span class="nx">onPause</span><span class="p">,</span> <span class="kc">false</span><span class="p">);</span>
+ <span class="nb">document</span><span class="p">.</span><span class="nx">addEventListener</span><span class="p">(</span><span class="s1">'resume'</span><span class="p">,</span> <span class="k">this</span><span class="p">.</span><span class="nx">onResume</span><span class="p">,</span> <span class="kc">false</span><span class="p">);</span>
+ <span class="p">},</span>
+ <span class="nx">onDeviceReady</span><span class="o">:</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
+ <span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="s2">"take-picture-button"</span><span class="p">).</span><span class="nx">addEventListener</span><span class="p">(</span><span class="s2">"click"</span><span class="p">,</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
+ <span class="c1">// Because the camera plugin method launches an external Activity,</span>
+ <span class="c1">// there is a chance that our application will be killed before the</span>
+ <span class="c1">// success or failure callbacks are called. See onPause() and</span>
+ <span class="c1">// onResume() where we save and restore our state to handle this case</span>
+ <span class="nx">appState</span><span class="p">.</span><span class="nx">takingPicture</span> <span class="o">=</span> <span class="kc">true</span><span class="p">;</span>
+
+ <span class="nx">navigator</span><span class="p">.</span><span class="nx">camera</span><span class="p">.</span><span class="nx">getPicture</span><span class="p">(</span><span class="nx">cameraSuccessCallback</span><span class="p">,</span> <span class="nx">cameraFailureCallback</span><span class="p">,</span>
+ <span class="p">{</span>
+ <span class="nx">sourceType</span><span class="o">:</span> <span class="nx">Camera</span><span class="p">.</span><span class="nx">PictureSourceType</span><span class="p">.</span><span class="nx">CAMERA</span><span class="p">,</span>
+ <span class="nx">destinationType</span><span class="o">:</span> <span class="nx">Camera</span><span class="p">.</span><span class="nx">DestinationType</span><span class="p">.</span><span class="nx">FILE_URI</span><span class="p">,</span>
+ <span class="nx">targetWidth</span><span class="o">:</span> <span class="mi">250</span><span class="p">,</span>
+ <span class="nx">targetHeight</span><span class="o">:</span> <span class="mi">250</span>
+ <span class="p">}</span>
+ <span class="p">);</span>
+ <span class="p">});</span>
+ <span class="p">},</span>
+ <span class="nx">onPause</span><span class="o">:</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
+ <span class="c1">// Here, we check to see if we are in the middle of taking a picture. If</span>
+ <span class="c1">// so, we want to save our state so that we can properly retrieve the</span>
+ <span class="c1">// plugin result in onResume(). We also save if we have already fetched</span>
+ <span class="c1">// an image URI</span>
+ <span class="k">if</span><span class="p">(</span><span class="nx">appState</span><span class="p">.</span><span class="nx">takingPicture</span> <span class="o">||</span> <span class="nx">appState</span><span class="p">.</span><span class="nx">imageUri</span><span class="p">)</span> <span class="p">{</span>
+ <span class="nb">window</span><span class="p">.</span><span class="nx">localStorage</span><span class="p">.</span><span class="nx">setItem</span><span class="p">(</span><span class="nx">APP_STORAGE_KEY</span><span class="p">,</span> <span class="nx">JSON</span><span class="p">.</span><span class="nx">stringify</span><span class="p">(</span><span class="nx">appState</span><span class="p">));</span>
+ <span class="p">}</span>
+ <span class="p">},</span>
+ <span class="nx">onResume</span><span class="o">:</span> <span class="kd">function</span><span class="p">(</span><span class="nx">event</span><span class="p">)</span> <span class="p">{</span>
+ <span class="c1">// Here we check for stored state and restore it if necessary. In your</span>
+ <span class="c1">// application, it's up to you to keep track of where any pending plugin</span>
+ <span class="c1">// results are coming from (i.e. what part of your code made the call)</span>
+ <span class="c1">// and what arguments you provided to the plugin if relevant</span>
+ <span class="kd">var</span> <span class="nx">storedState</span> <span class="o">=</span> <span class="nb">window</span><span class="p">.</span><span class="nx">localStorage</span><span class="p">.</span><span class="nx">getItem</span><span class="p">(</span><span class="nx">APP_STORAGE_KEY</span><span class="p">);</span>
+
+ <span class="k">if</span><span class="p">(</span><span class="nx">storedState</span><span class="p">)</span> <span class="p">{</span>
+ <span class="nx">appState</span> <span class="o">=</span> <span class="nx">JSON</span><span class="p">.</span><span class="nx">parse</span><span class="p">(</span><span class="nx">storedState</span><span class="p">);</span>
+ <span class="p">}</span>
+
+ <span class="c1">// Check to see if we need to restore an image we took</span>
+ <span class="k">if</span><span class="p">(</span><span class="o">!</span><span class="nx">appState</span><span class="p">.</span><span class="nx">takingPicture</span> <span class="o">&&</span> <span class="nx">appState</span><span class="p">.</span><span class="nx">imageUri</span><span class="p">)</span> <span class="p">{</span>
+ <span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="s2">"get-picture-result"</span><span class="p">).</span><span class="nx">src</span> <span class="o">=</span> <span class="nx">appState</span><span class="p">.</span><span class="nx">imageUri</span><span class="p">;</span>
+ <span class="p">}</span>
+ <span class="c1">// Now we can check if there is a plugin result in the event object.</span>
+ <span class="c1">// This requires cordova-android 5.1.0+</span>
+ <span class="k">else</span> <span class="k">if</span><span class="p">(</span><span class="nx">appState</span><span class="p">.</span><span class="nx">takingPicture</span> <span class="o">&&</span> <span class="nx">event</span><span class="p">.</span><span class="nx">pendingResult</span><span class="p">)</span> <span class="p">{</span>
+ <span class="c1">// Figure out whether or not the plugin call was successful and call</span>
+ <span class="c1">// the relevant callback. For the camera plugin, "OK" means a</span>
+ <span class="c1">// successful result and all other statuses mean error</span>
+ <span class="k">if</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">pendingResult</span><span class="p">.</span><span class="nx">pluginStatus</span> <span class="o">===</span> <span class="s2">"OK"</span><span class="p">)</span> <span class="p">{</span>
+ <span class="c1">// The camera plugin places the same result in the resume object</span>
+ <span class="c1">// as it passes to the success callback passed to getPicture(),</span>
+ <span class="c1">// thus we can pass it to the same callback. Other plugins may</span>
+ <span class="c1">// return something else. Consult the documentation for</span>
+ <span class="c1">// whatever plugin you are using to learn how to interpret the</span>
+ <span class="c1">// result field</span>
+ <span class="nx">cameraSuccessCallback</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">pendingResult</span><span class="p">.</span><span class="nx">result</span><span class="p">);</span>
+ <span class="p">}</span> <span class="k">else</span> <span class="p">{</span>
+ <span class="nx">cameraFailureCallback</span><span class="p">(</span><span class="nx">event</span><span class="p">.</span><span class="nx">pendingResult</span><span class="p">.</span><span class="nx">result</span><span class="p">);</span>
+ <span class="p">}</span>
<span class="p">}</span>
<span class="p">}</span>
<span class="p">}</span>
+
+<span class="c1">// Here are the callbacks we pass to getPicture()</span>
+<span class="kd">function</span> <span class="nx">cameraSuccessCallback</span><span class="p">(</span><span class="nx">imageUri</span><span class="p">)</span> <span class="p">{</span>
+ <span class="nx">appState</span><span class="p">.</span><span class="nx">takingPicture</span> <span class="o">=</span> <span class="kc">false</span><span class="p">;</span>
+ <span class="nx">appState</span><span class="p">.</span><span class="nx">imageUri</span> <span class="o">=</span> <span class="nx">imageUri</span><span class="p">;</span>
+ <span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="s2">"get-picture-result"</span><span class="p">).</span><span class="nx">src</span> <span class="o">=</span> <span class="nx">imageUri</span><span class="p">;</span>
+<span class="p">}</span>
+
+<span class="kd">function</span> <span class="nx">cameraFailureCallback</span><span class="p">(</span><span class="nx">error</span><span class="p">)</span> <span class="p">{</span>
+ <span class="nx">appState</span><span class="p">.</span><span class="nx">takingPicture</span> <span class="o">=</span> <span class="kc">false</span><span class="p">;</span>
+ <span class="nx">console</span><span class="p">.</span><span class="nx">log</span><span class="p">(</span><span class="nx">error</span><span class="p">);</span>
+<span class="p">}</span>
+
+<span class="nx">app</span><span class="p">.</span><span class="nx">initialize</span><span class="p">();</span>
</code></pre></div>
+<p>The corresponding html:</p>
+<div class="highlight"><pre><code class="language-html" data-lang="html"><span class="cp"><!DOCTYPE html></span>
+
+<span class="nt"><html></span>
+ <span class="nt"><head></span>
+ <span class="nt"><meta</span> <span class="na">http-equiv=</span><span class="s">"Content-Security-Policy"</span> <span class="na">content=</span><span class="s">"default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'; style-src 'self' 'unsafe-inline'; media-src *"</span><span class="nt">></span>
+ <span class="nt"><meta</span> <span class="na">name=</span><span class="s">"format-detection"</span> <span class="na">content=</span><span class="s">"telephone=no"</span><span class="nt">></span>
+ <span class="nt"><meta</span> <span class="na">name=</span><span class="s">"msapplication-tap-highlight"</span> <span class="na">content=</span><span class="s">"no"</span><span class="nt">></span>
+ <span class="nt"><meta</span> <span class="na">name=</span><span class="s">"viewport"</span> <span class="na">content=</span><span class="s">"user-scalable=no, initial-scale=1, maximum-scale=1, minimum-scale=1, width=device-width"</span><span class="nt">></span>
+ <span class="nt"><link</span> <span class="na">rel=</span><span class="s">"stylesheet"</span> <span class="na">type=</span><span class="s">"text/css"</span> <span class="na">href=</span><span class="s">"css/index.css"</span><span class="nt">></span>
+ <span class="nt"><title></span>Cordova Android Lifecycle Example<span class="nt"></title></span>
+ <span class="nt"></head></span>
+ <span class="nt"><body></span>
+ <span class="nt"><div</span> <span class="na">class=</span><span class="s">"app"</span><span class="nt">></span>
+ <span class="nt"><div></span>
+ <span class="nt"><img</span> <span class="na">id=</span><span class="s">"get-picture-result"</span> <span class="nt">/></span>
+ <span class="nt"></div></span>
+ <span class="nt"><Button</span> <span class="na">id=</span><span class="s">"take-picture-button"</span><span class="nt">></span>Take Picture<span class="nt"></button></span>
+ <span class="nt"></div></span>
+ <span class="nt"><script </span><span class="na">type=</span><span class="s">"text/javascript"</span> <span class="na">src=</span><span class="s">"cordova.js"</span><span class="nt">></script></span>
+ <span class="nt"><script </span><span class="na">type=</span><span class="s">"text/javascript"</span> <span class="na">src=</span><span class="s">"js/index.js"</span><span class="nt">></script></span>
+ <span class="nt"></body></span>
+<span class="nt"></html></span>
+</code></pre></div>
+<h2 id="testing-the-activity-lifecycle">Testing the Activity Lifecycle</h2>
+
+<p>Android provides a developer setting for testing Activity destruction on low
+memory. Enable the "Don't keep activities" setting in the Developer Options menu
+on your device or emulator to simulate low memory scenarios. You should always
+do some amount of testing with this setting enabled to make sure that your
+application is properly maintaining state.</p>
+
</div>
</div>
Modified: cordova/site/public/docs/en/dev/guide/platforms/android/plugin.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/dev/guide/platforms/android/plugin.html?rev=1727412&r1=1727411&r2=1727412&view=diff
==============================================================================
--- cordova/site/public/docs/en/dev/guide/platforms/android/plugin.html (original)
+++ cordova/site/public/docs/en/dev/guide/platforms/android/plugin.html Thu Jan 28 17:36:52 2016
@@ -1963,9 +1963,9 @@ Instead, this replacement CallbackContex
<div class="highlight"><pre><code class="language-text" data-lang="text">{
action: "resume",
pendingResult: {
- pluginServiceName: <name of the plugin e.g. "Camera">,
- pluginStatus: <description of the result's status>,
- result: <argument(s) that would have been given to the callback>
+ pluginServiceName: string,
+ pluginStatus: string,
+ result: any
}
}
</code></pre></div>
Modified: cordova/site/public/docs/en/dev/guide/platforms/ios/plugin.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/dev/guide/platforms/ios/plugin.html?rev=1727412&r1=1727411&r2=1727412&view=diff
==============================================================================
--- cordova/site/public/docs/en/dev/guide/platforms/ios/plugin.html (original)
+++ cordova/site/public/docs/en/dev/guide/platforms/ios/plugin.html Thu Jan 28 17:36:52 2016
@@ -1676,10 +1676,8 @@ class's <code class="prettyprint">ac
}
</code></pre></div>
<p>For more details, see
- <code class="prettyprint">[CDVInvokedUrlCommand.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVInvokedUrlCommand.h)</code>,
- <code class="prettyprint">[CDVPluginResult.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPluginResult.h)</code>,
-and
- <code class="prettyprint">[CDVCommandDelegate.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVCommandDelegate.h)</code>.</p>
+ <a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/Public/CDVInvokedUrlCommand.h">CDVInvokedUrlCommand.h</a>, <a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/Public/CDVPluginResult.h">CDVPluginResult.h</a>,
+and <a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/Public/CDVCommandDelegate.h">CDVCommandDelegate.h</a>.</p>
<h2 id="ios-cdvpluginresult-message-types">iOS CDVPluginResult Message Types</h2>
@@ -1774,10 +1772,8 @@ success callback is called, it passes in
<p>The <code class="prettyprint">CDVPlugin</code> class features other methods that your plugin can
override. For example, you can capture the <code class="prettyprint">[pause](../../../cordova/events/events.pause.html)</code>, <code class="prettyprint">[resume](../../../cordova/events/events.resume.html)</code>, app
terminate and <code class="prettyprint">handleOpenURL</code> events. See the
-<a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.h">CDVPlugin.h</a>
-and
-<a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.m">CDVPlugin.m</a>
-class for guidance.</p>
+<a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/Public/CDVPlugin.h">CDVPlugin.h</a> and <a href="https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/Public/CDVPlugin.m">CDVPlugin.m</a>
+classes for guidance.</p>
<h2 id="threading">Threading</h2>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org