Differences between revisions 41 and 42
Revision 41 as of 2014-10-09 18:29:54
Size: 7158
Revision 42 as of 2017-03-13 21:26:41
Size: 1149
Comment: Remove ancient info
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
== List of deprecated features ==
||Feature ||Deprecation Notice ||Remove By ||Issue ||
||iOS - Remove CDV_IsIPad and CDV_IsIPhone5 macros ||3.7.0 ||4.0.0 ||https://issues.apache.org/jira/browse/CB-7753 ||
||iOS - Remove CDVPlugin writeJavascript:, success:, and error: methods and CDVPluginResult toJSONString, toSuccessCallbackString: and toErrorCallbackString: methods ||3.6.0 ||4.0.0 ||https://issues.apache.org/jira/browse/CB-7000 ||
||iOS - Remove CDVWebViewDelegate::request:isFragmentIdentifierToRequest: ||3.5.0 ||3.8.0 ||https://issues.apache.org/jira/browse/CB-6637 ||

== List of deprecated and since removed features ==
||Feature ||Deprecation Notice ||Remove By ||Issue ||
||Plugman - remove support for <plugins-plist> elements ||3.1.0 ||3.4.0 ||https://issues.apache.org/jira/browse/CB-4455 and https://issues.apache.org/jira/browse/CB-4456 ||
||iOS - CDVCommandDelegate execute: method removal ||2.2.0 ||June 2014 ||https://issues.apache.org/jira/browse/CB-6998 ||
||Android - Remove Froyo Support ||2.8.0 ||July 2013 ||https://issues.apache.org/jira/browse/CB-3281 ||
||All - change <plugin> to <feature> in config.xml ||2.8.0 ||July 2013 / 3.0.0 ||https://issues.apache.org/jira/browse/CB-3172 ||
||iOS - remove CDVViewController.useSplashScreen property ||2.5.0 ||July 2013 / 3.0.0 ||https://issues.apache.org/jira/browse/CB-4145 ||
||iOS - change CDVConnection ReachableViaWWAN return from '2g' to 'cellular' ||2.6.0 ||July 2013 / 3.0.0 ||https://issues.apache.org/jira/browse/CB-2686 ||
||iOS - config.xml !EnableLocation preference removal ||2.6.0 ||July 2013 / 3.0.0 ||https://issues.apache.org/jira/browse/CB-2608 ||
||iOS - CDVURLProtocol registerPGHttpURLProtocol method removal ||2.0.0 ||Jan 2013 ||https://issues.apache.org/jira/browse/CB-2191 ||
||iOS - CDVURLProtocol registerURLProtocol method removal ||2.0.0 ||Jan 2013 ||https://issues.apache.org/jira/browse/CB-2192 ||
||iOS - CDVViewController invokeString property removal ||2.0.0 ||Jan 2013 ||https://issues.apache.org/jira/browse/CB-2193 ||
||iOS - CDVCommandDelegate registerPlugin method removal ||2.2.0 ||April 2013 ||https://issues.apache.org/jira/browse/CB-2194 ||
||iOS - !BackupWebStorage Cordova.plist property change from boolean to string ||2.2.0 ||April 2013 ||https://issues.apache.org/jira/browse/CB-2195 ||
||iOS - window.Settings (CDVDevice) ||2.5.0 ||August 2013 ||https://issues.apache.org/jira/browse/CB-2433 ||
||Android - backHistory removal ||2.2.0 ||April 2013 ||https://issues.apache.org/jira/browse/CB-2198 ||
||Android - exec() returns the success payload when the call completes synchronously ||2.2.0 ||April 2013 ||https://issues.apache.org/jira/browse/CB-2199 ||
||Android - !CordovaInterface.getContext() ||2.0.0 ||December 2012 ||https://issues.apache.org/jira/browse/CB-2196 ||
||Android - !CordovaInterface.cancelLoadUrl() ||2.0.0 ||December 2012 ||https://issues.apache.org/jira/browse/CB-2197 ||
||Android - device.name ||2.3.0 ||May 2013 ||https://issues.apache.org/jira/browse/CB-2200 ||
||Android - OS versions 2.1 and 3.x ||2.3.0 ||May 2013 ||https://issues.apache.org/jira/browse/CB-2201 ||
||Android - org.apache.cordova.api.Plugin in favour of org.apache.cordova.api.!CordovaPlugin ||2.3.0 ||May 2013 ||https://issues.apache.org/jira/browse/CB-2202 ||

== a few tips on what to do with deprecated code ==
=== Cordova Plugin Upgrade Guide ===
Cordova Plugin Upgrade Guide


=== The type "Plugin" is deprecated ===
The type "Plugin" is deprecated. So any old code (such as the code at http://docs.phonegap.com/en/2.0.0/guide_plugin-development_android_index.md.html ) that says

import org.apache.cordova.api.Plugin;
public class TestPhonegapPlugin extends Plugin {/*...*/}
will need to be updated to say

import org.apache.cordova.api.CordovaPlugin;
public class TestPhonegapPlugin extends CordovaPlugin {/*...*/}
Please also read the updated [[http://docs.phonegap.com/en/3.3.0/guide_platforms_android_plugin.md.html#Android%20Plugins|Android Plugin Guide]], since the threading details have changed.

If you want don't care about updating and just want your plugin to "work", you could drop a copy of the [[https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=blob_plain;f=framework/src/org/apache/cordova/api/Plugin.java;h=72171f2ac2d0de8c556661568f41ff2bd754fc1f;hb=df1536ea77e97b7d362a19582f8beddd168c5ec3|Plugin]] and [[https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=blob_plain;f=framework/src/org/apache/cordova/api/LegacyContext.java;h=fe154f7cff6d2f5d9d2024db34cafa354cd772aa;hb=df1536ea77e97b7d362a19582f8beddd168c5ec3|LegacyContext]] shims into your project.

== deprecation: window.addPlugin and window.plugins will be removed ==
The window.addPlugin and window.plugins will be removed.

You should switch to using cordova.require(). See http://simonmacdonald.blogspot.com/2012/08/so-you-wanna-write-phonegap-200-android.html

== deprecation: Removal of Legacy Context ==
!CordovaInterface may not be a Context object, therefore all plugins that use a context object ctx should use the new Cordova methods to access the activity to use the activities' methods

will no longer get the assets of the activity. Instead, plugin developers needing access to the activity should call getActivity, which should be implemented by the !CordovaInterface. It should be noted that if the developer is not using !DroidGap for their application, they are responsible for implementing this method and making sure the main activity is returned, and that plugin developers should be prepared for the case when the activity is null. (i.e. Lock-Screen Widgets). A working example of this method is below.


Deprecation Policy

Apache Cordova follows a MAJOR.MINOR.PATCH version schema.

  1. All public API method signatures will remain available between MAJOR releases. A signature is considered public if it is documented in the Cordova docs.
  2. All JS signatures that are slated for deprecation will have deprecation notices added via console.log to give developers sufficient warning.
  3. All native signatures will have analogue shims to maintain backward compatibility. It is recommended, if possible, these shims exist in discreet files and have a companion JIRA ticket assigned to the next MAJOR release for removal.
  4. This page is for upcoming deprecations. This policy first came into place with Android 2.0.0.
  5. On the mailing list, we adopted a 3 release deprecation policy by consensus: http://markmail.org/thread/46t6khgudddrzjcq#query:+page:1+mid:de4rmoh362bv7ckw+state:results

deprecation philosophy

All technology deprecates with time.

The ultimate purpose of PhoneGap is to cease to exist.

-- "PhoneGap Beliefs, Goals, and Philosophy" http://phonegap.com/2012/05/09/phonegap-beliefs-goals-and-philosophy/