* commit '49e43bb818d3b8ff5e9c7272d5039b9d2926aac9': add search tags for Design patterns
This commit is contained in:
Scott Main
@@ -1,4 +1,5 @@
|
||||
page.title=Accessibility
|
||||
page.tags="accessibility","navigation"
|
||||
@jd:body
|
||||
|
||||
<p>One of Android's missions is to organize the world's information and make it universally accessible and useful. Accessibility is the measure of how successfully a product can be used by people with varying abilities. Our mission applies to all users-including people with disabilities such as visual impairment, color deficiency, hearing loss, and limited dexterity.</p>
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Action Bar
|
||||
page.tags="actionbar","navigation"
|
||||
@jd:body
|
||||
|
||||
<img src="{@docRoot}design/media/action_bar_pattern_overview.png">
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Application Structure
|
||||
page.tags="navigation","layout"
|
||||
@jd:body
|
||||
|
||||
<p>Apps come in many varieties that address very different needs. For example:</p>
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Confirming & Acknowledging
|
||||
page.tags="dialog","toast"
|
||||
@jd:body
|
||||
|
||||
<p>In some situations, when a user invokes an action in your app, it's a good idea to <em>confirm</em> or <em>acknowledge</em> that action through text.</p>
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Gestures
|
||||
page.tags="gesture","input"
|
||||
@jd:body
|
||||
|
||||
<p>Gestures allow users to interact with your app by manipulating the screen objects you provide. The
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Multi-pane Layouts
|
||||
page.tags="tablet","navigation","layout","fragment"
|
||||
@jd:body
|
||||
|
||||
<p>When writing an app for Android, keep in mind that Android devices come in many different screen
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Navigation with Back and Up
|
||||
page.tags="navigation","activity"
|
||||
@jd:body
|
||||
|
||||
<p>Consistent navigation is an essential component of the overall user experience. Few things frustrate
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Notifications
|
||||
page.tags="notification"
|
||||
@jd:body
|
||||
|
||||
<p>The notification system allows your app to keep the user informed about events, such as new chat messages or a calendar event. Think of notifications as a news channel that alerts the user to important events as they happen or a log that chronicles events while the user is not paying attention.</p>
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Selection
|
||||
page.tags="actionmode","navigation"
|
||||
@jd:body
|
||||
|
||||
<p>Android 3.0 changed the <em>long press</em> gesture—that is, a touch that's held in the same position for a moment—to be the global gesture to select data.. This affects the way you should
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Settings
|
||||
page.tags="settings","preferences"
|
||||
@jd:body
|
||||
|
||||
<p>Settings is a place in your app where users indicate their preferences for how your app should
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Swipe Views
|
||||
page.tags="viewpager","navigation"
|
||||
@jd:body
|
||||
|
||||
<p>Efficient navigation is one of the cornerstones of a well-designed app. While apps are generally
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
page.title=Widgets
|
||||
page.tags="appwidget"
|
||||
@jd:body
|
||||
|
||||
<p>Widgets are an essential aspect of home screen customization. You can imagine them as "at-a-glance" views of an app's most important data and functionality that is accessible right from the user's home screen. Users can move widgets across their home screen panels, and, if supported, resize them to tailor the amount of information within a widget to their preference.</p>
|
||||
|
||||
Reference in New Issue
Block a user