Archive for the ‘phonegap’ Category
iOS PhoneGap – Splash screen control
Unfortunately a splash screen is still needed to hide the white flash that is visible just before the UIWebView loads its content. Previously before PhoneGap 1.0, you had no control over this – sometimes your content just takes an extra time to load and you want to control the duration of the splash screen.
There are two steps to enable this, firstly – in PhoneGap.plist, change the value for “AutoHideSplashScreen” to false (by default it is true for legacy code). This will not hide the splash screen, and it will remain on screen indefinitely.
Next, in your code, you will have to explicitly hide the splash screen.
After the deviceready event has been fired, you can call this function anytime you are ready:
navigator.splashscreen.hide();
If you want to just delay hiding the splash screen for 2 seconds for example, you can do this in your deviceready event handler:
setTimeout(function() {
navigator.splashscreen.hide();
}, 2000);
PhoneGap Xcode 4 Template (beta)
UPDATE: PhoneGap 0.9.5.1 includes the Xcode 4 template now, download it from phonegap.com
View the screencast below (best in full-screen, in HD).
Also, you can read the wiki article.
Xcode 4 template specs are undocumented and buggy. So, there are issues:
- We cannot automatically include the “www” folder in the template – the user has to add it in manually (a quick drag and drop). I added in checks and warnings if users try to run the app without adding this in.
- Some files, like .h and the -Info.plist file, are included in the ‘Copy Bundle Resources’ build phase by the template. No biggie during run-time, but for those with OCD they will want to remove these from the Build Phase (if only to get rid of the warning).
- Because Xcode 4 does not expand tildes (~), I cannot add a reference to the PhoneGap.framework in the user’s home folder, so I added it to a shared location /Users/Shared which has r+w permissions for everyone (the common folder /Library/Frameworks needs admin privileges). It was added here so users without admin privileges can still use PhoneGap.framework, and by extension, the Xcode 4 Template.
RELEASE NOTES
- beta1 – Initial release
- beta1.1 – Bug fix for issue #81 (moved framework from /Users/Shared/Library to /Users/Shared/PhoneGap)
- beta1.2 – Made /Users/Shared/PhoneGap writable to everyone
- beta1.3 – Fixed Template not copying over the ‘www’ directory from the framework location (happened only for users that only installed beta1.3 and didn’t migrate from an earlier beta version). This version was tested on a clean Mac OS X 10.7 Lion DP3 system running Xcode 4.1 DP5, and works great.
- beta2 – (UPCOMING) add AppleScript in the project Run Script build phase to get Xcode to automatically add the ‘www’ folder for you
Creating a PhoneGap project from the command line (for Xcode 4)
UPDATE: PhoneGap 0.9.5.1 includes the Xcode 4 template now, download it from phonegap.com
Currently the PhoneGap installer for iOS does not create an Xcode 4 template. The issue is tracked here.
I’ve created a shell script to create a PhoneGap project from the command line. You will still need PhoneGapLib installed – download the installer from http://phonegap.com and run it first.
Instructions are in the shell script itself (open it up in a text editor). View the script, then File -> Save As… to save it.
Cameron Perry has a good post about using PhoneGap with Xcode 4 that might solve some problems users might have.
UPDATE:
Nitobi is providing a web service to generate Xcode templates for PhoneGap-based projects.
iOS Keychain Plugin for PhoneGap
So what is the Keychain? It’s a framework to store data (particularly passwords) securely on Mac OS X and iOS. You really don’t want to store passwords and other sensitive information in HTML5 local or web storage. This is a PhoneGap plugin for iOS that provides access to the Keychain through Javascript. Based on Buzz Andersen’s work – namely SFHFKeychainUtils
View the README and check out the sample app’s index.html for usage. Play around with the Get, Set, and Remove examples, should be self-explanatory.

PayPal Plugin for PhoneGap iPhone
First release of the PayPal Plugin for PhoneGap iPhone. Right now it handles static payments only (no dynamic changes to include shipping etc). Thanks to Chris Booth of Signature Digital in the UK for sponsoring development and also allowing it to be released to the PhoneGap community.
Nothing much to look at in the first screenshot, but with CSS styling and using PayPal’s official web button images it can look better. View the README and check out the sample app’s index.html for usage. Triggering the “Pay” button will launch the native workflow in the second screenshot.


PhoneGap iAds Plugin
Hey its a new plugin for PhoneGap. I call it the “PhoneGap AdPlugin”, and even though it only supports iAds currently, there is potential for supporting the other ad networks as a backup to iAds. Make sure you read the RELEASE NOTES in the README for limitations.
Get the source and view the README
Below are screenshots from the test app included, called ‘iAdHost’
PhoneGap Mobile Spec tests on iPhone
Fil who has been working on the Mobile Spec came over and we tested the mobile spec on the current (EDGE) version of iPhone PhoneGap, and the tests look pretty sweet (see video).
It was pretty easy, I created a new Phonegap-based Application from the Xcode template, plopped in the contents of the Mobile Spec, and just ran the app in the iPhone Simulator. In this session, we see that iPhone PhoneGap passes 51 out of 64 tests, for a 79% pass rate.
Contributing to iPhone PhoneGap – Part 1
[update: do not modify the core, instead create a plugin and add it into your app project. See PhoneGap Plugins for examples]
There has been a major re-factoring of the iPhone PhoneGap codebase, to better enable users to get a current version of PhoneGap to use in their projects without mucking about in the core PhoneGap code.
You can view the code here: http://github.com/phonegap/phonegap-iphone
The README has more details, and I will elaborate on it more here, especially on how contributors can add to the code.
PhoneGapLib/javascripts/core This is where you will add/modify your javascript code for PhoneGap core. You can add more javascript files here, but make sure you update the “PhoneGapLib/Makefile” file to include the newly added javascript file. For adding the file in the Makefile, the pattern should be obvious.
PhoneGapLib/Classes This is where you will add/modify your Objective-C code for PhoneGap core. You can add more Objective-C files here, but make sure you add it to the PhoneGapLib Xcode project also.
PhoneGapLib/javascripts/phonegap.js This is dynamically generated, and is generated whenever PhoneGapLib is built. You can update this file by running “make” in the PhoneGapLib folder, but generally it should be called in your application that includes PhoneGapLib (which the PhoneGap-based Application Xcode template does).
I will walk you through how to add a new command, by adding Application Preferences support. Download the files here.
Preferences.h
@interface Preferences : PhoneGapCommand {
}
- (void) boolForKey:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options;
// other functions here
@end
Note that the class inherits from PhoneGapCommand. The class name you use here is important, since you will be referring to it in javascript.
To ‘expose’ a function to javascript, it must have the signature from the example ‘boolForKey’ method above (first argument is a NSMutableArray, the second argument is a NSMutableDictionary).
Let’s now look at the javascript command to access the function above.
preferences.js
function PreferencesManager() {
}
var g_Preferences = new PreferencesManager();
PreferencesManager.sharedPreferences = function() {
return g_Preferences;
}
PreferencesManager.prototype.boolForKey = function(key, callback) {
PhoneGap .exec("Preferences.boolForKey", key, GetFunctionName(callback));
}
The important line is the “PhoneGap.exec” line. The first argument to PhoneGap.exec is in the form of [className].[methodName] (refer to Preferences.h to see the corresponding function which should be obvious). The next arguments to PhoneGap.exec are two strings, which will be passed into the “boolForKey” method in the NSMutableArray which is the first argument. If an object (json object) is passed in as an argument to PhoneGap.exec, that data will be passed into the “boolForKey” method in the NSMutableDictionary which is the second argument.
Preferences.m
- (void) boolForKey:(NSMutableArray*)arguments withDict:(NSMutableDictionary*)options {
NSUInteger argc = [arguments count];
if (argc > 2) { // no key and/or callback - just return, no point in continuing
return;
}
NSString* key = [arguments objectAtIndex:0];
NSString* callback = [arguments objectAtIndex:1];
NSUserDefaults *userDefaults = [NSUserDefaults standardUserDefaults];
BOOL value = [userDefaults boolForKey:key];
NSString* retVal = value ? @"true" : @"false";
NSString* jsString = [[NSString alloc] initWithFormat:@"%@('%@', %@);", callback, key, retVal];
[webView stringByEvaluatingJavaScriptFromString:jsString];
[jsString release];
}
In the command itself, you can parse the arguments and options, and do whatever you need to do for your command. You can optionally write javascript back, using the method above, or the helper:
[super writeJavascript:@"alert('foo')"]
Don’t forget to add a Settings bundle file to your app as well.
Next: Adding your code to PhoneGapLib.
Create an iPhone PhoneGap application in 2 easy steps
Based on Jesse’s work on PhoneGapLib, I created a PhoneGapLib installer that will install the lib unto your computer, but most importantly, it will set a Xcode global variable to allow the PhoneGap Xcode template to work. The PhoneGapLib installer will also install a PhoneGap Xcode template.
Creating a PhoneGap iPhone project has never been easier. This way also, if PhoneGap core is updated it will not affect your code. The main parts of the code should already be checked-in (see Jesse’s post for the url). This is a work in progress. [Updated: Download a preview version]
To download the code and build the installer, go to http://github.com/phonegap/phonegap-iphone and read the README.md for build instructions. No binaries are provided at this time.
See screencast below:
The State of PhoneGap with Windows Mobile
Well there is no state really, except for the proof of concept currently (by PhoneGap contributor Jose Noheda). I was re-factoring the PoC code, and getting everything working with the PhoneGap Javascript common code. In a nutshell, PhoneGap WinMo cannot use the existing PhoneGap js [1], as js support in the IE control in WinMo is too primitive. The current IE in WinMo is based on desktop IE 4 (released in 1997) and only supports JScript 3/Javascript 1.3.
So where does this leave PhoneGap WinMo? These are the ways we can proceed:
- Have a totally separate Js codebase, based on JScript 3, for WinMo. Con: Maintenance nightmare?
- Upgrade to IE Mobile 6. This discussion has its own section, below.
- Use WebKit with Qt [5]. Pro: We can probably use Qt Webkit in Nokia phones (soon, not supported yet), because well, Nokia owns Qt. Con: Using Qt adds a 10MB overhead, minimum.
- Use our own WebKit control. Con: I don’t know how long this effort will take, and it is the riskiest.
Internet Explorer Mobile 6
IE Mobile 6 is based on desktop IE 6 (which was released in 2001) but with the IE 8 Javascript engine [2]. However, only newer (unreleased as of yet) phones will get this version, according to Microsoft [3]. Although there are development emulator images available, they are no substitute for testing on a device.
Even if we somehow get IE Mobile 6 on existing phones (with unofficial ROMs, eg through xda forums[6]), .NET code cannot take advantage of this, because Microsoft does not want to break existing compatibility with existing code that uses hosted controls [4].
Footnotes:
[1] Sample PhoneGap Javascript code that fails under IE Mobile 4 JScript http://pastie.org/485649
[2] IE Mobile 6 release blog post http://blogs.msdn.com/windowsmobile/archive/2008/11/11/internet-explorer-mobile-6.aspx
[3] IE Mobile 6 will not be available for current phones http://blogs.msdn.com/windowsmobile/archive/2008/11/11/internet-explorer-mobile-6.aspx#9063740 [All comments were deleted after the fact by MS]
[4] IE Mobile 6 will not be available in hosted controls (ie .NET WebBrowser component) http://blogs.msdn.com/windowsmobile/archive/2008/11/11/internet-explorer-mobile-6.aspx#9064039[All comments were deleted after the fact by MS]
[5] Qt toolkit http://www.qtsoftware.com/
[6] XDA Developers forum http://forum.xda-developers.com

