Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Fri, 2 Dec 2011 19:32:41 +0000 (UTC)
From: "Shazron Abdullah (Updated) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <1883167642.35633.1322854361938.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <250175736.22953.1322594860530.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CB-93) Only support iOS 4.2 and greater
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shazron Abdullah updated CB-93:
-------------------------------

    Description: 
Support iOS 4.2 going forward (in 1.4?) since it offers the most features built-in to the UIWebView: http://www.mobilexweb.com/blog/safari-ios-accelerometer-websockets-html5
On the native Objective-C side, supporting iOS 4 will also allow us to use blocks http://pragmaticstudio.com/blog/2010/7/28/ios4-blocks-1 which is a fundamental technology used in all of their framework APIs since iOS 4

Risk factors:
* Plugin problems - plugins using blocks in native code cannot be used on iOS 3. This can be mitigated with support for PhoneGap versions (as well as built in macros for iOS versions) in pre-processor macros, so this can be conditionally compiled. This can be solved with versioning in our future proposed plugin packaging
* Possibly maintaining a iOS 3.x branch at the last iOS 3.x supported PhoneGap version for bug fixes -- for those that want to still use that version -- don't really want to do this though

We stopped iOS 2.x support when iOS 4.x came out (thus, we usually only supported one version back from the current OS version).

[iPhone]
The oldest iPhone to have iOS 4.2 support is the iPhone 3G (released July 2008 - 3+ yrs old, discontinued). Current iPhone is the 4S, 3 models ahead.
[iPod Touch]
The oldest iPod Touch to have iOS 4.2 support is the iPod Touch 2nd Generation (released Sep 2008 - 3+ yrs old, discontinued). Current iPod Touch is the 4th Gen, 2 models ahead.
[iPad]
The oldest iPad to have iOS 4.2 support is the iPad 1 (released April 2010, 1+ yrs old, reportedly discontinued). Current iPad is the iPad 2, 1 model ahead.

*Essentially, we would drop device support for these models: original iPhone and iPod Touch 1st Generation*

  was:
Support iOS 4.2 going forward (in 1.4?) since it offers the most features built-in to the UIWebView: http://www.mobilexweb.com/blog/safari-ios-accelerometer-websockets-html5
On the native Objective-C side, supporting iOS 4 will also allow us to use blocks http://pragmaticstudio.com/blog/2010/7/28/ios4-blocks-1 which is a fundamental technology used in all of their framework APIs since iOS 4

Risk factors:
* Plugin problems - plugins using blocks in native code cannot be used on iOS 3. This can be mitigated with support for PhoneGap versions (as well as built in macros for iOS versions) in pre-processor macros, so this can be conditionally compiled. This can be solved with versioning in our future proposed plugin packaging
* Possibly maintaining a iOS 3.x branch at the last iOS 3.x supported PhoneGap version for bug fixes -- for those that want to still use that version -- don't really want to do this though

We stopped iOS 2.x support when iOS 4.x came out (thus, we usually only supported one version back from the current OS version).

[iPhone]
The oldest iPhone to have iOS 4.2 support is the iPhone 3G (released July 2008 - 3+ yrs old, discontinued). Current iPhone is the 4S, 3 models ahead.
[iPod Touch]
The oldest iPod Touch to have iOS 4.2 support is the iPod Touch 2nd Generation (released Sep 2008 - 3+ yrs old, discontinued). Current iPod Touch is the 4th Gen, 2 models ahead.
[iPad]
The oldest iPad to have iOS 4.2 support is the iPad 1 (released April 2010, 1+ yrs old, reportedly discontinued). Current iPad is the iPad 2, 1 model ahead.


> Only support iOS 4.2 and greater
> --------------------------------
>
>                 Key: CB-93
>                 URL: https://issues.apache.org/jira/browse/CB-93
>             Project: Apache Callback
>          Issue Type: Task
>          Components: iOS
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>             Fix For: 2.0.0
>
>
> Support iOS 4.2 going forward (in 1.4?) since it offers the most features built-in to the UIWebView: http://www.mobilexweb.com/blog/safari-ios-accelerometer-websockets-html5
> On the native Objective-C side, supporting iOS 4 will also allow us to use blocks http://pragmaticstudio.com/blog/2010/7/28/ios4-blocks-1 which is a fundamental technology used in all of their framework APIs since iOS 4
> Risk factors:
> * Plugin problems - plugins using blocks in native code cannot be used on iOS 3. This can be mitigated with support for PhoneGap versions (as well as built in macros for iOS versions) in pre-processor macros, so this can be conditionally compiled. This can be solved with versioning in our future proposed plugin packaging
> * Possibly maintaining a iOS 3.x branch at the last iOS 3.x supported PhoneGap version for bug fixes -- for those that want to still use that version -- don't really want to do this though
> We stopped iOS 2.x support when iOS 4.x came out (thus, we usually only supported one version back from the current OS version).
> [iPhone]
> The oldest iPhone to have iOS 4.2 support is the iPhone 3G (released July 2008 - 3+ yrs old, discontinued). Current iPhone is the 4S, 3 models ahead.
> [iPod Touch]
> The oldest iPod Touch to have iOS 4.2 support is the iPod Touch 2nd Generation (released Sep 2008 - 3+ yrs old, discontinued). Current iPod Touch is the 4th Gen, 2 models ahead.
> [iPad]
> The oldest iPad to have iOS 4.2 support is the iPad 1 (released April 2010, 1+ yrs old, reportedly discontinued). Current iPad is the iPad 2, 1 model ahead.
> *Essentially, we would drop device support for these models: original iPhone and iPod Touch 1st Generation*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira