| /external/chromium_org/chrome/browser/chromeos/input_method/ |
| input_method_manager_impl_unittest.cc | 83 ext1_engine1.layouts.push_back("us");
90 ext1_engine2.layouts.push_back("jp");
104 ext2_engine1.layouts.push_back("us");
111 ext2_engine2.layouts.push_back("us(dvorak)");
283 // Currently 5 keyboard layouts are supported for en-US, and 1 for ja. See
343 // Since all the IDs added avobe are keyboard layouts, Start() should not be
910 std::vector<std::string> layouts; local
992 std::vector<std::string> layouts; local
[all...] |
| input_method_util.cc | 233 // For ibus-xkb-layouts engine: third_party/ibus-xkb-layouts/files
366 // Ubuntu where the ibus-xkb-layouts engine could be missing.
456 // keyboard layouts and share the same layout of keyboard (Belgian). We need
633 std::vector<std::string> layouts; local
634 layouts.push_back("us");
639 layouts,
|
| input_method_engine.h | 42 const std::vector<std::string>& layouts,
|
| input_method_persistence.cc | 128 DVLOG(1) << "Only keyboard layouts are supported: "
|
| mock_input_method_manager.cc | 88 const std::vector<std::string>& layouts,
|
| mock_input_method_manager.h | 48 const std::vector<std::string>& layouts,
|
| /external/chromium_org/tools/gen_keyboard_overlay_data/ |
| gen_keyboard_overlay_data.py | 370 layouts = FetchSpreadsheetFeeds(client, KEYBOARD_GLYPH_SPREADSHEET_KEY,
373 for layout_name, layout in layouts.items():
456 def OutputJson(keyboard_glyph_data, hotkey_data, layouts, var_name, outdir):
464 'layouts': layouts,
519 layouts = FetchLayoutsData(client)
520 OutputJson(keyboard_glyph_data, hotkey_data, layouts, 'keyboardOverlayData',
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/refactoring/ |
| ExtractIncludeRefactoring.java | 252 List<IFile> layouts = getOtherLayouts(sourceFile); local
253 for (IFile file : layouts) {
397 * Returns a list of all the other layouts (in all configurations) in the project other
401 List<IFile> layouts = new ArrayList<IFile>(100); local
413 layouts.add((IFile) file);
423 return layouts;
434 // the convention for layouts (and use Locale.US to ensure that "Image" becomes
|
| /external/chromium_org/chrome/browser/ui/cocoa/ |
| confirm_bubble_cocoa.mm | 157 // Initializes controls specified by the ConfirmBubbleModel object and layouts
160 // layouts them programmatically. This function layouts controls in the botom-up
|
| /frameworks/base/docs/html/design/patterns/ |
| pure-android.jd | 161 for different screen sizes and densities and make use of concepts such as multi-pane layouts to
164 well as <a href="{@docRoot}design/patterns/multi-pane-layouts.html">Multi-pane Layouts</a> in this design guide.</p>
|
| /frameworks/base/docs/html/training/design-navigation/ |
| wireframing.jd | 58 <p>At this point, it's a good idea to think of screen map variations, in case your chosen patterns don't apply well in practice (when you sketch the application's screen layouts). Below is an example screen map variation for tablets that presents story lists for different categories side-by-side, with story view screens remaining independent.</p>
86 <p>After sketching out layouts on paper and choosing a digital wireframing tool that works for you, you can create the digital wireframes that will serve as the starting point for your application's visual design. Below are example wireframes for our news application, corresponding one-to-one with our screen maps from earlier in this lesson.</p>
123 <li><a href="{@docRoot}guide/components/fragments.html">Fragments</a>: implement re-usable, multi-pane layouts
|
| /frameworks/base/docs/html/training/tv/ |
| optimizing-navigation-tv.jd | 6 previous.title=Optimizing Layouts for TV
7 previous.link=optimizing-layouts-tv.html
203 In general, for layouts with horizontally scrolling components, place action controls on left or right hand side and
|
| /sdk/ |
| changes.txt | 66 with the view type declared in XML layouts.
92 there (such as in layouts). This can identify accidentally
100 problems such as missing translations, duplicate ids between layouts
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/properties/ |
| PropertyMetadata.java | 50 // *all* referenced XML attributes found in layouts, run against a bunch of
55 // which was *not* found in any of the representative layouts is added here
59 // layouts but which I still consider to be advanced:
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.tests/src/com/android/ide/eclipse/tests/functests/layoutRendering/ |
| ApiDemosRenderingTest.java | 238 // loop on the layouts and render them
239 File[] layouts = layoutFolder.listFiles(); local
240 for (File layout : layouts) {
|
| /cts/tests/tests/widget/src/android/widget/cts/ |
| SimpleExpandableListAdapterTest.java | 176 // the normal and last use different layouts
240 // the normal and last use different layouts
325 // the collapsed and expanded use different layouts
377 // the collapsed and expanded use different layouts
|
| /docs/source.android.com/src/devices/tech/input/ |
| validate-keymaps.jd | 39 Validates the specified key layouts, key character maps,
|
| /external/chromium/chrome/browser/ui/cocoa/download/ |
| download_shelf_controller.h | 105 // Re-layouts all download items based on their current state.
|
| /external/chromium_org/content/browser/loader/ |
| resource_buffer.cc | 16 // (alloc_end_). There are two layouts to keep in mind:
|
| /external/chromium_org/content/public/android/java/resource_map/org/chromium/content/ |
| R.java | 58 /** layouts */
|
| /external/chromium_org/media/base/ |
| channel_layout.h | 102 // Total number of layouts.
|
| multi_channel_resampler_unittest.cc | 134 // Test common channel layouts: mono, stereo, 5.1, 7.1.
|
| /external/chromium_org/third_party/mesa/src/src/mesa/vbo/ |
| vbo_attrib.h | 44 * program instruction formats and register layouts.
|
| /external/chromium_org/third_party/skia/src/core/ |
| SkBitmapScaler.h | 31 // This is typically intended for use during interactive layouts
|
| /external/chromium_org/v8/test/mjsunit/compiler/ |
| alloc-object.js | 30 // Test that inlined object allocation works for different layouts of
|
