am 66adf0d0: am 70af3cdb: Merge "docs: resolve bugs from external tracker" into jb-mr1-dev

* commit '66adf0d04d92257e60a583617fb97f136fefd192':
  docs: resolve bugs from external tracker
This commit is contained in:
Scott Main
2013-01-08 12:44:06 -08:00
committed by Android Git Automerger
16 changed files with 42 additions and 40 deletions

View File

@ -239,7 +239,7 @@ public class AppWidgetManager {
public static final String EXTRA_CUSTOM_SORT = "customSort";
/**
* A sentiel value that the AppWidget manager will never return as a appWidgetId.
* A sentinel value that the AppWidget manager will never return as a appWidgetId.
*/
public static final int INVALID_APPWIDGET_ID = 0;

View File

@ -32,7 +32,7 @@ import java.util.HashMap;
*
* <p>Each FileObserver instance monitors a single file or directory.
* If a directory is monitored, events will be triggered for all files and
* subdirectories (recursively) inside the monitored directory.</p>
* subdirectories inside the monitored directory.</p>
*
* <p>An event mask is used to specify which changes or actions to report.
* Event type constants are used to describe the possible changes in the

View File

@ -1,7 +1,7 @@
<html>
<body>
Provides tools for browsing the web.
<p>The only classes or interfaces in this package intended for use by SDK
developers are WebView, BroswerCallbackAdapter, BrowserCallback, and CookieManager.
<p>Provides tools for browsing the web.
<p>For more information about building apps with web-based content, see the
<a href="{@docRoot}guide/webapps/overview.html">Web Apps Overview</a>.
</body>
</html>

View File

@ -122,6 +122,7 @@ public void onCreate(Bundle savedInstanceState) {
<pre>
&#64;Override
public void onDestroy() {
super.onDestroy();
if (mServiceConn != null) {
unbindService(mServiceConn);
}

View File

@ -237,16 +237,16 @@ page.title=Wi-Fi Direct
*/
public class WiFiDirectBroadcastReceiver extends BroadcastReceiver {
private WifiP2pManager manager;
private Channel channel;
private MyWiFiActivity activity;
private WifiP2pManager mManager;
private Channel mChannel;
private MyWiFiActivity mActivity;
public WiFiDirectBroadcastReceiver(WifiP2pManager manager, Channel channel,
MyWifiActivity activity) {
super();
this.manager = manager;
this.channel = channel;
this.activity = activity;
this.mManager = manager;
this.mChannel = channel;
this.mActivity = activity;
}
&#064;Override
@ -333,7 +333,7 @@ protected void onCreate(Bundle savedInstanceState){
...
mManager = (WifiP2pManager) getSystemService(Context.WIFI_P2P_SERVICE);
mChannel = mManager.initialize(this, getMainLooper(), null);
mReceiver = new WiFiDirectBroadcastReceiver(manager, channel, this);
mReceiver = new WiFiDirectBroadcastReceiver(mManager, mChannel, this);
...
}
</pre>
@ -397,7 +397,7 @@ protected void onPause() {
that the discovery process succeeded and does not provide any information about the actual peers
that it discovered, if any:</p>
<pre>
manager.discoverPeers(channel, new WifiP2pManager.ActionListener() {
mManager.discoverPeers(channel, new WifiP2pManager.ActionListener() {
&#064;Override
public void onSuccess() {
...
@ -425,8 +425,8 @@ if (WifiP2pManager.WIFI_P2P_PEERS_CHANGED_ACTION.equals(action)) {
// request available peers from the wifi p2p manager. This is an
// asynchronous call and the calling activity is notified with a
// callback on PeerListListener.onPeersAvailable()
if (manager != null) {
manager.requestPeers(channel, myPeerListListener);
if (mManager != null) {
mManager.requestPeers(mChannel, myPeerListListener);
}
}
</pre>
@ -453,7 +453,7 @@ if (WifiP2pManager.WIFI_P2P_PEERS_CHANGED_ACTION.equals(action)) {
WifiP2pDevice device;
WifiP2pConfig config = new WifiP2pConfig();
config.deviceAddress = device.deviceAddress;
manager.connect(channel, config, new ActionListener() {
mManager.connect(mChannel, config, new ActionListener() {
&#064;Override
public void onSuccess() {

View File

@ -115,6 +115,7 @@ other mention of the element name.
<a href="{@docRoot}guide/topics/manifest/provider-element.html">&lt;provider&gt;</a>
<a href="{@docRoot}guide/topics/manifest/grant-uri-permission-element.html">&lt;grant-uri-permission /&gt;</a>
<a href="{@docRoot}guide/topics/manifest/meta-data-element.html">&lt;meta-data /&gt;</a>
<a href="{@docRoot}guide/topics/manifest/path-permission-element.html">&lt;path-permission /&gt;</a>
<a href="{@docRoot}guide/topics/manifest/provider-element.html">&lt;/provider&gt;</a>
<a href="{@docRoot}guide/topics/manifest/uses-library-element.html">&lt;uses-library /&gt;</a>

View File

@ -170,7 +170,7 @@ image is resized and cropped to fit in these dimensions, as appropriate.</li>
be cropped toward the center (if necessary).</li>
<li>{@link android.widget.ImageView#setPadding(int,int,int,int)} defines the padding for all
sides. (Note that, if the images have different aspect-ratios, then less
padding will cause for more cropping of the image if it does not match
padding will cause more cropping of the image if it does not match
the dimensions given to the ImageView.)</li>
</ul>

View File

@ -39,7 +39,7 @@ resources so the system must shut down background processes to recover memory.</
<p>When your activity is destroyed because the user presses <em>Back</em> or the activity finishes
itself, the system's concept of that {@link android.app.Activity} instance is gone forever because
the behavior indicates the activity is no longer needed. However, if the system destroys
the activity due to system constraints (rather than normal app behavior), then althought the actual
the activity due to system constraints (rather than normal app behavior), then although the actual
{@link android.app.Activity} instance is gone, the system remembers that it existed such that if
the user navigates back to it, the system creates a new instance of the activity using a set of
saved data that describes the state of the activity when it was destroyed. The saved data that the
@ -126,7 +126,7 @@ can save the state of the view hierarchy.</p>
state from the {@link android.os.Bundle} that the system
passes your activity. Both the {@link android.app.Activity#onCreate onCreate()} and {@link
android.app.Activity#onRestoreInstanceState onRestoreInstanceState()} callback methods receive
the same {@link android.os.Bundle} that containes the instance state information.</p>
the same {@link android.os.Bundle} that contains the instance state information.</p>
<p>Because the {@link android.app.Activity#onCreate onCreate()} method is called whether the
system is creating a new instance of your activity or recreating a previous one, you must check

View File

@ -265,7 +265,7 @@ signal that your activity instance is being completely removed from the system m
with the activity and your activity should perform most cleanup during {@link
android.app.Activity#onPause} and {@link android.app.Activity#onStop}. However, if your
activity includes background threads that you created during {@link
android.app.Activity#onCreate onCreate()} or other other long-running resources that could
android.app.Activity#onCreate onCreate()} or other long-running resources that could
potentially leak memory if not properly closed, you should kill them during {@link
android.app.Activity#onDestroy}.</p>

View File

@ -115,7 +115,7 @@ present. For example:</p>
<pre>
SharedPreferences sharedPref = getActivity().getPreferences(Context.MODE_PRIVATE);
long default = getResources().getInteger(R.string.saved_high_score_default));
long highScore = sharedPref.getInt(getString(R.string.saved_high_score), default);
int defaultValue = getResources().getInteger(R.string.saved_high_score_default);
long highScore = sharedPref.getInt(getString(R.string.saved_high_score), defaultValue);
</pre>

View File

@ -551,5 +551,5 @@ private InputStream downloadUrl(String urlString) throws IOException {
conn.setDoInput(true);
// Starts the query
conn.connect();
InputStream stream = conn.getInputStream();
return conn.getInputStream();
}</pre>

View File

@ -108,7 +108,7 @@ MyProject/
<p>By default, the <code>layout/main.xml</code> file is used for portrait orientation.</p>
<p>If you want a provide a special layout for landscape, including while on large screens, then
<p>If you want to provide a special layout for landscape, including while on large screens, then
you need to use both the <code>large</code> and <code>land</code> qualifier:</p>
<pre class="classic no-pretty-print">

View File

@ -17,12 +17,12 @@ next.link=create-view.html
<h2>You should also read</h2>
<ul>
<li><a href="{@docRoot}/guide/topics/ui/custom-components.html">Custom Components</a>
<li><a href="{@docRoot}guide/topics/ui/custom-components.html">Custom Components</a>
</li>
<li><a href="{@docRoot}/guide/topics/ui/ui-events.html">Input Events</a></li>
<li><a href="{@docRoot}/guide/topics/graphics/prop-animation.html">Property
<li><a href="{@docRoot}guide/topics/ui/ui-events.html">Input Events</a></li>
<li><a href="{@docRoot}guide/topics/graphics/prop-animation.html">Property
Animation</a></li>
<li><a href="{@docRoot}/guide/topics/graphics/hardware-accel.html">Hardware
<li><a href="{@docRoot}guide/topics/graphics/hardware-accel.html">Hardware
Acceleration</a></li>
<li><a href="{@docRoot}guide/topics/ui/accessibility/index.html">
Accessibility</a> developer guide</li>

View File

@ -153,4 +153,4 @@ important when your application isnt visible and therefore cant be control
UI.</p>
<p>A better approach is to register and unregister the media button event receiver when your
application gains and losses the audio focus. This is covered in detail in the next lesson.</p>
application gains and loses the audio focus. This is covered in detail in the next lesson.</p>

View File

@ -90,8 +90,8 @@ cell represents an APK.</p>
<tbody>
<tr>
<td class="blueCell">ETC1</td>
<td class="greenCell">ATI</td>
<td class="redCell">PowerVR</td>
<td class="redCell">ATI</td>
<td class="greenCell">PowerVR</td>
</tr>
</tbody>
</table>

View File

@ -32,7 +32,7 @@ Intent Filters</a></li>
<p>When you construct an intent, you must specify the action you want the intent to "trigger."
Android defines several actions, including {@link android.content.Intent#ACTION_SEND} which, as
you can probably guess, indicates that the intent is sending data from one activity to another,
even across process boundaries. To send data to another activity, all you need to do is speicify
even across process boundaries. To send data to another activity, all you need to do is specify
the data and its type, the system will identify compatible receiving activities and display them
to the user (if there are multiple options) or immediately start the activity (if there is only
one option). Similarly, you can advertise the data types that your activities support receiving