diff options
Diffstat (limited to 'docs/html/guide/topics/ui')
| -rw-r--r-- | docs/html/guide/topics/ui/binding.jd | 6 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/custom-components.jd | 4 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/declaring-layout.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/dialogs.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/how-android-draws.jd | 4 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/index.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/menus.jd | 8 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/notifiers/index.jd | 6 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/notifiers/notifications.jd | 6 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/notifiers/toasts.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/themes.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/topics/ui/ui-events.jd | 8 |
12 files changed, 26 insertions, 26 deletions
diff --git a/docs/html/guide/topics/ui/binding.jd b/docs/html/guide/topics/ui/binding.jd index 85aed18..4725321 100644 --- a/docs/html/guide/topics/ui/binding.jd +++ b/docs/html/guide/topics/ui/binding.jd @@ -37,7 +37,7 @@ binds to data of some type. AdapterView is useful whenever you need to display s <h2 id="FillingTheLayout">Filling the Layout with Data</h2> <p>Inserting data into the layout is typically done by binding the AdapterView class to an {@link -android.widget.Adapter}, which retireves data from an external source (perhaps a list that +android.widget.Adapter}, which retrieves data from an external source (perhaps a list that the code supplies or query results from the device's database). </p> <p>The following code sample does the following:</p> <ol> @@ -68,7 +68,7 @@ SimpleCursorAdapter adapter2 = new SimpleCursorAdapter(this, android.R.layout.simple_spinner_item, // Use a template // that displays a // text view - cur, // Give the cursor to the list adatper + cur, // Give the cursor to the list adapter new String[] {People.NAME}, // Map the NAME column in the // people database to... new int[] {android.R.id.text1}); // The "text1" view defined in @@ -86,7 +86,7 @@ you should call {@link android.widget.ArrayAdapter#notifyDataSetChanged()}. This that the data has been changed and it should refresh itself.</p> <h2 id="HandlingUserSelections">Handling User Selections</h2> -<p>You handle the user's selecction by setting the class's {@link +<p>You handle the user's selection by setting the class's {@link android.widget.AdapterView.OnItemClickListener} member to a listener and catching the selection changes. </p> <pre> diff --git a/docs/html/guide/topics/ui/custom-components.jd b/docs/html/guide/topics/ui/custom-components.jd index 76d1034..6027a82 100644 --- a/docs/html/guide/topics/ui/custom-components.jd +++ b/docs/html/guide/topics/ui/custom-components.jd @@ -159,7 +159,7 @@ custom components, styled text, or anything else you can think of.</p> <p class="note"><strong>Note:</strong> This does not apply to 3D graphics. If you want to use 3D graphics, you must extend {@link android.view.SurfaceView SurfaceView} -instead of View, and draw from a seperate thread. See the +instead of View, and draw from a separate thread. See the GLSurfaceViewActivity sample for details.</p> @@ -443,7 +443,7 @@ useful in certain circumstances. If there is a component that is already very similar to what you want, you can simply extend that component and just override the behavior that you want to change. You can do all of the things you would do with a fully customized component, but by starting with a more -specialized class in the View heirarchy, you can also get a lot of behavior for +specialized class in the View hierarchy, you can also get a lot of behavior for free that probably does exactly what you want.</p> <p>For example, the SDK includes a <a href="{@docRoot}guide/samples/NotePad/index.html">NotePad application</a> in the diff --git a/docs/html/guide/topics/ui/declaring-layout.jd b/docs/html/guide/topics/ui/declaring-layout.jd index 7ef22a6..ec22cbc 100644 --- a/docs/html/guide/topics/ui/declaring-layout.jd +++ b/docs/html/guide/topics/ui/declaring-layout.jd @@ -115,7 +115,7 @@ public void onCreate(Bundle savedInstanceState) { <p>The <code>onCreate()</code> callback method in your Activity is called by the Android framework when your Activity is launched (see the discussion on Lifecycles, in the -<a href="{@docRoot}guide/topics/fundamentals.html#lcycles">Application Fundamantals</a>, for more on this).</p> +<a href="{@docRoot}guide/topics/fundamentals.html#lcycles">Application Fundamentals</a>, for more on this).</p> <h2 id="attributes">Attributes</h2> diff --git a/docs/html/guide/topics/ui/dialogs.jd b/docs/html/guide/topics/ui/dialogs.jd index c0c0b1b..11c8a47 100644 --- a/docs/html/guide/topics/ui/dialogs.jd +++ b/docs/html/guide/topics/ui/dialogs.jd @@ -154,7 +154,7 @@ to the object and if the dialog is showing, it will dismiss it.</p> <h3>Using dismiss listeners</h3> -<p>If you'd like your applcation to perform some procedures the moment that a dialog is dismissed, +<p>If you'd like your application to perform some procedures the moment that a dialog is dismissed, then you should attach an on-dismiss listener to your Dialog.</p> <p>First define the {@link android.content.DialogInterface.OnDismissListener} interface. diff --git a/docs/html/guide/topics/ui/how-android-draws.jd b/docs/html/guide/topics/ui/how-android-draws.jd index 21f9833..efb55a2 100644 --- a/docs/html/guide/topics/ui/how-android-draws.jd +++ b/docs/html/guide/topics/ui/how-android-draws.jd @@ -51,7 +51,7 @@ and each View is responsible for drawing itself. </p> <div class="sidebox"><p> - To intiate a layout, call <code>{@link android.view.View#requestLayout}</code>. This method is typically + To initiate a layout, call <code>{@link android.view.View#requestLayout}</code>. This method is typically called by a View on itself when it believes that is can no longer fit within its current bounds.</p> </div> @@ -86,7 +86,7 @@ and each View is responsible for drawing itself. child. The child must use this size, and guarantee that all of its descendants will fit within this size.</li> <li><var>AT_MOST</var>: This is used by the parent to impose a maximum size on the - child. The child must gurantee that it and all of its descendants will fit + child. The child must guarantee that it and all of its descendants will fit within this size.</li> </ul> diff --git a/docs/html/guide/topics/ui/index.jd b/docs/html/guide/topics/ui/index.jd index ef23672..494bda8 100644 --- a/docs/html/guide/topics/ui/index.jd +++ b/docs/html/guide/topics/ui/index.jd @@ -74,7 +74,7 @@ and drawn, read <a href="how-android-draws.html">How Android Draws Views</a>.</p <p>The most common way to define your layout and express the view hierarchy is with an XML layout file. XML offers a human-readable structure for the layout, much like HTML. Each element in XML is -either a View or ViewGroup object (or descendent thereof). View objects are leaves in the tree, +either a View or ViewGroup object (or descendant thereof). View objects are leaves in the tree, ViewGroup objects are branches in the tree (see the View Hierarchy figure above).</p> <p>The name of an XML element is respective to the Java class that it represents. So a <code><TextView></code> element creates diff --git a/docs/html/guide/topics/ui/menus.jd b/docs/html/guide/topics/ui/menus.jd index bae94ca..0129e8f 100644 --- a/docs/html/guide/topics/ui/menus.jd +++ b/docs/html/guide/topics/ui/menus.jd @@ -86,7 +86,7 @@ an icon, a keyboard shortcut, an intent, and other settings for the item.</p> Usually, you'll want to use one that accepts an <var>itemId</var> argument. This is a unique integer that allows you to identify the item during a callback.</p> -<p>When a menu item is selected from the Options Menu, you will recieve a callback to the +<p>When a menu item is selected from the Options Menu, you will receive a callback to the <code>{@link android.app.Activity#onOptionsItemSelected(MenuItem) onOptionsItemSelected()}</code> method of your Activity. This callback passes you the <code>MenuItem</code> that has been selected. You can identify the item by requesting the @@ -216,7 +216,7 @@ from the {@code MenuItem}, which provides information about the currently select All we need from this is the list ID for the selected item, so whether editing a note or deleting it, we find the ID with the {@code AdapterContextMenuInfo.info} field of the object. This ID -is passed to the <code>editNote()</code> and <code>deleteNote()</code> methods to perfrom +is passed to the <code>editNote()</code> and <code>deleteNote()</code> methods to perform the respective action.</p> <p>Now, to register this context menu for all the items in a {@link android.widget.ListView}, @@ -338,7 +338,7 @@ and set whether the items can be checkable with <img align="right" src="{@docRoot}images/radio_buttons.png" alt="" /> <p>Any menu item can be used as an interface for turning options on and off. This can be indicated with a checkbox for stand-alone options, or radio buttons for groups of -mutually exlusive options (see the screenshot, to the right).</p> +mutually exclusive options (see the screenshot, to the right).</p> <p class="note"><strong>Note:</strong> Menu items in the Icon Menu cannot display a checkbox or radio button. If you choose to make items in the Icon Menu checkable, @@ -490,7 +490,7 @@ public boolean onCreateOptionsMenu(Menu menu){ null, // Specific items to place first (none) intent, // Intent created above that describes our requirements 0, // Additional flags to control items (none) - null); // Array of MenuItems that corrolate to specific items (none) + null); // Array of MenuItems that correlate to specific items (none) return true; }</pre> diff --git a/docs/html/guide/topics/ui/notifiers/index.jd b/docs/html/guide/topics/ui/notifiers/index.jd index 5b37f5b6..f7ccce7 100644 --- a/docs/html/guide/topics/ui/notifiers/index.jd +++ b/docs/html/guide/topics/ui/notifiers/index.jd @@ -25,7 +25,7 @@ and others do not. For example:</p> <li>When an event such as saving a file is complete, a small message should appear to confirm that the save was successful.</li> <li>If the application is running in the background and needs the user's attention, -the application should create a notificaiton that allows the user to respond at +the application should create a notification that allows the user to respond at his or her convenience.</li> <li>If the application is performing work that the user must wait for (such as loading a file), @@ -49,7 +49,7 @@ links to full documentation.</p> <img src="{@docRoot}images/toast.png" alt="" style="float:right" /> -<p>A toast notificaiton is a message that pops up on the surface of the window. +<p>A toast notification is a message that pops up on the surface of the window. It only fills the amount of space required for the message and the user's current activity remains visible and interactive. The notification automatically fades in and out, and does not accept interaction events. Because a toast can be created from a background @@ -97,7 +97,7 @@ for notifications and short activities that directly relate to the application i <p>You should use a dialog when you need to show a progress bar or a short message that requires confirmation from the user (such as an alert with "OK" and "Cancel" buttons). -You can use also use dialogs as integral componenents +You can use also use dialogs as integral components in your application's UI and for other purposes besides notifications. For a complete discussion on all the available types of dialogs, including its uses for notifications, refer to diff --git a/docs/html/guide/topics/ui/notifiers/notifications.jd b/docs/html/guide/topics/ui/notifiers/notifications.jd index e6fa48f..a0dd9f1 100644 --- a/docs/html/guide/topics/ui/notifiers/notifications.jd +++ b/docs/html/guide/topics/ui/notifiers/notifications.jd @@ -316,7 +316,7 @@ using Notification fields and flags. Some useful features include the following: your notification is on-going.</dd> <dt><var>number</var> field</dt> <dd>This value indicates the current number of events represented by the notification. - The appropriate number is overlayed on top of the status bar icon. + The appropriate number is overlaid on top of the status bar icon. If you intend to use this field, then you must start with "1" when the Notification is first created. (If you change the value from zero to anything greater during an update, the number is not shown.)</dd> @@ -375,7 +375,7 @@ pass it to the <var>contentView</var> field of your Notification. Pass the </pre> <p>This layout is used for the expanded view, - but the content of the ImageView and TextView still needs to be defined by the applicaiton. + but the content of the ImageView and TextView still needs to be defined by the application. RemoteViews offers some convenient methods that allow you to define this content...</p> </li> @@ -389,7 +389,7 @@ contentView.setTextViewText(R.id.text, "Hello, this message is in a custom expan notification.contentView = contentView; </pre> - <p>As shown here, pass the applicaiton's package name and the layout + <p>As shown here, pass the application's package name and the layout resource ID to the RemoteViews constructor. Then, define the content for the ImageView and TextView, using the {@link android.widget.RemoteViews#setImageViewResource(int, int) setImageViewResource()} and {@link android.widget.RemoteViews#setTextViewText(int, CharSequence) setTextViewText()}. diff --git a/docs/html/guide/topics/ui/notifiers/toasts.jd b/docs/html/guide/topics/ui/notifiers/toasts.jd index a800c3c..5b324d2 100644 --- a/docs/html/guide/topics/ui/notifiers/toasts.jd +++ b/docs/html/guide/topics/ui/notifiers/toasts.jd @@ -18,7 +18,7 @@ parent.link=index.html </div> </div> -<p>A toast notificaiton is a message that pops up on the surface of the window. +<p>A toast notification is a message that pops up on the surface of the window. It only fills the amount of space required for the message and the user's current activity remains visible and interactive. The notification automatically fades in and out, and does not accept interaction events.</p> diff --git a/docs/html/guide/topics/ui/themes.jd b/docs/html/guide/topics/ui/themes.jd index 41e8563..0399512 100644 --- a/docs/html/guide/topics/ui/themes.jd +++ b/docs/html/guide/topics/ui/themes.jd @@ -111,7 +111,7 @@ This technique can be used only in XML resources. </p> <h3 id="inTheManifest">Set the theme in the manifest</h3> -<p>To set this theme for all the activites of your application, open the AndroidManifest.xml file and +<p>To set this theme for all the activities of your application, open the AndroidManifest.xml file and edit the <code><application></code> tag to include the <code>android:theme</code> attribute with the theme name:</p> diff --git a/docs/html/guide/topics/ui/ui-events.jd b/docs/html/guide/topics/ui/ui-events.jd index f4d114a..60c8a1b 100644 --- a/docs/html/guide/topics/ui/ui-events.jd +++ b/docs/html/guide/topics/ui/ui-events.jd @@ -29,7 +29,7 @@ methods that look useful for UI events. These methods are called by the Android respective action occurs on that object. For instance, when a View (such as a Button) is touched, the <code>onTouchEvent()</code> method is called on that object. However, in order to intercept this, you must extend the class and override the method. Obviously, extending every View object -you want to use (just to handle an event) would be obsurd. This is why the View class also contains +you want to use (just to handle an event) would be absurd. This is why the View class also contains a collection of nested interfaces with callbacks that you can much more easily define. These interfaces, called <a href="#EventListeners">event listeners</a>, are your ticket to capturing the user interaction with your UI.</p> @@ -102,7 +102,7 @@ protected void onCreate(Bundle savedValues) { } </pre> -<p>You may also find it more conventient to implement OnClickListener as a part of your Activity. +<p>You may also find it more convenient to implement OnClickListener as a part of your Activity. This will avoid the extra class load and object allocation. For example:</p> <pre> public class ExampleActivity extends Activity implements OnClickListener { @@ -139,7 +139,7 @@ depends on the event. For the few that do, here's why:</p> this event can have multiple actions that follow each other. So, if you return <em>false</em> when the down action event is received, you indicate that you have not consumed the event and are also not interested in subsequent actions from this event. Thus, you will not be called for any other actions - within the event, such as a fingure gesture, or the eventual up action event.</li> + within the event, such as a finger gesture, or the eventual up action event.</li> </ul> <p>Remember that key events are always delivered to the View currently in focus. They are dispatched starting from the top @@ -168,7 +168,7 @@ you'll learn see some of the common callbacks used for event handling, including <li><code>{@link android.view.View#onTouchEvent}</code> - Called when a touch screen motion event occurs.</li> <li><code>{@link android.view.View#onFocusChanged}</code> - Called when the view gains or loses focus.</li> </ul> -<p>There are some other methods that you should be awere of, which are not part of the View class, +<p>There are some other methods that you should be aware of, which are not part of the View class, but can directly impact the way you're able to handle events. So, when managing more complex events inside a layout, consider these other methods:</p> <ul> |