Changes iOSDispatcher to use iframes to dispatch events

[guidomb]

Instead of using window.location.href to trigger
the webView:shouldStartLoadWithRequest:navigationType:
in the UIWebView's delegate now it creates a new
iframe and set its source to the same URL
usend in window.location.href.

This is done because I was doing several calls to the native code and only the last one was reaching. Using iframes make it work

[tcoulter]

Hi @guidomb. Thanks for the pull request, and this sounds like a great change. I can't make the change until I test it out on the Android side, which I don't have readily available. Once I get something set up, I'll let you know. Let's keep this PR open.

Do you know what other functions were being called in native code?

Thanks again.

[guidomb]

What do you mean by "other functions were being called in native code". Maybe I didn't make my self clear. This is what was happening to me.

I had this Javascript code loaded in my index.html

(function(){

var Logger = {
  debug: function(message) {
    Jockey.send("debug", {message: message});
  }
}

Logger.debug("Message 1");
Logger.debug("Message 2");
Logger.debug("Message 3");

})();

and in the iOS side:

[Jockey on:@"debug" perform:^(NSDictionary * payload){
  DDLogDebug(@"UIWebView: %@", [payload objectForKey:@"message"]);
}];

The output on the debug console was only Message 3. That is when I thought that it may be related on how the UIWebView handles the window.location function. Doing some googling I found that the recommended way was to use an iframe. So I made the change and then all the messages were shown on the console.

[AppsIncorporated]

for info on why this is important, see: http://stackoverflow.com/questions/9473582/ios-javascript-bridge

[tcoulter]

Sorry for the late response on this. Merging. Thanks for the PR.