From: William W. <flu...@gm...> - 2011-10-06 07:39:54
|
Hello all again, I'm curious what the limitations on XMLVM are when translating from Android to iPhone. For instance, I think I can assume that any non-native code should be translatable (even if it's been through a bytecode obfuscator or is written in another JVM language besides Java), but whether it will actually work will depend on the capabilities of the emulation layer on the receiving platform. For instance, Android preferences are sort of like Apple's property lists, but the exact capabilities are not the same. Android application lifecycle is a little different from iOS, especially if you run a service (even if the service isn't exposed through aidl). These are just examples of cases where the platforms are different in a way that is more than just the language they support. The purpose of this message is not to complain that the functionality is inadequate, but to inquire as to how I can best determine if any particular piece of functionality is present. A second question is if some functionality should turn out to not work or be missing, what's the best way to re-implement just that functionality on iOS while keeping the rest of the ported application? Will I get an error in the translation process, or some sort of stub in the generated code? |