1 page.title=<category> 2 parent.title=The AndroidManifest.xml File 3 parent.link=manifest-intro.html 4 @jd:body 5 6 <dl class="xml"> 7 <dt>syntax:</dt> 8 <dd><pre class="stx"><category android:<a href="#nm">name</a>="<i>string</i>" /></pre></dd> 9 10 <dt>contained in:</dt> 11 <dd><code><a href="{@docRoot}guide/topics/manifest/intent-filter-element.html"><intent-filter></a></code></dd> 12 13 <dt>description:</dt> 14 <dd>Adds a category name to an intent filter. See 15 <a href="{@docRoot}guide/components/intents-filters.html">Intents and 16 Intent Filters</a> for details on intent filters and the role of category 17 specifications within a filter.</dd> 18 19 <dt>attributes:</dt> 20 <dd><dl class="attr"> 21 <dt><a name="nm"></a>{@code android:name}</dt> 22 <dd>The name of the category. Standard categories are defined in the 23 {@link android.content.Intent} class as {@code CATEGORY_<i>name</i>} 24 constants. The name assigned here can be derived from those constants 25 by prefixing "{@code android.intent.category.}" to the 26 {@code <i>name</i>} that follows {@code CATEGORY_}. For example, 27 the string value for {@code CATEGORY_LAUNCHER} is 28 "{@code android.intent.category.LAUNCHER}". 29 30 <p> 31 Custom categories should use the package name as a prefix, to ensure 32 that they are unique. 33 </p></dd> 34 </dl></dd> 35 36 <!-- ##api level indication## --> 37 <dt>introduced in:</dt> 38 <dd>API Level 1</dd> 39 40 <dt>see also:</dt> 41 <dd><code><a href="{@docRoot}guide/topics/manifest/action-element.html"><action></a></code> 42 <br/><code><a href="{@docRoot}guide/topics/manifest/data-element.html"><data></a></code></dd> 43 44 </dl> 45
