diff options
Diffstat (limited to 'docs/html/guide/topics')
27 files changed, 56 insertions, 56 deletions
diff --git a/docs/html/guide/topics/appwidgets/index.jd b/docs/html/guide/topics/appwidgets/index.jd index fc0061d..ef0080a 100644 --- a/docs/html/guide/topics/appwidgets/index.jd +++ b/docs/html/guide/topics/appwidgets/index.jd @@ -382,7 +382,7 @@ so the Activity needs to accept this Intent. For example:</p> <p>Also, the Activity must be declared in the AppWidgetProviderInfo XML file, with the <code>android:configure</code> attribute (see <a href="#MetaData">Adding -the AppWidgetProvierInfo Metadata</a> above). For example, the configuration Activity +the AppWidgetProviderInfo Metadata</a> above). For example, the configuration Activity can be declared like this:</p> <pre> diff --git a/docs/html/guide/topics/fundamentals.jd b/docs/html/guide/topics/fundamentals.jd index 71705d3..935ec93 100644 --- a/docs/html/guide/topics/fundamentals.jd +++ b/docs/html/guide/topics/fundamentals.jd @@ -262,7 +262,7 @@ camera button has been pressed. </p> <p> -There are separate methods for activiating each type of component: +There are separate methods for activating each type of component: </p> <ul> diff --git a/docs/html/guide/topics/graphics/2d-graphics.jd b/docs/html/guide/topics/graphics/2d-graphics.jd index af584a2..051427b 100644 --- a/docs/html/guide/topics/graphics/2d-graphics.jd +++ b/docs/html/guide/topics/graphics/2d-graphics.jd @@ -43,7 +43,7 @@ including {@link android.graphics.drawable.BitmapDrawable}, {@link android.graph {@link android.graphics.drawable.PictureDrawable}, {@link android.graphics.drawable.LayerDrawable}, and several more. Of course, you can also extend these to define your own custom Drawable objects that behave in unique ways.</p> -<p>There are three ways to define and instantiate a Drawable: using an image saved in your project resouces; +<p>There are three ways to define and instantiate a Drawable: using an image saved in your project resources; using an XML file that defines the Drawable properties; or using the normal class constructors. Below, we'll discuss each the first two techniques (using constructors is nothing new for an experienced developer).</p> @@ -126,7 +126,7 @@ instead of directly transforming the Drawable, you should perform a <a href="#tw <a href="{@docRoot}guide/topics/ui/index.html">User Interface</a>. Hence, you understand the power and flexibility inherent in defining objects in XML. This philosophy caries over from Views to Drawables. If there is a Drawable object that you'd like to create, which is not initially dependent on variables defined by -your applicaton code or user interaction, then defining the Drawable in XML is a good option. +your application code or user interaction, then defining the Drawable in XML is a good option. Even if you expect your Drawable to change its properties during the user's experience with your application, you should consider defining the object in XML, as you can always modify properties once it is instantiated.</p> @@ -206,7 +206,7 @@ public class CustomDrawableView extends View { It's then given a color and the bounds of the shape are set. If you do not set the bounds, then the shape will not be drawn, whereas if you don't set the color, it will default to black.</p> <p>With the custom View defined, it can be drawn any way you like. With the sample above, we can -draw the shape progammatically in an Activity:</p> +draw the shape programmatically in an Activity:</p> <pre> CustomDrawableView mCustomDrawableView; @@ -248,7 +248,7 @@ of the object it's attached to. <h2 id="nine-patch">NinePatchDrawable</h2> <p>A {@link android.graphics.drawable.NinePatchDrawable} graphic is a stretchable bitmap image, which Android -will automatically resize to accomodate the contents of the View in which you have placed it as the background. +will automatically resize to accommodate the contents of the View in which you have placed it as the background. An example use of a NinePatch is the backgrounds used by standard Android buttons — buttons must stretch to accommodate strings of various lengths. A NinePatch drawable is a standard PNG image that includes an extra 1-pixel-wide border. It must be saved with the extension <code>.9.png</code>, @@ -271,7 +271,7 @@ and saved into the <code>res/drawable/</code> directory of your project. define this drawable area. </p> <p>To clarify the difference between the different lines, the left and top lines define -which pixels of the image are allowed to be replicated in order to strech the image. +which pixels of the image are allowed to be replicated in order to stretch the image. The bottom and right lines define the relative area within the image that the contents of the View are allowed to lie within.</p> <p> @@ -281,7 +281,7 @@ of the View are allowed to lie within.</p> <p>This NinePatch defines one stretchable area with the left and top lines and the drawable area with the bottom and right lines. In the top image, the dotted grey -lines identify the regions of the image that will be replicated in order to strech the image. The pink +lines identify the regions of the image that will be replicated in order to stretch the image. The pink rectangle in the bottom image identifies the region in which the contents of the View are allowed. If the contents don't fit in this region, then the image will be stretched so that they do. </p> @@ -333,7 +333,7 @@ the contents of a View object. So, if you have a TextView object, you can move, If it has a background image, the background image will be transformed along with the text. The {@link android.view.animation animation package} provides all the classes used in a tween animation.</p> -<p>A sequence of animation instructions defines the twen animation, defined by either XML or Android code. +<p>A sequence of animation instructions defines the tween animation, defined by either XML or Android code. Like defining a layout, an XML file is recommended because it's more readable, reusable, and swappable than hard-coding the animation. In the example below, we use XML. (To learn more about defining an animation in your application code, instead of XML, refer to the @@ -428,7 +428,7 @@ then assign the animation to the View with in the <a href="{@docRoot}guide/topics/resources/available-resources.html#animation">Available Resources</a>.</p> <p class="note"><strong>Note:</strong> Regardless of how your animation may move or resize, the bounds of the -View that holds your animation will not automatically adjust to accomodate it. Even so, the animation will still +View that holds your animation will not automatically adjust to accommodate it. Even so, the animation will still be drawn beyond the bounds of its View and will not be clipped. However, clipping <em>will occur</em> if the animation exceeds the bounds of the parent View.</p> diff --git a/docs/html/guide/topics/graphics/index.jd b/docs/html/guide/topics/graphics/index.jd index bc2a8bf..e1158be 100644 --- a/docs/html/guide/topics/graphics/index.jd +++ b/docs/html/guide/topics/graphics/index.jd @@ -112,7 +112,7 @@ like <code>drawBitmap(...)</code>, <code>drawRect(...)</code>, <code>drawText(.. Other classes that you might use also have <code>draw()</code> methods. For example, you'll probably have some {@link android.graphics.drawable.Drawable} objects that you want to put on the Canvas. Drawable has its own <code>{@link android.graphics.drawable.Drawable#draw(Canvas) draw()}</code> method -that takes your Canvas as an arguement.</p> +that takes your Canvas as an argument.</p> <h3 id="on-view">On a View</h3> @@ -124,7 +124,7 @@ and drawing with a Canvas in <code>{@link android.view.View#onDraw(Canvas) View. The most convenient aspect of doing so is that the Android framework will provide you with a pre-defined Canvas to which you will place your drawing calls.</p> -<p>To start, extend the {@link android.view.View} class (or descendent thereof) and define +<p>To start, extend the {@link android.view.View} class (or descendant thereof) and define the <code>{@link android.view.View#onDraw(Canvas) onDraw()}</code> callback method. This method will be called by the Android framework to request that your View draw itself. This is where you will perform all your calls to draw through the {@link android.graphics.Canvas}, which is passed to you through the <code>onDraw()</code> callback.</p> @@ -190,7 +190,7 @@ with <code>{@link android.graphics.Canvas#drawBitmap(Bitmap,Rect,RectF,Paint) dr you will see traces of the drawings you previously performed.</p> -<p>For a sample application, see the Lunar Landar game, in the SDK samples folder: +<p>For a sample application, see the Lunar Lander game, in the SDK samples folder: <code><your-sdk-directory>/samples/LunarLander/</code>. Or, browse the source in the <a href="{@docRoot}guide/samples/index.html">Sample Code</a> section.</p> diff --git a/docs/html/guide/topics/manifest/activity-element.jd b/docs/html/guide/topics/manifest/activity-element.jd index 83237c6..c22d3e1 100644 --- a/docs/html/guide/topics/manifest/activity-element.jd +++ b/docs/html/guide/topics/manifest/activity-element.jd @@ -24,7 +24,7 @@ page.title=<activity> android:<a href="#proc">process</a>="<i>string</i>" android:<a href="#screen">screenOrientation</a>=["unspecified" | "user" | "behind" | "landscape" | "portrait" | - "sensor" | "nonsensor"] + "sensor" | "nosensor"] android:<a href="#state">stateNotNeeded</a>=["true" | "false"] android:<a href="#aff">taskAffinity</a>="<i>string</i>" android:<a href="#theme">theme</a>="<i>resource or theme</i>" @@ -687,7 +687,7 @@ Values set here (other than "{@code stateUnspecified}" and keyboard. Rather, the contents of the window are automatically panned so that the current focus is never obscured by the keyboard and users can always see what they are typing. This is generally less - desireable than resizing, because the user may need to close the soft + desirable than resizing, because the user may need to close the soft keyboard to get at and interact with obscured parts of the window.</td> </tr> </table> diff --git a/docs/html/guide/topics/manifest/data-element.jd b/docs/html/guide/topics/manifest/data-element.jd index b48c5e0..b77fd05 100644 --- a/docs/html/guide/topics/manifest/data-element.jd +++ b/docs/html/guide/topics/manifest/data-element.jd @@ -28,7 +28,7 @@ attributes for each of its parts: These attributes are optional, but also mutually dependent: If a <code><a href="{@docRoot}guide/topics/manifest/data-element.html#scheme">scheme</a></code> is not specified for the intent filter, all the other URI attributes are ignored. If a -<code><a href="{@docRoot}guide/topics/manifest/data-element.html#host">host</a></code> is not specified for the filer, +<code><a href="{@docRoot}guide/topics/manifest/data-element.html#host">host</a></code> is not specified for the filter, the {@code port} attribute and all the path attributes are ignored. </p> diff --git a/docs/html/guide/topics/manifest/permission-tree-element.jd b/docs/html/guide/topics/manifest/permission-tree-element.jd index 3074354..aecc930 100644 --- a/docs/html/guide/topics/manifest/permission-tree-element.jd +++ b/docs/html/guide/topics/manifest/permission-tree-element.jd @@ -46,7 +46,7 @@ strings in the user interface.</dd> <dd>The name that's at the base of the permission tree. It serves as a prefix to all permission names in the tree. Java-style scoping should be used to ensure that the name is unique. The name must have more than -two period-separated seqments in its path — for example, +two period-separated segments in its path — for example, {@code com.example.base} is OK, but {@code com.example} is not.</dd> </dl></dd> diff --git a/docs/html/guide/topics/manifest/provider-element.jd b/docs/html/guide/topics/manifest/provider-element.jd index 2bb4ff4..7f51f8d 100644 --- a/docs/html/guide/topics/manifest/provider-element.jd +++ b/docs/html/guide/topics/manifest/provider-element.jd @@ -185,7 +185,7 @@ processes, and "{@code false}" if not. The default value is "{@code false}". Normally, a content provider is instantiated in the process of the application that defined it. However, if this flag is set to "{@code true}", the system can create an instance in every process where there's a client -that wants to interact withit, thus avoiding the overhead of interprocess +that wants to interact with it, thus avoiding the overhead of interprocess communication. </p></dd> diff --git a/docs/html/guide/topics/manifest/receiver-element.jd b/docs/html/guide/topics/manifest/receiver-element.jd index 280d402..b208917 100644 --- a/docs/html/guide/topics/manifest/receiver-element.jd +++ b/docs/html/guide/topics/manifest/receiver-element.jd @@ -17,7 +17,7 @@ page.title=<receiver> <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code></dd> <dt>can contain:</dt> -<dd><code><a href="{@docRoot}guide/topics/manifest/intent-filter-element.html"><intent-filer></a></code> +<dd><code><a href="{@docRoot}guide/topics/manifest/intent-filter-element.html"><intent-filter></a></code> <br/><code><a href="{@docRoot}guide/topics/manifest/meta-data-element.html"><meta-data></a></code></dd> <dt>description:</dt> diff --git a/docs/html/guide/topics/manifest/service-element.jd b/docs/html/guide/topics/manifest/service-element.jd index e5ac7b5..0a44e2c 100644 --- a/docs/html/guide/topics/manifest/service-element.jd +++ b/docs/html/guide/topics/manifest/service-element.jd @@ -17,7 +17,7 @@ page.title=<service> <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code></dd> <dt>can contain:</dt> -<dd><code><a href="{@docRoot}guide/topics/manifest/intent-filter-element.html"><intent-filer></a></code> +<dd><code><a href="{@docRoot}guide/topics/manifest/intent-filter-element.html"><intent-filter></a></code> <br/><code><a href="{@docRoot}guide/topics/manifest/meta-data-element.html"><meta-data></a></code></dd> <dt>description:</dt> diff --git a/docs/html/guide/topics/media/jet/jetcreator_manual.jd b/docs/html/guide/topics/media/jet/jetcreator_manual.jd index 9692d97..214c79e 100644 --- a/docs/html/guide/topics/media/jet/jetcreator_manual.jd +++ b/docs/html/guide/topics/media/jet/jetcreator_manual.jd @@ -993,7 +993,7 @@ Both would be used together in an interactive game or application.</p> results, scoring or other game actions can take place. </li> <li><span lang=EN-IE>Musical transitions between levels or action sequences can be - synchronized to be musically seemless.</li> + synchronized to be musically seamless.</li> </ol> diff --git a/docs/html/guide/topics/providers/content-providers.jd b/docs/html/guide/topics/providers/content-providers.jd index 86dcebf..5da760a 100644 --- a/docs/html/guide/topics/providers/content-providers.jd +++ b/docs/html/guide/topics/providers/content-providers.jd @@ -731,7 +731,7 @@ class name of the content provider (made lowercase). So, for example, the URI for a TransportationProvider class could be defined as follows: <pre>public static final Uri CONTENT_URI = - Uri.parse("content://com.example.codelab.transporationprovider");</pre> + Uri.parse("content://com.example.codelab.transportationprovider");</pre> <p> If the provider has subtables, also define {@code CONTENT_URI} constants for @@ -740,9 +740,9 @@ that identifies the content provider), and be distinguished only by their paths. For example: </p> -<p style="margin-left: 2em">{@code content://com.example.codelab.transporationprovider/train} -<br/>{@code content://com.example.codelab.transporationprovider/air/domestic} -<br/>{@code content://com.example.codelab.transporationprovider/air/international}</p> +<p style="margin-left: 2em">{@code content://com.example.codelab.transportationprovider/train} +<br/>{@code content://com.example.codelab.transportationprovider/air/domestic} +<br/>{@code content://com.example.codelab.transportationprovider/air/international}</p> <p> For an overview of {@code content:} URIs, see the <a href="#urisum">Content URI diff --git a/docs/html/guide/topics/resources/available-resources.jd b/docs/html/guide/topics/resources/available-resources.jd index 2a6a6ac..2680025 100644 --- a/docs/html/guide/topics/resources/available-resources.jd +++ b/docs/html/guide/topics/resources/available-resources.jd @@ -224,7 +224,7 @@ tags. <p> The following declares two strings: the first — simple text with no formatting (resulting in a CharSequence that is simply a String object) — the second includes formatting information in the string (resulting - in a CharSequence that is a complex data structure). If you are using the custom editor for string files in Eclipse, the HTML formatting tags will automatically be escaped and you will need to use {@link android.content.Context#getString(int) Context.getString()} and {@link android.text.Html#fromHtml} to retreive the resource and then convert it to formatted text. + in a CharSequence that is a complex data structure). If you are using the custom editor for string files in Eclipse, the HTML formatting tags will automatically be escaped and you will need to use {@link android.content.Context#getString(int) Context.getString()} and {@link android.text.Html#fromHtml} to retrieve the resource and then convert it to formatted text. </p> <pre> <resources> diff --git a/docs/html/guide/topics/resources/resources-i18n.jd b/docs/html/guide/topics/resources/resources-i18n.jd index 85b89d1..0162b50 100755 --- a/docs/html/guide/topics/resources/resources-i18n.jd +++ b/docs/html/guide/topics/resources/resources-i18n.jd @@ -754,7 +754,7 @@ Android platform defines a "View" style class that contains all of the standard view attributes: padding, visibility, background, etc.; when View is inflated it uses this style class to retrieve those values from the XML file (at which point style and theme -information is applied as approriate) and load them into its instance.</p> +information is applied as appropriate) and load them into its instance.</p> <p><strong>Configuration</strong>: For any particular resource identifier, there may be multiple different available values depending on the current configuration. 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> diff --git a/docs/html/guide/topics/views/custom-views.jd b/docs/html/guide/topics/views/custom-views.jd index c5f9346..4e0e164 100644 --- a/docs/html/guide/topics/views/custom-views.jd +++ b/docs/html/guide/topics/views/custom-views.jd @@ -151,7 +151,7 @@ custom components, styled text, or anything else you can think of.</p> <p><em>Note:</em> Except for 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> <p><code>onMeasure()</code> is a little more involved. <code>onMeasure()</code> @@ -171,7 +171,7 @@ result will be an exception at measurement time.</p> <li> The overridden <code>onMeasure()</code> method is called with width and height measure specifications (<code>widthMeasureSpec</code> and - <code>heighMeasureSpec</code> parameters, both are integer codes + <code>heightMeasureSpec</code> parameters, both are integer codes representing dimensions) which should be treated as requirements for the restrictions on the width and height measurements you should produce. A full reference to the kind of restrictions these specifications can require @@ -434,7 +434,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}samples/NotePad/index.html">NotePad application</a> in the |