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
Unless you have a bunch of code for your app, I would suggest just putting the native code for the three architectures that android supports and the moment, armv5, armv7, and x86. It willl triple the size of the code portion of your apk, but 3*(a small number) is still a small number. You can do this by modifying your jni/Application.mk file, or creating it if you don't already have it, and add the line:
ReplyDeleteAPP_ABI := armeabi armeabi-v7a x86
This will compile for all three.
Note though that there's a bug with the current ndk (ndk r6), that tries to link the x86 code to the arm code. This is fixed if you get the AOSP project, source.android.com, or you can just wait until google releases r6b, which will likely have the fix. Otherwise, if you you don't want to do that, you can just leave off the x86 portion of the line for now, and release your app without x86 code in it, and push an update when the new ndk comes out. I'm not aware of many popular devices that use x86 instructions yet.
Please see Multiple APK Support in the Android documentation. This details some of the specifics of releasing multiple APKs of the same product/application.
ReplyDeleteAs for the NDK specifics, and as already mentioned, you can utilize multiple platforms / ABIs in the APP_ABI value of your Android.mk.
You can declare supports-gl-texture in your AndroidManifest.xml for each separately compiled (and re-packaged) app. This will provide Market filtering, so a single user will only see one version of your app.
ReplyDelete