| /frameworks/base/docs/html/guide/topics/ui/notifiers/ |
| D | index.jd | 21 <p>Several types of situations may arise that require you to notify the user
22 about an event that occurs in your application. Some events require the user to respond
27 <li>If the application is running in the background and needs the user's attention,
28 the application should create a notificaiton that allows the user to respond at
31 performing work that the user must wait for (such as loading a file),
40 that come from the background and request the user's response.</li>
44 <p>This document summarizes each of these techniques for notifying the user and includes
53 It only fills the amount of space required for the message and the user's current
59 when you're fairly certain the user is paying attention
60 to the screen. A toast can not accept user interaction events; if you'd like
[all …]
|
| /frameworks/base/core/java/com/google/android/util/ |
| D | AbstractMessageParser.java | 947 private String user; field in AbstractMessageParser.Photo
951 public Photo(String user, String album, String photo, String text) { in Photo() argument
953 this.user = user; in Photo()
958 public String getUser() { return user; } in getUser()
988 public static String getRssUrl(String user) { in getRssUrl() argument
989 return "http://picasaweb.google.com/data/feed/api/user/" + user + in getRssUrl()
994 public static String getAlbumURL(String user, String album) { in getAlbumURL() argument
995 return "http://picasaweb.google.com/" + user + "/" + album; in getAlbumURL()
999 public static String getPhotoURL(String user, String album, String photo) { in getPhotoURL() argument
1000 return "http://picasaweb.google.com/" + user + "/" + album + "/photo#" in getPhotoURL()
[all …]
|
| /frameworks/base/docs/html/guide/practices/design/ |
| D | index.jd | 4 …m, to ensure that your applications offer outstanding performance and a great user experience. </p>
6 …n design that directly influence the user experience of your application, when in the hands of a m…
8 …user experience, in addition to a compelling technical feature set. The user experience is more th…
10 <p>An outstanding user experience has three key characteristics: it is
|
| D | responsiveness.jd | 8 …user, called the Application Not Responding (ANR) dialog. The user can choose to let the applicati…
10 …user input. For example, if an application blocks on some I/O operation (frequently a network acc…
19 most of your work there. This keeps the main thread (which drives the user
29 <p style="margin-top:.5em;padding:.5em;">An ANR dialog displayed to the user.</p>
93 whatever application the user is currently has running. If your application
94 has something to show the user in response to an Intent broadcast, it should
107 user input, show that progress is being made ({@link
115 indicate somehow that progress is being made, lest the user perceive that
|
| D | seamlessness.jd | 17 not have user focus at the time your background process displays the dialog. So
20 display the dialog in front of whatever the user was doing (such as dialing a
22 for the user. </p>
25 facility for notifying the user — the
27 notifications, your application can signal the user that an event has
29 focus and interrupting the user.</p>
32 loses state or user data because it doesn't correctly implement the onPause()
68 <p>If the user was editing data in your application when the other Activity
73 fashion. When the user revisits the application, she should be able to
77 user was composing an email when another Activity started up, the application
[all …]
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | activity_task_design.jd | 41 <li><a href=#notifications_get_back_tip>Notifications should let user easily get back</li>
59 framework, from a high-level, user-centric perspective useful to
108 components</a>)--> for the user to interact with, typically bundled up
118 which the user can pick to start an application.
131 cohesive user interface. An activity has a distinct visual user
135 of user action. Any application that presents anything on the display
140 When using an Android device, as the user moves through the user
149 set of related user actions. In general, each activity has a
153 launched (started) independently, and the user or system can start,
237 As the user moves from activity to activity, across applications, the
[all …]
|
| D | menu_design.jd | 57 A menu holds a set of commands (user actions) that are normally hidden, and
62 user controls in the content area of your application.
72 It is typically invoked by a user pressing a hard button, often labeled MENU.</li>
74 selected item. It is typically invoked by a user's touch & hold
110 On most devices, a user presses the MENU button to access the Options menu,
111 as shown in the screenshot below. To close the menu, the user presses
156 On some versions of Android, the user can display keyboard shortcuts in the
170 A user can touch & hold on content on the screen to
180 For example, in an email message list, a user can touch & hold on
186 A user can also touch & hold a <em>location</em> on the screen to
[all …]
|
| /frameworks/base/include/ui/ |
| D | CameraHardwareInterface.h | 41 void* user);
45 void* user);
50 void* user);
97 void* user) = 0;
|
| /frameworks/base/telephony/java/com/android/internal/telephony/gsm/ |
| D | ApnSetting.java | 32 String user; field in ApnSetting
42 String user, String password, int authType, String[] types) { in ApnSetting() argument
52 this.user = user; in ApnSetting()
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | permission-element.jd | 28 <dd>A user-readable description of the permission, longer and more
30 permission to the user — for example, when the user is asked
50 strings in the user interface.
85 minimal risk to other applications, the system, or the user.
88 asking for the user's explicit approval (though the user always
93 access to private user data or control over the device that can
94 negatively impact the user. Because this type of permission
98 user and require confirmation before proceeding, or some other
99 approach may be taken to avoid the user automatically allowing
106 automatically grants the permission without notifying the user or
[all …]
|
| D | activity-element.jd | 25 android:<a href="#screen">screenOrientation</a>=["unspecified" | "user" | "behind" |
48 implements part of the application's visual user interface. All activities
108 above the root activity) in certain situations when the user re-selects that
109 task from the home screen. Typically, this is done if the user hasn't visited
139 and from there goes to activity Q. The user next presses HOME, and then returns
140 to activity P. Normally, the user would see activity Q, since that is what they
142 of the activities on top of it (Q in this case) were removed when the user pressed
143 HOME and the task went to the background. So the user sees only P when returning
179 <td>The locale has changed — for example, the user has selected a new
186 <td>The keyboard type has changed — for example, the user has
[all …]
|
| /frameworks/base/media/libmedia/ |
| D | AudioTrack.cpp | 61 void* user, in AudioTrack() argument
66 frameCount, flags, cbf, user, notificationFrames, 0); in AudioTrack()
77 void* user, in AudioTrack() argument
82 0, flags, cbf, user, notificationFrames, sharedBuffer); in AudioTrack()
112 void* user, in set() argument
245 mUserData = user; in set()
479 …%d, loopCount %d, framecount %d, user %d", loopStart, loopEnd, loopCount, mFrameCount, cblk->user); in setLoop()
562 if (position > mCblk->user) return BAD_VALUE; in setPosition()
690 if (cblk->user < cblk->loopEnd) { in obtainBuffer()
692 "user=%08x, server=%08x", this, cblk->user, cblk->server); in obtainBuffer()
[all …]
|
| D | AudioRecord.cpp | 61 void* user, in AudioRecord() argument
66 frameCount, flags, cbf, user, notificationFrames); in AudioRecord()
94 void* user, in set() argument
194 mUserData = user; in set()
277 mNewPosition = mCblk->user + mUpdatePeriod; in start()
385 *position = mCblk->user; in getPosition()
463 "user=%08x, server=%08x", cblk->user, cblk->server); in obtainBuffer()
496 uint32_t u = cblk->user; in obtainBuffer()
573 if (mCblk->user >= mMarkerPosition) { in processAudioBuffer()
581 while (mCblk->user >= mNewPosition) { in processAudioBuffer()
[all …]
|
| /frameworks/base/docs/html/guide/appendix/faq/ |
| D | security.jd | 33 The Android user can choose to grant or deny an application's request for
65 keeping the user and security community informed of bugs and fixes. We will
81 developer onto a device. As with a home PC, the user must be
84 This decision can be informed by the user's judgment of the software
109 <li>shows the user unsolicited messages (especially messages urging the
110 user to buy something);</li>
111 <li>resists (or attempts to resist) the user's effort to uninstall it;</li>
114 <li>discloses the user's private information to a third party, without the
115 user's knowledge and consent;</li>
116 <li>destroys the user's data (or the device itself) without the user's
[all …]
|
| /frameworks/base/data/etc/ |
| D | Android.mk | 24 LOCAL_MODULE_TAGS := user
41 LOCAL_MODULE_TAGS := user
|
| /frameworks/base/include/media/ |
| D | AudioTrack.h | 103 typedef void (*callback_t)(int event, void* user, void *info);
140 void* user = 0,
159 void* user = 0,
182 void* user = 0,
|
| D | AudioRecord.h | 101 typedef void (*callback_t)(int event, void* user, void *info);
144 void* user = 0,
169 void* user = 0,
|
| /frameworks/base/camera/libcameraservice/ |
| D | CameraService.h | 140 … static void notifyCallback(int32_t msgType, int32_t ext1, int32_t ext2, void* user);
141 … static void dataCallback(int32_t msgType, const sp<IMemory>& dataPtr, void* user);
143 const sp<IMemory>& dataPtr, void* user);
145 static sp<Client> getClientFromCookie(void* user);
|
| /frameworks/base/cmds/keystore/ |
| D | keystore.c | 441 static struct user { struct
453 struct user *user = users; in process() argument
457 while (user->uid && user->uid != uid) { in process()
458 ++user; in process()
466 if (!(action->perm & user->perms)) { in process()
472 if (user->euid) { in process()
473 uid = user->euid; in process()
|
| /frameworks/base/docs/html/guide/topics/ |
| D | fundamentals.jd | 74 <li>By default, each application is assigned a unique Linux user ID.
76 that user, only to the application itself — although there are ways
81 It's possible to arrange for two applications to share the same user ID,
113 <dd>An <i>activity</i> presents a visual user interface for one focused endeavor
114 the user can undertake. For example, an activity might present a list of
119 or change settings. Though they work together to form a cohesive user interface,
128 as the first one that should be presented to the user when the application is
137 for example, a pop-up dialog that calls for a user response in the midst of
148 user actions directed at that space. Thus, views are where the activity's
149 interaction with the user takes place. For example, a view might display
[all …]
|
| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 12 that the system knows are running, how important these things are to the user,
42 what the user is currently doing. Various application components can
48 at the top of the screen that the user is interacting with (its
62 reached a memory paging state, so this action is required in order to keep the user
67 that is visible to the user on-screen but not in the foreground (its
78 processes are not directly visible to the user, they are generally doing things
79 that the user cares about (such as background mp3 playback or background
85 that is not currently visible to the user (its
87 have no direct impact on the user experience. Provided they implement
93 by the user is the last to be killed when running low on memory.
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | ui-events.jd | 23 <p>On Android, there's more than one way to intercept the events from a user's interaction with you…
24 When considering events within your user interface, the approach is to capture the events from
25 the specific View object that the user interacts with. The View class provides the means to do so.<…
34 called <a href="#EventListeners">event listeners</a>, are your ticket to capturing the user interac…
36 <p>While you will more commonly use the event listeners to listen for user interaction, there may
47 been registered is triggered by user interaction with the item in the UI.</p>
54 This is called when the user either touches the item
59 This is called when the user either touches and holds the item (when in touch mode), or
64 …This is called when the user navigates onto or away from the item, using the navigation-keys or tr…
67 …This is called when the user is focused on the item and presses or releases a key on the device.</…
[all …]
|
| /frameworks/base/docs/html/guide/basics/ |
| D | building-blocks.jd | 29 can include displaying a UI to the user. It doesn't have to, though - some
36 Android user interfaces are comprised of trees of Views. If you want to
38 game, or building some unusual new user interface widget) then you'd
57 media player; even when the user quits the media-selection UI, she
67 strongly-preferred mechanism for alerting the user of something that needs
73 access the user's list of contacts. Your application can access data that
|
| D | appmodel.jd | 7 the process it runs in, and the icon and application the user interacts with.
18 file that an application is distributed in and downloaded by the user when
21 <li><p>A <strong>task</strong> is generally what the user perceives as
42 <p>A key point here is: <em>when the user sees as an "application," what
51 <p>A task, then, from the user's perspective your application; and from the
52 application developer's perspective it is one or more activities the user
65 from the user's perspective, a new application starts at this point. If this
67 addition, you should only use the new task flag if it is possible for the user
69 new task. Otherwise, if the user presses HOME instead of BACK from the task
81 particular .apk are part of a single application to the user.</p>
[all …]
|
| /frameworks/base/docs/html/guide/topics/security/ |
| D | security.jd | 27 such as user and group IDs that are assigned to applications.
38 adversely impact other applications, the operating system, or the user. This
39 includes reading or writing the user's private data (such as contacts or
48 by prompting the user. The permissions required by an application are declared
64 signature-based permissions and who can share user IDs.</p>
71 own unique Linux user ID, creating a sandbox for it and preventing it from touching
72 other applications (or other applications from touching it). This user ID is
82 have them assigned the same user ID. By doing this, for purposes of security
84 user ID and file permissions. Note that in order to retain security, only two applications
86 be given the same user ID.</p>
[all …]
|