This Time i want to know how to determine which button is click in UIWebView.....
appDelegate.mystring = [[NSMutableString string]init];
NSString *b
The only method I know is by implementing webView:shouldStartLoadWithRequest:navigationType
method of UIWebViewDelegate
protocol. The required steps are as follows:
1) Create a new class subclassed from NSObject named, say, MyWebViewDelegate. You can implement only that method:
-(BOOL)webView:(UIWebView*)webView
sholdStartLoadWithRequest:(NSURLRequest *)request
navigationType:(UIWebViewNavigationType)navigationType
{
NSLog(@"%@", [[request URL] relativePath]);
}
2) Create instance of delegate in your code and set it as a delegate of UIWebView before loading page:
MyWebViewDelegate *mydelegate = [[MyWebViewDelegate alloc] init];
mywebview.delegate = mydelegate;
3) And then try to debug. Try to put breakpoint inside ..sholdStartLoadWithRequest:.. method and ensure that you application stops in that breakpoint. Maybe you shold do a little redesign of you HTML webpage to achieve this. After that try to distinguish different buttons by value of request
parameter.
Inside your html code use this snippet:
<html>
<head>
<script>
function iOSNativeBridge(){
this.sendRawMessageToiOS = function(message){
// alert(message);
console.log("Message string to iOS: [" + message+ "]");
var iframe = document.createElement("IFRAME");
iframe.setAttribute("src", "jscall://" + message);
document.documentElement.appendChild(iframe);
iframe.parentNode.removeChild(iframe);
iframe = null;
};
}
bridge = new iOSNativeBridge();
</script>
</head>
<body>
<a href="javascript:bridge.sendRawMessageToiOS('your message');">link</a>
<input type="button" value="button val" name="button" id="1" onClick="javascript:bridge.sendRawMessageToiOS('your message');">
</body>
</html>
on native side, in uiwebview's delegate method:
- (BOOL)webView:(UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:(UIWebViewNavigationType)navigationType {
NSString *jsCallPrefix = @"jscall://";
NSString *fullURLRequested = request.URL.absoluteString;
BOOL isJavaScriptCall = ([fullURLRequested hasPrefix:jsCallPrefix]);
if (isJavaScriptCall) {
NSString *messageConveyed = [fullURLRequested substringFromIndex:jsCallPrefix.length];
NSLog(@"Your message was: %@", messageConveyed);
return NO;
}
return YES;
}
With regards to the code on web side - I don't juggle with this dynamically created iframe without a reason. At first glance, it would seem sufficient just to change the location on webview's page (call document.location.href = "jscall://message"). The worst thing is, that is actually seems to work great. Unfortunately, if you take this shortcut, JS timers are messed up greatly. So take my advice - use this little, weird-looking, but working without any side-effects "sendRawMessageToiOS" as is :)
Little more in-depth description of what's going on in the above code: In the web-code, whenever I want to push some data to the native-side of my app, I call sendRawMessageToiOS(dataInStringToSend). It creates an iframe, adds it to the DOM tree and sets it's location to be "jscall://" + dataInStringToSend Then, as expected, the uiwebview's delegate is asked, whether or not I'm willing to start the request to download a content from a given address. I check if it's actual address (and return YES then) or only this masquerade with special "jscall://" prefix. If it is this special call, I read data that's conveyed with it, and respond NO (because webview should not try to start any real request).