/frameworks/base/docs/html/training/custom-views/ |
D | create-view.jd | 7 next.link=custom-drawing.html 25 <li><a href="{@docRoot}guide/topics/ui/custom-components.html">Custom Components</a> 37 <p>A well-designed custom view is much like any other well-designed class. It encapsulates a 41 well-designed class, though, a custom view should: 45 <li>Provide custom styleable attributes that work with Android XML layouts</li> 59 custom view can also 81 appearance and behavior with element attributes. Well-written custom views can also be added and 83 enable this behavior in your custom view, you must: 86 <li>Define custom attributes for your view in a {@code 95 <p>This section discusses how to define custom attributes and specify their values. [all …]
|
D | index.jd | 19 <li><a href="{@docRoot}guide/topics/ui/custom-components.html">Custom Components</a> 50 <dd>Create a class that acts like a built-in view, with custom 54 <dt><b><a href="custom-drawing.html">Custom Drawing</a></b></dt> 67 custom drawings run faster.
|
/frameworks/base/docs/html/guide/topics/ui/accessibility/ |
D | apps.jd | 18 <li><a href="#custom-views">Building Accessible Custom Views</a> 25 <li><a href="#custom-touch-events">Handling custom touch events</a></li> 82 <p>If you build custom controls that extend the {@link android.view.View} class, you must complete 84 make custom view controls compatible with accessibility services.</p> 235 <h2 id="custom-views">Building Accessible Custom Views</h2> 237 <p>If your application requires a <a href="{@docRoot}guide/topics/ui/custom-components.html">custom 238 view component</a>, you must do some additional work to ensure that your custom view is accessible. 244 <li>Send {@link android.view.accessibility.AccessibilityEvent} objects specific to your custom 256 android.view.KeyEvent#KEYCODE_DPAD_CENTER} appropriately. When building a custom {@link 260 <p>Your custom control should also treat the {@link android.view.KeyEvent#KEYCODE_ENTER} event the [all …]
|
D | checklist.jd | 72 <a href="{@docRoot}guide/topics/ui/custom-components.html">custom interface controls</a> for 73 your application, <a href="{@docRoot}guide/topics/ui/accessibility/apps.html#custom-views"> 74 implement accessibility interfaces</a> for your custom views and provide content descriptions. 75 For custom controls that are intended to be compatible with versions of Android back to 1.6, 121 <a href="{@docRoot}guide/topics/ui/custom-components.html">custom control</a> with a high degree 127 <li><strong>Custom controls and click handling:</strong> If a custom control in your 134 <a href="{@docRoot}guide/topics/ui/accessibility/apps.html#custom-touch-events">Handling custom 159 <li><strong>Custom controls with complex visual interactions:</strong> For custom controls that
|
/frameworks/base/docs/html/about/versions/ |
D | android-5.0-changes.jd | 165 {@link android.app.Notification.MediaStyle} template instead of a custom 298 overview, Android apps can define custom permissions as a means of managing 300 pre-defined system permissions. Apps define custom permissions in <a href= 306 There are a small number of scenarios where defining custom permissions is a 307 legitimate and secure approach. However, creating custom permissions is 314 that only one app can define a given custom permission, unless signed with the 319 Apps using duplicate custom permissions 323 Any app can define any custom permission it wants, so it can happen 324 that multiple apps might <strong>define the same custom permission</strong>. 326 same logical name for their custom permissions. Apps might also incorporate [all …]
|
/frameworks/base/docs/html/training/id-auth/ |
D | custom_auth.jd | 35 device. This lesson explains how to create a custom account type that works the 58 android.accounts.AccountAuthenticatorActivity}, which you can extend to create your own custom 63 were only one way to do it, there'd be no need for "custom" account types, after 92 custom account code.</p> 95 You've already implemented the meat of your custom account code; what's left is 101 <p>In order for the {@link android.accounts.AccountManager} to work with your custom account 121 things, the name of your custom account type and the icon that the system will 132 used to launch your custom authenticator activity. If your authenticator 171 accounts of your custom type will be able to enumerate and authenticate just as 182 an app wishes to use your custom account type, it can check the device to see if [all …]
|
/frameworks/base/docs/html/guide/topics/search/ |
D | index.jd | 10 <li><a href="adding-custom-suggestions.html">Adding Custom Suggestions</a></li> 31 <img src="{@docRoot}images/search/search-suggest-custom.png" alt="" height="417" /> 32 <p class="img-caption"><strong>Figure 1.</strong> Screenshot of a search dialog with custom 48 <li>Provide custom search suggestions that match actual results in your application data</li> 58 search interface in your application. When using the search dialog or a custom interface, you 71 <dt><strong><a href="adding-custom-suggestions.html">Adding Custom Suggestions</a></strong></dt> 72 <dd>How to provide suggestions based on custom data from your application and also offer them 107 implementing custom suggestions, you'll need to provide a similar "clear history" method in your
|
D | adding-custom-suggestions.jd | 49 <p>When using the Android search dialog or search widget, you can provide custom search suggestions 54 an example of a search dialog with custom suggestions.</p> 56 <p>Once you provide custom suggestions, you can also make them available to the system-wide Quick 59 <p>Before you begin with this guide to add custom suggestions, you need to have implemented the 67 <img src="{@docRoot}images/search/search-suggest-custom.png" alt="" height="417" /> 68 <p class="img-caption"><strong>Figure 1.</strong> Screenshot of a search dialog with custom 72 <p>When the user selects a custom suggestion, the Android system sends an {@link 75 android.content.Intent#ACTION_SEARCH} action, you can instead define your custom suggestions to use 81 <p>To provide custom suggestions, do the following:</p> 87 provides custom suggestions.</li> [all …]
|
/frameworks/base/docs/html/training/wearables/watch-faces/ |
D | drawing.jd | 23 face service, you can start writing code to initialize and draw your custom watch face.</p> 46 custom animations, configuring paint styles, and performing other computations. You can usually 53 <li>Declare variables for a custom timer, graphic objects, and other elements.</li> 55 <li>Initialize the custom timer in the <code>Engine.onVisibilityChanged()</code> method.</li> 78 run animations at custom time intervals. In these cases, you need to provide a custom timer that 87 these variables as shown in the snippet below. The custom timer is implemented as a 89 message queue. For this particular watch face, the custom timer ticks once every second. When the 193 <h3 id="Timer">Initialize the custom timer</h3> 196 providing a custom timer that ticks with the required frequency while the device is in 197 interactive mode. This enables you to create custom animations and other visual effects. [all …]
|
/frameworks/base/docs/html/training/volley/ |
D | request-custom.jd | 13 <li><a href="#custom-request">Write a Custom Request</a></li> 26 <p>This lesson describes how to implement your own custom request types, for types that 29 <h2 id="custom-request">Write a Custom Request</h2> 32 image, or JSON, you probably won't need to implement a custom {@code Request}.</p> 34 <p>For cases where you do need to implement a custom request, this is all you need 42 create your custom request by extending {@code Request<String>}. See the Volley
|
/frameworks/base/docs/html/training/transitions/ |
D | custom-transitions.jd | 17 <p>A custom transition enables you to create an animation that is not available from any of 18 the built-in transition classes. For example, you can define a custom transition that turns 22 <p>A custom transition, like one of the built-in transition types, applies animations to 28 custom transitions.</p> 34 <p>To create a custom transition, add a class to your project that extends the {@link 160 implemented as a custom transition. If the starting scene has five targets of which two are 175 a custom transition, use the view property values you captured to create an {@link 187 <p>Custom transitions work the same as built-in transitions. You can apply a custom transition
|
D | index.jd | 44 for common effects and lets you create custom animations and transition lifecycle callbacks.</p> 47 animate changes between view hierarchies. This class also covers how to create custom 75 <dt><a href="{@docRoot}training/transitions/custom-transitions.html">
|
/frameworks/base/docs/html/guide/topics/ui/ |
D | custom-components.jd | 10 <li><a href="#custom">Fully Customized Components</a></li> 45 of a screen element. To give an idea of the control you get with custom views, here are some 50 You could create a completely custom-rendered View type, for example a "volume 67 You could capture other events like key presses and handle them in some custom 72 The sections below explain how to create custom Views and use them in your application. 109 <h2 id="custom">Fully Customized Components</h2> 156 custom components, styled text, or anything else you can think of.</p> 321 of a customized View. The custom View is defined in the 324 <p>The LabelView sample demonstrates a number of different aspects of custom components:</p> 326 <li>Extending the View class for a completely custom component.</li> [all …]
|
/frameworks/base/docs/html/training/wearables/apps/ |
D | layouts.jd | 12 <li><a href="#CustomNotifications">Create custom notifications</a></li> 26 and the UI from a handheld app and expect a good experience. You should create custom layouts 42 a custom layout. You can only create and issue custom notifications on the wearable, and the 45 <p clas="note"><b>Note:</b> When creating custom notifications on the wearable, you can use the 49 <p>To create a custom notification:</p> 90 custom activity for the notification.</p>
|
/frameworks/base/docs/html/tools/devices/ |
D | managing-avds.jd | 75 <p>If necessary, click <strong>Show Advanced Settings</strong> to select a custom skin 89 you can create a custom device definition for your AVD:</p> 92 <li>To begin you custom device by using an existing device profile as a template, select 104 creating a custom device configuration.</p> 106 <li>Your custom device configuration is now available in the list of device definitions 108 with your custom device configuration, select the new configuration and follow the instructions 281 you can create your own custom skin definition, then apply it to your AVD from the 290 <p>To create and use a custom skin:</p> 328 <li>Archive the files in the skin folder and select the archive file as a custom skin. </li>
|
/frameworks/base/docs/html/distribute/analyze/ |
D | measure.jd | 117 ways to send custom data that you define and incorporate into your app. That 141 Custom dimensions are another way to send custom data that is specific to 142 your business. Good for capturing a state of something in your app, custom 144 use case might be using a user-scoped custom dimension to capture the 147 An example of a hit-level custom dimension could be capturing landscape or 157 A specific custom dimension that may be of interest to your business is the 161 behavior across platforms. Note that your custom identifier must be an identifier
|
/frameworks/base/core/java/com/android/internal/widget/ |
D | ScrollingTabContainerView.java | 420 final View custom = tab.getCustomView(); in update() local 421 if (custom != null) { in update() 422 final ViewParent customParent = custom.getParent(); in update() 424 if (customParent != null) ((ViewGroup) customParent).removeView(custom); in update() 425 addView(custom); in update() 427 mCustomView = custom; in update()
|
/frameworks/base/docs/html/training/wearables/ui/ |
D | index.jd | 21 <p>This class teaches you how to create custom UIs for your 23 <a href="{@docRoot}training/wearables/apps/layouts.html#CustomNotifications">custom 49 <dd>Learn how to create cards with custom layouts.</dd>
|
/frameworks/support/v4/java/android/support/v4/app/ |
D | FragmentActivity.java | 134 Object custom; field in FragmentActivity.NonConfigurationInstances 483 Object custom = onRetainCustomNonConfigurationInstance(); in onRetainNonConfigurationInstance() local 505 if (fragments == null && !retainLoaders && custom == null) { in onRetainNonConfigurationInstance() 511 nci.custom = custom; in onRetainNonConfigurationInstance() 612 return nc != null ? nc.custom : null; in getLastCustomNonConfigurationInstance()
|
/frameworks/support/v7/appcompat/src/android/support/v7/internal/widget/ |
D | ScrollingTabContainerView.java | 443 final View custom = tab.getCustomView(); in update() local 444 if (custom != null) { in update() 445 final ViewParent customParent = custom.getParent(); in update() 447 if (customParent != null) ((ViewGroup) customParent).removeView(custom); in update() 448 addView(custom); in update() 450 mCustomView = custom; in update()
|
/frameworks/opt/vcard/tests/res/raw/ |
D | v21_x_param.vcf | 4 ADR;X-custom:pobox;street
|
/frameworks/base/tools/layoutlib/bridge/tests/res/testApp/MyApplication/ |
D | .gitignore | 6 # We need the built .class files to load custom views and R class.
|
/frameworks/base/tools/layoutlib/ |
D | README | 1 Layoutlib is a custom version of the android View framework designed to run inside Eclipse.
|
/frameworks/base/docs/html/training/printing/ |
D | index.jd | 39 your application, including printing images, HTML pages and creating custom documents for 58 <strong><a href="custom-docs.html">Printing a Custom Document</a></strong>
|
/frameworks/base/docs/html/training/basics/actionbar/ |
D | overlaying.jd | 52 If you want your layout to be partially visible behind the action bar, create a custom 60 <p>To enable overlay mode for the action bar, you need to create a custom theme that 69 is set to {@code 11} or higher, your custom theme should use 87 running versions lower than Android 3.0, your custom theme should use
|