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