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 2013/06/08 01:07:16 UTC
[03/22] removed 2.8.0rc1 code due to issue
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/getting-started/symbian/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/getting-started/symbian/index.md b/docs/en/2.8.0rc1/guide/getting-started/symbian/index.md
deleted file mode 100644
index d73ad92..0000000
--- a/docs/en/2.8.0rc1/guide/getting-started/symbian/index.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Getting Started with Symbian
-============================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-Video Tutorials:
-----------------
-
-- [Cordova Installer - Xcode 4 Template](http://www.youtube.com/v/R9zktJUN7AI?autoplay=1)
-
-
-1. Requirements
----------------
-
-- Windows, OS X, or Linux
-
-There are also [QT for Symbian](http://wiki.phonegap.com/w/page/16494811/PhoneGap-Symbian-%28Qt%29) and [Symbian with Sony Ericsson](http://wiki.phonegap.com/w/page/16494782/Getting-Started-with-PhoneGap-Symbian-(WRT-on-Sony-Ericsson)) guides.
-
-
-2. Install SDK + Cordova
--------------------------
-
-- Download and install [cygwin](http://www.cygwin.com/setup.exe) (Windows only). Make sure you select "make" as it is not included by default
-- Download the latest copy of [Cordova](http://phonegap.com/download) and extract its contents. We will be working with the Android directory.
-
-
-3. Setup New Project
---------------------
-
-- In cygwin, navigate to where you extracted Cordova and go into the Symbian directory</li>
-
-
-4. Hello World
---------------
-
-- Open up index.html located in phonegap/symbian/framework/www with your favourite editor.
-- In the `body` tag, remove the line `"Build your phonegap app here! Dude!"` and add the line `<h1>Hello World</h1>`
-- In cygwin/terminal, type make. This will produce phonegap-symbian.wrt/app.wgz.
-
-
-5A. Deploy to Simulator
------------------------
-
-- For Mac or Linux you should install [Aptana Studio](http://www.aptana.org/products/studio2/download) and [Nokia WRT Plug-in for Aptana Studio](http://www.forum.nokia.com/info/sw.nokia.com/id/00d62bd8-4214-4c86-b608-5f11b94dad54/Nokia_WRT_Plug_in_for_Aptana_Studio.html). This has a browser-based javascript emulator
-- For Windows you can download the [S60 SDK](http://www.forum.nokia.com/info/sw.nokia.com/id/ec866fab-4b76-49f6-b5a5-af0631419e9c/S60_All_in_One_SDKs.html) which includes the S60 Emulator
-- Load the phonegap-symbian.wrt/app.wgz file into the emulator.
-
-
-5B. Deploy to Device
---------------------
-
-- Load the phonegap-symbian.wrt/app.wgz file into the device using bluetooth or email.
-
-
-Done!
------
-
-You can also checkout more detailed version of this guide [here](http://wiki.phonegap.com/w/page/16494780/Getting-Started-with-Phonegap-Nokia-WRT).
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/getting-started/tizen/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/getting-started/tizen/index.md b/docs/en/2.8.0rc1/guide/getting-started/tizen/index.md
deleted file mode 100644
index a45895e..0000000
--- a/docs/en/2.8.0rc1/guide/getting-started/tizen/index.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Getting Started with Tizen
-=========================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-1. Requirements
----------------
-
-- Linux Ubuntu 10.04/10.10/11.04/11.10 32-bit, Windows XP SP3/7 32-bit.
-
-2. Install SDK + Cordova
--------------------------
-
-- Download and install the [Tizen SDK](https://developer.tizen.org/sdk).
-- Download the latest copy of [Cordova](http://phonegap.com/download) and extract its contents. We will be working with the tizen directory.
-- (optional) Install Tizen Cordova template projects: copy the `/templates` directory content into you Tizen Eclipse IDE web templates directory (e.g: `/home/my_username/tizen-sdk/IDE/Templates/web`).
-
-3. Setup New Project
---------------------
-
-- **Method #1: Import a Cordova Tizen project sample**
- - Launch Tizen Eclipse IDE
- - Select **File** -> **Import** -> **Tizen Web Project**
-
- 
-
- - Click **Next**
- - Make sure that **Select root directory** is checked
- - Make sure **Copy projects into workspace** is checked
- - Click **Browse**
- - Browse to one of the Cordova Tizen "samples" project directory (e.g: `/cordova-basic`) and select it
-
- 
-
- - Click **Finish**
-
- 
-
- - Your project should now have been imported and appear **Project Explorer** view
-
-- **Method #2: Use Tizen Eclipse IDE Cordova Tizen project templates**
- - Launch Tizen Eclipse IDE
- - Select **File** -> **New** -> **Tizen Web Project**
- - Select **User Template** and **User defined** items
- - Select one of the Tizen Cordova template (e.g: **CordovaBasicTemplate**)
- - Fill-up the **Project name** and its target **Location**
-
- 
-
- - Click **Finish**
-
- 
-
- - Your project should now have been created and appear **Project Explorer** view
-
-4. Hello World
---------------
-- To build your project:
-
- - **Right Click** your project in the **Project Explorer** view and Select **Build Project**
-
- 
-
- - A widget package should have been generated in your project root directory (e.g: `cordova-basic.wgt`)
-
- - **Note** that the provided samples Tizen Cordova projects are not basic hello world applications. They contain a simple example usage of the Battery Cordova API.
-
-
-5A. Deploy to Simulator
------------------------
-
-- **Right Click** your project in the **Project Explorer** view and Select **Run As** and **Tizen Web Simulator Application**
-
- 
-
-5B. Deploy to Device/Emulator
---------------------
-
-- Make sure that your target device is properly launched/connected/configured ("Date and Time" settings must have been set correctly)
-- Select your application deployment target with the **Connection Explorer** view (Select **Window** Menu -> **Show View** -> **Connection Explorer** )
-
- 
-
-- **Right Click** your project in the **Project Explorer** view and Select **Run As** and **Tizen Web Application**
-
- 
-
-Done!
------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/getting-started/webos/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/getting-started/webos/index.md b/docs/en/2.8.0rc1/guide/getting-started/webos/index.md
deleted file mode 100644
index 37ab244..0000000
--- a/docs/en/2.8.0rc1/guide/getting-started/webos/index.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Getting Started with WebOS
-==========================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-Video Tutorials:
-----------------
-
-- [Cordova and HP Palm webOS quick start video](http://www.youtube.com/v/XEnAUbDRZfw?autoplay=1)
-- [How to convert iPhone app to a Palm](http://www.youtube.com/v/wWoJfQw79XI?autoplay=1)
-
-
-1. Requirements
----------------
-
-- Windows, OS X, or Linux
-
-
-2. Install SDK + Cordova
-----------------------------
-
-- Download and install [Virtual Box](http://www.virtualbox.org/)
-- Download and install [WebOS SDK](http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788&Itemid=321/)
-- Download and install [cygwin SDK](http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788&Itemid=321) (Windows only). Make sure you select "make" as it is not included by default
-- Download the latest copy of [Cordova](http://phonegap.com/download) and extract its contents. We will be working with the webOS directory.
-- Download and install XCode from the [Mac App Store](http://itunes.apple.com/ca/app/xcode/id497799835?mt=12) (OSX only)
-- Download and install Command Line Tools for XCode (OSX only); this can be done by going to XCode's Preferences -> Downloads -> Components and then click install on Command Line Tools
-
-
-3. Setup New Project
---------------------
-
-- Open up terminal/cygwin and navigate to where you extracted your Cordova Download. Go into the webOS directory.
-
-
-4. Hello World
---------------
-
-In phonegap/webOS/framework/www, open up index.html with your favourite editor. After the body tag add `<h1>Hello World</h1>`
-
-
-5A. Deploy to Simulator
------------------------
-
-- Open up your Palm Emulator from your applications folder/start menu.
-- Type `make` in your terminal/cygwin while in the webOS directory.
-
-
-5B. Deploy to Device
---------------------
-
-- Make sure your device is in [Developer Mode and plug it in.](http://developer.palm.com/index.php?option=com_content&view=article&id=1552&Itemid=59#dev_mode)
-- Type `make` in your terminal/cygwin while in the webOS directory.
-
-
-Done!
------
-
-You can also checkout more detailed version of this guide [here](http://wiki.phonegap.com/w/page/16494781/Getting-Started-with-PhoneGap-webOS).
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/getting-started/windows-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/getting-started/windows-8/index.md b/docs/en/2.8.0rc1/guide/getting-started/windows-8/index.md
deleted file mode 100644
index 1c2a6ad..0000000
--- a/docs/en/2.8.0rc1/guide/getting-started/windows-8/index.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Getting Started with Windows 8
-==================================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-During development of Windows 8 and Windows RT, Microsoft deprecated the name "Metro-style apps". On MSDN, this type of app is now called a "Windows Store" app. That's the name that we'll use in this guide. Also in this guide whenever we refer to Windows 8, you should take that to mean both Windows 8 and Windows RT.
-
-1. Requirements
----------------
-
-- Windows 8
-
-- Visual Studio 2012 Professional or better, or Visual Studio 2012 Express for Windows 8
-
-Follow the instructions [here](http://www.windowsstore.com/) to submit your apps Windows Store.
-
-2. Install SDK + Cordova
-----------------------------
-
-- Setup your preferred variant of Visual Studio 2012. All of the paid versions of the product (Professional, etc) let you build Windows Store apps. To build Windows Store apps using the [Express editions](http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products), you will need **Express for Windows 8**.
-- Download the latest copy of [Cordova](http://phonegap.com/download) and extract its contents. We will be working with the subfolder **lib\windows-8**.
-
-3. Setup New Project
---------------------
-
-You can already build Windows 8 apps using the "HTML/JavaScript track" available in Windows Store apps. The purpose of Cordova in Windows Store apps is to expose the same APIs used on all the other Cordova platforms.
-
-- Open Visual Studio 2012 and choose **New Project**.
-- Select **Installed - Template - Other Languages - JavaScript - Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like. We're using **CordovaWin8Foo** in this guide.
-
- 
-
-- Microsoft continues to use **default.html** as the default page for use in websites, whereas most "open web" developers use **index.html**. (Plus it's likely that in the other platform variants of your project you are using **index.html** as the name of your default page.) To fix this, in Solution Explorer rename the **default.html** file to **index.html**. Then double-click the **package.appxmanifest** file and change the **Start page** value to **index.html**.
-
- 
-
-- To include **cordova.js** in your project, right-click on the **js** folder in Solution Explorer and select **Add - New Item**. Locate the **cordova.js** file in the **lib\windows-8** folder that we called out previously.
-
-- Edit the code for **index.html**. Add a reference to **cordova.js**. You can do this manually, or by dragging the file from Solution Explorer.
-
-### Adding the reference...
- <!-- WinJS references -->
- <link href="//Microsoft.WinJS.1.0/css/ui-dark.css" rel="stylesheet" />
- <script src="//Microsoft.WinJS.1.0/js/base.js"></script>
- <script src="//Microsoft.WinJS.1.0/js/ui.js"></script>
-
- <!-- Cordova -->
- <script src="/js/cordova.js"></script>
-
- <!-- CordovaWin8Foo references -->
- <link href="/css/default.css" rel="stylesheet" />
- <script src="/js/default.js"></script>
-
-- Next we want to add some code that will demonstrate that Cordova is working.
-
-### Adding a 'deviceready' handler...
- <body>
- <p>Content goes here</p>
-
- <script type="text/javascript">
-
- console.log("Subscribing...");
- document.addEventListener("deviceready", function () {
-
- navigator.notification.alert("The device is ready!");
-
- });
-
- </script>
-
- </body>
-
-
-5. Test the Project
--------------------------------
-
-- Run the project from Visual Studio. You'll see the message box appear.
-
- 
-
-Done!
------
-
-That's it! You're now ready to build Windows Store apps with Cordova.
-
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/getting-started/windows-phone-7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/getting-started/windows-phone-7/index.md b/docs/en/2.8.0rc1/guide/getting-started/windows-phone-7/index.md
deleted file mode 100644
index 3a8f81f..0000000
--- a/docs/en/2.8.0rc1/guide/getting-started/windows-phone-7/index.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Getting Started with Windows Phone 7
-==================================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-Video Tutorials:
-----------------
-
-- [Cordova and Windows Phone quick setup video](http://www.youtube.com/v/wO9xdRcNHIM?autoplay=1)
-- [Cordova and Windows Phone deep dive](http://www.youtube.com/v/BJFX1GRUXj8?autoplay=1)
-
-
-1. Requirements
----------------
-
-- Windows 7, Windows 8 or Windows Vista with SP2
-
-Note: Running in VM has issues, if you are on a Mac, you will need to setup a bootcamp partition with Windows 7 or Vista
-
-Necessary for Installing on Device and Submitting to Market Place:
-
-- Become an [App Hub member](http://create.msdn.com/en-US/home/membership).
-
-
-2. Install SDK + Cordova
-----------------------------
-
-- Download and install [Windows Phone SDK](http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27570/)
-- Download the latest copy of [Cordova](http://phonegap.com/download) and extract its contents. We will be working with the subfolder: lib\windows-phone\
-- copy the file CordovaWP7_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates
-( if the template file does not exist, you will need to build it. See 2.1 below )
-if you have just installed VisualStudio, you should launch it once to create this folder
-if you prefer, you may add the project instead to the "Silverlight for Windows Phone" subfolder of "Visual C#". This is up to you, and only affects where the project template is shown when creating a new project. Also, You may need to create this folder.
-
-
-2.1. Building the template
------------------------------
-( note, this step may not be required. If the lib\windows-phone directory already contains a file CordovaWP7_x_x_x.zip then you may skip this step )
-- Open the file lib\windows-phone\templates\standalone\CordovaSolution.sln in Visual Studio Express for Windows Phone
-- From the file menu, select 'Export Template...'
-- Choose template type 'Project template'
-- Give the exported template a name, ex. CordovaStarter-2.1.0 will produce CordovaStarter-2.1.0.zip
-- Optionally, you may add a description, icon image, and Preview image. These are what is displayed in Visual Studio in the 'New Project' dialog.-
-- Note: If you select ( 'Automatically import the template ... ') then you will not need to copy the .zip file over as outlined in step 2.
-- Press 'Finish'
-
-
-
-
-3. Setup New Project
---------------------
-
-- Open Visual Studio Express for Windows Phone and choose **New Project**.
-- Select **CordovaStarter**. ( the version number will be displayed in the template description )
-- - note: If you do not see it, you may have to select the top level 'Visual C#' to see it
-- Give your project a name, and select OK.
-
- 
-
-
-4. Review the project structure
--------------------------------
-
-- The 'www' folder contains your Cordova html/js/css and any other resources included in your app.
-- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
-
- 
-
-
-5. Build and Deploy to Emulator
--------------------------------
-
-- Make sure to have **Windows Phone Emulator** selected in the top drop-down menu.
-- Hit the green **play button** beside the Windows Phone Emulator drop-down menu to start debugging or press F5.
-
- 
- 
-
-
-6. Build your project for the device
-------------------------------------
-
-In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone.
-
-- Make sure your phone is connected, and the screen is unlocked
-- In Visual Studio, select 'Windows Phone Device' from the top drop-down menu.
-- Hit the green **play button** beside the drop-down menu to start debugging or press F5.
-
- 
-
-
-Done!
------
-
-You can also checkout more detailed version of this guide [here](http://wiki.phonegap.com/w/page/48672055/Getting%20Started%20with%20PhoneGap%20Windows%20Phone%207).
-
-[register-url]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/getting-started/windows-phone-8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/getting-started/windows-phone-8/index.md b/docs/en/2.8.0rc1/guide/getting-started/windows-phone-8/index.md
deleted file mode 100644
index e69c7aa..0000000
--- a/docs/en/2.8.0rc1/guide/getting-started/windows-phone-8/index.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Getting Started with Windows Phone 8
-==================================
-
-This guide describes how to set up your development environment for Cordova and run a sample application. Note that Cordova used to be called PhoneGap, so some of the sites still use the old PhoneGap name.
-
-Note: Applications built with Apache Cordova for Windows Phone 8 will only run on Windows Phone 8 devices. If you are looking to target both 7.5 AND 8 devices, then you should be using Apache Cordova for Windows Phone 7, which does not have all the new shiny features included in IE10, but implements the same APIs.
-
-1. System Requirements
----------------
-
-- Operating System:
- - Windows 8 or Windows 8 Pro
- - The 64-bit version (x64) of Windows is required for the SDK.
- - The Pro version is recommended so you can run a device emulator.
-
-- Hardware:
- - 6.5 GB of free hard disk space
- - 4 GB RAM
- - 64-bit (x64) CPU
-
-- Windows Phone 8 Emulator
- - The phone emulator uses Hyper-V, so this list includes those pre-reqs.
- - Windows 8 Pro 64-bit edition or greater
- - Requires a processor that supports virtualization and [Second Level Address Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation)
- - See the [list of Intel processors that support VT-x (virtualization) and EPT (SLAT)](http://ark.intel.com/Products/VirtualizationTechnology)
- - Enable the virtualization capability (i.e., VT-x on Intel) in your BIOS settings, as usually this is disabled by default.
-
-- SDK + IDE ( Visual Studio )
- - Visual Studio 2012 Professional, Premium, or Ultimate. Note that Visual Studio Express for Windows Phone (included in the SDK) is not recommended because you can not build the template (see below) with VS Express, as it does not have the "Export Template" functionality, which is only in VS Pro or higher.
-
-- Register and pay for a [Windows Phone Dev Center](http://dev.windowsphone.com/en-us/publish) account if you want to install your app on a real device and/or submit it to Market Place.
-
-Note: Running the SDK in Virtual Machine might present some challenges. You can read this blog post that gives insight on the solutions to develop for [Windows Phone on a Mac](http://aka.ms/BuildaWP8apponaMac).
-
-
-2. Install SDK + Cordova
-----------------------------
-
-- Download and install [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
-- Download the latest copy of [Cordova](http://phonegap.com/download) and extract its contents. We will be working with the subfolder: lib\windows-phone-8\
-- copy the file CordovaWP8_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
-
-
-2.1. Building the template
------------------------------
-Note: this step may not be required. If the lib\windows-phone directory already contains a file CordovaWP8_x_x_x.zip then you may skip this step.
-
-In order to simplify the development process, Cordova comes with a Visual Studio template that allows creating a Cordova application rapidly. This template can be modified if needed and the below steps indicate how to proceed if you want to modify and re-generate the template.
-
-- Open the file lib\windows-phone\templates\standalone\CordovaSolution.sln in Visual Studio Express for Windows Phone
-- From the file menu, select 'Export Template...'
-- Choose template type 'Project template'
-- Give the exported template a name, ex. CordovaStarter-2.1.0 will produce CordovaStarter-2.1.0.zip
-- Optionally, you may add a description, icon image, and Preview image. These are what is displayed in Visual Studio in the 'New Project' dialog.-
-- Note: If you select ( 'Automatically import the template ... ') then you will not need to copy the .zip file over as outlined in step 2.
-- Press 'Finish'
-
-
-2.2 About the template
---------------------
-Apache Cordova for Windows Phone 8 has moved to only supporting the standalone template.
-
-The 'Stand-Alone' template includes ALL the source code for Apache Cordova. This project is easier to fine-tune to use just the features you need, thereby working around the permissions issues of using the dll. In order to exclude an API (Plugin) you are not using, you can simply right-click-select the Command class file in Visual Studio and choose 'do not include in project'.
-
-
-3. Setup New Project
---------------------
-
-- Open Visual Studio Express for Windows Phone and choose **New Project**.
-- Select **CordovaWP8**. ( the version number will be displayed in the template description )
-- Give your project a name, and select OK.
-
-
-
-
-4. Review the project structure
--------------------------------
-
-- The 'www' folder contains your Cordova html/js/css and any other resources included in your app.
-- Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
-
-
-
-
-5. Build and Deploy to Emulator
--------------------------------
-
-- Make sure to have **Windows Phone Emulator** selected in the top drop-down menu.
-- Hit the green **play button** beside the Windows Phone Emulator drop-down menu to start debugging or press F5.
-
-
-
-
-6. Build your project for the device
-------------------------------------
-
-In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 8.
-
-- Make sure your phone is connected, and the screen is unlocked
-- In Visual Studio, select 'Device' from the top drop-down menu.
-- Hit the green **play button** beside the drop-down menu to start debugging or press F5.
-
-
-
-
-Done!
------
-
-Further Reading
--------
-
-For more details on the specific differences between IE10 and WebKit browsers, and how to support both MS has a helpful [guide here](http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx)
-
-[register-url]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565(v=vs.105).aspx
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/android/index.md b/docs/en/2.8.0rc1/guide/plugin-development/android/index.md
deleted file mode 100644
index e262c8a..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/android/index.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-# Developing a Plugin on Android
-
-Writing a plugin requires an understanding of the architecture of Cordova-Android. Cordova-Android consists
-of an Android WebView with hooks attached to it. These plugins are represented as class mappings in the config.xml
-file.
-
-A plugin will consist of at least a single Java class that extends the `CordovaPlugin` class. A plugin must override one
-of the `execute` methods from `CordovaPlugin`. In addition to this, there is a best practice that
-the plugin should handle pause and resume events, and should handle message passing between plugins.
-Plugins with long-running requests, background activity (e.g. playing media), listeners or internal state should implement the `onReset()` method as well. This method is run when the `WebView` navigates to a new page or refreshes, which reloads the Javascript.
-
-## Plugin Class Mapping
-
-The JavaScript portion of a plugin always uses the `cordova.exec` method as follows:
-
- exec(<successFunction>, <failFunction>, <service>, <action>, [<args>]);
-
-This will marshal a request from the WebView to the Android native
-side, more or less boiling down to calling the `action` method on the
-`service` class, with the arguments passed in the `args` Array.
-
-Whether you distribute your plugin as Java file or as a JAR of its own, the plugin must be added to the `config.xml` file in your Cordova-Android application's `res/xml/` folder.
-
- <plugin name="<service_name>" value="<full_name_including_namespace>"/>
-
-The service name should match what you use in the JavaScript `exec` call, and the value will be the full name of the Java class including the namespace. Without this added, the plugin may compile but
-will not be reachable by Cordova.
-
-## Writing an Android Java Plugin
-
-We have JavaScript to fire off a plugin request to the native side. We
-have the Android Java plugin mapped properly via the `config.xml` file.
-So what does the final Android Java Plugin class look like?
-
-What gets dispatched to the plugin via JavaScript's `exec` function gets
-passed into the Plugin class's `execute` method. Most `execute`
-implementations look like this:
-
- @Override
- public boolean execute(String action, JSONArray args, CallbackContext callbackContext) throws JSONException {
- if ("beep".equals(action)) {
- this.beep(args.getLong(0));
- callbackContext.success();
- return true;
- }
- return false; // Returning false results in a "MethodNotFound" error.
- }
-
-We compare the value of the `action` parameter, and dispatch
-the request off to a (private) method in the class, optionally passing
-some of the parameters to the method.
-
-When catching exceptions and returning errors, it's important that the error we return to JavaScript match the Java exception as much as possible, for clarity.
-
-### Threading
-
-JavaScript in the WebView does *not* run on the UI thread. It runs on
-the WebCore thread. The `execute` method also runs on the WebCore thread.
-
-If you need to interact with the UI, you should use the following:
-
- @Override
- public boolean execute(String action, JSONArray args, final CallbackContext callbackContext) throws JSONException {
- if ("beep".equals(action)) {
- final long duration = args.getLong(0);
- cordova.getActivity().runOnUiThread(new Runnable() {
- public void run() {
- ...
- callbackContext.success(); // Thread-safe.
- }
- });
- return true;
- }
- return false;
- }
-
-If you do not need to run on the UI thread, but do not want to block the WebCore thread:
-
- @Override
- public boolean execute(String action, JSONArray args, final CallbackContext callbackContext) throws JSONException {
- if ("beep".equals(action)) {
- final long duration = args.getLong(0);
- cordova.getThreadPool().execute(new Runnable() {
- public void run() {
- ...
- callbackContext.success(); // Thread-safe.
- }
- });
- return true;
- }
- return false;
- }
-
-### Echo Android Plugin Example
-
-We would add the following to our config.xml:
-
- <plugin name="Echo" value="org.apache.cordova.plugin.Echo" />
-
-Then we would add the following file to
-`src/org/apache/cordova/plugin/Echo.java` inside our Cordova-Android
-application:
-
- package org.apache.cordova.plugin;
-
- import org.apache.cordova.api.CordovaPlugin;
- import org.apache.cordova.api.PluginResult;
- import org.json.JSONArray;
- import org.json.JSONException;
- import org.json.JSONObject;
-
- /**
- * This class echoes a string called from JavaScript.
- */
- public class Echo extends CordovaPlugin {
- @Override
- public boolean execute(String action, JSONArray args, CallbackContext callbackContext) throws JSONException {
- if (action.equals("echo")) {
- String message = args.getString(0);
- this.echo(message, callbackContext);
- return true;
- }
- return false;
- }
-
- private void echo(String message, CallbackContext callbackContext) {
- if (message != null && message.length() > 0) {
- callbackContext.success(message);
- } else {
- callbackContext.error("Expected one non-empty string argument.");
- }
- }
- }
-
-Let's take a look at the code. At the top we have all of the necessary
-Cordova `imports`. Our class extends from `CordovaPlugin`. We override
-the execute() method in order to recieve messages from exec(). Our method
-first compares against `action`: this plugin only supports
-one action, the `echo` action. Any other action will return false, which
-results in an error of type `INVALID_ACTION` - this will translate
-into an error callback invocation on the JavaScript side. Next, we grab
-the echo string using the `getString` method on our `args`, telling it
-we want to get the 0th parameter in the parameter array. We do a bit of
-parameter checking: make sure it is not `null`, and make sure it is not
-a zero-length string. If it is, we call callbackContext.error() (which,
-by now, you should know will invoke the error callback). If all of those
-checks pass, then we call callbackContext.success(), and pass in the
-`message` string we received as a parameter. This will finally translate
-into a success callback invocation on the JavaScript side. It will also
-pass the `message` parameter as a parameter into the JavaScript success
-callback function.
-
-## Debugging Plugins
-
-Eclipse can be used to debug an Android project, and the plugins can be debugged if the Java source is included in the project. Only the latest version of the Android Dev Tools is known to allow source code attachment to JAR dependencies, this is not fully supported at this time.
-
-## Common Pitfalls
-
-* Plugins have access to a `CordovaInterface` object. This object has access to the Android `Activity` that is running the application. This is the `Context` required to launch
-a new Android `Intent`. The `CordovaInterface` allows plugins to start an `Activity` for a result, and to set the callback plugin for when the `Intent` comes back to the application. This is important, since the
-`Intent`s system is how Android communicates between processes.
-* Plugins do not have direct access to the `Context` as they have in the past. The legacy `ctx` member is deprecated, and will be removed six months after 2.0 is released. All the methods that `ctx` has exist on the `Context`, so both `getContext()` and `getActivity()` are capable of returning the proper object required.
-
-## Use the Source
-
-One of the best ways to prepare yourself to write your own plugin is to
-have a [look at other plugins that already exist](https://github.com/apache/cordova-android/tree/master/framework/src/org/apache/cordova).
-
-You should also read through the comments in [CordovaPlugin.java](https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/api/CordovaPlugin.java).
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/bada/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/bada/index.md b/docs/en/2.8.0rc1/guide/plugin-development/bada/index.md
deleted file mode 100644
index 3e059a8..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/bada/index.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Developing a Plugin on Bada
-===========================
-
-Plugins are only supported on Bada 2.0 and above. Bada 1.2 does not support plugins.
-
-The Bada implementation is a full javascript implementation. Therefore, adding a custom plugin involves updating CordovaJS with your plugin code. Follow these steps to add a simple _Hello World_ plugin:
-
-1. Clone the CordovaJS repository
-
- git clone https://git-wip-us.apache.org/repos/asf/cordova-js.git
-
-2. Create a new javascript file under __lib/bada/plugin/bada/__ and name it _HelloWorld.js_. Add the following content:
-
- function HelloWorld() {
- }
-
- HelloWorld.prototype.printHello = function(success, fail, arg) {
- alert(Osp.Core.StringHelper('Hello %1', arg[0]));
- }
-
- module.exports = new HelloWorld();
-
-3. Add a link to your newly created plugin in __lib/bada/platform.js__ under the objects property:
-
- objects: {
- ...
- HelloWorld: {
- 'cordova/plugin/bada/HelloWorld'
- },
- ...
- }
- ...
-4. Update the plugin list under __lib/bada/exec.js__ to include your plugin
-
- var plugins = {
- ...
- "HelloWorld": require('cordova/plugin/bada/HelloWorld')
- };
-5. Now you can write your user-facing javascript however you like but remember that in order for your plugin to execute you need to call the following method
-
- exec(success, fail, 'HelloWorld', 'printHello', ['Jackson!']);
-
- success is the success callback that gets executed when the plugin succeeds
- fail is the failure callback that gets executed if the plugin fails
- 'HelloWorld' is the name of your plugin
- 'printHello' is your plugin action
- Finally, the last argument is your plugin parameters (if any).
-
-6. Run the following command to generate the new common javascript (make sure you have the jake npm module installed)
-
- jake
-
-7. Copy the newly generated javascript under __pkg/cordova.bada.js__ to your Bada project under __Res/js__
-
-6. That is it! You can now add new Bada plugins and implement the many features that are not currently supported by Cordova Bada.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/blackberry/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/blackberry/index.md b/docs/en/2.8.0rc1/guide/plugin-development/blackberry/index.md
deleted file mode 100644
index 84394e8..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/blackberry/index.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Developing a Plugin on BlackBerry
-=================================
-
-## How to make the Echo plugin on Blackberry
-
-In this article, we will explore how to develop the Echo plugin on BlackBerry. If you haven't read the
-top level article about the JavaScript part of the plugin, it would be best if you read that first
-and then this article. In addition, please download the [Cordova Blackberry repo](https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry-webworks.git;a=summary).
-
-To note, the Cordova-BlackBerry project allows you to deploy to BlackBerry devices like the
-Torch, Bold, etc and as well as the Playbook. There exists a distinction between deploying to
-normal BlackBerry hand held devices (ie, Torch and Bold) and the Playbook. The code base between
-the two are separate so when you develop for one, you have to duplicate your efforts for the other!
-Therefore in this article, the focus will be on the hand held devices and not the tablet. In the future,
-this guide should cover both platforms.
-
-Continuing on from the previous article, the Echo plugin is essentially returning whatever message a user
-provides to the `window.echo` function.
-
-The Echo function:
-
- window.echo = function(str, callback) {
- cordova.exec(callback, function(err) {
- callback('Nothing to echo.');
- }, "Echo", "echo", [str]);
- };
-
-## Modifying plugins.xml
-
-This file resides in your project's www folder and contains all of the references to the plugins that
-your Cordova project uses. We are going to add an additional reference so that when cordova.exec is called,
-Cordova will know how to map the "Echo" argument of `cordova.exec` to the Echo class that we want to write natively.
-
- <plugins>
- ...
- <plugin name="Echo" value="org.apache.cordova.echo.Echo"/>
- ...
- </plugins>
-
-## Adding Echo.java
-
-If you notice the structure of the value attribute, you'll see a defined path that leads to the Echo
-plugin. In the root folder of the Cordova BlackBerry WebWorks repo, look for a folder called framework.
-This folder contains all of the source code that runs natively on the BlackBerry. cd into the folder
-structure until you reach the path: `framework/ext/src/org/apache/cordova`. At this point, you'll see
-all of the plugin folders and inside each folder is the plugins' source code. So, we will add
-the folder echo to `framework/ext/src/org/apache/cordova/echo` and create a file called `Echo.java`
-at `framework/ext/src/org/apache/cordova/echo/Echo.java`.
-
-## Writing Echo.java
-
-The basic idea of writing a plugin is to create a class that extends the Plugin class and have
-a method called execute to return a PluginResult class. Any call to cordova.exec will pass in
-the action that we want to execute within the class as well as the arguments. In this case,
-"echo" is the action we want to execute within the class "Echo" and [str] are the arguments we are passing in.
-
- package org.apache.cordova.echo;
-
- import org.apache.cordova.api.Plugin;
- import org.apache.cordova.api.PluginResult;
- import org.apache.cordova.json4j.JSONArray;
- import org.apache.cordova.json4j.JSONException;
- import org.apache.cordova.json4j.JSONObject;
- /**
- * A simple plugin to demonstrate how to build a plugin for Blackberry
- * Basically echos back the msg that a user calls to this plugin
- */
- public final class Echo extends Plugin {
-
- public static final String echo = "echo";
-
- public PluginResult execute(String action, JSONArray args, String callbackId) {
- PluginResult result = new PluginResult(PluginResult.Status.INVALID_ACTION, "Echo: Invalid action:" + action);
- if(action.equals(echo)){
- try {
- String theMsg = args.getString(0);
- if(theMsg!= null || theMsg.length()>0){
- result = new PluginResult(PluginResult.Status.OK, theMsg);
- }else{
- result = new PluginResult(PluginResult.Status.ERROR, "Nothing to echo.");
- }
- } catch (JSONException e) {
- result = new PluginResult(PluginResult.Status.JSON_EXCEPTION, e.getMessage());
- }
- }
-
- return result;
- }
-
- }
-
-So if we look at the code above, we can see that within the execute method, we are first looking for
-what actions are coming in. The Echo plugin has only one action, "echo" so we will be only checking for
-that. If our plugin had more actions, it's simply a matter of adding more if-conditionals to check
-for those actions.
-
-We are then going to grab the message coming in from the arguments which is supplied by the args parameter.
-We can grab the first argument by simply doing `String theMsg = args.getString(0);`.
-
-We will do some error checking and if the message looks okay, we will instantiate a new PluginResult with
-an ok status: PluginResult.Status.OK and return the message: theMsg. After this, we will then return the
-result which will then pass back to JavaScript to be fired in the success callback. If something should fail,
-we can return various status exceptions like PluginResult.Status.ERROR, PluginResult.Status.JSON_EXCEPTION,
-or PluginResult.Status.INVALID_ACTION. When these types of results are passed back, they will fire the fail
-callback in JavaScript.
-
-## Updating the .jar in your project's www folder
-
-The addition of the Echo.java needs to be updated in your project so to build the .jar file, cd
-to the root directory of the BlackBerry WebWorks repo. Use the ant command:
-
- ant update -Dproject.path="~/path_to_my_project"
-
-This will build a new .jar file in the build/ext folder. Copy the `build/ext/cordova.jar` file into your
-project/www/ext folder.
-
-If all goes well, that should allow you to use the Echo plugin in BlackBerry.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/blackberry10/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/blackberry10/index.md b/docs/en/2.8.0rc1/guide/plugin-development/blackberry10/index.md
deleted file mode 100644
index 2b6bfca..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/blackberry10/index.md
+++ /dev/null
@@ -1,191 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-# Developing a Plugin on BlackBerry 10
-
-This is a continuation of the Plugin Development Guide for Cordova. Once you have reviewed that content, now let's look at things we need to have the Echo plugin for the BlackBerry 10 platform. Recall that the Echo plugin basically returns whatever string a user provides to the `window.echo` function:
-
- window.echo = function(str, callback) {
- cordova.exec(callback, function(err) {
- callback('Nothing to echo.');
- }, "Echo", "echo", [str]);
- };
-
-A native BlackBerry 10 plugin for Cordova contains JavaScript code and may also contain native code. The Echo plugin example demonstrates how to invoke native functionality from JavaScript. The native and JavaScript code communicate with each other through a framework provided by JNEXT. Every plugin must also include a plugin.xml file.
-
-
-## Creating the native part of your plugin ##
-
-To create the native portion of your plugin, open the BlackBerry 10 NDK IDE and select File > New > BlackBerry Project > Native Extension > BlackBerry WebWorks. Enter your desired project name / location and click finish.
-
-The project created by the IDE contains sample code for a memory plugin. You may replace or modify these files to include your own functionality.
-
-- ***name*_js.hpp** - C++ header for the JNEXT code.
-- ***name*_js.cpp** - C++ code for JNEXT.
-
-The native interface for the JNEXT extension can be viewed in the plugin header file located in the public folder of your project. It also contains constants and utility functions that can be used in your native code. Your plugin must be derived from JSExt which is defined in plugin.h. That is, you must implement the following class:
-
- class JSExt
- {
- public:
- virtual ~JSExt() {};
- virtual string InvokeMethod( const string& strCommand ) = 0;
- virtual bool CanDelete( void ) = 0;
- private:
- std::string m_id;
- };
-
-Therefore, your extension should include the plugin.h header file. In the Echo example, you use JSExt as follows in the echo_js.hpp file:
-
- #include "../public/plugin.h"
- #include <string>
-
- #ifndef ECHO_JS_H_
- #define ECHO_JS_H_
-
- class Echo : public JSExt
- {
- public:
- explicit Echo(const std::string& id);
- virtual ~Echo();
- virtual std::string InvokeMethod(const std::string& command);
- virtual bool CanDelete();
- private:
- std::string m_id;
- };
-
- #endif // ECHO_JS_H_
-
-The `m_id` is an attribute that contains the JNEXT id for this object. The id is passed to the class as an argument to the constructor. It is needed to trigger events on the JavaScript side from native.
-The CanDelete method is used by JNEXT to determine whether your native object can be deleted.
-The InvokeMethod function is called as a result from a request from JavaScript to invoke a method of this particular object. The only argument to this function is a string passed from JavaScript that this method should parse in order to determine which method of the native object should be executed.
-Now we implement these functions in echo_js.cpp. For the Echo example, we implement InvokeMethod function as follows:
-
- string Echo::InvokeMethod(const string& command) {
-
- //parse command and args from string
- int index = command.find_first_of(" ");
- string strCommand = command.substr(0, index);
- string strValue = command.substr(index + 1, command.length());
-
- // Determine which function should be executed
- if (strCommand == "echo") {
- return strValue;
- } else {
- return "Unsupported Method";
- }
- }
-
-Your native plugin must also implement the following callback functions:
-
-- `extern char* onGetObjList( void );`
-- `extern JSExt* onCreateObject( const string& strClassName, const string& strObjId );`
-
-The `onGetObjList` function returns a comma separated list of classes supported by JNEXT. JNEXT uses this function to determine the set of classes that JNEXT can instantiate. In our Echo plugin, we have the following in `echo_js.cpp`:
-
- char* onGetObjList() {
- static char name[] = "Echo";
- return name;
- }
-
-The `onCreateObject ` function takes two parameters. The first parameter is the name of the class requested to be created from the JavaScript side. Valid names are those that are returned in `onGetObjList`. The second parameter is the unique object id for the class. This method returns a pointer to the created plugin object. In our Echo plugin, we have the following in `echo_js.cpp`:
-
- JSExt* onCreateObject(const string& className, const string& id) {
- if (className == "Echo") {
- return new Echo(id);
- }
- return NULL;
- }
-
-##Creating the JavaScript part of your plugin##
-
-The JavaScript portion of your plugin must contain the following files:
-
-- **client.js** – This is considered the client side and contains the API that a Cordova application can call. The API in client.js calls makes calls to index.js. The API in client.js also connects callback functions to the events that fire the callbacks.
-
-- **index.js** – Cordova loads index.js and makes it accessible through the cordova.exec bridge. The client.js file makes calls to the API in the index.js file, which in turn makes call to JNEXT to communicate with the native side.
-
-The client and server side (client.js and index.js) interacts through the `Cordova.exec `function. So, in client.js you invoke the exec function and provide the necessary arguments. In the Echo plugin, we have the following in the client.js file:
-
- var service = "org.apache.cordova.blackberry.echo",
- exec = cordova.require("cordova/exec");
-
- module.exports = {
- echo: function (data, success, fail) {
- exec(success, fail, service, "echo", { data: data });
- }
- };
-
-Now, index.js interacts with the native side using JNEXT. So you attach a constructor function named Echo to JNEXT. Within the constructor you perform the following key operations using the init function:
-
-- Specify the required module exported by the native side. The name of the required module must match the name of a shared library file (.so file).
-
-`JNEXT.require("libecho")`
-
-- Create an object by using an acquired module and save the ID that's returned by the call.
-self.m_id = JNEXT.createObject("libecho.Echo");
-When your application calls the echo function in client.js, that call in turn calls the echo function in index.js, where the PluginResult object sends a response (data) back to client.js. Since the args argument passed into the functions was converted by JSON.stringfy() and encoded as a URIcomponent, you must call the following:
-
-`data = JSON.parse(decodeURIComponent(args.data));`
-
-You can now send the data back. Let’s put it all together:
-
- module.exports = {
-
- echo: function (success, fail, args, env) {
-
- var result = new PluginResult(args, env),
- data = JSON.parse(decodeURIComponent(args.data)),
- response = echo.getInstance().echo(data);
- result.ok(response, false);
- }
- };
-
-## Architecture of the plugin ##
-
-You can place the artifacts of the plugin, which includes the plugin.xml file, the source files (JavaScript, C++), and the binary files (.so) within any directory structure, as long as you correctly specify the file locations in the plugin.xml file. Below we show a typical structure that you can follow:
-
-***your_project_folder*** (>plugin.xml)
-
-- **www** (>client.js)
-- **src**
- - **blackberry10** (>index.js, **native** >*.cpp, *.hpp)
- - **device** (>*biary file* *.so)
- - **simulator** (>*binary file* *.so)
-
-(The list shows the hierarchical relationship among the top level folders. The parenthesis shows the contents of a given folder. All folder names appear in bold text. File names are preceded by the '>' sign.)
-
-## Contents of the plugin.xml file##
-The plugin.xml file contains the namespace of the extension and other metadata. Define the namespace and specify other metadata for the Echo plugin as follows:
-
- <plugin xmlns="http://www.phonegap.com/ns/plugins/1.0"
- id="org.apache.cordova.blackberry.echo"
- version="1.0.0">
- <js-module src="www/client.js">
- <merges target="navigator" />
- </js-module>
- <platform name="blackberry10">
- <source-file src="src/blackberry10/index.js" />
- <lib-file src="src/blackberry10/native/device/libecho.so" arch="device" />
- <lib-file src="src/blackberry10/native/simulator/libecho.so" arch="simulator" />
- <config-file target="www/config.xml" parent="/widget">
- <feature name="org.apache.cordova.blackberry.echo" value="org.apache.cordova.blackberry.echo" />
- </config-file>
- </platform>
- </plugin>
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/index.md b/docs/en/2.8.0rc1/guide/plugin-development/index.md
deleted file mode 100644
index d05147d..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/index.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-# Plugin Development Guide
-
-A Cordova plugin bridges a bit of functionality between the WebView
-powering a Cordova application and the native platform the Cordova
-application is running on. Plugins are composed of a single JavaScript
-interface used across all platforms, and native implementations
-following platform-specific Plugin interfaces that the JavaScript will
-call into. It should be noted that all of the core Cordova APIs are
-implemented using this exact architecture.
-
-This guide will go through each step necessary to write a simple Echo
-Plugin. The Echo Plugin will pass a string from JavaScript and send it
-into the native environment for the supported platforms. The native code
-will then return the same string back into the callbacks inside the
-plugin's JavaScript.
-
-This guide should give anyone the necessary overview and level of
-detail to write more complex plugins.
-
-## JavaScript
-
-The entry point for any plugin is JavaScript. The reason developers use
-Cordova is so they can use and write JavaScript, not Objective-C,
-not Java, not C#. The JavaScript interface for your plugin is the
-front-facing and arguably most important part of your Cordova plugin.
-
-You can structure your plugin's JavaScript however you like. The one
-thing you _must_ use to communicate between the Cordova JavaScript
- and native environments is the `cordova.exec` function. Here is an example:
-
- cordova.exec(function(winParam) {}, function(error) {}, "service",
- "action", ["firstArgument", "secondArgument", 42,
- false]);
-
-The parameters explained in more detail:
-
-1. `function(winParam) {}` - Success function callback. Assuming your
- `exec` call completes successfully, this function will be invoked
- (optionally with any parameters you pass back to it)
-2. `function(error) {}` - Error function callback. If the operation does
- not complete successfully, this function will be invoked (optionally
- with an error parameter)
-3. `"service"` - The service name to call into on the native side. This
- will be mapped to a native class. More on this in the native guides
- below
-4. `"action"` - The action name to call into. This is picked up by the
- native class receiving the `exec` call, and, depending on the
- platform, essentially maps to a class's method. For more detail
- please check out the native guides located at the end of this article.
-5. `[/* arguments */]` - Arguments to get passed into the native
- environment
-
-### Echo Plugin JavaScript Example
-
- window.echo = function(str, callback) {
- cordova.exec(callback, function(err) {
- callback('Nothing to echo.');
- }, "Echo", "echo", [str]);
- };
-
-Let's dive into this. The plugin attaches itself to `window`,
-specifically to the `echo` function. Plugin users would then use it as
-follows:
-
- window.echo("echome", function(echoValue) {
- alert(echoValue == "echome"); // should alert true.
- });
-
-First, let's take a look at the last three arguments to the `exec`
-function. We will be calling the `Echo` "service", requesting the `echo`
-"action", and passing an array of arguments containing the echo string,
-which is the first parameter into the `window.echo` function.
-
-The success callback passed into `exec` is simply a reference to the
-callback function that `window.echo` takes. We do a bit more for the
-error callback: if the native side fires off the error callback, we
-simply invoke the success callback and pass into it a "default" string.
-
-## Native
-
-Once you have defined a JavaScript for your plugin, you need to
-complement it with at least one native implementation. Below are
-specific guides for each platform Cordova supports. The below guides
-will continue on building the simple Echo Plugin example we started in
-this guide.
-
-- Developing a Plugin on Android
-- Developing a Plugin on Bada
-- Developing a Plugin on BlackBerry
-- Developing a Plugin on BlackBerry 10
-- Developing a Plugin on iOS
-- Developing a Plugin on webOS
-- Developing a Plugin on Windows Phone
-- Developing a Plugin on Tizen
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/ios/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/ios/index.md b/docs/en/2.8.0rc1/guide/plugin-development/ios/index.md
deleted file mode 100644
index f1de066..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/ios/index.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-# Developing a Plugin on iOS
-
-A plugin is an Objective-C class that extends the `CDVPlugin` class.
-
-Each plugin class must be registered using the config.xml file, as a <plugin> tag under the <plugins> key.
-
-## Plugin Class Mapping
-
-The JavaScript portion of a plugin always uses the `cordova.exec` method as follows:
-
- exec(<successFunction>, <failFunction>, <service>, <action>, [<args>]);
-
-This will marshal a request from the UIWebView to the iOS native side, more or less boiling down to calling the `action` method on the `service` class, with the arguments passed in the `args` Array.
-
-The plugin must be added under the `<plugins>` tag of the `config.xml` file in your Cordova-iOS application's project folder.
-
- <plugin name="service_name" value="PluginClassName" />
-
-The key `service_name` should match what you use in the JavaScript `exec` call, and the value will be the name of the Objective-C class of the plugin. Without this added, the plugin may compile but will not be reachable by Cordova.
-
-## Plugin Initialization and Lifetime
-
-There is one instance of a plugin object that is created per-UIWebView, and the lifetime of the instance is tied to the UIWebView. Plugins are not instantiated until they are first referenced by a call from JS, unless the `onload` attribute set within config.xml. E.g.:
-
- <plugin name="Echo" value="Echo" onload="true" />
-
-There is *no* designated initializer for plugins. Instead, plugins should use the `pluginInitialize` method for their start-up logic.
-
-Plugins with long-running requests, background activity (e.g. playing media), listeners or internal state should implement the `onReset` method and stop or clean up those activities. This method is run when the `UIWebView` navigates to a new page or refreshes, which reloads the Javascript.
-
-
-## Writing an iOS Cordova Plugin
-
-We have JavaScript fire off a plugin request to the native side. We have the iOS Objective-C plugin mapped properly via the `config.xml` file. So what does the final iOS Objective-C Plugin class look like?
-
-What gets dispatched to the plugin via JavaScript's `exec` function gets passed into the corresponding Plugin class's `action` method. A plugin method has this signature:
-
- - (void)myMethod:(CDVInvokedUrlCommand*)command
- {
- CDVPluginResult* pluginResult = nil;
- NSString* myarg = [command.arguments objectAtIndex:0];
-
- if (myarg != nil) {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK];
- } else {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR messageAsString:@"Arg was null"];
- }
- [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
- }
-
-1. [CDVInvokedUrlCommand.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVInvokedUrlCommand.h)
-2. [CDVPluginResult.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPluginResult.h)
-3. [CDVCommandDelegate.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVCommandDelegate.h)
-
-## iOS CDVPluginResult message types
-
-Using CDVPluginResult you can return a variety of result types back to your javascript callbacks, using class methods that look like:
-
- + (CDVPluginResult*)resultWithStatus:(CDVCommandStatus)statusOrdinal messageAs...
-
-The types you can create are: `String`, `Int`, `Double`, `Bool`, `Array`, `Dictionary`, `ArrayBuffer`, and `Multipart`. Or, don't attach any arguments (just send a status). Or, return an Error. You can even chose to not send any plugin result at all (your callback will not fire).
-
-### Notes
-
- * `messageAsArrayBuffer` expects `NSData*` and will convert to an `ArrayBuffer` for your javascript callback (and `ArrayBuffers` sent to a plugin from javascript are converted to `NSData*`).
- * `messageAsMultipart` expects an `NSArray*` containing any of the other supported types, and will send the whole array as the `arguments` to your javascript callback.
- * Quirk: this is not just syntactic sugar (though it is sweet). This way, all of the arguments are serialized/deserialized as necessary. e.g. it is safe to return `NSData*` as multipart, but not as `Array`/`Dictionary`.
-
-## Plugin Signatures
-
-The **new signature** supported beginning in **Cordova 2.1.0** is:
-
- - (void)myMethod:(CDVInvokedUrlCommand*)command;
-
-The **old (deprecated)** signature is:
-
- - (void)myMethod:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
-
-Basically, the options dictionary has been removed for the new signature, and the callbackId is not the 0th index item for the arguments array, but it is now in a separate property.
-
-## Echo Plugin iOS Plugin
-
-We would add the following to the `<plugins>` tag of the project's `config.xml` file:
-
- <plugin name="Echo" value="Echo" />
-
-Then we would add the following files (`Echo.h` and `Echo.m`) to the Plugins folder inside our Cordova-iOS
-application folder:
-
- /********* Echo.h Cordova Plugin Header *******/
-
- #import <Cordova/CDV.h>
-
- @interface Echo : CDVPlugin
-
- - (void)echo:(CDVInvokedUrlCommand*)command;
-
- @end
-
- /********* Echo.m Cordova Plugin Implementation *******/
-
- #import "Echo.h"
- #import <Cordova/CDV.h>
-
- @implementation Echo
-
- - (void)echo:(CDVInvokedUrlCommand*)command
- {
- CDVPluginResult* pluginResult = nil;
- NSString* echo = [command.arguments objectAtIndex:0];
-
- if (echo != nil && [echo length] > 0) {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:echo];
- } else {
- pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR];
- }
-
- [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
- }
-
- @end
-
-
-Let's take a look at the code. At the top we have all of the necessary Cordova imports. Our class extends from `CDVPlugin` - very important.
-
-This plugin only supports one action, the `echo` action. First, we grab the echo string using the `objectAtIndex` method on our `args`, telling it we want to get the 0th parameter in the arguments array. We do a bit of parameter checking: make sure it is not `nil`, and make sure it is not a zero-length string.
-
-If it is, we return a `PluginResult` with an `ERROR` status. If all of those checks pass, then we return a `PluginResult` with an `OK` status, and pass in the `echo` string we received in the first place as a parameter.
-
-Finally, we send the result to `self.commandDelegate`, which will execute the JavaScript that will callback to success or failure callbacks of the exec method on the JavaScript side. If the success callback was called, it will pass the `echo` parameter as a parameter.
-
-## Threading
-
-Plugin methods are executed on the UI thread. If your plugin requires a non-trivial amount of processing or requires a blocking call, you should make use of a background thread. An example:
-
- - (void)myPluginMethod:(CDVInvokedUrlCommand*)command
- {
- // Check command.arguments here.
- [self.commandDelegate runInBackground:^{
- NSString* payload = nil;
- // Some blocking logic...
- CDVPluginResult* pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:payload];
- // The sendPluginResult method is thread-safe.
- [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
- }];
- }
-
-
-## Advanced Plugin Functionality
-
-See other methods that you can override in:
-
-1. [CDVPlugin.h](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.h)
-2. [CDVPlugin.m](https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.m)
-
-For example, you can hook into the pause, resume, app terminate and handleOpenURL events.
-
-## Debugging Plugins
-
-To debug the Objective-C side, you would use Xcode's built in debugger. For JavaScript, on iOS 5.0 you can use [Weinre, an Apache Cordova Project](https://github.com/apache/cordova-weinre) or [iWebInspector, a third-party utility](http://www.iwebinspector.com/)
-
-For iOS 6, you would use Safari 6.0 to simply attach to your app running in the iOS 6 Simulator.
-
-## Common Pitfalls
-
-* Don't forget to add your plugin's mapping to config.xml - if you forgot, an error will be printed to the Xcode console log
-* Don't forget to add any hosts you connect to in the [whitelist](guide_whitelist_index.md.html#Domain%20Whitelist%20Guide) - if you forgot, an error will be printed to the Xcode console log
-
-## Deprecated Plugin Signature Note
-
-The **old (deprecated)** signature is:
-
- - (void) myMethod:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
-
-The options parameter for the Objective-C plugin method is deprecated, and it should not be used. For legacy reasons - the last JavaScript object passed in the args Array will be passed in as the options dictionary of the method in Objective-C. You must make sure that any JavaScript object that is passed in as an element in the args array occurs as the last item in the Array, if not it will throw off the array index of all subsequent parameters of the Array in Objective-C. Only one JavaScript object is supported for the options dictionary, and only the last one encountered will be passed to the native method. It is because of these error-prone reasons that they are being deprecated.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/tizen/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/tizen/index.md b/docs/en/2.8.0rc1/guide/plugin-development/tizen/index.md
deleted file mode 100644
index 5736f29..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/tizen/index.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Developing a Plugin on Tizen
-============================
-
-Plugins are currently not supported by the Tizen platform.
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/ef7308be/docs/en/2.8.0rc1/guide/plugin-development/webos/index.md
----------------------------------------------------------------------
diff --git a/docs/en/2.8.0rc1/guide/plugin-development/webos/index.md b/docs/en/2.8.0rc1/guide/plugin-development/webos/index.md
deleted file mode 100644
index a66ef9f..0000000
--- a/docs/en/2.8.0rc1/guide/plugin-development/webos/index.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
----
-
-Developing a Plugin on webOS
-============================
-
-Plugins are currently not supported by the webOS platform.