Searched refs:UI (Results 1 – 25 of 372) sorted by relevance
12345678910>>...15
/frameworks/base/docs/html/training/multiple-threads/ |
D | communicate-ui.jd | 1 page.title=Communicating with the UI Thread 12 <li><a href="#Handler">Define a Handler on the UI Thread</a></li> 13 <li><a href="#MoveValues">Move Data from a Task to the UI Thread</a> 33 from the task to objects running on the user interface (UI) thread. This feature allows your 34 tasks to do background work and then move the results to UI elements such as bitmaps. 37 Every app has its own special thread that runs UI objects such as {@link android.view.View} 38 objects; this thread is called the UI thread. Only objects running on the UI thread have access 40 <em>aren't</em> running on your UI thread, they don't have access to UI objects. To move data 41 from a background thread to the UI thread, use a {@link android.os.Handler} that's 42 running on the UI thread. [all …]
|
/frameworks/base/docs/html/training/activity-testing/ |
D | activity-ui-testing.jd | 1 page.title=Testing UI Components 12 <li><a href="#testcase">Create a Test Case for UI Testing with Instrumentation</a> 13 <li><a href="#test_method">Add Test Methods to Verify UI Behavior</a> 36 you can test an {@link android.app.Activity} with a simple push-button UI. You 37 can use the same general steps to test other, more sophisticated types of UI 40 <p class="note"><strong>Note:</strong> The type of UI testing in this lesson is 44 framework is suitable for creating white-box tests for UI components within an 45 application. An alternative type of UI testing is <em>black-box testing</em>, 50 <a href="{@docRoot}tools/testing/testing_ui.html">UI Testing guide</a>. 54 <h2 id="testcase">Create a Test Case for UI Testing with Instrumentation</h2> [all …]
|
/frameworks/base/docs/html/training/system-ui/ |
D | visibility.jd | 1 page.title=Responding to UI Visibility Changes 43 of system UI visibility changes. This is useful if you want to 44 synchronize other parts of your UI with the hiding/showing of system bars.</p> 48 <p>To get notified of system UI visibility changes, register an 64 // adjustments to your UI, such as showing the action bar or 68 // adjustments to your UI, such as hiding the action bar or 74 <p>It's generally good practice to keep your UI in sync with changes in system bar
|
D | immersive.jd | 91 keep all UI controls in sync with the system bars, to minimize the 93 here all UI controls are displayed along with the status bars. Once the app enters 94 immersive mode, the UI controls are hidden along with the system bars. 95 To ensure that your UI visibility stays in sync with system bar visibility, make sure to 98 <a href="visibility.html">Responding to UI Visibility Changes</a>.</p></li> 110 system bars and other UI controls hidden. You can achieve this state with either 114 <li><strong>Sticky flag</strong>—This is the UI you see if you use the 118 system UI visibility change listeners, because the transient appearance of the system bars isn't 119 considered a UI visibility change.</li> 140 the action bar and other UI controls somewhat frequently, but not be bothered with any UI [all …]
|
D | status.jd | 91 <li>It results in smoother UI transitions, because the system has the information it needs 92 to render your UI before instantiating your app's main activity.</li> 131 {@link android.view.View#setSystemUiVisibility setSystemUiVisibility()} sets UI flags at 133 {@link android.view.View#setSystemUiVisibility setSystemUiVisibility()} to set UI flags 150 <li>Once UI flags have been cleared (for example, by navigating away from the 152 See <a href="visibility.html">Responding to UI Visibility Changes</a> for a 153 discussion of how to listen for UI visibility changes so that your app can 156 <li>Where you set the UI flags makes a difference. If you hide the system bars in your activity's 159 won't get called, so the system bars will remain visible. If you want system UI changes to 160 persist as the user navigates in and out of your activity, set UI flags in [all …]
|
D | index.jd | 1 page.title=Managing the System UI 78 Guide</a>, you know the importance of designing your apps to conform to standard Android UI 116 <strong><a href="visibility.html">Responding to UI Visibility Changes</a></strong> 119 Learn how to register a listener to get notified of system UI visibility changes 120 so that you can adjust your app's UI accordingly.
|
D | navigation.jd | 80 want to hide the bars again. See <a href="visibility.html">Responding to UI Visibility Changes</a> … 81 discussion of how to listen for UI visibility changes so that your app can 84 <li>Where you set the UI flags makes a difference. If you hide the system bars in your activity's 87 won't get called, so the system bars will remain visible. If you want system UI changes to 88 persist as the user navigates in and out of your activity, set UI flags in 109 of your app's UI don't end up getting covered by system bars. For more
|
/frameworks/base/docs/html/tools/testing/ |
D | activity_testing.jd | 37 <a href="#UITesting">Appendix: UI Testing Notes</a> 40 <a href="#RunOnUIThread">Testing on the UI thread</a> 49 <a href="#UITestTroubleshooting">Troubleshooting UI tests</a> 112 directly to the UI of the activity under test. 228 <h2 id="UITesting">Appendix: UI Testing Notes</h2> 230 The following sections have tips for testing the UI of your Android application, specifically 231 to help you handle actions that run in the UI thread, touch screen and keyboard events, and home 234 <h3 id="RunOnUIThread">Testing on the UI thread</h3> 236 An application's activities run on the application's <strong>UI thread</strong>. Once the 237 UI is instantiated, for example in the activity's <code>onCreate()</code> method, then all [all …]
|
D | testing_ui.jd | 1 page.title=UI Testing 14 <li><a href="#uianalysis">Analyzing Your UI</a></li> 18 <LI><a href="#identifyUI">Identify UI Components</a></LI> 53 …UI) when it is running on a device. UI testing ensures that your application returns the correct U… 56 Functional or black-box UI testing does not require testers to know the internal implementation det… 58 …UI testing is to run tests manually and verify that the app is behaving as expected. However, this… 61 <p>The Android SDK provides the following tools to support automated, functional UI testing on your… 63 <LI>{@code uiautomatorviewer} - A GUI tool to scan and analyze the UI components of an Android appl… 64 <LI>{@code uiautomator} - A Java library containing APIs to create customized functional UI tests, … 75 <p>Here's a short overview of the steps required to automate UI testing: [all …]
|
/frameworks/base/docs/html/tools/help/uiautomator/ |
D | UiCollection.jd | 8 <p>Used to enumerate a container's user interface (UI) elements for the purpose of counting, 84 …<div class="jd-descrdiv">Searches for child UI element within the constraints of this <code><a hr… 103 …<div class="jd-descrdiv">Searches for child UI element within the constraints of this <code><a hr… 121 …<div class="jd-descrdiv">Searches for child UI element within the constraints of this <code><a hr… 139 … <div class="jd-descrdiv">Counts child UI element instances matching the <code>childPattern</code> 210 …<div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element re… 229 …<div class="jd-descrdiv">Performs a click at the center of the visible bounds of the UI element re… 268 <div class="jd-descrdiv">Clicks the bottom and right corner of the UI element</div> 286 <div class="jd-descrdiv">Clicks the top and left corner of the UI element</div> 304 <div class="jd-descrdiv">Check if UI element exists.</div> [all …]
|
D | index.jd | 23 …sting framework lets you test your user interface (UI) efficiently by creating automated functiona… 24 …e uiautomator} framework, see <a href="{@docRoot}tools/testing/testing_ui.html">UI Testing</a>.</p> 87 <td>Generate an XML file with a dump of the current UI hierarchy. If a filepath is not specified, b… 103 …asses, interfaces, and exceptions that allow you to capture and manipulate UI components on the ta… 114 <td>Used to enumerate a container's user interface (UI) elements for the purpose of counting, or ta… 124 <td>Represents a user interface (UI) element.</td> 129 <td>Provides support for searching for items in a scrollable UI container.</td> 134 <td>Represents a query for one or more target UI elements on a device screen. </td> 179 …omator/UiSelector.html">{@code UiSelector}</a> could not be matched to any UI element displayed.</…
|
/frameworks/base/docs/html/training/ |
D | best-ui.jd | 9 devices. Android provides a flexible framework for UI design that allows your app to display 10 different layouts for different devices, create custom UI widgets, and even control aspects 11 of the system UI outside your app's window.</p>
|
/frameworks/base/docs/html/auto/ |
D | overview.jd | 68 <li><a href="#uioverview">UI Overview</a></li> 78 <li><a href="#customizeui">Customizing the UI</a></li> 97 services you are already familiar with. Android Auto provides an easy to use UI model and 101 <dt style="margin-bottom:10px"><strong>Media UI</strong></dt> 103 Android Auto defines interaction models and car-specific UI patterns for apps. The 146 should not. Android Auto was designed to simplify not only the UI, but to optimize interactions 172 <p>The Android Auto app shows your app's customized UI on the vehicle's screen. To communicate 187 <p><strong>Android Auto App</strong> - Creates the UI and handles user interactions. 208 <p>The Android Auto app uses a car-specific UI model to display content and user interaction 209 opportunities. Android Auto provides you with a standard UI designed to minimize driver [all …]
|
/frameworks/base/docs/html/guide/topics/ui/ |
D | overview.jd | 1 page.title=UI Overview 22 draw some part of the UI. This hierarchy tree can be as simple or complex as you need 27 UI layout.</p> 34 <code><TextView></code> element creates a {@link android.widget.TextView} widget in your UI, 60 <p>For a complete guide to creating a UI layout, see <a href="declaring-layout.html">XML 66 <p>You don't have to build all of your UI using {@link android.view.View} and {@link 68 a standard UI layout for which you simply need to define the content. These UI components each
|
/frameworks/base/docs/html/guide/components/ |
D | processes-and-threads.jd | 197 your application interacts with components from the Android UI toolkit (components from the {@link 199 called the UI thread.</p> 202 components that run in the same process are instantiated in the UI thread, and system calls to 205 or a lifecycle callback method) always run in the UI thread of the process.</p> 207 <p>For instance, when the user touches a button on the screen, your app's UI thread dispatches the 209 the event queue. The UI thread dequeues the request and notifies the widget that it should redraw 214 everything is happening in the UI thread, performing long operations such as network access or 215 database queries will block the whole UI. When the thread is blocked, no events can be dispatched, 217 application appears to hang. Even worse, if the UI thread is blocked for more than a few seconds 223 <p>Additionally, the Andoid UI toolkit is <em>not</em> thread-safe. So, you must not manipulate [all …]
|
/frameworks/base/docs/html/tools/ |
D | index.jd | 35 <h3>Graphical UI Builders</h3> 37 <li>Build rich Android UI with drag and drop. 38 …<li>Visualize your UI on tablets, phones, and other devices. Switch themes, locales, even platform… 40 <li>Editor support for working with custom UI components.</li> 98 …<li>Graphical tools for debugging and optimizing UI, runtime inspecton of UI structure and perform… 106 <li>Integrated reports using standard test UI.</li>
|
/frameworks/base/docs/html/training/articles/ |
D | perf-anr.jd | 47 (frequently a network access) on the UI thread so the system can't 50 structure or computing the next move in a game on the UI thread. It's always important to make 55 <strong>you should not perform the work on the UI thread</strong>, but instead create a 56 worker thread and do most of the work there. This keeps the UI thread (which drives the user 79 the "UI thread" or "main thread"). 80 This means anything your application is doing in the UI thread that 85 <p>Therefore, any method that runs in the UI thread should do as little work 102 runs on the UI thread), you can notify the user. For example:</p> 145 as the UI thread by default.</p> 148 be sure that your UI thread does not block while waiting for the worker thread to [all …]
|
/frameworks/base/docs/html/training/wearables/ui/ |
D | index.jd | 16 principles</a> and implement the recommended <a href="{@docRoot}design/wear/patterns.html">UI 24 UI patterns:</p> 34 <p>The Wearable UI Library, which is part of the Google Repository in the Android SDK, 52 <dd>Learn how to implement the 2D Picker UI pattern to navigate through pages of data.</dd> 56 …<dd>Learn how to implement the long-press-to-dismiss UI pattern to exit full-screen activities.</d…
|
/frameworks/base/docs/html-intl/intl/ja/guide/publishing/ |
D | preparing.jd | 59 … JUnit およびその他のテスト ケースを実行できます。また、<a href="{@docRoot}tools/help/monkey.html">UI/Application Exercise… 62 …ーションを実際のデバイスでテストすることは非常に重要です。これによって、作成したユーザー インターフェース要素のサイズが正しく(特にタッチスクリーン UI の場合)、アプリケーションのパフォーマン… 64 …の画面、ネットワーク パフォーマンス、その他の属性をモデル化して可能な限り対象デバイスに適応させることができます。このようにして、アプリケーションの UI とパフォーマンスをテストできます。ただし… 66 <li>アプリケーションが <a href="http://www.t-mobileg1.com/">T-Mobile G1</a> デバイスを対象としている場合、UI が画面の向き変更に対応してい… 154 <p>コンパイルしたアプリケーションをリリースする前に、対象とする携帯端末(および可能ならば対象ネットワーク)上で徹底的にテストする必要があります。特に、UI 部分の MapView 要素がマップ …
|
/frameworks/base/docs/html/training/displaying-bitmaps/ |
D | index.jd | 43 android.graphics.Bitmap} objects in a way that keeps your user interface (UI) components responsive 64 <li>Android app UI’s frequently require several bitmaps to be loaded at once. Components such as 77 <dt><b><a href="process-bitmap.html">Processing Bitmaps Off the UI Thread</a></b></dt> 79 on the main UI thread. This lesson walks you through processing bitmaps in a background thread 84 responsiveness and fluidity of your UI when loading multiple bitmaps.</dd> 89 <dt><b><a href="display-bitmap.html">Displaying Bitmaps in Your UI</a></b></dt>
|
/frameworks/base/docs/html/training/backward-compatible-ui/ |
D | older-implementation.jd | 38 …UI features in a backward-compatible way is deciding on and implementing an older (fallback) solut… 47 …get.LinearLayout} containing buttons, or using the {@link android.widget.TabWidget} UI element.</p> 60 …UI components to older devices. Be mindful of the user experience: on older devices, users may not…
|
/frameworks/base/docs/html/training/keyboard-input/ |
D | visibility.jd | 14 <li><a href="#Respond">Specify How Your UI Should Respond</a></li> 24 how your UI and the text field appear above the input method. For example, when the vertical 90 <h2 id="Respond">Specify How Your UI Should Respond</h2> 93 for your app's UI. The system makes a decision as to how it should adjust the visible portion 94 of your UI, but it might not get it right. To ensure the best behavior for your app, 95 you should specify how you'd like the system to display your UI in the remaining space.</p> 127 <p>Specifying {@code "adjustResize"} is important if your UI includes controls that the
|
/frameworks/base/docs/html/design/style/ |
D | metrics-grids.jd | 2 page.metaDescription=Optimize your app's UI by designing layouts based on density-independent grids. 23 <p>Optimize your application's UI by designing 53 <p>Touchable UI components are generally laid out along 48dp units.</p> 68 targetability of UI elements on the other.</li> 76 <p>Spacing between each UI element is 8dp.</p>
|
/frameworks/base/samples/training/network-usage/ |
D | README.txt | 8 …s the XML feed, combines feed elements with HTML markup, and displays the resulting HTML in the UI. 10 -- Lets users control their network data usage through a settings UI. Users can choose to fetch the…
|
/frameworks/base/docs/html/distribute/essentials/quality/ |
D | tablets.jd | 20 <li><a href="#google-play">11. Showcase Your Tablet UI</a></li> 39 intuitive, well-designed UI. 90 tablets — you need to optimize your layouts and other UI components for 91 each targeted screen configuration. On tablets, optimizing your UI lets you 103 parts of your UI to replace "stretched UI" with an efficient multipane UI, 112 style="font-weight:500;">Get rid of "stretched" UI</span>: On tablets, single-pane 114 reduce the width of UI elements and consider using multi-pane layouts.</p> 134 <li>Adjust positioning of UI controls so that they are easily accessible to 139 <li>Padding of UI elements should normally be larger on tablets than on 158 multi-pane UI for tablets (see next section).</li> [all …]
|
12345678910>>...15