| /frameworks/base/docs/html/design/patterns/ |
| D | compatibility.jd | 15 <li>Deprecation of navigation hardware keys (Back, Menu, Search, Home) in favor of handling navigat…
26 <h4>Phones with virtual navigation controls</h4>
43 <h4>Phones with physical navigation keys</h4>
44 <p>Android phones with traditional navigation hardware keys don't display the virtual navigation ba…
59 <h4>Legacy apps on phones with virtual navigation controls</h4>
60 <p>When you run an app that was built for Android 2.3 or earlier on a phone with virtual navigation
61 controls, an action overflow control appears at the right side of the virtual navigation bar. You
|
| D | app-structure.jd | 2 page.tags=navigation,layout,tablet
19 navigation</li>
20 …ps such as Gmail or the Play Store that combine a broad set of data views with deep navigation</li>
25 <p>A typical Android app consists of top level and detail/edit views. If the navigation hierarchy is
64 <p>Many apps focus on the content display. Avoid navigation-only screens and instead let people get…
73 … Play Music allows navigation among artists, albums, and playlists through rich content display.
81 <h4>Set up action bars for navigation and actions</h4>
86 <p>All screens in your app should display action bars to provide consistent navigation and surface
95 through the navigation hierarchy.</li>
111 … of view controls for this task. Use the control that best matches your app's navigation needs:</p>
[all …]
|
| D | swipe-views.jd | 2 page.tags=viewpager,navigation,tabs
5 <a class="notice-developers right" href="{@docRoot}training/implementing-navigation/lateral.html">
12 <p itemprop="description">Efficient navigation is one of the cornerstones of a well-designed app. W…
13 built in a hierarchical fashion, there are instances where horizontal navigation can flatten
56 People app with swipe gesture navigation between top-level screens.
75 <p>If you used buttons in the past for previous/next navigation, replace them with
83 …he developer documentation on <a href="{@docRoot}training/implementing-navigation/lateral.html#hor…
|
| D | navigation.jd | 2 page.tags="navigation","activity","task","up navigation","back navigation"
6 <a class="notice-developers" href="{@docRoot}training/implementing-navigation/index.html">
13 <p itemprop="description">Consistent navigation is an essential component of the overall user exper…
14 users more than basic navigation that behaves in inconsistent and unexpected ways. Thoughtfully
15 following the guidelines for Back and Up will make your app's navigation predictable and reliable
17 <p>Action bars provide a second, standard navigation mechanism:
42 <p>The Back button also supports a few behaviors not directly tied to screen-to-screen navigation:
58 in the same place within the app's hierarchy, and no new navigation history is created.</p>
68 <p>When your app supports navigation from a list of items to a detail view of one of those items, i…
69 often desirable to support direction navigation from that item to another one which precedes or
[all …]
|
| /frameworks/base/docs/html/training/tv/start/ |
| D | navigation.jd | 12 <li><a href="#d-pad-navigation">Enable D-pad Navigation</a></li>
20 TV devices provide a limited set of navigation controls for apps. Creating an effective
21 navigation scheme for your TV app depends on understanding these limited controls and the limits
28 This lesson explains the minimum requirements for creating effective TV app navigation scheme and
33 <h2 id="d-pad-navigation">Enable D-pad Navigation</h2>
38 and right. To build a great TV-optimized app, you must provide a navigation scheme where the user
43 The Android framework handles directional navigation between layout elements automatically, so
45 navigation with a D-pad controller to discover any navigation problems. Follow these guidelines to
46 test that your app's navigation system works well with a D-pad on a TV device:
62 <h3 id="modify-d-pad-nav">Modifying directional navigation</h3>
[all …]
|
| D | index.jd | 29 navigation that works with just a directional pad and a select button.
34 environment, basic requirements for layouts and navigation, as well as guidance on how to handle
60 <dt><a href="{@docRoot}training/tv/start/navigation.html">
62 <dd>Learn the requirements for TV navigation and how to implement TV-compatible
63 navigation.</dd>
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | descendant-lateral.jd | 37 …navigation. In this lesson we discuss <em>descendant navigation</em>, allowing users to descend 'd…
40 <img src="{@docRoot}images/training/app-navigation-descendant-lateral-desc.png"
41 alt="Descendant and lateral navigation" id="figure-desc">
43 <p class="img-caption"><strong>Figure 1.</strong> Descendant and lateral navigation.</p>
49 <img src="{@docRoot}images/training/app-navigation-descendant-lateral-children.png"
55 …navigation can be provided using lists, tabs, and other user interface patterns. <em>User interfac…
66 …navigation interface. Examples of such targets include buttons, fixed-size list views, or text lin…
69 <img src="{@docRoot}images/training/app-navigation-descendant-lateral-buttons.png"
70 …alt="Example button-based navigation interface with relevant screen map excerpt. Also shows dashbo…
72 <p class="img-caption"><strong>Figure 3.</strong> Example button-based navigation interface with re…
[all …]
|
| D | ancestral-temporal.jd | 18 <li><a href="#temporal-navigation">Support Temporal Navigation: <em>Back</em></a></li>
19 …<li><a href="#ancestral-navigation">Provide Ancestral Navigation: <em>Up</em> and <em>Home</em></a…
24 <li><a href="{@docRoot}design/patterns/navigation.html">Android Design: Navigation</a></li>
34 ancestor screens. Additionally, we should ensure that temporal navigation via the <em>Back</em>
40 href="{@docRoot}design/patterns/navigation.html">Navigation</a> pattern guide.</p>
43 <h2 id="temporal-navigation">Support Temporal Navigation: <em>Back</em></h2>
45 <p>Temporal navigation, or navigation between historical screens, is deeply rooted in the Android
52 <img src="{@docRoot}images/training/app-navigation-ancestral-navigate-back.png"
74 <h2 id="ancestral-navigation">Provide Ancestral Navigation: <em>Up</em> and <em>Home</em></h2>
76 <p>Before Android 3.0, the most common form of ancestral navigation was the <em>Home</em> metaphor.
[all …]
|
| D | wireframing.jd | 25 <p>Now that we have a solid understanding of navigation patterns and screen grouping techniques, it…
28 <img src="{@docRoot}images/training/app-navigation-screen-planning-exhaustive-map.png"
34 … step is to choose and apply navigation patterns discussed in the previous lessons to this screen …
41 <p>Finally, let's look at how we present news stories. The first option to simplify navigation acro…
43 …esenting the new screen maps for handsets and tablets after applying these navigation patterns.</p>
46 <img src="{@docRoot}images/training/app-navigation-wireframing-map-example-phone.png"
52 <img src="{@docRoot}images/training/app-navigation-wireframing-map-example-tablet.png"
61 <img src="{@docRoot}images/training/app-navigation-wireframing-map-example-tablet-alt.png"
71 …re are two rows of tabs on the screen). If that happens, explore other navigation patterns, or var…
86 <a href="{@docRoot}images/training/app-navigation-wireframing-wires-phone.png">
[all …]
|
| D | index.jd | 24 …navigation to allow users to effectively and intuitively traverse your content. Each lesson covers…
43 practices for the <em>Back</em> button and temporal navigation, or navigation to previous screens
47 …onal elements discussed in previous lessons to demonstrate intuitive and efficient navigation.</dd>
|
| /frameworks/base/docs/html/training/implementing-navigation/ |
| D | descendant.jd | 22 …<li><a href="{@docRoot}training/design-navigation/descendant-lateral.html">Providing Descendant an…
39 …dant navigation</em> is navigation down the application's information hierarchy. This is described…
41 …navigation is usually implemented using {@link android.content.Intent} objects and {@link android.…
45 …navigation flow, a <em>master</em> screen contains a list of items in a collection, and a <em>deta…
47 …navigation/multiple-sizes.html">Planning for Multiple Touchscreen Sizes</a>. Descendant navigation…
|
| D | index.jd | 17 …<li><a href="{@docRoot}training/design-navigation/index.html">Designing Effective Navigation</a></…
40 <p>This class demonstrates how to implement the key navigation design patterns detailed in the
41 <a href="{@docRoot}training/design-navigation/index.html">Designing Effective Navigation</a> class.
45 implement navigation patterns with tabs, swipe views, and a navigation drawer. You should also
46 understand how to provide proper <em>Up</em> and <em>Back</em> navigation.</p>
63 <dd>Learn how to build an interface with a hidden navigation drawer on the side
67 <dd>Learn how to implement <em>Up</em> navigation using the action bar's app icon.</dd>
|
| D | nav-drawer.jd | 2 page.tags=DrawerLayout,navigation
39 <p>The navigation drawer is a panel that displays the app’s main navigation options
44 <p>This lesson describes how to implement a navigation drawer using the
50 <p>Before you decide to use a navigation drawer in your app, you should understand the use
52 <a href="{@docRoot}design/patterns/navigation-drawer.html">Navigation Drawer</a> design guide.</p>
58 <p>To add a navigation drawer, declare your user interface with a
62 that contains the contents of the navigation drawer.</p>
67 runtime), and a {@link android.widget.ListView} for the navigation drawer.</p>
80 <!-- The navigation drawer -->
100 navigation drawer is hidden.</li>
[all …]
|
| D | temporal.jd | 2 page.tags=back navigation,NavUtils,TaskStackBuilder
20 …<li><a href="{@docRoot}training/design-navigation/ancestral-temporal.html">Providing Ancestral and…
22 <li><a href="{@docRoot}design/patterns/navigation.html">Android Design: Navigation</a></li>
29 <p><em>Back</em> navigation is how users move backward through the history of screens
31 type of navigation, so <strong>your app should not add a Back button to the UI</strong>.</p>
41 concepts and principles for <em>Back</em> navigation as described in
42 the <a href="{@docRoot}design/patterns/navigation.html">Navigation</a> design
51 href="{@docRoot}training/implementing-navigation/nav-drawer.html">navigation drawer</a>.</li>
57 <p>How to implement proper <em>Back</em> navigation in these situations is described
72 <a href="{@docRoot}design/patterns/navigation.html#into-your-app"
[all …]
|
| /frameworks/base/docs/html/training/system-ui/ |
| D | navigation.jd | 43 <p>This lesson describes how to hide the navigation bar, which was introduced in
47 navigation bar, you should design your app to hide the status bar
49 Hiding the navigation and status bars (while still keeping them readily accessible)
53 <img src="{@docRoot}images/training/navigation-bar.png"
61 <p>You can hide the navigation bar using the
63 the navigation bar and the status bar:</p>
65 // Hide both the navigation bar and the status bar.
68 // hide the navigation bar.
76 <li>With this approach, touching anywhere on the screen causes the navigation bar (and
101 the navigation bar, so that the content doesn't resize as the navigation bar hides and
|
| D | index.jd | 66 bar, and [2] navigation bar.</p>
71 of device status, and device navigation. Typically the system bars (which consist of the status
72 and navigation bars, as shown in figure 1) are displayed
94 Learn how to dim the status and navigation bars.
103 <strong><a href="navigation.html">Hiding the Navigation Bar</a></strong>
106 Learn how to hide the navigation bar, in addition to the status bar.
|
| D | dim.jd | 44 <p>This lesson describes how to dim the system bars (that is, the status and the navigation
49 visually recede. As soon as the user touches either the status bar or the navigation bar area of
66 <p>As soon as the user touches the status or navigation bar, the flag is cleared,
70 <p>Figure 1 shows a gallery image in which the navigation bar is dimmed (note that the Gallery app
71 completely hides the status bar; it doesn't dim it). Notice that the navigation bar (right
72 side of the image) has faint white dots on it to represent the navigation controls:</p>
|
| /frameworks/support/samples/SupportDesignDemos/src/com/example/android/support/design/widget/ |
| D | NavigationViewUsageBase.java | 41 NavigationView navigation = (NavigationView) findViewById(R.id.navigation); in onCreate() local
42 navigation.setNavigationItemSelectedListener(getNavigationItemSelectedListener()); in onCreate()
43 navigation.inflateHeaderView(R.layout.design_navigation_header); in onCreate()
|
| /frameworks/base/docs/html/design/handhelds/ |
| D | index.jd | 8 the Home screen experience, global device navigation, and notifications.
54 clear navigation path between multiple ongoing tasks.</p>
55 <p>The Recents button at the right side of the navigation bar displays the apps that the user has
66 status, and device navigation. Typically the system bars are displayed concurrently with your app.
82 <p>The navigation bar is present only on devices that don't have
83 the traditional hardware keys. It houses the device navigation controls Back, Home, and
128 <p>A typical Android app uses action bars, and many apps will include a navigation drawer.</p>
138 <p>If your app's structure is more complex, the navigation drawer can display the main navigation
139 options. The navigation drawer expands from the left edge of the screen, overlaying the content
141 <p><a href="{@docRoot}design/patterns/navigation-drawer.html">More on the Navigation Drawer</a></p>
|
| /frameworks/base/docs/html/training/accessibility/ |
| D | testing.jd | 19 <li><a href="#test-navigation">Testing focus navigation</a></li>
20 <li><a href="#test-gestures">Testing gesture navigation</a></li>
77 navigation</a> on devices with Android 4.1 (API Level 16) or higher.
78 <p class="note"><strong>Note:</strong> Keyboards and D-pads provide different navigation paths
80 content, keyboard and D-pad navigation only allow focus on input fields and buttons.</p>
168 focus navigation and audible prompts.</p>
214 <h3 id="test-navigation">Testing focus navigation</h3>
216 <p>Focus navigation is the use of directional controls to navigate between the individual user
218 manual dexterity often use this mode of navigation instead of touch navigation. As part of
222 <p>You can test navigation of your application using only focus controls, even if your test devices
[all …]
|
| /frameworks/base/core/java/android/content/res/ |
| D | Configuration.java | 480 public int navigation; field in Configuration
763 navigation = o.navigation; in setTo()
895 switch (navigation) { in toString()
901 default: sb.append(" nav="); sb.append(navigation); break; in toString()
930 navigation = NAVIGATION_UNDEFINED; in setToDefaults()
1014 if (delta.navigation != NAVIGATION_UNDEFINED in updateFrom()
1015 && navigation != delta.navigation) { in updateFrom()
1017 navigation = delta.navigation; in updateFrom()
1158 if (delta.navigation != NAVIGATION_UNDEFINED in diff()
1159 && navigation != delta.navigation) { in diff()
[all …]
|
| /frameworks/base/core/jni/ |
| D | android_content_res_Configuration.cpp | 39 jfieldID navigation; member
55 out->navigation = env->GetIntField(clazz, gConfigurationClassInfo.navigation); in android_Configuration_getFromJava()
88 gConfigurationClassInfo.navigation = GetFieldIDOrDie(env, clazz, "navigation", "I"); in register_android_content_res_Configuration()
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | uses-configuration-element.jd | 9 keyboard / navigation control / touch screen." Dianne says that that's what they mean and
11 keyboard / navigation control / touch screen to work." But then what does "undefined" mean?
32 or a particular navigation device, like a trackball. The specification is
50 <dd>Whether or not the application requires a five-way navigation control
103 <dd>The navigation device required by the application, if any. The value
112 <td>The application does not require any type of navigation control.
113 (The navigation requirement is not defined.)
117 <td>The application does not require a navigation control.</td>
120 <td>The application requires a D-pad (directional pad) for navigation.</td>
123 <td>The application requires a trackball for navigation.</td>
[all …]
|
| /frameworks/base/docs/html/wear/preview/features/ |
| D | ui-nav-actions.jd | 2 meta.tags="wear", "wear-preview", "navigation", "action"
22 <li><a href="http://www.google.com/design/spec-wear/components/navigation-drawer.html">
33 navigation and action drawers</a>
40 for Android Wear, Wear 2.0 adds interactive navigation and action drawers.
41 The navigation drawer appears at the top of the screen and lets users jump to
43 the app, similar to the navigation drawer on a phone. The action drawer appears
61 <p>This lesson describes how to implement action and navigation drawers in your
67 To add an action or a navigation drawer, declare your user interface with a
74 navigation drawer, and an action drawer.</p>
107 to populate the navigation drawer contents. To populate the action drawer with
|
| /frameworks/base/docs/html-intl/intl/zh-cn/design/patterns/ |
| D | navigation.jd | 2 page.tags="navigation","activity","task","up navigation","back navigation"
6 <a class="notice-developers" href="{@docRoot}training/implementing-navigation/index.html">
|