SCWB and iOS 4 Development for Legacy Devices
- Author:
Vanish
00:00:00 - 0Comments
• iPhone Dev
When we originally developed SCWB, we had to suppress the default keyboard so we could provide our own with the custom buttons necessary to do what the app needs to do. iOS 3.2 threw us a bit of a curveball. It happened again with iOS 4.
In iOS 3.0.x thru 3.1.x it was a bit of a hack. With the release of iOS 3.2 for the iPad, Apple decided to change how that hack had to work, so we scrambled (and by we, I mean Develish) to find a new hack. We got that corrected ahead of the release of the iPad. With the release of iOS 4, Apple changed this once again, but in a good way. They actually provided an accepted method to suppress the keyboard. Very cool. We again were ready in time for the release of iOS 4. What is not so cool, is the troubles this led to in updating the app on some iPads (We still can't figure out why it worked on some and not on others. No common thread at all) and legacy devices, like the iPod Touch 1G.
There has been a considerable amount of crap being flung about the relevance of the iPad, it's name, it being yet another device that refuses Flash, etc. I'm getting tired of repeating myself, so here in somewhat of a nutshell, is my take on it.
Read on for the lengthy nutshell. ;)
Yes, it is true that Snow Leopard comes with these critical web development tools pre-installed, however the installations are at the mercy of Apple's system updates. Customizing them with extra libraries, etc. has been known to be an effort in futility as they are automatically "updated".
