Here are my thoughts on the overall architecture of android.
Intent => The Robot is requested to do something. Activity => The Robot performs the activity requested. Loose coupling here in the sense that the activity chosen will be based on where the Robot is at the time, what it is doing, what it has done, etc. The consumer wish begets a satisfying Robotic Action of what should be. In the PC, the intent and action are unified. You click with the mouse and actions happen. On a Mobile device however, the Intent plays a more central role. The Wish (Intent) has a centrality and the action becomes the other. Hence,a mobile device becomes the remote control for your life. The Mobile Device is the Intent, it is the Wish. Everything begins with the Intent and ends with the Action, but you need a Controller in between these. So you have an Intent, Controller and Action Model. This loose coupling between Intent and Action is an essential to mobility because in an interaction with your environment, as one's location changes the only thing that may remain stable is the Intent. So, below is what I think the main building blocks of Android should be changed to. Intent Broadcast/Explicit/Implicit Controller Intent receiver/Android manifest/explicit Intent Action Activity/notification/service Intent => This is how to have the Consumer request things well. Controller => This is the shortest possible link between the Intent and Action Action => This is how the request of the Consumer is satisfied in a pleasing way. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
