The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
Since you would like to have your new application work on both the iPhone and iPad please use Flurry's iPhone SDK.
ReplyDeleteIf you have an application that is only meant to work on the iPad please use Flurry's iPad SDK.
I think the iPhone 4.0+ SDK may work properly on iPad. I have this address where you can ask directly to Flurry Support, they always give me an answer to my questions.
ReplyDeleteFlurry iPhone/iPad Support
iphonesupport@flurry.com
With the latest 3.0.7 Flurry SDK version both libraries and headers are identical (tested with md5). Looks like they have merged both branches, possibly as of the 3.0 version. They should make that clear by releasing a common iOS SDK but the answer to your question is now clear: either one will do.
ReplyDeleteI don't think there is a difference in the Flurry library, they are the same for iPhone and iPad. I think the only difference is when you first set up an application, it asks what platform you're targeting, perhaps just for their own metrics.
ReplyDelete