Thanks. That helps put things in perspective. I need intents to start the components and within the components there can be various other work done etc.
On Mar 11, 4:04 am, Muthu Ramadoss <[email protected]> wrote: > Here's my 2 sec tutorial: > > Android Component 1: > Activity - the screen. > View - the widgets inside the screen. > > Android Component 2: > Service - logic running in background. > > Android Component 3: > Content Provider - data storage. > > Android Component 4: > Broadcast Receiver - code waiting to be run, triggered by matching intent. > > Intent - the trigger to start the above components. > > http://developer.android.com/reference/android/content/Intent.html > > take care, > Muthu Ramadoss. > > http://linkedin.com/in/tellibitz+91-9840348914http://androidrocks.in- Android > Consulting. > > On Wed, Mar 11, 2009 at 1:29 AM, Lovedumplingx <[email protected]>wrote: > > > > > So I'm still working to get the paradigm down. > > > Activities are related to screens and everything you want a user to > > see needs to be part of an activity. But what's with the Intent? Are > > all intents tied to an activity? > > > I thought I had read that Intents were more like events. If that's > > the case cool...but I'm really struggling on where Intents fit into > > the whole concept. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
