Mark, Thanks. I suppose it needs to be in there to kick off the activity life cycle etc. wonder if that could not be done at run time and not needing that activity to be in the manifest when that activity is purely internal.
Thanks again Satya On Mon, Nov 17, 2008 at 2:09 PM, Mark Murphy <[EMAIL PROTECTED]> wrote: > > Satya Komatineni wrote: >> Is it necessary for an activity to be in manifest.xml for that to be >> invoked by its explicit component name? > > Yes, but... > >> And also what are the minimal intent filters that are needed? > > No intent filters are needed for an activity that is "to be invoked by > its explicit component name". > >> What I noticed is the following: >> >> 1. The activity has to be in the manifest.xml >> 2. It doesn't seem to need any additional filters > > Correct. > > Intent filters are only needed if you intend for your activity to > respond to an intent, whether that be the LAUNCHER intent (so it shows > up in the launcher), an intent representing an action to be performed > against a piece of content you are providing, etc. > > If you don't need any of that, and you just want to start the activity > by name, you do not need intent filters. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.4 Published! > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
