You'd probably get a better answer in the developer forum, but here's my understanding from http://developer.android.com/guide/topics/fundamentals.html#procthread. Activities have 1 process (and in fact 1 thread). If you have a long operation in a View, your activity will be blocked. That is why the documentation recommends spawning a new thread and using handlers to process long operations.
On Jul 16, 2:14 pm, FwAnK <[email protected]> wrote: > Thanks but that's not really what I was looking for. > > My question concerns how Android works under the hood. Are activities > rendering their UI's directly from their own process? Or is there a > core process that handles all rendering for each activity (by way of > proxy UI objects perhaps). I want to learn more about how Android > actually works, not so much the API's here... > > Can anyone point me the right way please? > > -F > > On Jul 16, 10:53 am, lbcoder <[email protected]> wrote: > > > > > look under android:process ... > > :http://developer.android.com/guide/topics/manifest/application-elemen... > > > On Jul 16, 12:40 pm, FwAnK <[email protected]> wrote: > > > > ...or are *activity* GUI components actually just proxy objects that > > > are communicating to their respective real GUI objects that reside > > > somewhere in a core Android process? > > > > Just curious. I'm wondering how multiple JVM processes (referring to > > > activities here) are able to share a common GUI window. > > > > -F --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
