From 7f877069274c94b373478a8d0c969c9cfd93864f Mon Sep 17 00:00:00 2001
From: Elliott Hughes The listening classes, called broadcast receivers, extend {@link android.content.BroadcastReceiver
BroadcastReceiver}. If you want Android to instantiate the object whenever an appropriate
intent notification is sent, define the receiver with a
diff --git a/docs/html/guide/appendix/faq/commontasks.jd b/docs/html/guide/appendix/faq/commontasks.jd
index e88a8672e98a8..c4fc52a5eefda 100644
--- a/docs/html/guide/appendix/faq/commontasks.jd
+++ b/docs/html/guide/appendix/faq/commontasks.jd
@@ -328,7 +328,7 @@ loopback interface.
mapZoom The map zoom of the map location associated with this panorama. This value is passed on to the
- Maps activity when the Street View "Go to Maps" menu item is chosen. It corresponds to the z paramaeter in
+ Maps activity when the Street View "Go to Maps" menu item is chosen. It corresponds to the z parameter in
the geo: intent. <receiver> element
- in the AndroidManifext.xml file. If the caller is expected to instantiate the
+ in the AndroidManifest.xml file. If the caller is expected to instantiate the
object in preparation to receive a message, this is not required. The receiver
will get a call to their {@link android.content.BroadcastReceiver#onReceive(android.content.Context,android.content.Intent)
BroadcastReceiver.onReceive()} method. A receiver can define an <intent-filter> tag
@@ -468,7 +468,7 @@ user receiving new e-mail.
diff --git a/docs/html/guide/appendix/glossary.jd b/docs/html/guide/appendix/glossary.jd
index ef81631db74b9..97669ba2b679c 100644
--- a/docs/html/guide/appendix/glossary.jd
+++ b/docs/html/guide/appendix/glossary.jd
@@ -167,7 +167,7 @@ page.title=Glossary
mapZoom The map zoom of the map location associated with this panorama. This value is passed on to the
- Maps activity when the Street View "Go to Maps" menu item is chosen. It corresponds to the z paramaeter in
+ Maps activity when the Street View "Go to Maps" menu item is chosen. It corresponds to the z parameter in
the geo: intent.
If you will be running your applications only on actual device hardware, you do not need an AVD — see Developing On a Device for information -on running your applicaiton.
+on running your application.default.properties - Properties for the build system. Do not modify
this file.build.properties - Customizable properties for the build system. You can edit this
- file to overried default build settings used by Ant.src/your/package/namespace/ActivityName.java - The Activity class
you specified during project creation.bin/ - Output directory for the build script.Note: When installing JDK on Windows, the default is to install
in the "Program Files" directory. This location will cause ant to fail, because of
the space. To fix the problem, you can specify the JAVA_HOME variable like this:
-set JAVA_HOME=c:\Prora~1\Java\. The easiest solution, however, is to
+set JAVA_HOME=c:\Progra~1\Java\. The easiest solution, however, is to
install JDK in a non-space directory, for example: c:\java\jdk1.6.0_02.
Once the server has set up connections to all emulator instances, you can use adb commands to control and access those instances. Because the server manages connections to emulator/device instances and handles commands from multiple adb clients, you can control any emulator/device instance from any client (or from a script).
-The sections below describe the commands that you can use to access adb capabilities and manage the state of an emulator/device. Note that if you are developing Android applications in Eclipse and have installed the ADT plugin, you do not need to access adb from the command line. The ADT plugin provides a trasparent integration of adb into the Eclipse IDE. However, you can still use adb directly as necessary, such as for debugging.
+The sections below describe the commands that you can use to access adb capabilities and manage the state of an emulator/device. Note that if you are developing Android applications in Eclipse and have installed the ADT plugin, you do not need to access adb from the command line. The ADT plugin provides a transparent integration of adb into the Eclipse IDE. However, you can still use adb directly as necessary, such as for debugging.
diff --git a/docs/html/guide/developing/tools/adt.jd b/docs/html/guide/developing/tools/adt.jd index f28b24c2af013..219be673db380 100644 --- a/docs/html/guide/developing/tools/adt.jd +++ b/docs/html/guide/developing/tools/adt.jd @@ -4,7 +4,7 @@ page.title=ADT PluginThe Android Development Tools (ADT) plugin adds powerful extensions to the Eclipse integrated development environment. It allows you to create and debug your Android applications easier and faster. If you use Eclipse, the ADT plugin gives you an incredible boost in developing Android applications:
Note that the "Android Editors" feature of ADT requires several optional Eclipse components (for example, WST). If you encounter an error when -installing ADT, your Eclipse installion might not include those components. +installing ADT, your Eclipse installation might not include those components. For information about how to quickly add the necessary components to your Eclipse installation, see the troubleshooting topic ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui".
diff --git a/docs/html/guide/developing/tools/draw9patch.jd b/docs/html/guide/developing/tools/draw9patch.jd index f25fabb7b9723..9607ae75527a7 100644 --- a/docs/html/guide/developing/tools/draw9patch.jd +++ b/docs/html/guide/developing/tools/draw9patch.jd @@ -5,7 +5,7 @@ page.title=Draw 9-patch {@link android.graphics.NinePatch} graphic using a WYSIWYG editor.For an introduction to Nine-patch graphics and how they work, please read the section on Nine-patch in the -Ninepatch Images topic.
+Nine-patch Images topic.
diff --git a/docs/html/guide/developing/tools/emulator.jd b/docs/html/guide/developing/tools/emulator.jd
index 82d3c8dd6d0af..70c94a053698a 100644
--- a/docs/html/guide/developing/tools/emulator.jd
+++ b/docs/html/guide/developing/tools/emulator.jd
@@ -1334,7 +1334,7 @@ B:10.0.2.15:<serverPort>
You can use the power command to control the simulated power state of the emulator instance.The usage for the command is:
power <display|ac|status|present|health|capactiy>+
power <display|ac|status|present|health|capacity>
The event command supports the subcommands listed in the table below.
The emulator lets you simulate various network latency levels, so that you can test your applicaton in an environment more typical of the actual conditions in which it will run. You can set a latency level or range at emulator startup or you can use the console to change the latency dynamically, while the application is running in the emulator.
+The emulator lets you simulate various network latency levels, so that you can test your application in an environment more typical of the actual conditions in which it will run. You can set a latency level or range at emulator startup or you can use the console to change the latency dynamically, while the application is running in the emulator.
To set latency at emulator startup, use the -netdelay emulator option with a supported <delay> value, as listed in the table below. Here are some examples:
emulator -netdelay gprs emulator -netdelay 40 100diff --git a/docs/html/guide/practices/design/responsiveness.jd b/docs/html/guide/practices/design/responsiveness.jd index ecd743d59550b..1d5a235e821d0 100644 --- a/docs/html/guide/practices/design/responsiveness.jd +++ b/docs/html/guide/practices/design/responsiveness.jd @@ -80,7 +80,7 @@ responsive to input and thus avoid ANR dialogs caused by the 5 second input event timeout. These same practices should be followed for any other threads that display UI, as they are also subject to the same timeouts. -
The specific constraint on IntentReciever execution time emphasizes what +
The specific constraint on IntentReceiver execution time emphasizes what they were meant to do: small, discrete amounts of work in the background such as saving a setting or registering a Notification. So as with other methods called in the main thread, applications should avoid potentially long-running diff --git a/docs/html/guide/practices/ui_guidelines/activity_task_design.jd b/docs/html/guide/practices/ui_guidelines/activity_task_design.jd index e2fc89c6ddba2..6cd219937b38c 100644 --- a/docs/html/guide/practices/ui_guidelines/activity_task_design.jd +++ b/docs/html/guide/practices/ui_guidelines/activity_task_design.jd @@ -469,7 +469,7 @@ page.title=Activity and Task Design Guidelines re-use activities in other applications, and how your activities might be re-used by other applications. If you add an activity with the same intent filter as an - exisiting activity, then the system presents the user with a choice + existing activity, then the system presents the user with a choice between the activities.
@@ -879,7 +879,7 @@ page.title=Activity and Task Design GuidelinesYou can either test that an activity matches the intent, which you can do before starting the activity, or catch an exception if starting the - activity fails. Both approaches are descibed in the blog posting + activity fails. Both approaches are described in the blog posting Can I use this Intent?.
@@ -938,7 +938,7 @@ page.title=Activity and Task Design Guidelines the menus, the system compares the "Share" request (an Intent object) to available activities (by looking at their intent filters) and displays choices to share. In this case, it - matches Email, Gmail, Messaging and Picassa. If your activity + matches Email, Gmail, Messaging and Picasa. If your activity can send a picture or upload it to a website, all it needs to do is make itself available for sharing (by setting its intent filter). @@ -978,7 +978,7 @@ page.title=Activity and Task Design Guidelinesandroid:versionCode — An integer value that represents
the version of the application code, relative to other versions.
-The value is an integer so that other applications can programatically +
The value is an integer so that other applications can programmatically evaluate it, for example to check an upgrade or downgrade relationship. You can set the value to any integer you want, however you should make sure that each successive release of your application uses a greater value. The system does not @@ -78,7 +78,7 @@ normative.
versionCode set to 1, then monotonically increase the value with each release, regardless whether the release constitutes a major or minor release. This means that theandroid:versionCode value does not necessarily have a
-strong resemblence to the application release version that is visible to the
+strong resemblance to the application release version that is visible to the
user (see android:versionName, below). Applications and publishing
services should not display this version value to users.
Also, the Activity must be declared in the AppWidgetProviderInfo XML file, with the
android:configure attribute (see Adding
-the AppWidgetProvierInfo Metadata above). For example, the configuration Activity
+the AppWidgetProviderInfo Metadata above). For example, the configuration Activity
can be declared like this:
diff --git a/docs/html/guide/topics/fundamentals.jd b/docs/html/guide/topics/fundamentals.jd index 71705d354f622..935ec93e7f67e 100644 --- a/docs/html/guide/topics/fundamentals.jd +++ b/docs/html/guide/topics/fundamentals.jd @@ -262,7 +262,7 @@ camera button has been pressed.-There are separate methods for activiating each type of component: +There are separate methods for activating each type of component:
There are three ways to define and instantiate a Drawable: using an image saved in your project resouces; +
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).
@@ -126,7 +126,7 @@ instead of directly transforming the Drawable, you should perform a User Interface. 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. @@ -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.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:
+draw the shape programmatically in an Activity:CustomDrawableView mCustomDrawableView; @@ -248,7 +248,7 @@ of the object it's attached to.NinePatchDrawable
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
.9.png, @@ -271,7 +271,7 @@ and saved into theres/drawable/directory of your project. define this drawable area.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.
@@ -281,7 +281,7 @@ of the View are allowed to lie within.
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.
@@ -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. -A sequence of animation instructions defines the twen animation, defined by either XML or Android code. +
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 Available Resources.
Note: 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 will occur if the animation exceeds the bounds of the parent View.
diff --git a/docs/html/guide/topics/graphics/index.jd b/docs/html/guide/topics/graphics/index.jd index bc2a8bf7fca26..e1158be7a067c 100644 --- a/docs/html/guide/topics/graphics/index.jd +++ b/docs/html/guide/topics/graphics/index.jd @@ -112,7 +112,7 @@ likedrawBitmap(...),drawRect(...),drawText(.. Other classes that you might use also havedraw()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{@link android.graphics.drawable.Drawable#draw(Canvas) draw()}method -that takes your Canvas as an arguement. +that takes your Canvas as an argument.On a View
@@ -124,7 +124,7 @@ and drawing with a Canvas in{@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. -To start, extend the {@link android.view.View} class (or descendent thereof) and define +
To start, extend the {@link android.view.View} class (or descendant thereof) and define the
@@ -190,7 +190,7 @@ with{@link android.view.View#onDraw(Canvas) onDraw()}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 theonDraw()callback.{@link android.graphics.Canvas#drawBitmap(Bitmap,Rect,RectF,Paint) dr you will see traces of the drawings you previously performed. -For a sample application, see the Lunar Landar game, in the SDK samples folder: +
For a sample application, see the Lunar Lander game, in the SDK samples folder:
diff --git a/docs/html/guide/topics/manifest/activity-element.jd b/docs/html/guide/topics/manifest/activity-element.jd index 83237c61dd5b3..c22d3e12d45c1 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:process="string" android:screenOrientation=["unspecified" | "user" | "behind" | "landscape" | "portrait" | - "sensor" | "nonsensor"] + "sensor" | "nosensor"] android:stateNotNeeded=["true" | "false"] android:taskAffinity="string" android:theme="resource or theme" @@ -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. diff --git a/docs/html/guide/topics/manifest/data-element.jd b/docs/html/guide/topics/manifest/data-element.jd index b48c5e0432474..b77fd059917b4 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<your-sdk-directory>/samples/LunarLander/. Or, browse the source in the Sample Code section.schemeis not specified for the intent filter, all the other URI attributes are ignored. If a -hostis not specified for the filer, +hostis not specified for the filter, the {@code port} attribute and all the path attributes are ignored. diff --git a/docs/html/guide/topics/manifest/permission-tree-element.jd b/docs/html/guide/topics/manifest/permission-tree-element.jd index 3074354c773e9..aecc9307460ef 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.- 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.
diff --git a/docs/html/guide/topics/manifest/provider-element.jd b/docs/html/guide/topics/manifest/provider-element.jd index 2bb4ff40f03b2..7f51f8d064acb 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. diff --git a/docs/html/guide/topics/manifest/receiver-element.jd b/docs/html/guide/topics/manifest/receiver-element.jd index 280d40243b840..b2089177b6053 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><application>- can contain:
-<intent-filer>+<intent-filter><meta-data>- description:
diff --git a/docs/html/guide/topics/manifest/service-element.jd b/docs/html/guide/topics/manifest/service-element.jd index e5ac7b58148a9..0a44e2c0cf547 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><application>- can contain:
-<intent-filer>+<intent-filter><meta-data>- description:
diff --git a/docs/html/guide/topics/media/jet/jetcreator_manual.jd b/docs/html/guide/topics/media/jet/jetcreator_manual.jd index 9692d9767815b..214c79eed7b39 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. results, scoring or other game actions can take place.- Musical transitions between levels or action sequences can be - synchronized to be musically seemless.
+ synchronized to be musically seamless. diff --git a/docs/html/guide/topics/providers/content-providers.jd b/docs/html/guide/topics/providers/content-providers.jd index 86dcebfa1e759..5da760a17eb0c 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:public static final Uri CONTENT_URI = - Uri.parse("content://com.example.codelab.transporationprovider");+ Uri.parse("content://com.example.codelab.transportationprovider");
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:
-{@code content://com.example.codelab.transporationprovider/train}
-
{@code content://com.example.codelab.transporationprovider/air/domestic}
-
{@code content://com.example.codelab.transporationprovider/air/international}
{@code content://com.example.codelab.transportationprovider/train}
+
{@code content://com.example.codelab.transportationprovider/air/domestic}
+
{@code content://com.example.codelab.transportationprovider/air/international}
Configuration: 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 85aed18af5a03..4725321d1a1c9 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
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).
The following code sample does the following:
You handle the user's selecction by setting the class's {@link +
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.
diff --git a/docs/html/guide/topics/ui/custom-components.jd b/docs/html/guide/topics/ui/custom-components.jd index 76d1034408779..6027a82673b6a 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.Note: 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.
@@ -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.For example, the SDK includes a NotePad application in the diff --git a/docs/html/guide/topics/ui/declaring-layout.jd b/docs/html/guide/topics/ui/declaring-layout.jd index 7ef22a6be2419..ec22cbca09d37 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) {
The
+Application Fundamentals, for more on this).onCreate()callback method in your Activity is called by the Android framework when your Activity is launched (see the discussion on Lifecycles, in the -Application Fundamantals, for more on this).Attributes
diff --git a/docs/html/guide/topics/ui/dialogs.jd b/docs/html/guide/topics/ui/dialogs.jd index c0c0b1bc58da4..11c8a47eb300d 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.Using dismiss listeners
-If you'd like your applcation to perform some procedures the moment that a dialog is dismissed, +
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.
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 21f9833849546..efb55a2832361 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.
@@ -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.- To intiate a layout, call
{@link android.view.View#requestLayout}. This method is typically + To initiate a layout, call{@link android.view.View#requestLayout}. This method is typically called by a View on itself when it believes that is can no longer fit within its current bounds.
The name of an XML element
is respective to the Java class that it represents. So a <TextView> element creates
diff --git a/docs/html/guide/topics/ui/menus.jd b/docs/html/guide/topics/ui/menus.jd
index bae94ca532bf8..0129e8f8ffabf 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.
When a menu item is selected from the Options Menu, you will recieve a callback to the +
When a menu item is selected from the Options Menu, you will receive a callback to the
{@link android.app.Activity#onOptionsItemSelected(MenuItem) onOptionsItemSelected()}
method of your Activity. This callback passes you the
MenuItem 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 editNote() and deleteNote() methods to perfrom
+is passed to the editNote() and deleteNote() methods to perform
the respective action.
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
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).
+mutually exclusive options (see the screenshot, to the right).Note: 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; } diff --git a/docs/html/guide/topics/ui/notifiers/index.jd b/docs/html/guide/topics/ui/notifiers/index.jd index 5b37f5b623aa5..f7ccce771411f 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:
-A toast notificaiton is a message that pops up on the surface of the window. +
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
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 e6fa48fe2385a..a0dd9f11d5ec5 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.
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...
As shown here, pass the applicaiton's package name and the layout +
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 a800c3c900dfd..5b324d282b45b 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
A toast notificaiton is a message that pops up on the surface of the window. +
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.
diff --git a/docs/html/guide/topics/ui/themes.jd b/docs/html/guide/topics/ui/themes.jd index 41e85635e6ba7..0399512665335 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.To set this theme for all the activites of your application, open the AndroidManifest.xml file and +
To set this theme for all the activities of your application, open the AndroidManifest.xml file and
edit the <application> tag to include the android:theme attribute with the
theme name:
onTouchEvent() 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 event listeners, are your ticket to capturing the user interaction with your UI.
@@ -102,7 +102,7 @@ protected void onCreate(Bundle savedValues) {
}
-You may also find it more conventient to implement OnClickListener as a part of your Activity. +
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:
public class ExampleActivity extends Activity implements OnClickListener {
@@ -139,7 +139,7 @@ depends on the event. For the few that do, here's why:
this event can have multiple actions that follow each other. So, if you return false 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.
+ within the event, such as a finger gesture, or the eventual up action event.
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
{@link android.view.View#onTouchEvent} - Called when a touch screen motion event occurs.{@link android.view.View#onFocusChanged} - Called when the view gains or loses focus.There are some other methods that you should be awere of, which are not part of the View class, +
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:
Note: 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.
onMeasure() is a little more involved. onMeasure()
@@ -171,7 +171,7 @@ result will be an exception at measurement time.
onMeasure() method is called with width and
height measure specifications (widthMeasureSpec and
- heighMeasureSpec parameters, both are integer codes
+ heightMeasureSpec 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.
For example, the SDK includes a NotePad application in the diff --git a/docs/html/guide/tutorials/hello-world.jd b/docs/html/guide/tutorials/hello-world.jd index 79b723d162d6e..9be63bd1c4499 100644 --- a/docs/html/guide/tutorials/hello-world.jd +++ b/docs/html/guide/tutorials/hello-world.jd @@ -478,12 +478,12 @@ particularly powerful with the code-completion features of IDEs like Eclipse because it lets you quickly and interactively locate the specific reference you're looking for.
-It's possible yours looks slighly different than this (perhaps the hexadecimal values are different). +
It's possible yours looks slightly different than this (perhaps the hexadecimal values are different).
For now, notice the inner class named "layout", and its
member field "main". The Eclipse plugin noticed the XML
layout file named main.xml and generated a class for it here. As you add other
resources to your project (such as strings in the res/values/string.xml file or drawables inside
-the res/drawable/ direcory) you'll see R.java change to keep up.
res/drawable/ directory) you'll see R.java change to keep up.
When not using Eclipse, this class file will be generated for you at build time (with the Ant tool).
You should never edit this file by hand.
diff --git a/docs/html/guide/tutorials/views/hello-autocomplete.jd b/docs/html/guide/tutorials/views/hello-autocomplete.jd index fba1ad887506b..07235a14ab48b 100644 --- a/docs/html/guide/tutorials/views/hello-autocomplete.jd +++ b/docs/html/guide/tutorials/views/hello-autocomplete.jd @@ -44,7 +44,7 @@ protected void onCreate(Bundle savedInstanceState) { textView.setAdapter(adapter); } -Here, we create an AutoComplteteTextView from our layout. We then +
Here, we create an AutoCompleteTextView from our layout. We then
create an {@link android.widget.ArrayAdapter} that binds a simple_dropdown_item_1line
layout item to each entry in the COUNTRIES array (which we'll add next).
The last part sets the ArrayAdapter to associate with our AutoCompleteTextView.
onCreate() method):
diff --git a/docs/html/guide/tutorials/views/hello-gridview.jd b/docs/html/guide/tutorials/views/hello-gridview.jd
index ffb6c93efde57..186c4e7513a60 100644
--- a/docs/html/guide/tutorials/views/hello-gridview.jd
+++ b/docs/html/guide/tutorials/views/hello-gridview.jd
@@ -94,7 +94,7 @@ public class ImageAdapter extends BaseAdapter {
}
First we take care of some required methods inherited from BaseAdapter.
- The constructor and getCount() are self-explanitory. Normally, getItem()
+ The constructor and getCount() are self-explanatory. Normally, getItem()
should return the actual object at the specified position in our Adapter, but for this Hello World,
we're not going to bother. Likewise, getItemId() should return the row id of
the item, but right now we don't care.
public class HelloMapView extends MapActivity {
@@ -134,7 +134,7 @@ mZoom = (ZoomControls) mapView.getZoomControls();
By using the ZoomControls object provided by MapView, we don't have to do any of the work required to actually perform the zoom operations. The ZoomControls widget that MapView returns for us is already hooked into the MapView and works as soon as we add it to the - layout. The controls will appear whenever the user touches the map, then dissapear after + layout. The controls will appear whenever the user touches the map, then disappear after a few moments of inactivity.
Notice that the TabWidget and the FrameLayout elements have specific android namespace IDs. These are necessary
- so that the TabHost can automatically retireve references to them, populate the TabWidget with the tabs that we'll define
+ so that the TabHost can automatically retrieve references to them, populate the TabWidget with the tabs that we'll define
in our code, and swap the views in the FrameLayout. We've also defined our own IDs for each TextView, which we'll use to
associate each tab with the view that it should reveal.
Of course, you can diff --git a/docs/html/sdk/1.5_r3/installing.jd b/docs/html/sdk/1.5_r3/installing.jd index 8c3e8ee841864..c01dd36c6e638 100644 --- a/docs/html/sdk/1.5_r3/installing.jd +++ b/docs/html/sdk/1.5_r3/installing.jd @@ -95,7 +95,7 @@ the tools included in the SDK (skip to Next Steps).
Android offers a custom plugin for the Eclipse IDE, called Android Development Tools (ADT), that is designed to give you a powerful, integrated environment in which to build Android applications. It -extends the capabilites of Eclipse to let you quickly set up new Android +extends the capabilities of Eclipse to let you quickly set up new Android projects, create an application UI, add components based on the Android Framework API, debug your applications using the Android SDK tools, and even export signed (or unsigned) APKs in order to distribute your application.
@@ -125,7 +125,7 @@ and click Next.https://dl-ssl.google.com/android/eclipse/-
If you have trouble aqcuiring the plugin, try using "http" in the URL, +
If you have trouble acquiring the plugin, try using "http" in the URL, instead of "https" (https is preferred for security reasons).
Click OK.
https://dl-ssl.google.com/android/eclipse/-
If you have trouble aqcuiring the plugin, try using "http" in the Location URL, +
If you have trouble acquiring the plugin, try using "http" in the Location URL, instead of "https" (https is preferred for security reasons).
Click OK.
Note that there are features of ADT that require some optional Eclipse components (for example, WST). If you encounter an error when -installing ADT, your Eclipse installion might not include these components. +installing ADT, your Eclipse installation might not include these components. For information about how to quickly add the necessary components to your Eclipse installation, see the troubleshooting topic ADT @@ -271,7 +271,7 @@ begin developing applications. Here are a few ways you can get started:
<sdk>/platforms/<platfrom>/samples,
+ included in <sdk>/platforms/<platform>/samples,
then compile and run it in your development environmentR.java and old auto-generated AIDL java files from the
src/ folder. (This
-does not apply to your own hand-crafted parcelabe AIDL java files.)
+does not apply to your own hand-crafted parcelable AIDL java files.)
Note: The "activitycreator" tool has been replaced by the new "android" tool. For information on creating new projects with the android tool, @@ -368,7 +368,7 @@ if it performs any of the following:
listens for special keypress events that only occur on a keypad, then your application should degrade gracefully when there is no keyboard available.T-Mobile G1 Compatability
+T-Mobile G1 Compatibility
-This version of the SDK has been tested for compatability with the first +
This version of the SDK has been tested for compatibility with the first Android-powered mobile device, the T-Mobile G1.
diff --git a/docs/html/sdk/android-1.5.jd b/docs/html/sdk/android-1.5.jd index 748f3ee4e44b0..ac4890080cfda 100644 --- a/docs/html/sdk/android-1.5.jd +++ b/docs/html/sdk/android-1.5.jd @@ -108,7 +108,7 @@ new APIs introduced since Android 1.0, you can remove the attribute or set it to "1". However, before publishing your application, you must make sure to compile your application against the Android library that corresponds to the application's -android:minSdkVeresion value.
+android:minSdkVersion value.
The sections below describe the system and software requirements for using the Android NDK, as well as platform compatibility considerations that affect -appplications using libraries produced with the NDK.
+applications using libraries produced with the NDK.