| /external/chromium_org/chrome/common/extensions/ |
| extension_constants.h | 76 // The extension id of the Chrome component application.
79 // The extension id of the Cloud Print component application.
82 // The extension id of the Enterprise Web Store component application.
85 // The extension id of GMail application.
88 // The extension id of the Google Doc application.
91 // The extension id of the Google Play Music application.
94 // The extension id of the Google Search application.
97 // The extension id of the Google Sheets application.
100 // The extension id of the Google Slides application.
124 // The extension id of the settings application
[all...] |
| /external/libvpx/libvpx/ |
| usage.dox | 28 A context is a storage area allocated by the calling application that the
31 application. The context structure as seen by the application is of fixed
47 Each supported codec will expose an interface structure to the application
73 initialized in different modes. Most notably, the application may choose to
79 initialization time to ensure the application is using a header file that
112 useful to an application at runtime, but may be of use to vpx for support.
118 (us), that the application wants the codec to spend processing before
121 example, an application sets a <code>deadline</code> of 1000us, and the
124 function are preserved. If, for the same frame, an application instead set
[all...] |
| /frameworks/base/docs/html/training/design-navigation/ |
| wireframing.jd | 25 <p>Now that we have a solid understanding of navigation patterns and screen grouping techniques, it's time to apply them to our screens. Let's take another look at our exhaustive screen map for the example news application from the <a href="screen-planning.html">first lesson</a>, below.</p>
29 alt="Exhaustive screen map for the example news application" id="figure-exhaustive-map">
31 <p class="img-caption"><strong>Figure 1.</strong> Exhaustive screen map for the example news application.</p>
47 alt="Final screen map for the example news application on handsets" id="figure-map-example-phone">
49 <p class="img-caption"><strong>Figure 2.</strong> Final screen map for the example news application on handsets.</p>
53 alt="Final screen map for the example news application on tablets, in landscape" id="figure-map-example-tablet">
55 <p class="img-caption"><strong>Figure 3.</strong> Final screen map for the example news application on tablets, in landscape.</p>
58 <p>At this point, it's a good idea to think of screen map variations, in case your chosen patterns don't apply well in practice (when you sketch the application's screen layouts). Below is an example screen map variation for tablets that presents story lists for different categories side-by-side, with story view screens remaining independent.</p>
77 <li>Is there screen 'master' functionality, allowing re-use of visual elements across different screens? For example, Action Bars should be visible on almost every screen in your application.</li>
86 <p>After sketching out layouts on paper and choosing a digital wireframing tool that works for you, you can create the digital wireframes that will serve as the starting point for your application's visual design. Below are example wireframes for our news application, corresponding one-to-one w (…)
[all...] |
| screen-planning.jd | 25 <p>Most apps have an inherent information model that can be expressed as a tree or graph of object types. In more obvious terms, you can draw a diagram of different kinds of information that represents the types of things users interact with in your app. Software engineers and data architects often use entity-relationship diagrams (ERDs) to describe an application's information model.</p>
27 <p>Let's consider an example application that allows users to browse through a set of categorized news stories and photos. One possible model for such an app is shown below in the form of an ERD.</p>
31 alt="Entity-relationship diagram for the example news application" id="figure-erd">
33 <p class="img-caption"><strong>Figure 1.</strong> Entity-relationship diagram for the example news application.</p>
38 <p>Once you define the information model, you can begin to define the contexts necessary to enable users to effectively discover, view, and act upon the data in your application. In practice, one way to do this is to <em>determine the exhaustive set of screens</em> needed to allow users to navigate to and interact with the data. The set of screens we actually expose should generally vary depending on the target device; it's important to consider this early in the design process to ensure that the application can adapt to its environment.</p>
40 <p>In our example application, we want to enable users to <strong>view</strong>, <strong>save</strong>, and <strong>share</strong> <em>categorized</em> <strong>stories</strong> and <strong>photos</strong>. Below is an exhaustive list of screens that covers these use cases.</p>
61 alt="Exhaustive screen map for the example news application" id="figure-exhaustive-map">
63 <p class="img-caption"><strong>Figure 2.</strong> Exhaustive screen map for the example news application.</p>
70 <p>At this point, it's possible to design a completely functional application from this exhaustive screen map. A simplistic user interface could consist of lists and buttons le (…)
[all...] |
| /frameworks/base/core/res/res/values/ |
| attrs_manifest.xml | 25 application tag (to supply a default theme for all activities) or
37 application tag (to supply a default label for all application
53 application tag (to supply a default icon for all application
66 associated item. Use with the application tag (to supply a default
67 logo for all application components), or with the activity, receiver,
81 <!-- Name of the activity to be launched to manage application's space on
83 application's space needs to be managed and is usually invoked
104 <!-- Option to indicate this application is only for testing purposes
[all...] |
| /external/chromium/chrome/browser/ui/cocoa/ |
| install.sh | 7 # Called by the application to install in a new location. Generally, this
8 # means that the application is running from a disk image and wants to be
9 # copied to /Applications. The application, when running from the disk image,
12 # This script will be run as root if the application determines that it would
60 # If this script is not running as root and the application is installed
62 # This will allow other admin users to update the application from their own
66 # If the script is not running as root and the application is not installed
79 # better than the alternative, which is to make the application
104 # Because this script is launched by the application itself, the installation
109 # helper. Since the user approved the application launch if quarantined, i
[all...] |
| /external/chromium_org/build/android/ |
| update_verification.py | 28 print 'Application data saved to %s' % backup_file
36 raw_input('Set the application state. Once ready, press enter and '
54 logging.info('Restoring the application data...')
72 'the application data is preserved.')
79 'Performs semi-automated application update verification testing. '
80 'When given --save, it takes a snapshot of the application data '
85 '2. Restores the previously stored snapshot of application data '
92 parser.add_option('--package-name', help='Package name for the application.')
94 help=('Save a snapshot of application data. '
103 help=('Path to the application data to be restored or the
[all...] |
| /external/chromium_org/chrome/browser/mac/ |
| install.sh | 7 # Called by the application to install in a new location. Generally, this
8 # means that the application is running from a disk image and wants to be
9 # copied to /Applications. The application, when running from the disk image,
12 # This script will be run as root if the application determines that it would
63 # If this script is not running as root and the application is installed
65 # This will allow other admin users to update the application from their own
69 # If the script is not running as root and the application is not installed
82 # better than the alternative, which is to make the application
107 # Because this script is launched by the application itself, the installation
112 # helper. Since the user approved the application launch if quarantined, i
[all...] |
| /frameworks/base/docs/html/guide/appendix/ |
| glossary.jd | 7 <dt id="apk">.apk file</dt> <dd>Android application package file. Each
8 Android application is compiled and packaged in a single file that
9 includes all of the application's code (.dex files), resources, assets,
10 and manifest file. The application package file can have any name but
12 <code>myExampleAppname.apk</code>. For convenience, an application package
14 <p>Related: <a href="#application">Application</a>.</p>
18 <dd>Compiled Android application code file.
28 for a Web URL, or com.example.rumbler.SHAKE_PHONE for a custom application
34 <dd>A single screen in an application, with supporting Java code, derive
[all...] |
| /packages/apps/UnifiedEmail/src/com/android/mail/utils/ |
| MimeType.java | 38 public static final String ANDROID_ARCHIVE = "application/vnd.android.package-archive";
41 static final String GENERIC_MIMETYPE = "application/octet-stream";
45 "message/rfc822", "application/eml");
49 "application/zip", "application/x-gzip", "application/x-bzip2",
50 "application/x-compress", "application/x-compressed", "application/x-tar");
170 * Valid mime types are "message/rfc822" and "application/eml"
[all...] |
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/manifest/pages/ |
| ApplicationAttributesPart.java | 36 * Application's attributes section part for Application page.
38 * This part is displayed at the top of the application page and displays all the possible
39 * attributes of an application node in the AndroidManifest (icon, class name, label, etc.)
43 /** Listen to changes to the UI node for <application> and updates the UI */
51 "Application Attributes", // section title
52 "Defines the attributes specific to the application.", // section description
57 * Changes and refreshes the Application UI node handle by the this part.
156 * This listener synchronizes the UI with the actual presence of the application XML node.
161 // The UiElementNode for the application XML node always exists, eve
[all...] |
| ApplicationPage.java | 39 * Page for "Application" settings, part of the AndroidManifest form editor.
51 /** The Application Toogle part */
53 /** The Application Attributes part */
59 super(editor, PAGE_ID, "Application"); // tab's label, keep it short
79 form.setText("Android Manifest Application");
99 "Application Nodes",
100 "List of all elements in the application");
105 * Retrieves the application UI node. Since this is a mandatory node, it *always*
114 // return the ui root node, as a dummy application root node.
120 * Changes and refreshes the Application UI node handled by the sub parts
[all...] |
| /frameworks/base/core/java/android/webkit/ |
| WebStorage.java | 23 * {@link WebView}. It manages the Application Cache API, the Web SQL Database
26 * The Application Cache API provides a mechanism to create and maintain an
27 * application cache to power offline Web applications. Use of the Application
30 * one application cache per application.
33 * Similar to the Application Cache, use of the Web SQL Database can be attributed
134 * Gets the origins currently using either the Application Cache or Web SQL
145 * Gets the amount of storage currently being used by both the Application
160 * enforced on a per-origin basis for the Application Cache API
[all...] |
| /frameworks/base/docs/html/sdk/api_diff/14/changes/ |
| android.app.Application.html | 10 android.app.Application
74 Class android.app.<A HREF="../../../../reference/android/app/Application.html" target="_top"><font size="+2"><code>Application</code></font></A>
87 <A NAME="android.app.Application.onTrimMemory_added(int)"></A>
88 <nobr><code>void</code> <A HREF="../../../../reference/android/app/Application.html#onTrimMemory(int)" target="_top"><code>onTrimMemory</code></A>(<code>int</code>)</nobr>
94 <A NAME="android.app.Application.registerActivityLifecycleCallbacks_added(android.app.Application.ActivityLifecycleCallbacks)"></A>
95 <nobr><code>void</code> <A HREF="../../../../reference/android/app/Application.html#registerActivityLifecycleCallbacks(android.app.Application.ActivityLifecycleCallbacks)" target="_top"><code>registerActivityLifecycleCallbacks</code></A>(<code>ActivityLifecycleCallbacks</code>)</nobr>
101 <A NAME="android.app.Application.unregisterActivityLifecycleCallbacks_added(android.app.Application.ActivityLifecycleCallbacks)"></ (…)
[all...] |
| /packages/apps/Bluetooth/src/com/android/bluetooth/gatt/ |
| ContextMap.java | 33 * This class manages application callbacks and keeps track of GATT connections.
55 * Application entry mapping UUIDs to appIDs and callbacks.
58 /** The UUID of the application */
61 /** The id of the application */
64 /** Application callbacks */
106 /** Our internal application list */
113 * Add an entry to the application context list.
122 * Remove the context for a given application ID.
139 * Add a new connection for a given application ID.
167 * Get an application context by ID
[all...] |
| /external/chromium_org/native_client_sdk/src/doc/devguide/ |
| distributing.rst | 4 Distributing Your Application
20 distribution step is requred. Making PNaCl a part of your web application is as
26 The only constraint for distributing PNaCl modules with a web application is
57 Packaged application
60 A packaged application is a special zip file (with a .crx extension) hosted in
61 the Chrome Web Store. This file contains all of the application parts: A Chrome
63 Client application files. Refer to
65 for more information about creating a packaged application.
84 **multi-platform zip files.** This feature lets you structure your application
221 #. Modify your application as necessary so that it uses the files for th
[all...] |
| /frameworks/base/docs/html/training/connect-devices-wirelessly/ |
| nsd.jd | 16 <li><a href="#teardown">Unregister Your Service on Application Close</a></li>
42 <p>This lesson shows you how to build an application that can broadcast its
45 to connect to the same application running on another device.</p>
77 two devices on the network both have the NsdChat application installed, one of
82 layer the application uses. The syntax is
84 code snippet, the service uses HTTP protocol running over TCP. An application
101 that your application always uses port 1337 puts it in potential conflict with
104 service broadcast, there's no need for the port your application uses to be
126 interface contains callbacks used by Android to alert your application of the
186 players. The key to letting your application see this vibrant ecosystem o
[all...] |
| /external/bluetooth/bluedroid/stack/include/ |
| avdt_api.h | 70 /* The marker bit is used by the application to mark significant events such
126 /* Application service category. This indicates the application
134 ** AVDTP and the application. More detailed descriptions of the error codes
354 ** to the application. This function is required for all registered stream
362 ** packet ready for the application. This function is required for SNK
370 ** application buffer assigned by AVDT_SetMediaBuf. Caller can assign different
372 ** This callback is called when AVDTP has a media packet ready for the application.
381 ** packet ready for the application. This function is required for streams
448 ** application in the system. Before this function can b
[all...] |
| /frameworks/base/docs/html/google/play/ |
| filters.jd | 10 your application from the store.</li>
70 whether to show your application to a user who is browsing or searching for
76 dependencies expressed by the application's manifest file and publishing
79 <p>If the application is compatible with the device according to the filter
80 rules, Google Play displays the application to the user. Otherwise, Google Play
81 hides your application from search results and category browsing, even if a user
88 only. Google Play's filters will thus prevent the application from being available on any device
91 <p>All filtering restrictions are associated with an application's version and can
92 change between versions. For example, if a user has installed your application and you publish an
100 compares the application requirements to each of the user's registered device
[all...] |
| /frameworks/base/docs/html/training/articles/ |
| perf-anr.jd | 28 is an "Application Not Responding" (ANR) dialog.</p>
35 to design responsiveness into your application so the system never displays
39 application is not responding and provides guidelines for ensuring that your
40 application stays responsive. </p>
45 <p>Generally, the system displays an ANR if an application cannot respond to
46 user input. For example, if an application blocks on some I/O operation
63 <p>In Android, application responsiveness is monitored by the Activity Manager
65 for a particular application when it detects one of the following
80 This means anything your application is doing in the UI thread that
82 application is not giving itself a chance to handle the input event or inten
[all...] |
| /frameworks/base/test-runner/src/android/test/ |
| ServiceTestCase.java | 19 import android.app.Application;
39 * <p>For more information about application testing, read the
82 * associated {@link android.app.Application Application}. The ServiceTestCase framework
104 private Application mApplication;
148 * (Context, Application) to it. This is called automatically by {@link #startService} or
215 * object refers to a communication channel between the application and
224 * method. An example of this is in the ApiDemos sample application, in the
296 * Sets the application that is used during the test. If you do not call this method,
299 * @param application The Application object that is used by the service under test
[all...] |
| /libcore/luni/src/main/java/org/xml/sax/ |
| HandlerBase.java | 25 * <p>Application writers can extend this class when they need to
28 * application has not supplied its own.</p>
61 * the SAX default behaviour: application writers can override it
92 * <p>By default, do nothing. Application writers may override this
111 * <p>By default, do nothing. Application writers may override this
139 * <p>By default, do nothing. Application writers may override this
156 * <p>By default, do nothing. Application writers may override this
175 * <p>By default, do nothing. Application writers may override this
194 * <p>By default, do nothing. Application writers may override this
215 * <p>By default, do nothing. Application writers may override thi
[all...] |
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/ |
| org.eclipse.equinox.app_1.3.1.R36x_v20100803.jar | |
| /frameworks/base/docs/html/tools/testing/ |
| testing_android.jd | 83 <a href="{@docRoot}tools/help/monkey.html">UI/Application Exerciser Monkey</a>
90 provides an architecture and powerful tools that help you test every aspect of your application
109 Test suites are contained in test packages that are similar to main application packages, so
115 the application under test and use this information to automatically create the build files,
122 href="{@docRoot}tools/help/monkey.html">UI/Application Exerciser Monkey</a>,
129 tests and view results. The document assumes you have a basic knowledge of Android application
148 statements test a part of the application under test. You organize test methods into classes
150 the application under test. Each class is a container for related test methods, although it
157 use test tools to load the test package and the application under test, and the tools then
182 Create an appropriate name for the test package. If the application
[all...] |
| /development/samples/HoneycombGallery/ |
| _index.html | 1 <p>This is a demo application highlighting how to use some of the new APIs in
16 <p>The image gallery shows how all these pieces can work together in one application.</p>
21 <p>The application includes the following key classes:<p>
24 A fragment responsible for containing the "content" of the application.
34 This is the main entry point of the application. MainActivity is
43 in your application.</li></ul>
|
