This is an informative response. That paragraph there from Kevin Duffey hit on the concepts that I was trying to solidify regarding the architecture that the Android SDK lives within.
> However, if you are trying to figure out if you can just take any exectuable > app like jboss/tomcat and run it as is on the phone..the answer is no. The > Android framework would require at a bare minimum an Activity of some sort.. > from there you could launch a service and then with some work get it to run. > Likewise for other libraries that have executable code... let's say a Swing > app, you would still have to redo the UI to work under Android, as it's a > different set of UI apis for Android. If you had a library that does > unzipping, or an image codec, you could make use of those, most likely with > no changes unless they have some native/JNI stuff in them.. but even then I > don't know for sure that you wouldn't run in to some issues. They could for > example utilize some JDK code that isn't supported on the Dalvik jvm as it's > not a full J2SE implementation. Swing code, I think applet code, Corba, > stuff like that I don't believe exists in the Android SDK.
-- 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
