Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:small (Results 2226 - 2250 of 8773) sorted by null

<<81828384858687888990>>

/frameworks/base/docs/html/guide/topics/ui/
index.jd	48 small phones to large TV sets. This class shows you how to implement a user interface that's
/frameworks/base/docs/html/training/design-navigation/
descendant-lateral.jd	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> 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>
/frameworks/base/docs/html/training/multiscreen/
index.jd	44 ranging from small phones to large TV sets. Therefore, it?s important
/frameworks/base/docs/html/training/secure-file-sharing/
index.jd	45 If you want to share small amounts of text or numeric data between apps, you should send an
/frameworks/base/docs/html-intl/intl/ja/training/tv/playback/
now-playing.jd	117 // A small bitmap for the artwork is also recommended
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/phone/
PhoneStatusBarView.java	82 // The status bar is very small so augment the view that the user is touching
/frameworks/base/tools/layoutlib/bridge/src/com/android/layoutlib/bridge/impl/
ParserFactory.java	106 // just allocate what is needed. We're mostly reading small files
/frameworks/native/data/etc/
tablet_core_hardware.xml	22 Personal Media Players (PMPs), small tablets (7" or less), and similar
/frameworks/native/include/input/
VelocityControl.h	41 // small precise motions that are performed without any acceleration.
/frameworks/native/services/sensorservice/
GravitySensor.cpp	54 // the accelerometer may have a small scaling error. This
/frameworks/opt/datetimepicker/src/com/android/datetimepicker/time/
CircleView.java	118 // Draw a small black circle in the center.
/frameworks/rs/cpu_ref/linkloader/android/
test-librsloader.c	53 // Note: Since our table is small, we are using trivial O(n) searching
/frameworks/rs/java/tests/ImageProcessing/src/com/android/rs/image/
grain.rs	27 * small values are not calculated to gain efficiency.
/frameworks/rs/java/tests/ImageProcessing2/src/com/android/rs/image/
grain.fs	26 * small values are not calculated to gain efficiency.
/frameworks/rs/java/tests/ImageProcessing_jb/src/com/android/rs/image/
grain.rs	27 * small values are not calculated to gain efficiency.
/frameworks/support/v7/appcompat/res/values-v11/
styles_base_text.xml	57 <style name="Base.TextAppearance.AppCompat.Small.Inverse">
/hardware/broadcom/wlan/bcmdhd/dhdutil/include/
dhdioctl.h	60 #define DHD_IOCTL_SMLEN 256 /* "small" length ioctl buffer required */
/hardware/intel/common/libva/test/decode/
loadjpeg.c	2 * Small jpeg decoder library - testing application
tinyjpeg-internal.h	2 * Small jpeg decoder library (Internal header)
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/test/
cpu_speed_test.cc	90 // lots of small partitions which might will test the other condition.
/libcore/luni/src/main/java/java/io/
FileWriter.java	24 * Since this may induce some performance penalty, in particular if many small
/libcore/luni/src/main/java/javax/crypto/
ExemptionMechanismSpi.java	58 * if the provided buffer is too small for the result key blob.
/libcore/luni/src/main/java/javax/net/ssl/
SSLEngineResult.java	61 * The size of the destination buffer is too small to hold the result of
/libcore/luni/src/main/java/org/apache/harmony/crypto/internal/
NullCipherSpi.java	127 throw new ShortBufferException("output buffer too small");
/libcore/luni/src/test/java/libcore/java/lang/
IntegerTest.java	75 Integer.parseInt("Kona", 10); // base too small

Completed in 1380 milliseconds

<<81828384858687888990>>