uiwebview

I am using an Cordova 2.4 component Cleaver and an embedded view in my native iOS 6 application. So far I have managed to create the project structure, link the Cordova libraries and set up the Hello World app that does work providing "Device Ready" feedback. This is all great but it loads all html from the www repository distributed inside the app itself (including all js libraries). What I really want yo do is this: 1 - popup the cleaver component (which is nothing else than an embedded uiwebview) in my app. Easy - done. 2 - load some html content from a URL pointing to a servlet on my

Here's my issue: I am using the phonegap framework to develop a hybrid app, and I need this application to have graphs for which I had decided to use the highcharts library. The problem is that I can't seem to be able to scroll after touching on the chart (at least while touching inside the selected portion of the image). What I want to do is prevent the chart from taking any events and show a plain graph with anything being highlighted and be able to scroll even if im doing it over the graph. Code: chart1 = new Highcharts.Chart({ chart: { renderTo: 'containerBar', animation: false, type: 'bar

It seems to be really hard to improve the performance of a UIWebView, especially for websites like Mashable or Ars Technica, where tons of scripts are loaded and long, multi-page articles are common. I'm aware of 3 similar questions, but they both have no working solution: UIWebView scrolls jerkily - private API calls like -(void)_setDrawInWebThread:(BOOL)arg1 and -(void)_setDrawsCheckededPattern:(BOOL)arg1 are suggested, and we know that they aren't allowed in App Store apps How to get fast, smooth scrolling with UIWebView? - someone talked about CATiledLayer, but there was no clear pointer

everyone. I'm trying to get all image urls of the current page in UIWebView. So, here is my code. - (void)webViewDidFinishLoad:(UIWebView*)webView { NSString *firstImageUrl = [self.webView stringByEvaluatingJavaScriptFromString:@"var images = document.getElementsByTagName('img');images[0].src.toString();"]; NSString *imageUrls = [self.webView stringByEvaluatingJavaScriptFromString:@"var images= document.getElementsByTagName('img');var imageUrls = "";for(var i = 0; i < images.length; i++){var image = images[i];imageUrls += image.src;imageUrls += \\’,\\’;}imageUrls.toString();"]; NSLog(@

I'm kind of new in objective c, but I'm developing an app which has a UIWebView that loads some web content. All the web pages require client certificate for authentication and I'm struggling with it for dew days. Does anyone know the flow how to implement it in UIWebView? Thanks! To avoid any problem in the UIWebView, you have to make a reques to you website root, with the client certificate, before the request of the web view. You can use the UIWebViewDelegate method: -(BOOL)webView:(UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:

I have an iPhone app with an embedded UIWebview (Safari) control. I'd like to be able to store the images from certain webpages locally. Can I programmatically access the path where UIWebview downloads images? Or do I need to parse the HTML and then go find the image resource out on the net and download it again? I do not know if you can access the preloaded images from Safari's cache... However you can easily find the image URLs without parsing HTML, by running a bit of javascript instead: NSString *script = @"var n = document.images.length; var names = [];" "for (var i = 0; i < n; i++) {" "

I've been working on a proof of concept app that leverages two-way communication between Objective C (iOS 7) and JavaScript using the WebKit JavaScriptCore framework. I was finally able to get it working as expected, but have run into a situation where the UIWebView loses its reference to the iOS object that I've created via JSContext. The app is a bit complex, here are the basics: I'm running a web server on the iOS device (CocoaHTTPServer) The UIWebView initially loads a remote URL, and is later redirected back to localhost as part of the app flow (think OAuth) The HTML page that the app