HomeSort by relevance Sort by last modified time
    Searched full:applications (Results 76 - 100 of 3186) sorted by null

1 2 34 5 6 7 8 91011>>

  /external/libvpx/libvpx/
mainpage.dox 10 applications with the VP8 video codec, a high quality, royalty free, open
26 - The \ref readme contains instructions on recompiling the sample applications.
  /frameworks/base/core/java/android/os/
NetworkOnMainThreadException.java 22 * <p>This is only thrown for applications targeting the Honeycomb
23 * SDK or higher. Applications targeting earlier SDK versions
  /frameworks/base/location/lib/java/com/android/location/provider/
ProviderPropertiesUnbundled.java 22 * This class is an interface to Provider Properties for unbundled applications.
25 * applications, and must remain API stable. See README.txt in the root
ProviderRequestUnbundled.java 27 * This class is an interface to Provider Requests for unbundled applications.
30 * applications, and must remain API stable. See README.txt in the root
  /packages/apps/QuickSearchBox/benchmarks/src/com/android/quicksearchbox/benchmarks/
ApplicationsLatency.java 39 new ComponentName("com.android.providers.applications",
40 "com.android.providers.applications.ApplicationLauncher");
  /packages/providers/ApplicationsProvider/
AndroidManifest.xml 2 package="com.android.providers.applications"
9 <provider android:name="ApplicationsProvider" android:authorities="applications"
  /packages/providers/ApplicationsProvider/res/values-en-rGB/
strings.xml 19 <string name="app_label" msgid="8842303127802367578">"Search Applications Provider"</string>
22 <string name="settings_description" msgid="966629744054022387">"Names of installed applications"</string>
  /packages/providers/ApplicationsProvider/res/values-fr/
strings.xml 20 <string name="search_label" msgid="6182832093760999173">"Applications"</string>
22 <string name="settings_description" msgid="966629744054022387">"Noms des applications installées"</string>
  /packages/providers/ApplicationsProvider/src/com/android/providers/applications/
ApplicationsProvider.java 17 package com.android.providers.applications;
50 import android.provider.Applications;
62 * Fetches the list of applications installed on the phone to provide search suggestions.
64 * {@link android.provider.Applications} should be updated.
67 * to date list of installed applications. Alternatively, Launcher could be updated to use this
100 private static final String APPLICATIONS_TABLE = "applications";
114 * An in-memory database storing the details of applications installed on
124 * applications list within this window.
130 matcher.addURI(Applications.AUTHORITY, SearchManager.SUGGEST_URI_PATH_QUERY,
132 matcher.addURI(Applications.AUTHORITY, SearchManager.SUGGEST_URI_PATH_QUERY + "/*"
    [all...]
  /packages/providers/ApplicationsProvider/tests/
AndroidManifest.xml 18 package="com.android.providers.applications.tests">
25 android:targetPackage="com.android.providers.applications"
  /packages/providers/TelephonyProvider/res/values/
strings.xml 20 Applications" UI. This is the version of the label for tablet
26 Applications" UI. The TelephonyProvider stores configuration
  /frameworks/base/docs/html/about/versions/
android-2.3-highlights.jd 129 <h3>Control over applications</h3>
131 <p>A shortcut to the Manage Applications control now appears in the Options Menu
133 application activity. Once the user enters Manage Applications, a new Running
134 tab displays a list of active applications and the storage and memory being used
141 <p>An updated set of standard applications lets the user take new approaches to
182 download manager facility in the system that any other applications can use, to
194 let developers bring new types of applications to the Android
208 common operations faster and more efficient for all applications. Of particular
215 applications. </li>
218 distribution. The changes improve responsiveness for all applications, bu
    [all...]
android-3.0-highlights.jd 66 <p>The new UI brings fresh paradigms for interaction, navigation, and customization and makes them available to all applications &mdash; even those built for earlier versions of the platform. Applications written for Android 3.0 are able to use an extended set of UI objects, powerful graphics, and media capabilities to engage users in new ways.</p>
70 <p>Across the system and in all applications, users have quick access to notifications, system status, and soft navigation buttons in a System Bar, available at the bottom of the screen. The System Bar is always present and is a key touchpoint for users, but in a new "lights out mode" can also be dimmed for full-screen viewing, such as for videos.</p>
74 <p>In every application, users have access to contextual options, navigation, widgets, or other types of content in an Action Bar, displayed at the top of the screen. The Action Bar is always present when an application is in use, although its content, theme, and other properties are managed by the application rather than the system. The Action Bar is another key touchpoint for users, especially with action items and an overflow dropdown menu, which users frequently access in a similar manner in most applications. </p>
85 <p>Five customizable Home screens give users instant access to all parts of the system from any context. Each screen offers a large grid that maintains spatial arrangement in all orientations. Users can select and manipulate Home screen widgets, app shortcuts, and wallpapers using a dedicated visual layout mode. Visual cues and drop shadows improve visibility when adjusting the layout of shortcuts and widgets. Each Home screen also offers a familiar launcher for access to all installed applications, as well as a Search box for universal search of apps, contacts, media files, web content, and more.</p>
97 <p>Multitasking is a key strength of Android and it is central to the Android 3.0 experience. As users launch applications to handle various tasks, they can use the Recent Apps list in the System Bar to see the tasks underway and quickly jump from one application context to another. To help users rapidly identify the task associated with each app, the list shows a snapshot of its actual state when the user last viewed it.</p>
130 <p>The Android 3.0 platform includes an updated set of standard applications that are designed for use on larger screen devices. The sections below highlight some of the new features. </p>
153 <p>The Android 3.0 platform is designed specially to meet the unique needs of applications on devices with larger screen sizes. It offers all of the tools developers need to create incredible visual and interaction experiences on these devices.</p>
174 <p>Starting with Android 3.0, developers can break the Activities of their applications into subcomponents called Fragments, then combine them in a variety of ways to create a richer, more interactive experience. For example, an application can use a set of Fragments to create a true multipane UI, with the user being able to interact with each pane independently. Fragments can be added, removed, replaced, and animated inside an Activity dynamically, and they are modular and reusable across multiple Activities. Because they are modular, Fragments also offer an efficient way for developers to write applications that can run properly on both larger screen as well as smaller screen devices.</p
    [all...]
android-2.3.3.jd 52 applications to interact with more types of tags in new ways.</p>
54 <p>A new, comprehensive set of APIs give applications read and write access
72 <p>Advanced tag dispatching now gives applications more control over how and
74 used a single-step intent dispatch to notify interested applications that a tag
77 other applications (<code>android.nfc.NfcAdapter.enableForegroundDispatch()</code>).
92 Applications can receive these messages from
102 <li>{@link android.nfc.tech.TagTechnology}, an interface that gives applications
117 <p>To use the NFC API, applications must request permission from the user by
122 their applications are not discoverable to users whose devices do not support
133 connections. This lets applications communicate with simple devices that may no
    [all...]
android-3.1.jd 52 integrating connected peripherals with applications running on the platform.
55 interactions. Using the APIs, developers can create applications that are able to
82 both USB devices and USB accessories. Applications can acquire an instance of
114 their applications are not availabe to users whose devices do not provide the
133 <p>For complete information about how to develop applications that interact with
137 <p class="note">To look at sample applications that use the USB host API, see <a
144 <p>Android 3.1 exposes a new MTP API that lets applications interact directly
185 specification. Methods in the class let applications get a device?s
189 5.3.1 of the MTP specification. Methods in the class let applications get an
200 these capabilities to let users interact with their applications using mice
    [all...]
  /frameworks/base/docs/html/guide/practices/app-design/
seamlessness.jd 26 other applications or dialogs, inadvertent loss of data, unintended blocking,
28 your applications run and the system interactions that can affect your
30 interacts seamlessly with the system and with other applications. </p>
54 used by other applications, you should expose it via a ContentProvider, rather
58 with the system and other applications. The Android system is designed to treat
59 applications as a sort of federation of loosely-coupled components, rather than
62 by allowing you to integrate cleanly and seamlessly with other applications, and
78 Way" is to do just that: Android applications that accept or edit input should
92 applications to understand your data format; if you change that format, you'll
93 break any other applications that aren't similarly updated.</p
    [all...]
  /frameworks/base/docs/html/guide/practices/
seamlessness.jd 27 other applications or dialogs, inadvertent loss of data, unintended blocking,
29 your applications run and the system interactions that can affect your
31 interacts seamlessly with the system and with other applications. </p>
55 used by other applications, you should expose it via a ContentProvider, rather
59 with the system and other applications. The Android system is designed to treat
60 applications as a sort of federation of loosely-coupled components, rather than
63 by allowing you to integrate cleanly and seamlessly with other applications, and
79 Way" is to do just that: Android applications that accept or edit input should
93 applications to understand your data format; if you change that format, you'll
94 break any other applications that aren't similarly updated.</p
    [all...]
  /libcore/luni/src/main/java/org/w3c/dom/ls/
LSResourceResolver.java 16 * <code>LSResourceResolver</code> provides a way for applications to
18 * <p> Applications needing to implement custom handling for external
29 * <p> Many DOM applications will not need to implement this interface, but it
30 * will be especially useful for applications that build XML documents from
31 * databases or other specialized input sources, or for applications that
54 * (i.e. entities), applications must use the value
56 * , applications must use the value
  /frameworks/base/docs/html/tools/
workflow.jd 4 <p>Developing applications for Android devices is facilitated by a group of tools that are
7 it can directly invoke the tools that you need while developing applications.</p>
16 alt="Development process for Android applications"
19 <strong>Figure 1.</strong> The development process for Android applications.
23 <p>The basic steps for developing applications (with or without Eclipse) are shown in figure 1. The
30 applications.</p>
75 <dd>Run your Android applications on an emulated Android platform.</dd>
108 sign your applications, but you can set up Eclipse to do this automatically as well.</p>
133 Testing Framework, and the ability to run applications in either the
  /development/samples/TicTacToeLib/
_index.html 3 then make them available to your other Android applications. </p>
6 <code>GameActivity</code> to other applications. Dependent applications simply
  /frameworks/base/docs/html/training/camera/
index.jd 48 leveraging existing camera applications. In later lessons, you dive deeper
56 <dd>Leverage other applications and capture photos with just a few lines of code.</dd>
58 <dd>Leverage other applications and record videos with just a few lines of code.</dd>
  /packages/apps/Launcher2/res/values-fr/
strings.xml 22 <string name="application_name" msgid="8424725141379931883">"Lanceur d\'applications"</string>
24 <string name="uid_name" msgid="3371120195364560632">"Applications de base Android"</string>
41 <string name="group_applications" msgid="2103752818818161976">"Applications"</string>
54 <string name="all_apps_button_label" msgid="2578400570124163469">"Applications"</string>
63 <string name="accessibility_all_apps_button" msgid="8803738611398979849">"Applications"</string>
67 <string name="menu_manage_apps" msgid="2308685199463588895">"Gérer les applications"</string>
94 <string name="apps_customize_apps_scroll_format" msgid="5494241912377704885">"Page des applications : %1$d sur %2$d"</string>
97 <string name="workspace_cling_move_item" msgid="791013895761065070">"Vous pouvez placer vos applications préférées ici."</string>
98 <string name="workspace_cling_open_all_apps" msgid="2459977609848572588">"Pour voir toutes vos applications, appuyez sur le cercle."</string>
99 <string name="all_apps_cling_title" msgid="2559734712581447107">"Sélectionner des applications"</string
    [all...]
  /packages/apps/Settings/res/xml/
application_settings.xml 30 android:fragment="com.android.settings.applications.ManageApplications"
36 android:fragment="com.android.settings.applications.ManageApplications"
43 android:fragment="com.android.settings.applications.ManageApplications"
  /prebuilts/tools/common/proguard/proguard4.7/examples/ant/
applications2.xml 1 <!-- This Ant build file illustrates how to process applications,
5 <project name="Applications" default="obfuscate" basedir="../..">
34 <!-- Preserve all public applications. -->
  /prebuilts/tools/common/proguard/proguard4.7/examples/
applications.pro 2 # This ProGuard configuration file illustrates how to process applications.
4 # java -jar proguard.jar @applications.pro
35 # Preserve all public applications.

Completed in 1611 milliseconds

1 2 34 5 6 7 8 91011>>