| /development/samples/training/threadsample/res/values-xlarge/ |
| bools.xml | 2 <!-- The reason this is done is that on ICS tablets (>= sw600) , hiding the navigation has no function, but
|
| /external/chromium_org/chrome/browser/resources/uber/ |
| uber.css | 15 #navigation {
18 /* This is a hack to prevent the navigation bar from occluding pointer events
30 #navigation.background {
34 #navigation.changing-content {
|
| /external/chromium_org/content/public/android/java/src/org/chromium/content/browser/ |
| WebContents.java | 12 * @return The navigation controller associated with this WebContents.
|
| /external/chromium_org/win8/metro_driver/ |
| chrome_url_launch_handler.h | 24 // If metro chrome was launched due to a URL navigation/search request then
25 // the navigation should be done when the frame window is initialized. This
26 // function is called to complete the pending navigation when we receive a
50 // Helper function to initiate a navigation or search request in chrome.
|
| /external/eigen/demos/opengl/ |
| README | 2 Navigation:
|
| /external/jmonkeyengine/engine/src/desktop/jme3tools/navigation/ |
| GCSailing.java | 5 package jme3tools.navigation;
|
| RLSailing.java | 5 package jme3tools.navigation;
|
| /frameworks/base/docs/html/training/tv/ |
| index.jd | 39 <dt><b><a href="optimizing-navigation-tv.html">Optimizing Navigation for TV</a></b></dt>
40 <dd>Shows you how to design navigation for TVs, including:
42 <li>handling D-pad navigation</li>
|
| optimizing-navigation-tv.jd | 1 page.title=Optimizing Navigation for TV
18 <li><a href="#HandleDpadNavigation">Handle D-pad Navigation</a></li>
20 <li><a href="#DesignForEasyNavigation">Design for Easy Navigation</a></li>
25 <li><a href="{@docRoot}training/design-navigation/index.html">Designing Effective Navigation</a></li>
37 This lesson shows you how to optimize navigation for TV by:
42 <li>Providing highly obvious feedback for UI navigation.</li>
46 <h2 id="HandleDpadNavigation">Handle D-pad Navigation</h2>
51 To build a great TV-optimized app, you must provide a navigation scheme in which the user can
56 When you design navigation for D-pad, follow these guidelines
[all...] |
| /development/samples/training/NavigationDrawer/res/values/ |
| strings.xml | 18 <string name="app_name">Navigation Drawer Example</string>
29 <string name="drawer_open">Open navigation drawer</string>
30 <string name="drawer_close">Close navigation drawer</string>
|
| /external/chromium_org/chrome/browser/prerender/ |
| prerender_final_status.cc | 48 "Cross-Site Navigation Pending",
60 "Navigation Uncommitted",
61 "New Navigation Entry",
|
| /external/chromium_org/third_party/WebKit/Source/devtools/front_end/ |
| screencastView.css | 31 .screencast-navigation {
38 .screencast-navigation button {
53 .screencast-navigation button:hover {
57 .screencast-navigation button:active {
61 .screencast-navigation button[disabled] {
65 .screencast-navigation button.back {
69 .screencast-navigation button.forward {
73 .screencast-navigation button.reload {
77 .screencast-navigation input {
85 .screencast-navigation input:focus
[all...] |
| /packages/apps/Contacts/res/layout/ |
| people_navigation_item.xml | 17 <!-- This is the text view layout that is shown in the spinner for the navigation drop down menu on
20 of navigation drop down list of the action bar.
22 the navigation drop down list of the action bar. -->
|
| /external/chromium_org/chrome/browser/ |
| referrer_policy_browsertest.cc | 190 // Content initiated navigation, from HTTP to HTTP.
197 // Content initiated navigation, from HTTPS to HTTP.
204 // User initiated navigation, from HTTP to HTTP.
211 // User initiated navigation, from HTTPS to HTTP.
218 // User initiated navigation, middle click, from HTTP to HTTP.
225 // User initiated navigation, middle click, from HTTPS to HTTP.
232 // User initiated navigation, target blank, from HTTP to HTTP.
239 // User initiated navigation, target blank, from HTTPS to HTTP.
246 // User initiated navigation, middle click, target blank, from HTTP to HTTP.
253 // User initiated navigation, middle click, target blank, from HTTPS to HTTP
[all...] |
| /external/chromium_org/components/sessions/ |
| serialized_navigation_entry.cc | 38 SerializedNavigationEntry navigation; local
39 navigation.index_ = index;
40 navigation.unique_id_ = entry.GetUniqueID();
41 navigation.referrer_ = entry.GetReferrer();
42 navigation.virtual_url_ = entry.GetVirtualURL();
43 navigation.title_ = entry.GetTitle();
44 navigation.page_state_ = entry.GetPageState();
45 navigation.transition_type_ = entry.GetTransitionType();
46 navigation.has_post_data_ = entry.GetHasPostData();
47 navigation.post_id_ = entry.GetPostID()
65 SerializedNavigationEntry navigation; local
[all...] |
| /frameworks/base/docs/html/design/patterns/ |
| app-structure.jd | 2 page.tags="navigation","layout","tablet"
10 navigation</li>
11 <li>Apps such as Gmail or the Play Store that combine a broad set of data views with deep navigation</li>
16 <p>A typical Android app consists of top level and detail/edit views. If the navigation hierarchy is
55 <p>Many apps focus on the content display. Avoid navigation-only screens and instead let people get to
64 Play Music allows navigation among artists, albums, and playlists through rich content display.
72 <h4>Set up action bars for navigation and actions</h4>
77 <p>All screens in your app should display action bars to provide consistent navigation and surface
86 through the navigation hierarchy.</li>
95 well. Navigation supports switching views of day, week, month, and agenda views.
[all...] |
| /sdk/eclipse/plugins/com.android.ide.eclipse.tests/unittests/com/android/ide/eclipse/adt/internal/editors/resources/manager/ |
| ConfigMatchTest.java | 34 import com.android.resources.Navigation;
108 null, // navigation state
109 null, // navigation method
132 null, // navigation state
133 null, // navigation method
156 null, // navigation state
157 null, // navigation method
180 null, // navigation state
181 null, // navigation method
204 NavigationState.EXPOSED.getResourceValue(), // navigation stat
[all...] |
| /external/chromium_org/content/browser/frame_host/ |
| navigation_entry_screenshot_manager.h | 23 // current navigation entry of a NavigationControllerImpl, and managing these
24 // captured images. These image-captures are used for history navigation using
35 // Clears screenshots of all navigation entries.
51 // This sets the screenshot on the navigation entry.
74 // The navigation controller that owns this screenshot-manager.
|
| /development/samples/AppNavigation/res/values/ |
| strings.xml | 17 <string name="app_name">App Navigation Sample</string>
18 <string name="app_nav_home_label">App Navigation</string>
20 <string name="simple_up_label">Simple Up Navigation</string>
21 <string name="simple_up_description">This demo shows the simple case of up navigation that does not ever need to cross across different tasks. Press the up button on the action bar to return to the demo list. For simple drill-down navigation, the application up and system back buttons will navigate to the same location, leaving the task\'s back stack in the same state.</string>
24 <string name="peer_description">This is an activity that shows content with many navigation peers. Think of a content browser that offers links to related content items. Pressing back from this activity will return to the previously viewed content item if you reached this point through a related link. If you reached it from the app nav example home activity, back will return there. Navigating up from this activity will always return to the app nav example home activity and clean up the back stack along the way.</string>
29 <string name="view_from_other_task_description">This combined demo shows how to handle up navigation when another task has launched your app\'s activity on its own task stack. Navigating up in this scenario should synthesize a task stack representing the most common or direct navigation path to the parent activity. The code example shows how to handle this using helper code from the support library. Press the button below to launch a separate task and begin the demo.</string>
33 <string name="outside_task_description">This activity has been launched in a new task. You can confirm this by pressing the Recents button now and switching back to the app navigation example task. This activity will view content with the fake mimetype \"application/x-example\" which will be received by another code example activity to continue the demo. Press the View button below.</string>
40 <string name="intermediate_description">This activity is a parent for the example content viewer activity. Navigating up from the content viewer will lead here. Navigating up from here will lead back to the app navigation home activity. Note that if you reached this activity by navigating up from the example content vi (…)
[all...] |
| /development/samples/SupportAppNavigation/res/values/ |
| strings.xml | 17 <string name="app_name">Support App Navigation Sample</string>
18 <string name="app_nav_home_label">Support App Navigation</string>
20 <string name="simple_up_label">Simple Up Navigation</string>
21 <string name="simple_up_description">This demo shows the simple case of up navigation that does not ever need to cross across different tasks. Press the up button on the action bar to return to the demo list. For simple drill-down navigation, the application up and system back buttons will navigate to the same location, leaving the task\'s back stack in the same state.</string>
24 <string name="peer_description">This is an activity that shows content with many navigation peers. Think of a content browser that offers links to related content items. Pressing back from this activity will return to the previously viewed content item if you reached this point through a related link. If you reached it from the app nav example home activity, back will return there. Navigating up from this activity will always return to the app nav example home activity and clean up the back stack along the way.</string>
29 <string name="view_from_other_task_description">This combined demo shows how to handle up navigation when another task has launched your app\'s activity on its own task stack. Navigating up in this scenario should synthesize a task stack representing the most common or direct navigation path to the parent activity. The code example shows how to handle this using helper code from the support library. Press the button below to launch a separate task and begin the demo.</string>
33 <string name="outside_task_description">This activity has been launched in a new task. You can confirm this by pressing the Recents button now and switching back to the app navigation example task. This activity will view content with the fake mimetype \"application/x-example\" which will be received by another code example activity to continue the demo. Press the View button below.</string>
40 <string name="intermediate_description">This activity is a parent for the example content viewer activity. Navigating up from the content viewer will lead here. Navigating up from here will lead back to the app navigation home activity. Note that if you reached this activity by navigating up from the example content vi (…)
[all...] |
| /external/proguard/docs/ |
| style.css | 114 body.navigation
120 ul.navigation
129 ul.navigation li
140 ul.navigation li.title
147 ul.navigation li a
157 ul.navigation li a:hover,
158 ul.navigation li a:focus
|
| /frameworks/base/docs/html/training/implementing-navigation/ |
| temporal.jd | 1 page.title=Providing Proper Back Navigation
2 page.tags="back navigation","NavUtils","TaskStackBuilder"
14 <li><a href="#back-fragments">Implement Back Navigation for Fragments</a></li>
15 <li><a href="#back-webviews">Implement Back Navigation for WebViews</a></li>
20 <li><a href="{@docRoot}training/design-navigation/ancestral-temporal.html">Providing Ancestral and Temporal Navigation</a></li>
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
[all...] |
| /frameworks/base/docs/html/training/system-ui/ |
| index.jd | 39 bar, and [2] navigation bar.</p>
44 of device status, and device navigation. Typically the system bars (which consist of the status
45 and navigation bars, as shown in figure 1) are displayed
67 Learn how to dim the status and navigation bars.
76 <strong><a href="navigation.html">Hiding the Navigation Bar</a></strong>
79 Learn how to hide the navigation bar, in addition to the status bar.
|
| /prebuilts/tools/common/proguard/proguard4.7/docs/ |
| style.css | 127 body.navigation
133 ul.navigation
142 ul.navigation li
153 ul.navigation li.title
160 ul.navigation li a
170 ul.navigation li a:hover,
171 ul.navigation li a:focus
|
| /external/chromium_org/chrome/common/extensions/docs/templates/intros/ |
| webNavigation.html | 33 For a navigation that is successfully completed, events are fired in the
41 <code>onErrorOccurred</code> event. For a specific navigation, there are no
62 If a navigation was triggered via <a
75 frames that already started a new navigation, or that a navigation only
79 In general, the webNavigation events are closely related to the navigation
109 to render the source and destination of a web page. Therefore, if a navigation
111 the old page until the new navigation is committed (i.e. the
114 process ID, so you can still determine which frame a navigation came from.
131 qualifiers</em> can be returned that further define the navigation
[all...] |
