HomeSort by relevance Sort by last modified time
    Searched full:layouts (Results 226 - 250 of 709) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /frameworks/base/docs/html/tools/sdk/
eclipse-adt.jd 304 typos, orientation tags in layouts, overlapping names for 9-patches and images, and class
    [all...]
  /external/chromium_org/chrome/browser/extensions/api/input_ime/
input_ime_api.cc 304 std::vector<std::string> layouts; local
305 layouts.assign(component.layouts.begin(), component.layouts.end());
312 component.id.c_str(), languages, layouts,
  /external/chromium_org/ui/base/ime/win/
imm32_manager.cc 549 // Retrieve the number of layouts installed in this system.
556 // Retrieve the keyboard layouts in an array and check if there is an RTL
558 scoped_ptr<HKL[]> layouts(new HKL[size]);
559 ::GetKeyboardLayoutList(size, layouts.get());
561 if (IsRTLPrimaryLangID(PRIMARYLANGID(layouts[i]))) {
  /packages/apps/Mms/src/com/android/mms/model/
SlideshowModel.java 88 LayoutModel layouts, ArrayList<SlideModel> slides,
91 mLayout = layouts;
141 LayoutModel layouts = new LayoutModel(rootLayout, regions); local
164 context, sme, layouts, pb);
229 SlideshowModel slideshow = new SlideshowModel(layouts, slides, document, pb, context);
  /external/chromium_org/chrome/browser/chromeos/input_method/
input_method_engine.cc 83 const std::vector<std::string>& layouts,
105 manager->AddInputMethodExtension(ibus_id_, engine_name, layouts, languages,
496 // TODO(komatsu): Support non-us keyboard layouts.
  /external/chromium_org/media/base/
channel_mixer.cc 31 // of not being one of the invalid layouts, but lets double check to be sure.
36 // The unit test will verify all possible layouts, so this can be a DCHECK.
137 // Verify that the layouts are supported
  /external/qemu/android/
qemulator.c 140 emulator->layout = emulator->layout_file->layouts;
457 layout = emulator->layout_file->layouts;
460 layout = emulator->layout_file->layouts;
  /frameworks/base/docs/html/distribute/googleplay/strategies/
app-quality.jd 74 A great way to improve UI performance is to minimize the complexity of your layouts. If you open up <a href="{@docRoot}tools/help/hierarchy-viewer.html">hierarchyviewer</a> and see that your layouts are more than 5 levels deep, it may be time to simplify your layout. Consider refactoring those deeply nested LinearLayouts into RelativeLayout. The impact of View objects is cumulative &mdash; each one costs about 1 to 2 KB of memory, so large view hierarchies can be a recipe for disaster, causing frequent VM garbage collection passes which block the main (UI) thread. You can learn more in <a href="http://www.youtube.com/watch?v=wDBM6wVEO70">World of ListView</a>, another session at Google I/O.</p>
101 If you don't have the luxury of working with a UI designer, there are some ways in which you can improve your app's appearance yourself. First, get familiar with Adobe Photoshop, Adobe Fireworks, or some other raster image editing tool. Mastering the art of the pixel in these apps takes time, but honing this skill can help build polish across your interface designs. Also, master the resources framework by studying the framework UI assets and layouts and reading through the <a href="{@docRoot}guide/topics/resources/index.html">resources documentation</a>. Techniques such as 9-patches and resource directory qualifiers are somewhat unique to Android, and are crucial in building flexible yet aesthetic UIs.</p>
  /frameworks/base/docs/html/guide/practices/app-design/
seamlessness.jd 180 to landscape mode. It's important to make sure your layouts and drawables
187 layouts.) If you do that much, the system handles the rest, and your
225 about specific keyboard layouts -- unless, of course, you're really interested
  /frameworks/base/docs/html/guide/practices/
seamlessness.jd 181 to landscape mode. It's important to make sure your layouts and drawables
188 layouts.) If you do that much, the system handles the rest, and your
226 about specific keyboard layouts -- unless, of course, you're really interested
  /frameworks/base/docs/html/training/animation/
cardflip.jd 203 use the two layouts in the fragments that you'll later animate. The following layouts
250 Create fragment classes for the front and back of the card. These classes return the layouts
  /development/samples/HoneycombGallery/src/com/example/android/hcgallery/
MainActivity.java 187 // performance so you should only do this for simple layouts. More complicated
188 // layouts can be better served with individual animations on child views to
  /external/chromium/chrome/browser/chromeos/login/
base_login_display_host.cc 169 // The login screen will enable alternate keyboard layouts, but we don't want
177 // and US dvorak keyboard layouts.
  /external/chromium/chrome/browser/resources/
keyboard_overlay.js 68 * Returns layouts data.
71 return keyboardOverlayData['layouts'];
  /external/chromium_org/chrome/browser/chromeos/display/
display_preferences.cc 85 const base::DictionaryValue* layouts = local_state->GetDictionary( local
87 for (DictionaryValue::Iterator it(*layouts); !it.IsAtEnd(); it.Advance()) {
  /external/chromium_org/media/audio/win/
audio_unified_win_unittest.cc 114 // channel layouts.
182 // TODO(henrika): extend support to other input channel layouts as well.
  /frameworks/base/docs/html/sdk/installing/
studio-tips.jd 87 <h3>Creating layouts</h3>
118 <a href="{@docRoot}tools/debugging/debugging-ui.html">optimize your layouts</a>.</p>
  /frameworks/base/services/java/com/android/server/input/
PersistentDataStore.java 388 "Found multiple current keyboard layouts.");
395 // Maintain invariant that layouts are sorted.
  /packages/apps/Calendar/src/com/android/calendar/
CalendarViewAdapter.java 37 * for small screen layouts. The pull down menu replaces the tabs uses for big screen layouts
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/sdk/
WidgetClassLoader.java 36 * Parser for the text file containing the list of widgets, layouts and layout params.
279 // look for a match in the layouts. We don't use the layout map as it only contains the
  /cts/tests/tests/holo/src/android/holo/cts/
ThemeTestActivity.java 33 * {@link Activity} that iterates over all the test layouts for a single theme
  /development/tools/emulator/skins/HVGA/
layout 354 layouts {
  /development/tools/emulator/skins/QVGA/
layout 354 layouts {
  /development/tools/emulator/skins/WQVGA400/
layout 354 layouts {
  /development/tools/emulator/skins/WQVGA432/
layout 354 layouts {

Completed in 855 milliseconds

1 2 3 4 5 6 7 8 91011>>