| /frameworks/base/docs/html/distribute/googleplay/quality/ |
| tablet.jd | 9 <li><a href="#optimize-layouts">2. Optimize your layouts</a></li>
75 <h2 id="optimize-layouts">2. Optimize your layouts for larger screens</h2>
82 — you need to optimize your layouts and other UI components for each
89 tablets, you can start by making minor adjustments to your layouts, fonts, and
103 layouts lead to awkward whitespace and excessive line lengths. Use padding to
104 reduce the width of UI elements and consider using multi-pane layouts.</p>
108 <li>Provide custom layouts as needed for <code>large</code> and
109 <code>xlarge</code> screens. You can also provide layouts that are loaded base
[all...] |
| /cts/hostsidetests/holo/app/src/android/holo/app/ |
| CaptureActivity.java | 26 * Iterates through all themes and all layouts, starting the Activity to capture the images.
|
| /cts/tests/tests/holo/src/android/holo/cts/ |
| LayoutPickerActivity.java | 26 * {@link ListActivity} for picking layouts. Used by the Holo Test Utilities activity.
|
| /developers/build/prebuilts/gradle/CustomNotifications/CustomNotificationsSample/src/main/res/values/ |
| strings.xml | 32 the notification to see the different layouts.</b>
|
| /developers/samples/android/ui/notifications/CustomNotifications/CustomNotificationsSample/src/main/res/values/ |
| strings.xml | 32 the notification to see the different layouts.</b>
|
| /development/samples/ActionBarCompat/src/com/example/android/actionbarcompat/ |
| ActionBarHelperHoneycomb.java | 73 * Returns a {@link Context} suitable for inflating layouts for the action bar. The
|
| /development/samples/browseable/CustomNotifications/res/values/ |
| strings.xml | 32 the notification to see the different layouts.</b>
|
| /external/chromium_org/ui/events/keycodes/ |
| keyboard_code_conversion.h | 26 // layouts, that may generate different text for a certain key than on a US
|
| /external/robolectric/src/main/java/com/xtremelabs/robolectric/shadows/ |
| ShadowLayoutInflater.java | 16 * Shadow of {@code LayoutInflater} that actually inflates layouts into {@code View}s that are functional enough to
|
| /frameworks/base/core/java/android/hardware/input/ |
| IInputManager.aidl | 41 // Keyboard layouts configuration.
|
| /frameworks/base/core/java/android/widget/ |
| Space.java | 27 * in general purpose layouts.
|
| /frameworks/base/docs/html/training/monetization/ |
| index.jd | 17 <li>Experience with <a href="{@docRoot}guide/topics/ui/declaring-layout.html">XML layouts</a></li>
|
| /frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/ |
| ExpandableNotificationRow.java | 27 /** does this row contain layouts that can adapt to row expansion */
|
| /frameworks/support/v7/gridlayout/src/android/support/v7/widget/ |
| Space.java | 27 * in general purpose layouts.
|
| /sdk/emulator/skins/dynamic/ |
| layout | 1 # This layout file only defines all the parts. The layouts section
|
| /development/samples/training/ads-and-ux/src/com/example/training/ads/ |
| AdsCatalogActivity.java | 112 // Set up the various ad layouts on different flip pages.
113 final int[] layouts = { local
118 int layoutId = layouts[mNum];
|
| /external/chromium/chrome/browser/chromeos/input_method/ |
| xkeyboard_unittest.cc | 169 std::set<std::string> layouts; local
178 // All 4*3*3 layouts should be different.
179 EXPECT_TRUE(layouts.insert(layout).second) << "layout: " << layout;
|
| /external/chromium/chrome/browser/chromeos/login/ |
| language_switch_menu.cc | 136 // If we have switched the locale, enable the keyboard layouts that
183 // Here, we should enable keyboard layouts associated with the locale so
184 // that users can use those keyboard layouts on the login screen.
|
| /external/chromium_org/ash/desktop_background/ |
| wallpaper_resizer_unittest.cc | 98 WallpaperLayout layouts[4] = { local
104 const int length = arraysize(layouts);
107 WallpaperLayout layout = layouts[i];
|
| /frameworks/base/docs/html/guide/practices/ |
| tablets-and-handsets.jd | 11 <li><a href="#Fragments">Creating Single-pane and Multi-pane Layouts</a></li>
45 resources</a> (such as alternative layouts that reposition some views or alternative
56 UI into separate parts, which you can then combine to create multi-pane layouts when running on a
67 supports different screen sizes and densities with flexible layouts and alternative bitmaps,
80 different combinations—in multi-pane layouts on tablets and single-pane layouts on handsets.
112 <li><strong>Implement flexible layouts</strong>, as discussed in the
125 information about creating flexible layouts, refer to the links provided above.</p>
136 <h2 id="Fragments">Creating Single-pane and Multi-pane Layouts</h2>
167 layouts with different combinations of fragments, such that you can design "multi-pane" layouts fo
[all...] |
| /frameworks/base/docs/html/guide/topics/ui/ |
| declaring-layout.jd | 1 page.title=Layouts
19 <li><a href="#CommonLayouts">Common Layouts</a></li>
20 <li><a href="#AdapterViews">Building Layouts with an Adapter</a>
47 vocabulary that corresponds to the View classes and subclasses, such as those for widgets and layouts.</li>
52 <p>The Android framework gives you the flexibility to use either or both of these methods for declaring and managing your application's UI. For example, you could declare your application's default layouts in XML, including the screen elements that will appear in them and their properties. You could then add code in your application that would modify the state of the screen objects, including those declared in XML, at run time. </p>
62 for debugging layouts — it reveals layout property values,
66 you quickly analyze your layouts and hierarchies for inefficiencies or other problems.</li>
70 <p>The advantage to declaring your UI in XML is that it enables you to better separate the presentation of your application from the code that controls its behavior. Your UI descriptions are external to your application code, which means that you can modify or adapt it without having to modify your source code and recompile. For example, you can create XML layouts for different screen orientations, different device screen sizes, and different languages. Additionally, declaring the layout in XML makes it easier to visualize the structure of your UI, so it's easier to debug problems. As such, this document focuses on teaching you how to declare your layout in XML. If you're
79 Layout Objects</a>. There are also a collection of tutorials on building various layouts in the
84 <p>Using Android's XML vocabulary, you can quickly design UI layouts and the screen elements they contain, in the same way you create web pages in HTML — with a (…)
[all...] |
| /external/skia/bench/ |
| bench_util.py | 122 layout_dic: dictionary to store tile layouts. See parse() for descriptions.
130 layouts = TILE_LAYOUT_RE_COMPILED.search(line)
131 if layouts and len(layouts.groups()) == 2:
132 tile_layout = '%sx%s' % layouts.groups()
|
| /external/chromium_org/chrome/browser/chromeos/input_method/ |
| input_method_manager_impl.cc | 163 std::vector<std::string> layouts; local
165 // layouts, so it appears first on the list of active input
169 layouts.push_back(initial_layout);
175 // Add candidates to layouts, while skipping duplicates.
180 if (!Contains(layouts, candidate) && IsLoginKeyboard(candidate))
181 layouts.push_back(candidate);
184 active_input_method_ids_.swap(layouts);
392 // Legacy IMEs or xkb layouts are alwayes active.
423 const std::vector<std::string>& layouts,
438 id, name, layouts, languages, false, options_url, inputview_url)
[all...] |
| input_method_util_unittest.cc | 60 std::vector<std::string> layouts; variable
62 layouts.push_back("us");
67 layouts,
78 layouts,
91 std::vector<std::string> layouts; local
92 layouts.push_back(raw_layout);
97 layouts,
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| widget_design.jd | 13 <li>App Widget layouts should be flexible, resizing to fit their parent container</li>
24 <li><a href="#design">Designing Widget Layouts and Background Graphics</a></li>
118 Layouts and Background Graphics</a> below, using nine-patch backgrounds and flexible layouts for app
227 <h2 id="design">Designing Widget Layouts and Background Graphics</h2>
255 <p>For the contents of the widget, you should use flexible layouts such as {@link
257 android.widget.FrameLayout}. Just as your activity layouts must adapt to different physical screen
258 sizes, widget layouts must adapt to different Home screen grid cell sizes.</p>
297 use flexible layouts attributes like so:</p>
301 alt="Excerpt flexible layouts and attributes for an example music widget
[all...] |
