/frameworks/base/docs/html/training/ |
D | advanced.jd | 5 <p>Advanced Training contains a variety of classes that teach you best practices in Android 6 development. These classes simplify the steps required to enhance your app with powerful 9 <p>What you see now is still the beginning. We plan to add many more classes, expand and refine 10 existing classes, re-organize, and build courses that help you enhance your apps using 11 objective-oriented collections of classes.</p>
|
D | index.jd | 2 page.metaDescription=Android Training provides a collection of classes that aim to help you build g… 6 <p>Welcome to Android Training. Here you'll find a collection of classes that aim to help you 13 on Android, you should walk through each of these classes, beginning with
|
/frameworks/base/tools/layoutlib/create/ |
D | README.txt | 21 as generated by the Android build, right before the classes are converted to a DEX format. 25 - some classes need to be overridden, for example all the drawing code that is 27 - some of the classes that need to be changed are final and/or we need access 32 - modifies some of the classes directly using some bytecode manipulation, 34 - injects some new classes, 42 change with the Android platform as new classes are added, changed or removed. 61 The goal of the analyzer is to create a graph of all the classes from the input JAR 64 To do that, the analyzer is created with a list of base classes to keep -- everything 74 With this information, the analyzer parses the input zip to find all the classes. 75 All classes deriving from the requested bases classes are kept. [all …]
|
/frameworks/base/docs/html/training/backward-compatible-ui/ |
D | new-implementation.jd | 40 … subclass the <code>CompatTab</code> and <code>TabHelper</code> abstract classes and use new APIs.… 44 …classes for <code>CompatTab</code> and <code>TabHelper</code> that use newer APIs are a <em>proxy<… 46 <p>You can directly use newer APIs in these concrete classes—and not crash on earlier devices… 48 …te classes. For example, the native tab implementation can be provided by <code>CompatTabHoneycomb… 50 <img src="{@docRoot}images/training/backward-compatible-ui-classes-honeycomb.png" 51 alt="Class diagram for the Honeycomb implementation of tabs." id="figure-classes">
|
D | abstracting.jd | 41 <p>In this class, you build a tabbed user interface (UI) component that uses abstract classes with … 45 …ing language involves the creation of one or more interfaces or abstract classes to hide implement… 47 …er classes you want to be able to use in a backward compatible way, then create abstract classes, … 49 <p>After creating abstract classes for these new APIs, any number of implementations can be created… 63 …s structure to support these two implementations and their abstract base classes (or interfaces) i… 65 <img src="{@docRoot}images/training/backward-compatible-ui-classes.png" 66 …alt="Class diagram of abstract base classes and version-specific implementations." id="figure-clas… 68 <p class="img-caption"><strong>Figure 1.</strong> Class diagram of abstract base classes and versio…
|
D | older-implementation.jd | 64 …tally laid-out {@link android.widget.Button} widgets). Implement this in classes called <code>TabH… 67 <img src="{@docRoot}images/training/backward-compatible-ui-classes-eclair.png" 68 alt="Class diagram for the Eclair implementation of tabs." id="figure-classes">
|
/frameworks/base/tools/layoutlib/bridge/tests/src/com/android/layoutlib/bridge/ |
D | TestDelegates.java | 46 final String[] classes = CreateInfo.DELEGATE_CLASS_NATIVES; in testNativeDelegates() local 47 final int count = classes.length; in testNativeDelegates() 49 loadAndCompareClasses(classes[i], classes[i] + "_Delegate"); in testNativeDelegates()
|
/frameworks/base/services/input/ |
D | EventHub.cpp | 164 classes(0), configuration(NULL), virtualKeyMap(NULL), in Device() 268 return device->classes; in getDeviceClasses() 1049 device->classes |= INPUT_DEVICE_CLASS_KEYBOARD; in openDeviceLocked() 1056 device->classes |= INPUT_DEVICE_CLASS_CURSOR; in openDeviceLocked() 1067 device->classes |= INPUT_DEVICE_CLASS_TOUCH | INPUT_DEVICE_CLASS_TOUCH_MT; in openDeviceLocked() 1073 device->classes |= INPUT_DEVICE_CLASS_TOUCH; in openDeviceLocked() 1080 uint32_t assumedClasses = device->classes | INPUT_DEVICE_CLASS_JOYSTICK; in openDeviceLocked() 1084 device->classes = assumedClasses; in openDeviceLocked() 1093 device->classes |= INPUT_DEVICE_CLASS_SWITCH; in openDeviceLocked() 1100 device->classes |= INPUT_DEVICE_CLASS_VIBRATOR; in openDeviceLocked() [all …]
|
/frameworks/base/docs/html/tools/testing/ |
D | testing_android.jd | 26 <a href="#TestCaseClasses">Test case classes</a> 29 <a href="#AssertionClasses">Assertion classes</a> 32 <a href="#MockObjectClasses">Mock object classes</a> 55 <h2>Key classes</h2> 100 new to Android testing, you can start with general-purpose test case classes such as {@link 101 android.test.AndroidTestCase} and then go on to use more sophisticated classes. 104 The Android JUnit extensions provide component-specific test case classes. These classes 144 structure of tests, test case classes, test packages, and test projects. 148 statements test a part of the application under test. You organize test methods into classes 156 Android test package. In JUnit, you use a test runner to execute test classes. In Android, you [all …]
|
D | testing_eclipse.jd | 38 It lets you quickly import the classes of the application under test, so that your 133 combine Activity classes, test case classes, or ordinary classes, your main test case 134 should extend one of the Android test case classes or JUnit classes, because these provide the 144 To create a test package, start with one of Android's test case classes defined in 146 {@link junit.framework.TestCase TestCase} class. The Android test classes for Activity objects 148 classes, please read the topic <a href="{@docRoot}tools/testing/testing_android.html"> 153 for your test case classes and the Android package name you want to use. To learn more 168 added classes yet, this node won't have any children, and its icon will not be filled in. 185 are extending. You can also browse the available classes. 227 tutorial with more information about creating test classes and methods. [all …]
|
D | testing_otheride.jd | 176 JUnit test case runner classes and Android instrumentation classes. 244 ordinary classes, you should extend one of the Android test classes or JUnit classes, 254 To create a test package, start with one of Android's test classes in the Java package 257 classes also provide instrumentation for testing. 260 For test classes that extend {@link junit.framework.TestCase TestCase}, you probably want to 308 application to the current AVD or device, and then runs all the test classes in the test 526 The fully-qualified Java class name for one of the test case classes. Only this test 541 Runs all test classes that extend {@link android.test.InstrumentationTestCase}. 548 Runs all test classes that do <em>not</em> extend either 567 Runs all test classes that implement {@link android.test.PerformanceTestCase}. [all …]
|
D | contentprovider_testing.jd | 20 <a href="#MockObjects">Mock object classes</a> 112 The test case class and mock object classes for provider testing set up this isolated testing 135 classes</a>. 144 <h3 id="MockObjects">Mock object classes</h3> 147 {@link android.test.mock.MockContentResolver}, which are standard mock object classes. To
|
D | service_testing.jd | 17 <a href="#MockObjects">Mock object classes</a> 109 objects are described in <a href="#MockObjects">Mock object classes</a>. 116 <h2 id="MockObjects">Mock object classes</h2> 139 Context classes you can use are described in more detail in
|
/frameworks/testing/uiautomator/cmds/uiautomator/src/com/android/commands/uiautomator/ |
D | RunTestCommand.java | 154 private void addTestClasses(String classes) { in addTestClasses() argument 155 String[] classArray = classes.split(CLASS_SEPARATOR); in addTestClasses()
|
/frameworks/compile/mclinker/lib/MC/ |
D | README | 6 to MCInst classes
|
/frameworks/base/tools/preload/ |
D | PrintHtmlDiff.java | 88 Iterable<LoadedClass> classes) { in printTable() argument 100 for (LoadedClass clazz : classes) { in printTable()
|
/frameworks/base/core/java/android/ddm/ |
D | README.txt | 1 Some classes that handle DDM traffic.
|
/frameworks/base/tools/layoutlib/ |
D | README | 4 None of the com.android.* or android.* classes in layoutlib run on devices.
|
/frameworks/base/docs/html/guide/topics/location/ |
D | index.jd | 29 can build these capabilities into your applications using the classes of the {@link 36 the device through the classes in the {@code android.location} package. The 67 com.google.android.maps package. The classes of the com.google.android.maps 88 in the SDK. So that you can develop using the classes of the
|
/frameworks/native/opengl/tools/glgen/ |
D | gen | 65 mkdir classes 66 javac -d classes com/google/android/gles_jni/GLImpl.java javax/microedition/khronos/opengles/GL10.j…
|
/frameworks/wilhelm/src/ |
D | README.txt | 14 objects/ OpenSL ES and OpenMAX AL objects aka classes
|
/frameworks/base/docs/html/tools/help/ |
D | monkeyrunner_concepts.jd | 81 You can also add your own classes to the monkeyrunner API. This is described 91 use Python syntax to access the constants, classes, and methods of the API. 255 You can extend the monkeyrunner API with classes you write in the Java programming language 257 monkeyrunner API with your own classes or to extend the existing classes. You can also use this 266 In your plugin code, you can import and extend the the main monkeyrunner classes
|
/frameworks/base/docs/html/guide/topics/resources/ |
D | available-resources.jd | 41 and {@code R.plurals} classes.</dd> 47 Saved in {@code res/values/} but each accessed from unique {@code R} sub-classes (such as {@code
|
/frameworks/base/tools/aidl/ |
D | generate_java.cpp | 77 document->classes.push_back(cl); in generate_java()
|
/frameworks/base/docs/html/guide/google/gcm/ |
D | demo.jd | 80 …<li>In a text editor, edit the <code>gcm-demo-server/WebContent/WEB-INF/classes/api.key</code> and… 89 [mkdir] Created dir: build/classes 93 [javac] Compiling 6 source files to build/classes 136 [enhance] DataNucleus Enhancer (version 1.1.4) : Enhancement of classes 137 …[enhance] DataNucleus Enhancer completed with success for 0 classes. Timings : input=28 ms, enhanc… 138 …[enhance] DataNucleus Enhancer completed and no classes were enhanced. Consult the log for full de…
|