| /frameworks/base/docs/html/training/implementing-navigation/ |
| nav-drawer.jd | 1 page.title=Creating a Navigation Drawer
2 page.tags="DrawerLayout", "navigation"
15 <li><a href="#ListItemClicks">Handle Navigation Click Events</a></li>
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
49 <p><strong>Navigation Drawer Design</strong></p>
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
[all...] |
| /frameworks/base/docs/html/design/patterns/ |
| navigation.jd | 1 page.title=Navigation with Back and Up
2 page.tags="navigation","activity","task","up navigation","back navigation"
5 <a class="notice-developers" href="{@docRoot}training/implementing-navigation/index.html">
8 <p>Implementing Effective Navigation</p>
12 <p>Consistent navigation is an essential component of the overall user experience. Few things frustrate
13 users more than basic navigation that behaves in inconsistent and unexpected ways. Android 3.0
14 introduced significant changes to the global navigation behavior. Thoughtfully following the
15 guidelines for Back and Up will make your app's navigation predictable and reliable for your users.</p
[all...] |
| /frameworks/base/docs/html/training/design-navigation/ |
| wireframing.jd | 2 parent.title=Designing Effective Navigation
6 previous.title=Providing Ancestral and Temporal Navigation
25 <p>Now that we have a solid understanding of navigation patterns and screen grouping techniques, it's time to apply them to our screens. Let's take another look at our exhaustive screen map for the example news application from the <a href="screen-planning.html">first lesson</a>, below.</p>
28 <img src="{@docRoot}images/training/app-navigation-screen-planning-exhaustive-map.png"
34 <p>Our next step is to choose and apply navigation patterns discussed in the previous lessons to this screen map, maximizing navigation speed and minimizing the number of touches to access data, while keeping the interface intuitive and consistent with Android best practices. We also need to make different choices for our different target device form factors. For simplicity, let's focus on tablets and handsets.</p>
41 <p>Finally, let's look at how we present news stories. The first option to simplify navigation across different story categories is to use horizontal paging, with a set of labels above the horizontal swiping surface, indicating the currently visible and adjacently accessible categories. On tablets in the landscape orientation, we can go a step further and present the horizontally-pageable <em>Story List</em> screen as a left pane, and the <em>Story View</em> screen as the primary content pane on the right.</p>
43 <p>Below are diagrams representing 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
[all...] |
| /external/chromium/chrome/browser/ |
| errorpage_uitest.cc | 30 // The first navigation should fail, and the second one should be the error
44 // The first navigation should fail, and the second one should be the error
67 // The first navigation should fail, and the second one should be the error
74 // The first navigation should fail, and the second one should be the error
97 // The first navigation should fail, and the second one should be the error
104 // The first navigation should fail, and the second one should be the error
109 // The first navigation should fail, and the second one should be the error
130 // The first navigation should fail, and the second one should be the error
137 // The first navigation should fail, and the second one should be the error
142 // The first navigation should fail, and the second one should be the erro
[all...] |
| /external/chromium_org/sync/protocol/ |
| session_specifics.proto | 63 // Identifies the index of the current navigation in navigations. For
64 // example, if this is 2 it means the current navigation is navigations[2].
70 // Tabs are navigated, and the navigation data is here.
71 repeated TabNavigation navigation = 7;
105 // The unique navigation id (within this client).
107 // Timestamp for when this navigation last occurred (in client time).
112 // User used the address bar to trigger this navigation.
116 // The beginning of a navigation chain.
120 // The id for this navigation, which is globally unique with high
135 // The status code from the last navigation
[all...] |
| /development/samples/training/NavigationDrawer/src/com/example/android/navigationdrawerexample/ |
| MainActivity.java | 47 * <p>When a navigation (left) drawer is present, the host activity should detect presses of
48 * the action bar's Up affordance as a signal to open and close the navigation drawer. The
54 * list or tab navigation in that a view switch does not create navigation history.
56 * of Up navigation active for activities further down the navigation hierarchy.</li>
58 * parent for Up navigation. This allows a user to jump across an app's navigation
59 * hierarchy at will. The application should treat this as it treats Up navigation from
61 * This is the only form of navigation drawer that should be used outside of the roo
[all...] |
| /frameworks/support/v7/appcompat/src/android/support/v7/app/ |
| ActionBar.java | 35 * A window feature at the top of the activity that may display the activity title, navigation
65 * <p>For information about how to use the action bar, including how to add action items, navigation
73 * Standard navigation mode. Consists of either a logo or icon and title text with an optional
80 * List navigation mode. Instead of static title text this mode presents a list menu for
81 * navigation within the activity. e.g. this might be presented to the user as a dropdown list.
86 * Tab navigation mode. Instead of static title text this mode presents a series of tabs for
87 * navigation within the activity.
92 * Use logo instead of icon if available. This flag will cause appropriate navigation modes to
101 * Show 'home' elements in this action bar, leaving more space for other navigation elements.
146 * Set the action bar into custom navigation mode, supplying a view for custom navigation
[all...] |
| /external/chromium_org/chrome/android/java/src/org/chromium/chrome/browser/util/ |
| KeyNavigationUtil.java | 10 * This is a helper class to handle navigation related checks for key events.
23 * @return Whether the event should be processed as a navigation down.
33 * @return Whether the event should be processed as a navigation up.
43 * @return Whether the event should be processed as a navigation right.
53 * @return Whether the event should be processed as any of navigation up or navigation down.
|
| /external/chromium_org/content/public/browser/ |
| navigation_details.h | 22 // navigation.
28 // The type of navigation that just occurred. Note that not all types of
33 // The index of the previously committed navigation entry. This will be -1
44 // True if the navigation was in-page. This means that the active entry's
48 // True when the main frame was navigated. False means the navigation was a
71 // The changed navigation entry after it has been updated.
|
| /external/chromium_org/tools/telemetry/telemetry/core/backends/chrome/ |
| inspector_page.py | 28 # Marks the navigation as complete and unblocks the
50 """Executes action_function, and waits for the navigation to complete.
52 action_function is expect to result in a navigation. This function returns
53 when the navigation is complete or when the timeout has been exceeded.
71 raise util.TimeoutException('Timed out while waiting %ds for navigation. '
78 evaluated when the navigation is committed. This is after the context of
|
| /development/samples/Support4Demos/src/com/example/android/supportv4/widget/ |
| DrawerLayoutActivity.java | 48 * <p>When a navigation (left) drawer is present, the host activity should detect presses of
49 * the action bar's Up affordance as a signal to open and close the navigation drawer.
54 * list or tab navigation in that a view switch does not create navigation history.
56 * of Up navigation active for activities further down the navigation hierarchy.</li>
58 * parent for Up navigation. This allows a user to jump across an app's navigation
59 * hierarchy at will. The application should treat this as it treats Up navigation from
61 * This is the only form of navigation drawer that should be used outside of the roo
[all...] |
| /external/chromium_org/chrome/browser/resources/options/ |
| options_settings_app.css | 5 /* Don't use the large margin used for the navigation bar. Settings App uses a
13 * navigation bar (which is not used for the settings app) in reaction to a
34 /* Settings App is narrower due to no navigation margin, so the roomy language
|
| /external/chromium_org/chrome/renderer/ |
| chrome_render_process_observer.h | 37 // any 'clear cache' commands that were delayed until the next navigation.
58 // navigation event.
70 // If true, the web cache shall be cleared before the next navigation event.
|
| /external/chromium_org/content/common/ |
| view_message_enums.h | 41 // The navigation is the result of session restore and should honor the
48 // Like RESTORE, except that the navigation contains POST data.
51 // Navigation type not categorized by the other types.
|
| /external/chromium_org/content/public/test/ |
| test_navigation_observer.h | 20 // MessageLoop and quit when the navigation completes loading.
27 // Like above but waits for one navigation.
58 // If true the navigation has started.
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| 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
39 requires a five-way navigation control, a touch screen that can be operated
53 <dd>Whether or not the application requires a five-way navigation control
106 <dd>The navigation device required by the application, if any. The value
115 <td>The application does not require any type of navigation control.
116 (The navigation requirement is not defined.)
120 <td>The application does not require a navigation control.</td>
123 <td>The application requires a D-pad (directional pad) for navigation.</td
[all...] |
| /frameworks/base/docs/html/training/accessibility/ |
| index.jd | 2 page.tags="navigation","input"
33 accessibility, leveraging platform features like focus navigation and content
43 navigation with a keyboard or directional pad, set labels and fire events
|
| /development/samples/browseable/AdvancedImmersiveMode/ |
| _index.jd | 10 navigation bar with a swipe.</p>
|
| /external/antlr/antlr-3.4/runtime/JavaScript/src/org/antlr/runtime/tree/ |
| Tree.js | 9 * This is a tree node without any payload; just navigation and factory stuff.
|
| /external/chromium/chrome/browser/resources/ |
| webui.css | 30 .page-navigation {
|
| webui2.css | 24 .page-navigation {
|
| /external/chromium/chrome/browser/ui/toolbar/ |
| toolbar_model.h | 17 // edit. It populates its states from the current navigation entry retrieved
18 // from the navigation controller returned by GetNavigationController().
58 // Returns the navigation controller used to retrieve the navigation entry
|
| /external/chromium_org/chrome/android/java/src/org/chromium/chrome/browser/infobar/ |
| InfoBarListeners.java | 14 * effect of a navigation, replacing the infobar...
|
| /external/chromium_org/chrome/browser/ui/ |
| browser_navigator.h | 71 // Any redirect URLs that occurred for this navigation before |url|.
75 // Indicates whether this navigation will be sent using POST.
81 // The post data when the navigation uses POST.
95 // [out] The WebContents in which the navigation occurred or that was
112 // The disposition requested by the navigation source. Default is
128 // The transition type of the navigation. Default is
133 // Whether this navigation was initiated by the renderer process. Default is
173 // If false then the navigation was not initiated by a user gesture.
199 // [in] Specifies a Browser object where the navigation could occur or the
203 // [out] Specifies the Browser object where the navigation occurred or th
[all...] |
| /external/chromium_org/chrome/browser/ui/startup/ |
| startup_browser_creator_win.h | 14 // charm or via a url navigation in metro, then this function fetches the
|
