/frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/ |
D | MockAnswerUtil.java | 41 Method implementation = getClass().getMethod("answer", method.getParameterTypes()); in answer() local 42 if (!implementation.getReturnType().equals(method.getReturnType())) { in answer() 45 + implementation.getReturnType()); in answer() 49 return implementation.invoke(this, args); in answer()
|
/frameworks/base/docs/html/training/backward-compatible-ui/ |
D | new-implementation.jd | 9 next.link=older-implementation.html 40 …de> abstract classes and use new APIs. Your application can use this implementation on devices run… 44 … and <code>TabHelper</code> that use newer APIs are a <em>proxy</em> implementation. Since the abs… 48 …implementation is to append the API level or platform version code name corresponding to the APIs … 51 alt="Class diagram for the Honeycomb implementation of tabs." id="figure-classes"> 53 <p class="img-caption"><strong>Figure 1.</strong> Class diagram for the Honeycomb implementation of… 57 <p><code>CompatTabHoneycomb</code> is the implementation of the <code>CompatTab</code> abstract cla… 86 <p><code>TabHelperHoneycomb</code> is the implementation of the <code>TabHelper</code> abstract cla… 111 // the base implementation.
|
D | index.jd | 46 …application-specific, intermediary Java interfaces that abstract the implementation of the UI comp… 48 <dt><strong><a href="new-implementation.html">Proxying to the New APIs</a></strong></dt> 49 <dd>Learn how to create an implementation of your interface that uses newer APIs.</dd> 51 …<dt><strong><a href="older-implementation.html">Creating an Implementation with Older APIs</a></st… 52 <dd>Learn how to create a custom implementation of your interface that uses older APIs.</dd> 55 …<dd>Learn how to choose an implementation to use at runtime, and begin using the interface in your…
|
D | older-implementation.jd | 7 previous.link=new-implementation.html 34 <p>This lesson discusses how to create an implementation that mirrors newer APIs yet supports older… 64 …implementation of action bar tabs, you can use a {@link android.widget.TabWidget} and {@link andro… 68 alt="Class diagram for the Eclair implementation of tabs." id="figure-classes"> 70 <p class="img-caption"><strong>Figure 1.</strong> Class diagram for the Eclair implementation of ta… 72 <p>The <code>CompatTabEclair</code> implementation stores tab properties such as the tab text and i… 82 // Our older implementation simply stores this 93 <p>The <code>TabHelperEclair</code> implementation makes use of methods on the 122 // the base implementation.
|
D | using-component.jd | 7 previous.link=older-implementation.html 64 …activity that can support the two tab implementations. For the older implementation (<code>TabHelp… 96 <p>For the <code>TabHelperHoneycomb</code> implementation, all you need is a {@link android.widget.… 107 … shown in the previous section to determine which <code>TabHelper</code> implementation to use.</p> 135 <p>Below are two screenshots of this implementation running on an Android 2.3 and Android 4.0 devic…
|
D | abstracting.jd | 7 next.link=new-implementation.html 39 …ces running earlier versions of the platform, you need to provide an implementation that supports … 45 …s the creation of one or more interfaces or abstract classes to hide implementation details. In th… 49 …ity, these implementations can vary by required API level. Thus, one implementation may use recent… 61 …s of your abstraction layer and begin using your new backward-compatible implementation sooner.</p> 91 <p>You can use an abstract class instead of an interface here to simplify the implementation of com…
|
/frameworks/base/docs/html/distribute/analyze/ |
D | start.jd | 12 Analytics is designed around the way you work, with flexible implementation 20 "https://developers.google.com/analytics/solutions/mobile-implementation-guide"> 21 mobile app implementation guide</a>. 44 "https://developers.google.com/analytics/solutions/mobile-implementation-guide"> 45 step-by-step implementation guide</a> to get Google Analytics working in your 59 implementation. 76 your Google Analytics implementation. Updates you make using Tag Manager get
|
/frameworks/base/docs/html/ndk/guides/audio/ |
D | index.jd | 4 <p>The NDK package includes an Android-specific implementation of the 15 implementation</a> of OpenSL ES, focusing on the differences between this implementation and the 26 programming notes</a> to ensure proper implementation of OpenSL ES.
|
/frameworks/native/opengl/specs/ |
D | EGL_ANDROID_blob_cache.txt | 61 device-specific EGL implementation. 74 * client API implementation may use to insert a key/value pair into the 82 * client API implementation may use to retrieve a cached value from the 138 key, a client API implementation can call the application-provided callback 153 guarantees, the cache implementation should attempt to cache the most 157 client API implementation can call the application-provided callback 179 implementation. The cache implementation can simply drop a value if it 191 requested again. If needed, the cache implementation can handle those 197 RESPONSE: This is entirely dependent upon the cache implementation.
|
D | EGL_ANDROID_create_native_client_buffer.txt | 115 correspond to a valid pixel format for the implementation. If EGL_ALPHA_SIZE 117 valid pixel format for the implementation. The 145 EGL implementation, the error EGL_BAD_PARAMETER is generated. 148 of gralloc usage flags for the EGL implementation, or is incompatible 164 The set of valid color combinations is implementation-specific and may 167 and implementation should be documented by that version.
|
/frameworks/base/tools/layoutlib/create/ |
D | README.txt | 46 provides all the necessary missing implementation for rendering graphics in Eclipse. 73 The analyzer is also given a list of classes to exclude. A fake implementation of these classes is 124 modified to update all references to these non-desktop classes. An alternate implementation of 136 changes the calls to a method in each class instead of changing the implementation of the method. 177 injected. The implementation for these classes has been taken from Android's libcore 180 added to the Dalvik VM for performance reasons. An implementation that is very close to the 190 bridge then registers a listener on the method signature and can provide an implementation. 200 original class name. This allows the bridge to literally replace an implementation. 209 native code in Eclipse, we need to provide a full alternate implementation. Sub-classing doesn't 219 not present in the Desktop VM. An implementation for these classes is also injected. [all …]
|
/frameworks/base/docs/html/training/game-controllers/ |
D | compatibility.jd | 46 <p>The examples in this lesson are based on the reference implementation 59 need to provide an implementation that supports Android 4.1 and higher while 185 <li>Define an intermediary Java interface that abstracts the implementation of 187 <li>Create a proxy implementation of your interface that uses APIs in Android 189 <li>Create a custom implementation of your interface that uses APIs available 272 higher and calls an {@code InputManagerCompat} method, the proxy implementation 274 However, if your game is running on Android 3.1 up to Android 4.0, the custom implementation 277 version-specific implementation is used at runtime, the implementation passes 288 <p>{@code InputManagerCompatV16} is an implementation of the 296 // The InputManagerCompatV16 class is a reference implementation. [all …]
|
/frameworks/base/docs/html/google/play/licensing/ |
D | adding-licensing.jd | 121 <p>The LVL includes a complete {@code Policy} implementation called ServerManagedPolicy 134 Rather, that responsibility is left to a {@code Policy} implementation that you provide 140 implementation of {@code Policy}. </p> 153 <p>A typical implementation would extract some or all fields from the license 169 example, your implementation of <code>allowAccess()</code> could take into 171 backend server. In all cases, an implementation of <code>allowAccess()</code> 175 such cases, your implementation can maintain a count of retry responses and 201 <p>In your licensing implementation, you can use one of the complete policies 204 points to understand and account for in your implementation.</p> 243 recommended. See the ServerManagedPolicy implementation for an example of how to [all …]
|
D | overview.jd | 128 adding licensing to your application and helps ensure a more secure, robust implementation for your 137 <dd>Your implementation determines whether to allow access to the 140 application). The implementation can evaluate the various fields of the license 141 response and apply other constraints, if needed. The implementation also lets 146 <dd>Your implementation manages access to the 148 response. Your implementation can manage access in any way needed, including 180 the SDK, so you can develop and test the licensing implementation in your 205 the design of your implementation itself. The service provides the building 208 practices in the following documents, you can help ensure that your implementation will be
|
D | licensing-reference.jd | 58 <td width="100%">Default {@code Policy} implementation. Uses settings provided by the 64 <td>Alternative {@code Policy} implementation. Enforces licensing based on a direct 78 <td>Default Obfuscator implementation that uses AES encryption/decryption 93 <td>Default DeviceLimiter implementation that is a no-op (allows access to all 124 <td>One-way IPC callback implementation over which the application receives an 227 implementation.</p> 257 <p>Any {@code Policy} implementation can extract the extras settings from the license 258 response and use them as needed. The LVL default {@code Policy} implementation, <a 261 implementation and an illustration of how to obtain, store, and use the 373 <p>The {@code ServerManagedPolicy} implementation uses the extracted timestamp [all …]
|
/frameworks/base/docs/html/training/graphics/opengl/ |
D | environment.jd | 56 <p>This lesson explains how to complete a minimal implementation of {@link 90 <p>The following code example shows a minimal implementation of an activity that uses a 126 implementation, it is common to 148 <p>One other optional addition to your {@link android.opengl.GLSurfaceView} implementation is to set 165 <p>The implementation of the {@link android.opengl.GLSurfaceView.Renderer} class, or renderer, 182 <p>Here is a very basic implementation of an OpenGL ES renderer, that does nothing more than draw a
|
/frameworks/minikin/doc/ |
D | hyb_file_format.md | 21 to the implementation in TeX. 75 character. Note that, in the current implementation, automatic hyphenation is disabled 93 implementation for consumers of the data would be to build a hash table at load time. 111 it with edge slots), which would require very minimal changes to the implementation (TODO
|
/frameworks/av/include/private/ |
D | README | 3 These include files are part of the private implementation details of
|
/frameworks/base/include/private/ |
D | README | 3 These include files are part of the private implementation details of
|
/frameworks/base/docs/html/guide/topics/ui/accessibility/ |
D | apps.jd | 87 <strong>Note:</strong> The implementation steps in this document describe the requirements for 295 accessibility event. As of API Level 14, the default implementation of this method calls {@link 315 <p class="note"><strong>Note:</strong> If your implementation of this event completely 317 do not call the super implementation of this method in your code.</p> 326 do override this method, you must call its super implementation and then only modify properties 332 the view. The default {@link android.view.View} implementation has a standard set of view 386 handled by the default implementation. The {@link android.view.View} class provides a default 387 implementation for these event types:</p> 442 The {@link android.view.View} implementation provides default values for these properties. Many of 453 following example code demonstrates a basic implementation of this method.</p> [all …]
|
/frameworks/base/docs/html/training/displaying-bitmaps/ |
D | display-bitmap.jd | 56 <p>Here’s an implementation of a {@link android.support.v4.view.ViewPager} with {@link 104 <p>Here is an implementation of the details {@link android.app.Fragment} which holds the {@link and… 105 you see the drawbacks of this implementation? How could it be improved?</p> 218 android.support.v4.view.ViewPager} implementation with minimal image loading latency and the ability 230 <p>To start with, here is a standard {@link android.widget.GridView} implementation with {@link 311 <p>Once again, the problem with this implementation is that the image is being set in the UI thread. 396 <p>This implementation allows for flexibility in how the images are processed and loaded without
|
/frameworks/base/docs/html/training/basics/activity-lifecycle/ |
D | recreating.jd | 91 pairs. The default implementation of this method saves information about the state of the activity's 115 <p class="caution"><strong>Caution:</strong> Always call the superclass implementation of {@link 116 android.app.Activity#onSaveInstanceState onSaveInstanceState()} so the default implementation 173 <p class="caution"><strong>Caution:</strong> Always call the superclass implementation of {@link 174 android.app.Activity#onRestoreInstanceState onRestoreInstanceState()} so the default implementation
|
/frameworks/base/docs/html/training/printing/ |
D | custom-docs.jd | 61 // Start a print job, passing in a PrintDocumentAdapter implementation 70 implementation of the print adapter class is discussed in the next section.</p> 121 you expect the execution of these methods in your implementation to take a significant amount of 129 <p>Within an implementation of the {@link android.print.PrintDocumentAdapter} class, your 132 The implementation of the {@link android.print.PrintDocumentAdapter#onLayout onLayout()} method in 135 content type. The following code example shows a basic implementation of the {@link 191 printing. The following code example shows an implementation where the number of pages is 217 written and the output file to be used. Your implementation of this method must then render each
|
/frameworks/base/docs/html/training/load-data-background/ |
D | handle-results.jd | 30 {@link android.support.v4.content.CursorLoader} in your implementation of 34 implementation of {@link android.support.v4.app.LoaderManager.LoaderCallbacks#onLoadFinished 113 the framework calls your implementation of
|
/frameworks/base/docs/html/google/play/billing/ |
D | billing_testing.jd | 25 implementation:</p> 55 <p>When your In-app Billing implementation is ready, you can test purchasing of your in-app SKUs in… 77 of your In-app Billing implementation during development or in preparation for 172 implementation before distributing the app to all of your users. </p> 190 <p>We recommend that you first test your In-app Billing implementation using static responses from 195 <p>To test your implementation with static responses, you make an In-app Billing request using a 227 implementation using these responses.</p> 298 working in your application, you can test your In-app Billing implementation by making actual in-app 309 <p>To test your In-app Billing implementation with actual in-app purchases, you will need to 319 <p>To test your In-app Billing implementation with actual purchases, follow these steps:</p> [all …]
|