Return-Path:
For projects that were created with the cordova CLI:
cordova
CLI version - see The Command-line Interface cordova platform update android
-Update the cordova
CLI version. See The Command-line Interface.
Run cordova platform update android
For projects not created with the cordova CLI, run:
-bin/update <project_path>
bin/update <project_path>
+
Copy any native Android assets from your res
directory to the new project.
Copy over any plugins you installed from the src
subdirectories into the new project.
Make sure to upgrade any deprecated <plugin>
references from your old config.xml
file to the new <feature>
specification.
Update any references to the org.apache.cordova.api
package to be org.apache.cordova
.
NOTE: all core APIs have been removed and must be installed as plugins. Please see the Using Plugman to Manage Plugins Guide for details.
Update any references to the org.apache.cordova.api
package to be org.apache.cordova
.
NOTE: all core APIs have been removed and must be installed as plugins. Please see the Using Plugman to Manage Plugins Guide for details.
+Remove cordova-2.7.0.jar
from the project's libs
directory.
Add cordova-2.8.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova.js
into your project.
Update your HTML to use the new cordova.js
file.
Copy the res/xml/config.xml
file to match framework/res/xml/config.xml
.
Remove cordova-2.6.0.jar
from the project's libs
directory.
Add cordova-2.7.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.7.0.js
into your project.
Update your HTML to use the new cordova-2.7.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-2.5.0.jar
from the project's libs
directory.
Add cordova-2.6.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.6.0.js
into your project.
Update your HTML to use the new cordova-2.6.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-2.4.0.jar
from the project's libs
directory.
Add cordova-2.5.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.5.0.js
into your project.
Update your HTML to use the new cordova-2.5.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-2.3.0.jar
from the project's libs
directory.
Add cordova-2.4.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.4.0.js
into your project.
Update your HTML to use the new cordova-2.4.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-2.2.0.jar
from the project's libs
directory.
Add cordova-2.3.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.3.0.js
into your project.
Update your HTML to use the new cordova-2.3.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-2.1.0.jar
from the project's libs
directory.
Add cordova-2.2.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.2.0.js
into your project.
Update your HTML to use the new cordova-2.2.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-2.0.0.jar
from the project's libs
directory.
Add cordova-2.1.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.1.0.js
into your project.
Update your HTML to use the new cordova-2.1.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
Remove cordova-1.9.0.jar
from the project's libs
directory.
Add cordova-2.0.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-2.0.0.js
into your project.
Update your HTML to use the new cordova-2.0.0.js
file.
Copy the res/xml/config.xml
to match framework/res/xml/config.xml
.
config.xml
will be replacing cordova.xml
and plugins.xml
. This
-new file is a combination of the previous two. However, the old files
-are deprecated, and while currently still work, will cease working in
-a future release.
The config.xml
file will replace cordova.xml
and plugins.xml
.
+This new file is a combination of the previous two. However, the old
+files are deprecated, and while currently still work, will cease
+working in a future release.
Remove cordova-1.8.0.jar
from the project's libs
directory.
Add cordova-1.9.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.9.0.js
into your project.
Update your HTML to use the new cordova-1.9.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove cordova-1.8.0.jar
from the project's libs
directory.
Add cordova-1.8.1.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.8.1.js
into your project.
Update your HTML to use the new cordova-1.8.1.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove cordova-1.7.0.jar
from the project's libs
directory.
Add cordova-1.8.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.8.0.js
into your project.
Update your HTML to use the new cordova-1.8.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove cordova-1.7.0.jar
from the project's libs
directory.
Add cordova-1.8.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.8.0.js
into your project.
Update your HTML to use the new cordova-1.8.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove cordova-1.6.1.jar
from the project's libs
directory.
Add cordova-1.7.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.7.0.js
into your project.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove cordova-1.6.0.jar
from the project's libs
directory.
Add cordova-1.6.1.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.6.1.js
into your project.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove cordova-1.5.0.jar
from the project's libs
directory.
Add cordova-1.6.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.6.0.js
into your project.
Update your HTML to use the new cordova-1.6.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove phonegap-1.4.0.jar
from the project's libs
directory.
Add cordova-1.5.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new cordova-1.5.0.js
into your project.
Update your HTML to use the new cordova-1.5.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove phonegap-1.3.0.jar
from the project's libs
directory.
Add phonegap-1.4.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new phonegap-1.4.0.js
into your project.
Update your HTML to use the new phonegap-1.4.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove phonegap-1.2.0.jar
from the project's libs
directory.
Add phonegap-1.3.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new phonegap-1.3.0.js
into your project.
Update your HTML to use the new phonegap-1.2.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove phonegap-1.1.0.jar
from the project's libs
directory.
Add phonegap-1.2.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new phonegap-1.2.0.js
into your project.
Update your HTML to use the new phonegap-1.2.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove phonegap-1.0.0.jar
from the project's libs
directory.
Add phonegap-1.1.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new phonegap-1.1.0.js
into your project.
Update your HTML to use the new phonegap-1.1.0.js
file.
Update res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
Remove phonegap-0.9.6.jar
from the project's libs
directory.
Add phonegap-1.0.0.jar
to the project's libs
directory.
If you are using Eclipse, please refresh your eclipse project and do a clean.
If you use Eclipse, please refresh your Eclipse project and do a clean.
Copy the new phonegap-1.0.0.js
into your project.
Update your HTML to use the new phonegap-1.0.0.js
file.
Add the res/xml/plugins.xml
to match framework/res/xml/plugins.xml
.
To deploy to a device, make sure it is plugged into your computer. Enable development mode and obtain the IP address as desribed in the -emulator section above. You will also need to obtain the PIN from the -the Settings application under About â Hardware:
+emulator section above. You also need to obtain the PIN from the +Settings application under About â Hardware: Modified: cordova/site/public/docs/en/edge/guide_platforms_blackberry10_tools.md.html URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_blackberry10_tools.md.html?rev=1539110&r1=1539109&r2=1539110&view=diff ============================================================================== --- cordova/site/public/docs/en/edge/guide_platforms_blackberry10_tools.md.html (original) +++ cordova/site/public/docs/en/edge/guide_platforms_blackberry10_tools.md.html Tue Nov 5 19:34:36 2013 @@ -181,7 +181,7 @@ arguments.<project-name>
specifies the apps display name
NOTE: the create
command bootstraps dependency installation
+
NOTE: the create
command bootstraps dependency installation
through the npm install
command. Depending on the installation
directory and system permissions, this may require administrator
privileges. If there's problem on OSX/Linux, run sudo npm install
@@ -210,7 +210,7 @@ emulator. This is required only if the d
password protected.
--pin <device-pin>
specifies the PIN of the BlackBerry device,
which identifies that device as a valid host for the debug
-token. This argument is required only if you are creating a debug
+token. This argument is required only when creating a debug
token.
error
, warn
If you have previously defined a default target (and previously
installed a debug token, if that target is a BlackBerry device), you
-can run the script with no arguments, and the script will package your
-app and deploy it to the default target. For example:
+can run the script with no arguments, and the script packages your
+app and deploys it to the default target. For example:
<path-to-project>/cordova/build debug
run
-The run
command deploys the app on the specified BlackBerry device
-or an emulator. Before deploying your app, you must first create a
-target for the device or emulator you want to deploy your app to using
-the target script. The deploy script will deploy the most recent build of your app.
+The run
command deploys the app's most recent build on the specified
+BlackBerry device or an emulator. To deploy your app, you need to
+specify a target for the device or emulator:
<path-to-project>/cordova/run <target>
-where
-
-
--
-
<target>
specifies the name of a previously added target. If
-<target>
is a device, then that device must be connected to your
-computer by USB connection or be connected to the same Wi-Fi network
-as your computer.
-
+...where <target>
specifies the name of a previously added target.
+If <target>
is a device, then it must be connected to your computer
+via USB cable, or else over the same Wi-Fi network as your computer.
plugin
Modified: cordova/site/public/docs/en/edge/guide_platforms_blackberry10_upgrading.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_blackberry10_upgrading.md.html?rev=1539110&r1=1539109&r2=1539110&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_platforms_blackberry10_upgrading.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_platforms_blackberry10_upgrading.md.html Tue Nov 5 19:34:36 2013
@@ -170,7 +170,9 @@ platform add blackberry10
.
Copy or overwrite any native assets from your original project
(Resources
, etc.)
Copy your config.xml
into the www
directory, and remove any plugin definitions. You will modify settings here instead of the platform directory.
Copy the config.xml
file into the www
directory, and remove any
+plugin definitions. You need to modify settings here rather than
+within the platform directory.
Use the cordova CLI tool to install any plugins you need. Note that the CLI handles all core APIs as plugins, so they may need to be added. Only plugins marked 3.0.0 and above are compatible with the CLI.
Copy or overwrite any native assets from your original project
(Resources
, etc.)
Copy your config.xml
into the www
directory, and remove any plugin definitions. You will modify settings here instead of the platform directory.
Copy the config.xml
file into the www
directory, and remove any
+plugin definitions. You need to modify settings here rather than
+within the platform directory.
Use the cordova CLI tool to install any plugins you need. Note that the CLI handles all core APIs as plugins, so they may need to be added. Only 3.0.0 plugins are compatible with the CLI.
If you are prompted whether a device is connected to your computer, answer no.
-NOTE: On BlackBerry OS 5, the application is installed in the +
NOTE: On BlackBerry OS 5, the application is installed in the
Downloads
directory.
NOTE: On BlackBerry OS 5, the application is installed in the +
NOTE: On BlackBerry OS 5, the application is installed in the
Downloads
directory.
NOTE: The BlackBerry platform ignores the package name placeholder +
NOTE: The BlackBerry platform ignores the package name placeholder
(com.example.project_name
), but it's still required for use by
cross-platform tools.
Deprecation Warnings: When an application programming interface +
Deprecation Warnings: When an application programming interface
(API) is changed or replaced by another API, it is marked as
deprecated. The API still works in the near term, but is eventually
removed. Some of these deprecated interfaces are reflected in Apache
Modified: cordova/site/public/docs/en/edge/guide_platforms_ios_upgrading.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_ios_upgrading.md.html?rev=1539110&r1=1539109&r2=1539110&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_platforms_ios_upgrading.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_platforms_ios_upgrading.md.html Tue Nov 5 19:34:36 2013
@@ -171,7 +171,7 @@ created with an older set of command-lin
cordova
CLI utility. See The Command-line Interface for information
how to update the version of the CLI.
NOTE: Xcode 4.6 is required, Xcode 5 is recommended. Currently, to submit to the +
NOTE: Xcode 4.6 is required, Xcode 5 is recommended. Currently, to submit to the Apple App Store, you should use the latest shipped version of the iOS SDK, which is iOS 7. iOS 7 SDK is not required yet, but this may change quickly.
@@ -182,25 +182,31 @@ iOS 7 SDK is not required yet, but this bin/update path/to/project
-For CLI projects, run:
+For CLI projects:
- 1. Update the `cordova` CLI version - see The Command-line Interface
- 2. Run `cordova platform update ios`
-
+Update the cordova
CLI version. See The Command-line Interface.
Run cordova platform update ios
1. Remove the values "width=device-width, height=device-height" from your meta tag
-"viewport" attribute in your index.html file, see https://issues.apache.org/jira/browse/CB-4323
-2. Update your media, media-capture and splashscreen core plugins for iOS 7 support
-
+Remove width=device-width, height=device-height
from the
+index.html
file's viewport
meta
tag. (See the relevent
+bug.)
Update your media, media-capture and splashscreen core plugins for +iOS 7 support.
1. Update your Project Settings if Xcode 5 prompts you to do so (in the Issues Navigator)
-2. Update your "Compiler for C/C++/Objective-C" setting, under the "Build Settings"
-tab, "Build Options" section. Choose "Default compiler (Apple LLVM 5.0)"
-
+Update your Project Settings if Xcode 5 prompts you to do so (in the Issues Navigator).
Update your Compiler for C/C++/Objective-C setting, under the +Build Settings tab, Build Options section. Choose Default +compiler (Apple LLVM 5.0).
Delete your CordovaLib
directory, and copy the CordovaLib
directory from the new project into your project's root directory.
NOTE: Starting with Cordova 3.0.0, projects do not come with any
-plugins, you will have to install the ones you require for your
-project using the plugman
command-line utility. See Using Plugman to
-Manage Plugins.
NOTE: Starting with Cordova 3.0.0, plugins are not pre-installed,
+and you need to use the plugman
command-line utility to install them
+yourself. See Using Plugman to Manage Plugins.
Copy the www/cordova.js
(note that it does not have a version suffix anymore, the version is in the file itself in the header) file from the new project into your www
directory, and delete your www/cordova-2.7.0.js
file.
Update the Cordova script reference in your www/index.html
file (and any other files that contain the script reference) to point to the new cordova.js
file.
Update any <plugin>
tags that are in your config.xml
to <feature>
tags. Note that existing <plugin>
tags will still work, but are deprecated. You can copy this information in the config.xml
for a new project. For example:
Update any <plugin>
tags in the config.xml
file to <feature>
tags. Note that existing <plugin>
tags still work, but are deprecated. You can copy this information in the config.xml
file for a new project. For example:
<plugins>
<plugin name="LocalStorage" value="CDVLocalStorage" />
@@ -277,7 +282,7 @@ Manage Plugins.
<!-- other <feature> tags -->
Delete your CordovaLib
directory, and copy the CordovaLib
directory from the new project into your project's root directory.
Delete the CordovaLib
directory, and copy the CordovaLib
directory from the new project into your project's root directory.
Add these two frameworks to your project:
@@ -351,7 +356,7 @@ ImageIOIn your config.xml
file, add this new line.
Delete your cordova
directory, and copy the cordova
directory from the new project into your project's root directory. In 2.4.0, this has fixed scripts.
Delete your CordovaLib
directory, and copy the CordovaLib
directory from the new project into your project's root directory.
Add AssetsLibrary.framework as a resource to your project. (Go here for instructions on how to do so.).
Add AssetsLibrary.framework as a resource to your project. (See Apple's documentation for instructions on how to do so.).
<plugin name="InAppBrowser" value="CDVInAppBrowser" />
-Note that Objective-C plugins are not whitelisted anymore. To whitelist your connections with the app whitelist, you will need to set the User-Agent
header of the connection to the same user-agent as the main Cordova WebView.
-You can get this by accessing the userAgent
property off the main view-controller. The main view-controller (CDVViewController) also has a URLisAllowed
method for you to check whether a URL will pass the whitelist.
Note that Objective-C plugins are not whitelisted anymore. To whitelist your connections with the app whitelist, you need to set the User-Agent
header of the connection to the same user-agent as the main Cordova WebView.
+You can get this by accessing the userAgent
property off the main view-controller. The main view-controller (CDVViewController
) also has a URLisAllowed
method for you to check whether a URL passes the whitelist.
Device API changes:
@@ -418,7 +423,7 @@ You can get this by accessing the
NOTE: In 2.2.0, the bin/create
script copy in the CordovaLib
sub-project into your project. To have the same kind of setup, just copy in the right CordovaLib
into your project directory, and update the CordovaLib
sub-project location (relative to the project) in the Xcode File Inspector.
NOTE: In 2.2.0, the bin/create
script copy in the CordovaLib
sub-project into your project. To have the same kind of setup, just copy in the right CordovaLib
into your project directory, and update the CordovaLib
sub-project location (relative to the project) in the Xcode File Inspector.
CDVDevice
.
Select the Run button.
NOTE: If your project is not working as expected in the Simulator, please take a note of any errors in the console log in Xcode for clues.
+NOTE: If your project is not working as expected in the Simulator, please take a note of any errors in the console log in Xcode for clues.
CDVDevice
.
Update the Cordova script reference in your www/index.html
file (and any other files that contain the script reference) to point to the new cordova-1.9.0.js
file.
NOTE: 1.9.0 supports the new BackupWebStorage
boolean Cordova.plist
setting. It's enabled by default, so set it to
+
NOTE: 1.9.0 supports the new BackupWebStorage
boolean Cordova.plist
setting. It's enabled by default, so set it to
false
to disable it, especially on iOS 6. See Release Notes: Safari and UIKit Section
cordova-js
).
Integrate any settings, Plugins and ExternalHosts entries that you had in your backed-up Cordova.plist into the new Cordova.plist
.
Integrate any project-specific code that you have in your backed-up AppDelegate.h
and AppDelegate.m
into the new AppDelegate files. Any UIWebViewDelegate
or CDVCommandDelegate
code in AppDelegate.m
will need to go into MainViewController.m
now (see commented out sections in that file).
Integrate any project-specific code that you have in your backed-up AppDelegate.h
and AppDelegate.m
into the new AppDelegate
files. Any UIWebViewDelegate
or CDVCommandDelegate
code in AppDelegate.m
needs to go into MainViewController.m
now (see commented-out sections in that file).
Integrate any project-specific code that you have in your backed-up MainViewController.h
and MainViewController.m
into the new MainViewController files.
Click on the project icon in the Project Navigator, select your Project, then select the Build Settings tab.
Enter Compiler for C/C++/Objective-C in the search field.
cordova-js
for the Replace string, then press the Replace All button.
Enter PG for the Find string, and CDV for the Replace string, then press the Replace All button.
Press Command-B to build, you will still have deprecations +
Press Command-B to build. You still have deprecations
that you can get rid of in the future (see CDVDeprecated.h
. For
example, replace classes in your code that use PG* to CDV*).
NOTE: Running the SDK in Virtual Machine may present challenges. +
NOTE: Running the SDK in Virtual Machine may present challenges. Read Windows Phone on a Mac for insights on developing solutions.
@@ -187,7 +187,7 @@ insights on developing solutions. SDK.Download and extract the latest copy of
-Cordova. You will be working in the
+Cordova. You need to work in the
lib\windows-phone-8\wp7
subdirectory, lib\windows-phone-8\wp8
contains the Windwos Phone 8 version of Cordova.
NOTE: Skip this step if the lib\windows-phone
directory already
+
NOTE: Skip this step if the lib\windows-phone
directory already
contains a CordovaWP7_x_x_x.zip
file.
To simplify development, Cordova bundles a script to build Visual @@ -248,7 +248,7 @@ vary depending on installed version:
Before testing your application on a device, the device must be registered. Consult -[Microsoft's documentation][http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx] +Microsoft's documentation.aspx) for details on how to deploy and test on Windows Phone 7. These are the basic steps:
Modified: cordova/site/public/docs/en/edge/guide_platforms_wp8_index.md.html URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_wp8_index.md.html?rev=1539110&r1=1539109&r2=1539110&view=diff ============================================================================== --- cordova/site/public/docs/en/edge/guide_platforms_wp8_index.md.html (original) +++ cordova/site/public/docs/en/edge/guide_platforms_wp8_index.md.html Tue Nov 5 19:34:36 2013 @@ -220,7 +220,7 @@ current interface.Register and pay for a Windows Phone Dev Center account if you want to install your app on a real device or submit it to Market Place.
NOTE: Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for Windows Phone on a Mac.
+NOTE: Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for Windows Phone on a Mac.
Download and extract the latest copy of
Cordova. The lib\windows-phone-8\wp8
-subdirectory is where you will do your work.
Copy the CordovaWP8_x_x_x.zip
file to the \My Documents\Visual
Studio 2012\Templates\ProjectTemplates\
directory.
NOTE: Skip this step if the lib\windows-phone
directory already
+
NOTE: Skip this step if the lib\windows-phone
directory already
contains a CordovaWP8_x_x_x.zip
file.
To simplify development, Cordova bundles a script to build Visual @@ -298,7 +298,7 @@ start debugging, or type F5Before testing your application on a device, the device must be registered. Consult -[Microsoft's documentation][http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx] +Microsoft's documentation.aspx) for details on how to deploy and test on Windows Phone 8. These are the basic steps:
Modified: cordova/site/public/docs/en/edge/guide_platforms_wp8_tools.md.html URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_wp8_tools.md.html?rev=1539110&r1=1539109&r2=1539110&view=diff ============================================================================== --- cordova/site/public/docs/en/edge/guide_platforms_wp8_tools.md.html (original) +++ cordova/site/public/docs/en/edge/guide_platforms_wp8_tools.md.html Tue Nov 5 19:34:36 2013 @@ -177,8 +177,14 @@ repo has subdirectories for each:
Run the batch file to create and install the templates.
-The root of the repo contains a file createTemplates.bat. Double clicking this file will generate 2 .zip files. (CordovaWP7xxx.zip + CordovaWP8xxx.zip where x.x.x is the current version number) To easily use these files in Visual Studio, copy them to
-"My Documents\Visual Studio 2012\Templates\ProjectTemplates\" You will then be able to create new Apache Cordova Windows Phone apps from the Visual Studio File->New Project menu.
+The root of the repo contains a createTemplates.bat
file.
+Double-clicking it generates two .zip
files:
+CordovaWP7_x_x_x.zip
and CordovaWP8_x_x_x.zip
, where x.x.x
+represents the current version number. To easily use these files in
+Visual Studio, copy them to My Documents\Visual Studio
+2012\Templates\ProjectTemplates\
. You are then able to create
+new Apache Cordova Windows Phone apps from Visual Studio's
+File â New Project menu.
If you run the batch file from the command line, you can also call with a parameter to install automatically
@@ -237,7 +243,7 @@ name. Here is the syntax for both Windo
-By default the run
command will be called with --emulator --debug
if flags are not provided.
+By default the run
command is called with --emulator --debug
if flags are not provided.
Cleaning
Modified: cordova/site/public/docs/en/edge/guide_platforms_wp8_upgrading.md.html
URL: http://svn.apache.org/viewvc/cordova/site/public/docs/en/edge/guide_platforms_wp8_upgrading.md.html?rev=1539110&r1=1539109&r2=1539110&view=diff
==============================================================================
--- cordova/site/public/docs/en/edge/guide_platforms_wp8_upgrading.md.html (original)
+++ cordova/site/public/docs/en/edge/guide_platforms_wp8_upgrading.md.html Tue Nov 5 19:34:36 2013
@@ -177,15 +177,14 @@ projects.
For projects that were created with the cordova CLI:
-- Update the
cordova
CLI version - see The Command-line Interface
-- Run
cordova platform update wp8
(or wp7
, per the platforms you added to your project).
+Update the cordova
CLI version. See The Command-line Interface.
+Run cordova platform update wp8
(or wp7
, per the platforms you added to your project).
For projects not created with the cordova CLI, run:
-
-bin\update <project_path>
-
+ bin\update <project_path>
+
Upgrade to the CLI (3.0.0) from 2.9.0
@@ -218,7 +217,7 @@ added. Only 3.0.0 plugins are compatible
Build and test.
NOTE: all core APIs are removed from Cordova version 3.0, and must +
NOTE: all core APIs are removed from Cordova version 3.0, and must be installed separately as plugins. For more information on how to re-enable these features in a non-CLI workflow, see Using Plugman to Manage Plugins.
@@ -366,10 +365,7 @@ Manage Plugins.Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.9.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.9.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.8.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.8.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.7.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.7.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.6.1.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.6.1.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.6.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.6.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.5.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.5.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.4.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.4.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.3.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.3.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: You can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.2.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.2.0.js
file.
Navigate to the new distribution and add the WP7CordovaClassLib.dll
file.
NOTE: you can view the DLL's version by right-clicking on the reference, and selecting Properties.
Copy the new cordova-1.1.0.js
into your project. (Be sure it is marked as Content.)
Update your HTML to use the new cordova-1.1.0.js
file.
The <dependency>
tag allows you specify other plugins on which the
+
The <dependency>
tag allows you to specify other plugins on which the
current plugin depends. While future versions will access them from
plugin repositories, in the short term plugins are directly referenced
as URLs by <dependency>
tags. They are formatted as follows:
src
(required):
Location of the file relative to plugin.xml
. If the src
file
-cannot be found, plugman stops and reverses the installation, issues
+can't be found, plugman stops and reverses the installation, issues
a notification about the problem, and exits with a non-zero code.
target-dir
:
@@ -705,7 +705,7 @@ Examples:
src
(required):
The location of the file relative to plugin.xml
.
-If src
cannot be found, plugman stops and reverses the
+If src
can't be found, plugman stops and reverses the
installation, issues a warning about the problem, and exits with a
non-zero code.
arch
: The architecture for which the .so
file has been built,