rhodes 3.4.2 → 3.5.1.12

data/doc/device-caps.txt

@@ -2,43 +2,10 @@
 
 ## Introduction
 
-Rhodes provide access to device specific capabilities such as GPS, PIM, camera, SMS, video player, accelerometer, proximity detector and [native UI elements](ui).  Below is the device support matrix showing what release supports what device capabilities on a per device operating system basis.
-
-<table class="device-caps">
-	<tr>
-		<th>Capability</th>
-		<th>iOS</th>
-		<th>Windows Mobile</th>
-		<th>Windows Phone</th>
-		<th>BlackBerry</th>
-		<th>Android</th>
-		<th>RhoSimulator</th>
-		<th>Symbian</th>
-		<th>Windows Desktop</th>
-	</tr>
-	<tr><td class='cap'>GeoLocation</td><td>0.3</td><td>0.3</td><td class='tbd'>TBD</td><td>0.3</td><td>1.0</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>PIM Contacts</td><td>0.3</td><td>0.3</td><td class='tbd'>TBD</td><td>0.3</td><td>1.0</td><td class='tbd'>3.5</td><td>3.1</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>PIM Calendar</td><td>2.2</td><td>2.2</td><td class='tbd'>TBD</td><td>2.2</td><td>2.2</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Camera</td><td>1.0</td><td>1.0</td><td class='tbd'>TBD</td><td>1.0</td><td>1.0</td><td>3.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Barcode</td><td>2.1</td><td>2.1</td><td class='tbd'>TBD</td><td>2.1</td><td>2.1</td><td class='tbd'>4.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Date/Time picker</td><td>1.2.2</td><td>2.0</td><td class='tbd'>TBD</td><td>1.2</td><td>1.2</td><td>3.0</td><td class='tbd'>TBD</td><td>3.0</td></tr>
-	<tr><td class='cap'>Menu</td><td>1.2.2</td><td>2.0</td><td>3.0</td><td>1.2</td><td>1.5</td><td>3.0</td><td>3.1</td><td>3.0</td></tr>
-	<tr><td class='cap'>Toolbar</td><td>1.2.2</td><td>2.3</td><td>3.0</td><td class='tbd'>n/a</td><td>1.5</td><td>3.0</td><td>3.1</td><td>3.0</td></tr>
-	<tr><td class='cap'>Tab Bar</td><td>1.2.2</td><td class='tbd'>3.5</td><td>3.0</td><td class='tbd'>n/a</td><td>1.5</td><td>3.1</td><td>3.1</td><td class='tbd'>3.4</td></tr>
-	<tr><td class='cap'>Nav Bar</td><td>2.0</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>n/a</td><td>2.0</td><td class='tbd'>4.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Signature Capture</td><td>2.1</td><td>3.0</td><td class='tbd'>TBD</td><td class='tbd'>3.5</td><td>2.1</td><td class='tbd'>4.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr class='tbd'><td class='cap'>Audio/Video capture</td><td>4.0</td><td>4.0</td><td class='tbd'>TBD</td><td>4.0</td><td>4.0</td><td>4.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Bluetooth</td><td>2.2</td><td>2.2</td><td class='tbd'>TBD</td><td>2.2</td><td>2.2</td><td class='tbd'>4.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>NFC</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td>3.0</td><td class='tbd'>4.0</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Push</td><td>1.2</td><td class='tbd'>4.0</td><td class='tbd'>TBD</td><td>1.2</td><td>2.2</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Screen rotation</td><td>2.1</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td>2.0</td><td>2.1</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Native Maps</td><td>1.4</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td>1.4</td><td>1.5</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Alerts/Audio File Playback</td><td>1.2</td><td>1.5</td><td class='tbd'>TBD</td><td>1.2</td><td>1.2</td><td>3.1</td><td class='tbd'>TBD</td><td>3.1</td></tr>
-	<tr><td class='cap'>Ringtones</td><td>3.5</td><td>1.5</td><td class='tbd'>TBD</td><td>1.5</td><td>1.5</td><td class='tbd'>3.5</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-	<tr><td class='cap'>Printing</td><td>3.4</td><td>3.4</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td><td class='tbd'>TBD</td></tr>
-</table>	
-
-**NOTE: As of Rhodes version 3.3.3, the [Barcode](/rhodes/device-caps#barcode), [NFC](/rhodes/device-caps#nfc), and [Inline Signature Capture](/rhodes/device-caps#signature-capture) APIs, as well as [Rhom data encryption](/rhodes/rhom#database-encryption) are removed from Rhodes. These features are only supported in Motorola RhoMobile Suite. If you wish to use these features, you will need to [upgrade to RhoMobile Suite](/rhoelements/rhoelements-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements']( /rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
+Rhodes provide access to device specific capabilities such as GPS, PIM, camera, SMS, video player, accelerometer, proximity detector and [native UI elements](ui).  Check the [API Compatibility Matrix](/rhoelements/apicompatibility) for complete details on which APIs are supported on the variety of operating systems.
+
+
+**NOTE: As of Rhodes version 3.3.3, the [Barcode](/rhodes/device-caps#barcode), [NFC](/rhodes/device-caps#nfc), and [Inline Signature Capture](/rhodes/device-caps#signature-capture) APIs, as well as [Rhom data encryption](/rhodes/rhom#database-encryption) are removed from Rhodes. These features are only supported in Motorola RhoMobile Suite. If you wish to use these features, you will need to [upgrade to RhoMobile Suite](/rhomobile-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements']( /rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
 
 ## System class
 The System Ruby class provides access to the system specific information.
@@ -170,11 +137,22 @@ To get current application Locale:
 	:::ruby
     LocalizationSimplified::get_cur_locale #get current application locale
 
+To use client with the HTTP proxy you should pass its URL as the first command line argument `-http_proxy_url=http://<login>:<passwod>@<host>:<port>` (Windows Desktop only), add it to rhoconfig.txt, or call the setter method from Ruby code:
+    :::ruby
+    System.set_http_proxy_url(url)
+
+To stop using HTTP proxy (that was set by the command line, rhoconfig.txt or Ruby code) call:
+    :::ruby
+    System.unset_http_proxy()
+
+**NOTE: `System.set_http_proxy_url(url)` and `System.unset_http_proxy()` are implemented only for Windows Mobile, WinCE and Windows Desktop  **
+
 To modify application window position and size:
     :::ruby
     System.set_window_frame(x,y,width,height) #change application window position and size
     System.set_window_position(x,y) #change application window position
     System.set_window_size(width,height) #change application window size
+    System.lock_window_size(locked) #lock/unlock window size change by user
 
 **NOTE: These methods implemented only for Windows Desktop  **
 
@@ -235,7 +213,7 @@ To show currency (see rails analog for details):
 
 Geolocation information is available in two ways: as an asynchronous service through Ajax calls to a predefined local URL, or in a controller using Ruby calls to the GeoLocation class.
 
-You need to enable the GPS capability to use GeoLocaiton. This is done by adding the following line to build.yml:
+You need to enable the GPS capability to use GeoLocation. This is done by adding the following line to build.yml:
 
 	:::yaml
 	capabilities:
@@ -452,7 +430,7 @@ These two parameters are used to paginate contacts list. If used with :count exa
 
 The next parameters are available at Android only.
 
- * :select - list of contact properties have to be selected from phonebook (Use it to enchance query performance)
+ * :select - list of contact properties have to be selected from phonebook (Use it to enhance query performance)
  * :conditions - hash of conditions to query contacts. Look for more details below.
 
 **NOTE: It is allowed to pass additional params hash at all platforms. Platforms that has no extended functionality will just skip these**
@@ -534,11 +512,11 @@ Condition like
 	:::ruby
 	{:phone => 'not_nil'}
 will select all contacts which has at least one phone.
-The next conditions are currently suported:
+The following conditions are currently supported:
 - 'not_nil'
 - 'is_nil'
 
-**NOTE: It may be useful to sort received contacts (espessially if paginated). Contacts is ordered by 'display_name' column and then splitted for pages. Unfortunately the order inside page is lost while passing the list to ruby**
+**NOTE: It may be useful to sort received contacts (especially if paginated). Contacts is ordered by 'display_name' column and then split for pages. Unfortunately the order inside page is lost while passing the list to ruby**
 
 	:::ruby
 	@count = Rho::RhoContact.find(:count, :conditions => {:phone => 'not_nil'})
@@ -619,10 +597,10 @@ On iPhone and Android additional event properties are supported. These are:
 
 Recurrence properties:
 "recurrence", "frequency"('daily', 'weekly', 'monthly', 'yearly'), "interval", "count", "end_date"
-"count" and "end" rucurrence properties are mutual exclusive. "end" is date/time beyond last event occurence but within same day.     
+"count" and "end" recurrence properties are mutual exclusive. "end" is date/time beyond last event occurrence but within same day.
 
 ### Recurrence properties
-Recurrence properties are groupped in separate hash stored as single event property (event[Rho::RhoEvent::RECURRENCE]).
+Recurrence properties are grouped in separate hash stored as single event property (event[Rho::RhoEvent::RECURRENCE]).
 
 ### Names of properties
 There are helper constants defined in Rho::RhoEvent which can be used to address event values and as predefined set of values (for frequency).
@@ -743,13 +721,13 @@ See controller and view in the /app/Image folder of the [ System API Samples app
 
 ## Barcode
 
-**NOTE: As of Rhodes version 3.3.3, the [Barcode](/rhodes/device-caps#barcode) API is removed from Rhodes. This feature is only supported in Motorola RhoMobile Suite. If you wish to use this feature, you will need to [upgrade to RhoMobile Suite](/ rhoelements/rhoelements-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements'](/rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
+**NOTE: As of Rhodes version 3.3.3, the [Barcode](/rhodes/device-caps#barcode) API is removed from Rhodes. This feature is only supported in Motorola RhoMobile Suite. If you wish to use this feature, you will need to [upgrade to RhoMobile Suite](/rhomobile-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements'](/rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
 
 The Barcode API allows to try recognize barcode on an image:
 	:::ruby
 	Barcode.barcode_recognize(image_file_full_path)
 
-Barcode recognition functionality realized as Rhode Native extension. You should add "Barcode" to extension list in build.yml located in your application folder. `Barcode.barcode_recognize(image_file_full_path)` return string with recognized code or emty string if not any recognized barcodes on the image. You can combine Camera for get picture with Barcode recognition for process barcode data - see sample below.
+Barcode recognition functionality realized as Rhode Native extension. You should add "Barcode" to extension list in build.yml located in your application folder. `Barcode.barcode_recognize(image_file_full_path)` return string with recognized code or empty string if not any recognized barcodes on the image. You can combine Camera for get picture with Barcode recognition for process barcode data - see sample below.
 
 For barcode recognition we use Zbar library (iPhone, and Windows Mobile platforms) and ZXing library (Android and BlackBerry platforms). In this case we support next barcode types :
 
@@ -757,9 +735,9 @@ For barcode recognition we use Zbar library (iPhone, and Windows Mobile platform
 * iPhone platform: UPC-A, UPC-E, EAN-8, EAN-13, Code 39, Code 128, QR Code .
 * Android and BlackBerry platforms: UPC-A, UPC-E, EAN-8, EAN-13, Code 39, Code 128, Code 93, QR Code, ITF, Codabar
 
-**NOTE: We are very sorry, but we are removed ZBar source code from our project by ZBar license requirements. For build Barcode extension for WM, you should download ZBar sources from http://zbar.sourceforge.net/ and copy to [rhodes root]/lib/extensions/barcode/ext/barcode/shared/zbar/zbar/ folder "include" and "zbar" folders from ZBar sources. Also you should fix ZBar sources for building by Microsoft Visual Studio (move define of inner function variables to begin of functions, etc.). See detailed instructon in your Rhodes installation at /lib/extensions/barcode/ext/barcode/shared/zbar/zbar/README.TXT**
+**NOTE: We are very sorry, but we are removed ZBar source code from our project by ZBar license requirements. For build Barcode extension for WM, you should download ZBar sources from http://zbar.sourceforge.net/ and copy to [rhodes root]/lib/extensions/barcode/ext/barcode/shared/zbar/zbar/ folder "include" and "zbar" folders from ZBar sources. Also you should fix ZBar sources for building by Microsoft Visual Studio (move define of inner function variables to begin of functions, etc.). See detailed instructions in your Rhodes installation at /lib/extensions/barcode/ext/barcode/shared/zbar/zbar/README.TXT**
 
-On Android and iOS (not supported on iPhone 2G and iPhone 3G !) now supported real-time barcode recognizing (second parameter is hash with options):
+On Android and iOS (not supported on iPhone 2G and iPhone 3G !) real-time barcode recognition is supported (second parameter is hash with options):
 	:::ruby
 	Barcode.take_barcode(url_for(:action => :take_callback), {})
 
@@ -767,7 +745,7 @@ On Android also you can use front camera for take_barcode :
 	:::ruby
 	Barcode.take_barcode(url_for(:action => :take_callback), {:camera => 'front'})
 
-This code open special UI for real-time barcode recognizing from camera. If any barcode found recognizing stopped and user can select - confirm recognizing barcode or continue recognizig. If user confirmed or cancelled the callback will be called.
+This code open special UI for real-time barcode recognizing from camera. If any barcode found, recognizing stopped and user can select - confirm recognizing barcode or continue recognizing. If user confirmed or cancelled the callback will be called.
 In callback are these parameters.
  
  * "status" - "ok" or "cancel"
@@ -800,13 +778,17 @@ The following parameters are in the hash.
 
 **NOTE: On Windows Mobile and Windows CE devices only "bmp" is supported as 'imageFormat'.**
 
+**NOTE: On Blackberry devices only "png" is supported as 'imageFormat'.**
+
 After user entered signature (or canceled) provided callback url will be called. Callback parameters will be the following.
 
  * status - 'ok' or 'cancel'
  * signature_uri - path to the image with signature   
 
+**NOTE: To take signature on Blackberry devices press Menu button then select 'Capture'.**
+
 ### Inline signature capture
-**NOTE: As of Rhodes version 3.3.3, the Inline Signature Capture API is removed from Rhodes. This feature is only supported in Motorola RhoMobile Suite. If you wish to use this feature, you will need to [upgrade to RhoMobile Suite](/ rhoelements/rhoelements-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements'](/rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
+**NOTE: As of Rhodes version 3.3.3, the Inline Signature Capture API is removed from Rhodes. This feature is only supported in Motorola RhoMobile Suite. If you wish to use this feature, you will need to [upgrade to RhoMobile Suite](/rhomobile-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements'](/rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
 
 Windows Mobile and Windows CE devices support signature capture started in window, which you can show over current page(scrolling is not supported in this case).
 
@@ -1043,9 +1025,9 @@ You can find complete example of using Bluetooth API in [Rhodes-System-Api-Sampl
 ## NFC
 
 NFC (Near Field Communication). NFC API provide access to NFC functionality. You can check NFC availability on current device and register callback for listen event when NFC tag near of device. Currently NFC supported only on Android. And also Android version must be 2.3.3 or later.
-NFC API implemented in native extension. You should add "nfc" to extension list in your nuild.yml before start using NFC in your application. Please see detailed doc: [Rhodes NFC extension](/rhodes/nfc).
+NFC API implemented in native extension. You should add "nfc" to extension list in your build.yml before start using NFC in your application. Please see detailed doc: [Rhodes NFC extension](/rhodes/nfc).
 
-**NOTE: As of Rhodes version 3.3.3, the [NFC](/rhodes/nfc) API is removed from Rhodes. This feature is only supported in Motorola RhoMobile Suite. If you wish to use this feature, you will need to [upgrade to RhoMobile Suite](/rhoelements/rhoelements-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements'](/rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
+**NOTE: As of Rhodes version 3.3.3, the [NFC](/rhodes/nfc) API is removed from Rhodes. This feature is only supported in Motorola RhoMobile Suite. If you wish to use this feature, you will need to [upgrade to RhoMobile Suite](/rhomobile-install). Your application's build.yml will also need to be modified to [indicate the application type is 'Rhoelements'](/rhoelements/rhoelements2-native#enabling-motorola-device-capabilities). Additionally, a [RhoElements license](/rhoelements/licensing) is required.**
 
 ## Ringtone manager
 
@@ -1076,7 +1058,7 @@ See controller and view in the /app/Ringtones folder of the [System API Samples
 ## Printing
 
 ### Printing on iOS
-iOS inlude printing support. You should prepare File for printing and open it by standart platform - use:
+iOS include printing support. You should prepare File for printing and open it by standart platform - use:
 	:::ruby
 	System.open_url(file_full_path)
 
@@ -1092,7 +1074,7 @@ Android do not support printing. You can use any third-party application for pri
 You should prepare file for printing and open it by standart platform - use:
 	:::ruby
 	System.open_url(file_full_path)
-Android platfrom open that file in application registered for file extension or show select dialog for manually choose application if there are more than one application registered for this extension.
+Android platform opens that file in application registered for file extension or show select dialog for manually choose application if there are more than one application registered for this extension.
 
 We recommend prepare PDF. You can use PDF-Writer pure Ruby library for it - we include it into rhodes - just include "pdf-writer" and "thread" extensions to your application extension list in build.yml.
 	:::yaml
@@ -1102,235 +1084,7 @@ See example in our [System API Samples application Generate PDF example](http://
 
 
 ## PUSH Notifications
-Push notification support is currently available for Android, Blackberry and iPhone. 
-
-Testing push is a little more involved than some other features because it requires additional setup on both the RhoConnect application and Rhodes application. Please refer to [RhoConnect Device Push](/rhoconnect/push) for more information.
-
-### Setup
-
-First, enable push in your rhodes application in build.yml:
-
-	:::yaml
-	capabilities:
-	  - push
-	  - vibrate #=> if you want to enable vibrate in your push messages
-
-Next, your RhoConnect application should be running on a network that is accessible to your device. For example, you might have your RhoConnect application running on a LAN with IP 192.168.1.10, PORT 9292. Then make sure your device is connected to the same LAN and setup your application [rhoconfig.txt](configuration#run-time-configuration) syncserver as follows:
-
-	syncserver = 'http://192.168.1.10:9292/application'
-
-Now your Rhodes application is configured to receive push messages.
-
-To handle push message in ruby code it's needed to register push callback
-
-    :::ruby
-    class AppApplication < Rho::RhoApplication
-      def initialize
-        super
-        System.set_push_notification "/app/Push/push_callback", ""
-      end
-    end
-
-Push callback set up in form of local application URL and called as callback nevermind rho_callback=1 specified in it's parameters list or not.
-There is several push message parameters that can be handled by Rhodes authomatically. These are:
-- alert
-- sound
-- vibrate
-- do_sync
-Every parameter can be specified in a push message body with its value:
-
-    :::text
-    alert=some message here&sound=alert.wav&vibrate=3&do_sync=sync_src1,sync_src2
-
-Automatic push message parameters handling takes its place in case no custom push callback or push callback returns "rho_push":
-
-    :::ruby
-    def push_callback
-    
-      # do some work here
-    
-      "rho_push"
-    end
-
-### iPhone
-<a id="iphone-push-setup"></a>iPhone PUSH support uses the Apple Push Notification Service (APNS) introduced in iPhone SDK 3.0.  In order to use the service, you will need to obtain a push-enabled provisioning profile and a server-side push certificate used for encrypting RhoConnect->APNS traffic.
-
-In case of iPhone, regardless of the operation, the user will be presented with the option to activate the application if it is not running.
-
-**NOTE: For testing push, you will need to build and deploy your application to a physical iPhone (or iPad) device. Apple does not support testing push on simulators.**
-
-#### Setup Push Certificate
-The first step to setting up your environment is to create an APNS push certificate. To create the SSL certificate, follow the "Creating the SSL Certificate and Keys" section on the 
-[developer site](https://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ProvisioningDevelopment/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW4).
-
-Once you have the certificate, you will need to export it to a .pem format using [these instructions](https://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ProvisioningDevelopment/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW6). Make sure to name the output file 'apple_push_cert.pem' file from these instructions, since this is what we configured in our RhoConnect application.
-
-Once you have this file, copy it to your RhoConnect application directory under the settings folder:
-
-	:::term
-	$ cd myrhoconnectapp
-	$ cp /path/to/apple_push_cert.pem settings/apple_push_cert.pem
-
-Now your RhoConnect application is ready to send APNS messages.
-
-#### Setup Provisioning Profile
-Next, you can setup your Apple Push Provisioning Profile using Apple's [developer site instructions](https://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ProvisioningDevelopment/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW5).  Once you have the profile installed in XCode and on your test device, you are ready to test push.
-
-#### Setup iPhone Device
-Setting up the device is the same process as [building any normal Rhodes application](build#build-for-iphoneipad). When you start the application, make sure to also open the console window (cmd-shift-R). When the application starts, you should see some output in the console that shows the device token (towards the top):
-
-	2010-08-19 10:14:22.627 rhorunner[1486:307] Device token is <10fd92ab fa8ee481 55d9af6e 73290863 22b323fd 0d18fdbd 19e92d03 c0fef7c8>
-
-This confirms that your application is running with push enabled. Once you login to the RhoConnect application and sync, you will see the device registered on the RhoConnect console under the user id you used to login. Now you are ready to [test push from your RhoConnect application](/rhoconnect/push-server-setup#testing-push-in-the-rhoconnect-web-console).
-
-#### Alert Audio File Setup for iPhone
-In case of iPhone, audio files for the push alert should be placed in the `/public/alerts` folder and build script will copy them into root of the application main bundle (iPhone wouldn't play file from any other place).
-
-### Android
-<a id="android-push-setup"></a>Android PUSH support uses the Android Cloud to Device Messaging (AC2DM) system introduced in Android 2.2 (Froyo). In order to use the service, you will need to register your role-based google account (or use existing one) and then register this account in [Google C2DM program](http://code.google.com/android/c2dm/signup.html).
-
-Here are some guidelines for developing and testing an Android application that uses the C2DM feature:
-
-* To develop and test your C2DM applications, you need to run and debug the applications on an Android 2.2 system image that includes the necessary underlying Google services. 
-* To develop and debug on an actual device, you need a device running an Android 2.2 system image that includes the Market application. 
-* To develop and test on the Android Emulator, you need to download the Android 2.2 version of the Google APIs Add-On into your SDK using the Android SDK and AVD Manager. Specifically, you need to download the component named "Google APIs by Google Inc, Android API 8". Then, you need to set up an AVD that uses that system image.
-* Android C2DM system uses an existing connection for Google services. This requires users to set up their Google account on their mobile devices (and on emulator!).
-
-#### Setup application
-As first step, register role-based google account for your application. Here for example it will be referred as push-app@gmail.com.
-
-Then modify your application's build.yml and specify there google account used to send PUSH messages:
-
-	:::yaml
-	android:
-	  push:
-	    sender: push-app@gmail.com
-        
-
-This is the same address used by RhoConnect to retrieve authtoken. See [here](/rhoconnect/push-server-setup#testing-push-in-the-rhoconnect-web-console) for more information.
-
-**NOTE: WARNING! This e-mail address MUST NOT be the same as origin of google account on phone! This mean that google account registered on your phone/emulator MUST NOT be push-app@gmail.com; it MUST be another one. This is known bug in Android C2DM implementation - if sender and receiver are the same, underlying android service crash and lose message. More details [here](http://groups.google.com/group/android-c2dm/browse_thread/thread/128790789c4e9d6a/67aca1e1764724d4). This is actual not for all Android versions.**
-
-At Android it is possible to set up status bar notifications for PUSH messages. In this case push message is handled by application only after user has opened the notification.
-There are two modes available for push notifications:
- - <i>always</i> - push notification is shown always
- - <i>background</i> - push notification is shown only if application is backgrounded (not started)
-If no push notification mode is specified in build.yml then no notifications are shown at all.
-
-	:::yaml
-	android:
-	  push:
-	    notification: background
-
-### BlackBerry
-<a id="blackberry-push-setup"></a>Notifications to BlackBerry are sent using PAP 2.0 message through a BES/MDS server.
-
-On the simulator, this is done via the MDS simulator tool (which you've probably already seen in the form of a console window everytime you do 'rake run:bb'). On the device, this is done through the BES/MDS server that the phone is configured to use.  
-
-These instructions assume you are familiar with BES/MDS concepts (for more information please see [here](http://na.blackberry.com/eng/services/business/server/full/)).
-
-In case of Blackberry, if the application is in the background, an alert operation will bring the application upfront; other operations will not. 
-
-#### Setup MDS Simulator
-<i>Make sure you close the BlackBerry simulator and MDS simulator before continuing for your changes to take effect!</i>
-
-To enable the push port in your MDS simulator, edit the following file:
-
-	C:\Program Files\Research In Motion\BlackBerry JDE <VERSION YOU ARE BUILDING>\MDS\config\rimpublic.property
-
-Uncomment the last line of the file, which should be 'push.application.reliable.ports=100':
-
-  push.application.reliable.ports=100
-
-#### Setup BlackBerry Simulator
-To listen for incoming messages on BlackBerry, the Rhodes application will start when device powers on and will run a listener thread in the background. You will use the "push_port" option in the [rhoconfig.txt](configuration#run-time-configuration) to specify the listening port for incoming push messages. If "push_port" is not specified, default will be 100 as shown in the previous section.
-
-**NOTE: For testing push, the BlackBerry simulator requires a 'kickstart' process.  When the simulator starts, open the web browser on the simulator and navigate to any web page (i.e. http://m.google.com/). Now your simulator is ready to receive push messages.**
-
-Now you are ready to [testing Push in the RhoConnect Web Console](/rhoconnect/push-server-setup#testing-push-in-the-rhoconnect-web-console).
-
-#### Setup BlackBerry Device
-To test push on a BlackBerry device, you will need to use a device that is configured with a BES server. Then, all you need to do is [build your Rhodes application for the device](build#build-for-blackberry).
-
-#### BlackBerry 5.0 Push service
-Rhodes 2.2 and higher support new [Blackberry Push Service](http://na.blackberry.com/eng/developers/javaappdev/pushapi.jsp)
-
-Define in [rhoconfig.txt](configuration#run-time-configuration) which push to use (if empty or missed only MDS push is supported).	
-
-	push_options = 'mds;push_service'
-
-These parameters from [PushApplicationDescriptor](http://www.blackberry.com/developers/docs/5.0.0api/net/rim/blackberry/api/push/PushApplicationDescriptor.html). Set them in [rhoconfig.txt](configuration#run-time-configuration):
-
-	push_service_url  = 'https://pushapi.eval.blackberry.com/'
-	push_service_port = 20558
-	push_service_appname = 'RhoTest'
-	push_service_type = 'BPAS'
-
-#### Alert Audio File Setup for Blackberry
-In case of Blackberry, if the audio file is in the public folder, the file name will be `/apps/public/alerts/test-file.mp3`.
-
-### Push Callback
-Rhodes applications can also handle PUSH notifications that didn't come from a RhoConnect application. 
-
-In this example, we will get the device ID so we can register the device with some push server:
-	:::ruby
-	System.get_property('device_id')
-
-Application can set push callback to process any commands from server:
-	:::ruby
-	System.set_push_notification("/app/Settings/push_notify", '')
-
-Callback parameters:
-
-* since Rhodes 2.0.4 : contain push message parameters as hash
-* rhodes  < 2.0.4 : message - contain server push message body
-
-Callback return:
-
-* empty string - do not run Rhodes push command processing
-* "rho_push" - to run rhodes push command processing (for alerts, sounds, etc...)
-
-Example:
-	:::ruby
-	def push_notify
-	  puts 'push_notify: ' + @params.inspect  
-	  "rho_push"
-	end
-
-### Push Payload
-The Rhodes push payload allows more than one operation in a single message. 
- 
-There are no required operations. There are default operations - if operation is not specified, no default operation will be performed.
-
-Payload may include following operations which client will perform when it receives the PUSH message:
-
-do_sync - do sync on spec specified sync source; use "all" to sync all sources  
-	:::ruby
-	# one or more sources, or "all" can be specified
-	do_sync = "Product,Customer" 
-
-alert - bring app upfront and show specified message
-	:::ruby
-	alert = "Some message"
-
-vibrate - vibrate for the specified number of milliseconds, up to 25500; if 0 or no duration is specified, it will vibrate for 2500 millisecond.
-
-To enable vibrate in your rhodes application in build.yml:
-
-	capabilities:
-	 - vibrate
-    	  
-Example of vibrate call:
-     
-	vibrate = 2000 #=> duration in milliseconds
-
-sound - play specified file if media type supported by the phone. iPhone will ignore media-type parameter.
-	:::ruby
-	sound = "hello.mp3"
-
-File should be included to the application bundle in `/public/alerts` folder.
-
-Media type should be either specified explicitly or may be recognized from file extension. Known file extensions are: .mp3 - audio/mpeg; .wav - audio/x-wav.
+Push notification support is currently available for Android, BlackBerry, iOS, and RoConnect Push Service on Android and Windows Mobile. Please refer to [RhoConnect Device Push](/rhoconnect/push) for information on setting up RhoConnect Push on the RhoConnect server and the Rhodes client.
 
 ## Alerts
 
@@ -1359,14 +1113,14 @@ Popup window always close after clicking on any button.
 	* :question - '?' icon
 	* :info - informational icon
 * :buttons - array of buttons for popup window. Each button defined by its id and title. Button can be specified by Hash with :id and :title keys or just String - in this case both id and title will be set to this value.
-* :callback - url to be called when any of the button will be clicked. This callback will be called with @params hash containing three keys: :button_id, :button_title and :button_index.
+* :callback - url to be called when any of the button will be clicked. This callback will be called with @params hash containing three keys: button_id, button_title, and button_index.
 
 Example:
 	:::ruby
 	def on_dismiss_popup
-	  id = @params[:button_id]
-	  title = @params[:button_title]
-	  index = @params[:button_index]
+	  id = @params['button_id']
+	  title = @params['button_title']
+	  index = @params['button_index']
 	  if id == 'Yes'
 	    # Handle 'Yes' button
 	  elsif id == 'No'
@@ -1464,7 +1218,7 @@ It is possible to customize the URI with build.yml settings. Default Rhodes URI
 - host name
 - path prefix
 - optional path and query
-You can customize sheme and host name parts with following build.yml parameters:
+You can customize scheme and host name parts with following build.yml parameters:
     :::ruby
     android:
         URIScheme: myapp
@@ -1513,7 +1267,7 @@ In application you can get start params by
 
 For previous example start params will be "string_with_params".
 
-For execute you rhodes based application from enother rhodes based application use next code:
+For execute you rhodes based application from another rhodes based application use next code:
 	:::ruby
 	System.open_url('myapp:string_with_params')
 
@@ -1540,14 +1294,14 @@ MapView class provides an embeddable map interface, similar to the one provided
 
 Provider:
 
-There are two providers supported now - 'Google', 'ESRI', "RhoGoogle" and "OSM". 
+The supported providers are 'Google', 'ESRI', "RhoGoogle" and "OSM". 
 
 * 'Google' supported on iPhone, Android and BB. 
 * 'ESRI' supported on iPhone, Android, BB and WM. 
-* 'RhoGoogle' own GoogleMap provider based on Google Static Map API. Have additional features (offline caching for example).  Supported on Android and WM
-* 'OSM' - Open Street Map, support only 'roadmap' map type.   Supported on Android and WM
+* 'RhoGoogle' own GoogleMap provider based on Google Static Map API. Has additional features (offline caching for example). Supported on Android and WM.
+* 'OSM' - Open Street Map, supports only 'roadmap' map type. Supported on Android and WM.
 
-For use ESRI maps in your projects on iPhone:
+To use ESRI maps in your projects on iPhone:
 
 * Install [ESRI iOS SDK](http://resources.arcgis.com/content/arcgis-iphone/api) - use default folders during installations !
 * Add "esri" to your applications extensions list in build.yml file.
@@ -1574,14 +1328,14 @@ Map settings:
 	* [latitude,longitude,latitudeDelta,longitudeDelta]. The area currently displayed by the map view. The region encompasses both the latitude and longitude point on which the map is centered and the span of coordinates to display. The span values provide an implicit zoom value for the map. The larger the displayed area, the lower the amount of zoom. Similarly, the smaller the displayed area, the greater the amount of zoom. 
 		* latitude,longitude - map coordinate of the region center
 		* latitudeDelta - the amount of north-to-south distance (measured in degrees) to display on the map. Unlike longitudinal distances, which vary based on the latitude, one degree of latitude is always approximately 111 kilometers (69 miles).
-		* longitudeDelta - the amount of east-to-west distance (measured in degrees) to display for the map region. The number of kilometers spanned by a longitude range varies based on the current latitude. For example, one degree of longitude spans a distance of approximately 111 kilometers (69 milies) at the equator but shrinks to 0 kilometers at the poles.
+		* longitudeDelta - the amount of east-to-west distance (measured in degrees) to display for the map region. The number of kilometers spanned by a longitude range varies based on the current latitude. For example, one degree of longitude spans a distance of approximately 111 kilometers (69 miles) at the equator but shrinks to 0 kilometers at the poles.
 	* {:center => center, :radius => radius}. Another way to define area displayed by the map view.
 		* center - string describing center of area. Can be any string allowed by google geocoding service. Examples: "1 infinite loop, cupertino, ca 95014", "California, USA", "37.365519,-121.982918"
 		* radius - radius of displayed area measured in degrees
 * zoom_enabled - true if zoom of the map is enabled
-* scroll_enabled - true if scrool of the map is enabled
+* scroll_enabled - true if scroll of the map is enabled
 * shows_user_location - true if current user location is displayed on the map 
-* api_key - Maps JavaScript API Key ([sign up for it here](http://code.google.com/apis/maps/signup.html)). Note that this parameter is ignored on Android! For Android you should get another key and specify it in the app's build.yml as described [here](build#Prerequisites_5)
+* api_key - Maps JavaScript API Key ([sign up for it here](http://code.google.com/apis/maps/signup.html)). Note that this parameter is ignored on Android! For Android you should get another key and specify it in the app's build.yml as described [here](build#build-for-android)
 
 Annotations - array of map annotation objects (list of pins on the map). Annotation:
 
@@ -1636,13 +1390,13 @@ See GeoLocation/controller.rb of [system API sample application](http://github.c
 	  apps         #Rho::RhoApplication::get_base_app_path
 	    app        #Rho::RhoApplication::get_app_path('app') - contain models
 	      model1   #Rho::RhoApplication::get_model_path('app','model1')
-	  public       #contains files from application public folder
-	  db           #contains schema and data files
-	    db-files   #contains files stored in database(blobs)
+	    public     #contains files from application public folder
+	    db         #contains schema and data files
+	      db-files #contains files stored in database(blobs)
 	               # for file paths from camera callback etc: Rho::RhoApplication::get_blob_path(relative_file_path); 
 	               # to create file path for blob: Rho::RhoApplication::get_blob_folder()
-	  lib          #contains rho framework library files. Blackberry does not has this folder, library files are stored in jar
-	  RhoLog.txt   #application log
+	    lib        #contains rho framework library files. Blackberry does not has this folder, library files are stored in jar
+	    RhoLog.txt #application log
 
 ### Read\write file example
 	:::ruby	
@@ -1696,7 +1450,7 @@ Application can creates folders and files under apps and db roots.
 	               # for file paths from camera callback etc: Rho::RhoApplication::get_blob_path(relative_file_path); 
 	               # to create file path for blob: Rho::RhoApplication::get_blob_folder()
 
-On iOS platform only files stored in /Documents/ bakuped in iCloud etc.
+On iOS platform only files stored in /Documents/ backup in iCloud etc.
 Before Rhodes 3.3.2 all files stored in /Documents/ but Apple require do not placing files in Documents folder except user produced files. 
 Now all files except databases stored in /Library/Caches/Private Documents/ - files in this folder do not bakup.
 If you want make any files should be bakup - use "user folder" for it - Rho::RhoApplication::get_user_path. All you files created in old version in Rho::RhoApplication::get_base_app_path now should be open in Rho::RhoApplication::get_user_path.
@@ -1719,8 +1473,8 @@ Also there are few additional parameters in build.yml (use it only if you want t
 	f.write('my own file !')
 	f.close  
 
-Also you can set special iOS attiribute "do not bakup" to any files or folders or files related to database :
-### setup "do not bakup" attribute for files related database conaint Model 'Product'
+Also you can set special iOS attribute "do not bakup" to any files or folders related to database :
+### setup "do not bakup" attribute for files related database Model 'Product'
 	:::ruby
 	require_model 'Product'
 	db = Rho::RHO::get_src_db('Product')
@@ -1728,13 +1482,10 @@ Also you can set special iOS attiribute "do not bakup" to any files or folders o
 
 
 #### Windows Mobile
-Device/simulator files folder root - Program Files/<app name>/rho
-
-#### Desktop win32 simulator
-To use client with the HTTP proxy you should pass its URL as the first command line argument `-http_proxy_url=http://<login>:<passwod>@<host>:<port>` or add it to rhoconfig.txt.
+Device/simulator files folder root - Program Files/&lt;app name>/rho
 
 ## Shutdown hook
-Like any application written in Ruby, rhodes can register a shutdown hook. Shutdown hook is routine registered for execution when the program exits. It usefull for cleanup on exit, saving program states, etc. To create you own shutdown hook you should add at_exit block to the file application.rb. 
+Like any application written in Ruby, rhodes can register a shutdown hook. Shutdown hook is routine registered for execution when the program exits. It useful for cleanup on exit, saving program states, etc. To create you own shutdown hook you should add at_exit block to the file application.rb. 
 For example:
 	:::ruby
 	at_exit do
@@ -1768,7 +1519,7 @@ To make phone calls enable the phone capability. This is done by adding the foll
 	<a href="mailto:test@host.com?subject=testing123">Mailto</a>
 Note, even for an empty address, you must add the @ symbol: <a href="mailto:@?subject=testing123">Mailto</a>
 
-Blackberry: if you need cc, bcc feilds, use rhomailto scheme:
+Blackberry: if you need cc, bcc fields, use rhomailto scheme:
 	:::html
     <a href="rhomailto:test@host.com?cc=geny@mail.ru&bcc=vasy@gmail.com&body=testMessage&subject=sub1">Send e-mail to test@host.com</a>
     
@@ -1798,7 +1549,7 @@ When using jQuery and/or jQuery Mobile in application code, you cannot use usual
     #TestController method:
     def send_mail
         WebView.navigate( 'mailto:test@host.com' )        
-        #to open url inexternal application you can use System.open_url
+        #to open url in external application you can use System.open_url
     end
 
 ### Blackberry
@@ -1901,7 +1652,7 @@ Blackberry 5.0 and above has new BrowserField class, which support javascript, a
 
 WebView.execute_js is also supported in this mode.
 
-NOTE: on Blackberry 6.0 and above it is recommended to use full browser mode. Because overwise some UI elements like combobox is not selectable by trackball:
+NOTE: on Blackberry 6.0 and above it is recommended to use full browser mode, because otherwise some UI elements like combobox are not selectable by trackball:
 
 	# use full browser only on BB 6.0 and above
 	use_bb_full_browser=6