| /external/clang/test/Coverage/ |
| ast-printing.cpp | 5 // RUN: %clang_cc1 -fdump-record-layouts %s
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.tests/src/com/android/ide/eclipse/adt/internal/editors/layout/refactoring/testdata/ |
| completion9-expected-completion64.txt | 54 <ViewStub /> : A android.view.ViewStub lets you lazily include other XML layouts inside your application at runtime.
61 <include /> : Lets you statically include XML layouts inside other XML layouts.
62 <merge ></merge> : A root tag useful for XML layouts inflated using a ViewStub.
|
| completion1-expected-completion11.txt | 54 <ViewStub /> : A android.view.ViewStub lets you lazily include other XML layouts inside your application at runtime.
61 <include /> : Lets you statically include XML layouts inside other XML layouts.
|
| completion1-expected-completion12.txt | 54 <ViewStub /> : A android.view.ViewStub lets you lazily include other XML layouts inside your application at runtime.
61 <include /> : Lets you statically include XML layouts inside other XML layouts.
|
| /sdk/layoutopt/libs/uix/src/resources/rules/ |
| TooManyLevels.rule | 9 analysis << [node: null, description: "This layout has too many nested layouts: " +
|
| /frameworks/base/docs/html/guide/developing/tools/ |
| layoutopt.jd | 7 layouts and layout hierarchies of your applications.<p>
11 href="{@docRoot}guide/developing/debugging/debugging-ui.html#layoutopt">Optimizing layouts with
|
| /development/samples/Snake/ |
| _index.html | 6 <p>This code demonstrates how to create custom View layouts and
|
| /development/tools/emulator/skins/WSVGA/ |
| layout | 24 layouts {
|
| /development/tools/emulator/skins/WXGA720/ |
| layout | 24 layouts {
|
| /development/tools/emulator/skins/WXGA800/ |
| layout | 24 layouts {
|
| /sdk/layoutlib_api/sample/ |
| README.txt | 16 (render in context, expand empty layouts, etc...
|
| /packages/apps/Mms/src/com/android/mms/layout/ |
| LayoutParameters.java | 21 /* Layouts type definition */
26 /* Parameters for known layouts */
|
| /external/llvm/test/MC/ELF/ |
| no-fixup.s | 10 // CHECK-NEXT: assembler - Number of fragment layouts
|
| /frameworks/base/core/tests/coretests/src/android/widget/layout/linear/ |
| LLOfButtons2.java | 20 * One of two simple vertical linear layouts of buttons used to test out
|
| LLOfButtons1.java | 28 * One of two simple vertical linear layouts of buttons used to test out
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/resources/ |
| CyclicDependencyValidator.java | 44 * dependencies when offering layouts to be included within a given file, etc.
46 * @param file the target file that candidate layouts should not directly or
|
| /development/tools/findunused/ |
| find_unused_resources.rb | 107 layouts = Hash.new
119 layouts[id] = FilePosition.new(filename, file.lineno)
146 layouts.delete(id)
151 layouts.delete(id)
156 layouts.delete(id)
162 result.unusedLayoutIds = layouts
|
| /external/qemu/docs/ |
| ANDROID-SKIN-FILES.TXT | 16 Each skin can have several "layouts" (e.g. "landscape" and "portrait")
43 Layouts & Parts:
46 Each skin file must define a list of 'parts' and a list of 'layouts'.
60 skin file contains two layouts: one for landscape mode, and another one for
61 portrait mode. More layouts can be used if needed. For example, one could
65 Skin Layouts:
68 Each skin layout is a named sub-key of the top-level 'layouts' key in the
71 layouts {
80 Defines two layouts named 'portrait' and 'landscape'.
|
| /frameworks/base/docs/html/resources/articles/ |
| future-proofing.jd | 49 <p><b>Technique to Avoid, #3: Going Overboard with Layouts</b></p>
53 layouts are now likely to cause crashes. This was always a risk for
54 excessively complex layouts, but you can think of Android 1.5 as being
56 worry about this, but if your app has very complicated layouts, you'll
57 need to put it on a diet. You can simplify your layouts using the more
|
| /external/qemu/android/skin/ |
| file.h | 104 SkinLayout* layouts; member in struct:SkinFile
111 SkinLayout* __layout = (file)->layouts; \
|
| /frameworks/base/core/tests/coretests/res/layout/ |
| drawable_background_minimum_size.xml | 32 <!-- Different views and layouts that should initially be small but still contain
33 some content (hence the minimal text inside each of the layouts). Each of these
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| widget_design.jd | 12 <li>App Widget layouts should be flexible, resizing to fit their parent container</li>
23 <li><a href="#design">Designing Widget Layouts and Background Graphics</a></li>
110 Layouts and Background Graphics</a> below, using nine-patch backgrounds and flexible layouts for app
219 <h2 id="design">Designing Widget Layouts and Background Graphics</h2>
247 <p>For the contents of the widget, you should use flexible layouts such as {@link
249 android.widget.FrameLayout}. Just as your activity layouts must adapt to different physical screen
250 sizes, widget layouts must adapt to different Home screen grid cell sizes.</p>
287 use flexible layouts attributes like so:</p>
291 alt="Excerpt flexible layouts and attributes for an example music widget
[all...] |
| /cts/tests/src/android/content/cts/ |
| AvailableIntentsActivity.java | 26 * what it layouts. We only need an activity even if it's empty for this test.
|
| /development/samples/MultiResolution/ |
| _index.html | 13 resources such as layouts and graphical assets for different screen configurations</li>
|
| /frameworks/base/core/tests/coretests/src/android/view/menu/ |
| MenuLayout.java | 44 * This activity is meant to try a bunch of different menu layouts. So,
|
