| /external/libxml2/include/libxml/ |
| entities.h | 45 struct _xmlNode *next; /* next sibling link */
46 struct _xmlNode *prev; /* previous sibling link */
|
| /frameworks/base/docs/html/training/design-navigation/ |
| descendant-lateral.jd | 37 <p>One way of providing access to the full range of an application's screens is to expose hierarchical navigation. In this lesson we discuss <em>descendant navigation</em>, allowing users to descend 'down' a screen hierarchy into a child screen, and <em>lateral navigation</em>, allowing users to access sibling screens.</p>
46 <p>There are two types of sibling screens: collection-related and section-related screens. <em>Collection-related</em> screens represent individual items in the collection represented by the parent. <em>Section-related</em> screens represent different sections of information about the parent. For example, one section may show textual information about an object while another may provide a map of the object's geographic location. The number of section-related screens for a given parent is generally small.</p>
89 <p>For collection-related screens, and especially for textual information, vertically scrolling lists are often the most straightforward and familiar kind of interface. For more visual or media-rich content items such as photos or videos, vertically scrolling grids of items, horizontally scrolling lists (sometimes referred to as <em>carousels</em>), or stacks (sometimes referred to as <em>cards</em>) can be used instead. These UI elements are generally best used for presenting item collections or large sets of child screens (for example, a list of stories or a list of 10 or more news topics), rather than a small set of unrelated, sibling child screens.</p>
111 <p>Using tabs is a very popular solution for lateral navigation. This pattern allows grouping of sibling screens, in that the tab content container in the parent screen can embed child screens that otherwise would be entirely separate contexts. Tabs are most appropriate for small sets (4 or fewer) of section-related screens.</p>
149 <p>Another popular lateral navigation pattern is horizontal paging, also referred to as swipe views. This pattern applies best to collection-related sibling screens, such as a list of categories (world, business, technology, and health stories). Like tabs, this pattern also allows grouping screens in that the parent presents the contents of child screens embedded within its own layout.</p>
158 <p>In a horizontal paging UI, a single child screen (referred to as a <em>page</em> here) is presented one at a time. Users are able to navigate to sibling screens by touching and dragging the screen horizontally in the direction of the desired adjacent page. This gestural interaction is often complemented by another UI element indicating the current page and available pages, to aid discoverability and provide more context to the user. This practice is especially necessary when using this pattern for lateral navigation of section-related sibling screens. Examples of such elements include tick marks, scrolling labels, and tabs.</p>
169 <p>Additionally, for sibling-related screens, horizontal paging is most appropriate where there is some similarity in content type and when the number of siblings is relatively small. In these cases, this pattern can be used along with tabs above the content region to maximize the interface's intuitiveness. For collection-related screens, horizontal paging is most intuitive when there is a natural ordered relationship between screens, for example if each page represents consecutive calendar days. For infinite collections (again, calendar days), especially those with content in both directions, this paging mechanism can work quite well.</p>
|
| /libcore/luni/src/main/java/javax/xml/transform/dom/ |
| DOMResult.java | 108 * If <code>nextSibling</code> is not a sibling of <code>node</code>,
121 * @throws IllegalArgumentException If <code>nextSibling</code> is not a sibling of <code>node</code>.
130 // cannot be a sibling of a null node
158 * If <code>nextSibling</code> is not a sibling of <code>node</code>,
170 * @throws IllegalArgumentException If <code>nextSibling</code> is not a sibling of <code>node</code>.
179 // cannot be a sibling of a null node
219 // cannot be a sibling of a null node
275 // cannot be a sibling of a null node
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.gldebugger/src/com/android/ide/eclipse/gltrace/views/detail/ |
| ShaderSourceDetailsProvider.java | 77 * either the requested node itself, or its parent or sibling.
86 // if it is not the parent, then it could be a sibling, in which case
|
| /system/core/debuggerd/ |
| backtrace.cpp | 109 for (pid_t sibling : siblings) {
110 dump_thread(&log, map, pid, sibling);
|
| /development/ndk/platforms/android-3/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /external/apache-xml/src/main/java/org/apache/xpath/compiler/ |
| Keywords.java | 67 /** following-sibling axes string. */
69 "following-sibling";
77 /** preceding-sibling axes string. */
79 "preceding-sibling";
|
| /external/chromium-trace/catapult/telemetry/third_party/webpagereplay/third_party/ |
| __init__.py | 27 # Modules in dns/ import sibling modules by "import dns/xxx", but
|
| /external/dagger2/compiler/src/main/java/dagger/internal/codegen/ |
| MissingBindingSuggestions.java | 25 * subgraph. If a binding matching a key exists in a sub- or sibling component, that is often what
|
| /external/libgdx/extensions/gdx-freetype/src/com/badlogic/gdx/graphics/g2d/freetype/ |
| FreeTypeFontGeneratorLoader.java | 46 generator = new FreeTypeFontGenerator(file.sibling(file.nameWithoutExtension()));
|
| /external/libgdx/gdx/src/com/badlogic/gdx/files/ |
| FileHandleStream.java | 50 public FileHandle sibling (String name) {
method in class:FileHandleStream
|
| /external/skia/gyp/ |
| android_deps.gyp | 16 # Also this assumes that the android directory is a sibling to the directory
|
| /external/skia/tools/ |
| reformat-json.py | 32 # This assumes that the 'gm' directory has been checked out as a sibling of
|
| /prebuilts/ndk/current/platforms/android-12/arch-arm/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-12/arch-mips/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-12/arch-x86/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-13/arch-arm/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-13/arch-mips/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-13/arch-x86/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-14/arch-arm/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-14/arch-mips/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-14/arch-x86/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-15/arch-arm/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-15/arch-mips/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
| /prebuilts/ndk/current/platforms/android-15/arch-x86/usr/include/linux/ |
| ioport.h | 23 struct resource *parent, *sibling, *child; member in struct:resource
|
