On Wed, Feb 1, 2012 at 7:22 PM, awtDroid <[email protected]> wrote: > This is a large OEM app running on a custom tablet-like display, so > it's not going on the market and has nothing to do with a cellphone. >
You said that already... I'm implying that the fact it's going on your custom device shouldn't be an excuse to not read up on the API and implement it correctly with respect to the Android semantics. > Our current system uses a single exe and multiple dll's which all > create widgets from a shared widget library. So currently we can make > a change to only one of the dll's, which could change the widgets > owned by this dll, without rebuilding the exe and other dll's. With > Android everything is packaged into a single APK. Within this APK we > could have multiple jar's, however making a UI change to one of the > jars would require the whole APK be rebuilt, if I understand this > correctly. > I don't see what dlls and exes have to do with it: this has nothing to do with windows. You're writing Java code, right? Or are you using the NDK and interfacing to your .so code? Right, if you have change the libraries within the apk, you have to rebuild it. This is simply because it's java, it's statically linked to the jars in the file. An apk is just a zip file with some dalvik bytecode in it, along with some other resources... What are you needing this for, anyway? Is it that you want to have multiple processes communicating to display stuff on the screen? kris -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
