Merge "Fix Minor typos" into jb-dev
This commit is contained in:
committed by
Android (Google) Code Review
commit
27ad058a94
@@ -224,7 +224,7 @@ style="font-weight:500;">App Widgets</span> can resize automatically to fit the
|
|||||||
|
|
||||||
<p>Apps can take advantage of vsync timing for free, through Android’s <strong>animation framework</strong>. The animation framework now uses vsync timing to automatically handle synchronization across animators.</p>
|
<p>Apps can take advantage of vsync timing for free, through Android’s <strong>animation framework</strong>. The animation framework now uses vsync timing to automatically handle synchronization across animators.</p>
|
||||||
|
|
||||||
<p>For specialized uses, apps can access vsync timing through APIs exposed by a new Choreographer class. Apps can request invalidation on the next vsync frame — a good way to schedule animation when the app is not using the animation framework. For more advanced uses, apps can post a calllback that the Choreographer class will run on the next frame. </p>
|
<p>For specialized uses, apps can access vsync timing through APIs exposed by a new Choreographer class. Apps can request invalidation on the next vsync frame — a good way to schedule animation when the app is not using the animation framework. For more advanced uses, apps can post a callback that the Choreographer class will run on the next frame. </p>
|
||||||
|
|
||||||
<h3>New animation actions and transition types</h3>
|
<h3>New animation actions and transition types</h3>
|
||||||
|
|
||||||
|
|||||||
@@ -51,7 +51,7 @@ page.title=Migration
|
|||||||
<dd>To use the GCM service, you need to obtain a Simple API Key from Google APIs console page. For more information, see <a href="gs.html">Getting Started</a>. Note that GCM <em>only</em> accepts Simple API Key—using ClientLogin or OAuth2 tokens will not work.
|
<dd>To use the GCM service, you need to obtain a Simple API Key from Google APIs console page. For more information, see <a href="gs.html">Getting Started</a>. Note that GCM <em>only</em> accepts Simple API Key—using ClientLogin or OAuth2 tokens will not work.
|
||||||
</dd>
|
</dd>
|
||||||
<dt><strong>Sender ID</strong></dt>
|
<dt><strong>Sender ID</strong></dt>
|
||||||
<dd>In C2DM, the Sender ID is an email address. In GCM, the Sender ID is a project ID that you acquire from the API console, as described in <a href="https://devsite.googleplex.com/android/gcm/gs.html#create-proj">Getting Started</a>. </dd>
|
<dd>In C2DM, the Sender ID is an email address. In GCM, the Sender ID is a project ID that you acquire from the API console, as described in <a href="gs.html#create-proj">Getting Started</a>. </dd>
|
||||||
|
|
||||||
<dt><strong>JSON format</strong></dt>
|
<dt><strong>JSON format</strong></dt>
|
||||||
<dd>GCM HTTP requests support JSON format in addition to plain text. For more information, see the <a href="gcm.html#send-msg">Architectural Overview</a>.</dd>
|
<dd>GCM HTTP requests support JSON format in addition to plain text. For more information, see the <a href="gcm.html#send-msg">Architectural Overview</a>.</dd>
|
||||||
|
|||||||
@@ -66,7 +66,7 @@ page.title=Developer Tools
|
|||||||
<h3>Powerful Debugging</h3>
|
<h3>Powerful Debugging</h3>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>Full Java debugger with on-device debugging and Android-specidic tools</li>
|
<li>Full Java debugger with on-device debugging and Android-specific tools</li>
|
||||||
<li>Built-in memory analysis, performance/CPU profiling, OpenGL ES tracing.</li>
|
<li>Built-in memory analysis, performance/CPU profiling, OpenGL ES tracing.</li>
|
||||||
<li>Graphical tools for debugging and optimizing UI, runtime inspecton of UI structure and performance.</li>
|
<li>Graphical tools for debugging and optimizing UI, runtime inspecton of UI structure and performance.</li>
|
||||||
<li>Runtime graphical analysis of your app's network bandwidth usage.</li>
|
<li>Runtime graphical analysis of your app's network bandwidth usage.</li>
|
||||||
|
|||||||
@@ -126,7 +126,7 @@ including when it's created for the first time. As such, you should implement {@
|
|||||||
android.app.Activity#onResume()} to initialize components that you release during {@link
|
android.app.Activity#onResume()} to initialize components that you release during {@link
|
||||||
android.app.Activity#onPause()} and perform any other initializations that must occur each time the
|
android.app.Activity#onPause()} and perform any other initializations that must occur each time the
|
||||||
activity enters the Resumed state (such as begin animations and initialize components only used
|
activity enters the Resumed state (such as begin animations and initialize components only used
|
||||||
while the actiivty has user focus).</p>
|
while the activity has user focus).</p>
|
||||||
|
|
||||||
<p>The following example of {@link android.app.Activity#onResume()} is the counterpart to
|
<p>The following example of {@link android.app.Activity#onResume()} is the counterpart to
|
||||||
the {@link android.app.Activity#onPause()} example above, so it initializes the camera that's
|
the {@link android.app.Activity#onPause()} example above, so it initializes the camera that's
|
||||||
|
|||||||
@@ -285,6 +285,6 @@ android.app.Activity#onStop} in all situations except one: when you call {@link
|
|||||||
android.app.Activity#finish()} from within the {@link android.app.Activity#onCreate onCreate()}
|
android.app.Activity#finish()} from within the {@link android.app.Activity#onCreate onCreate()}
|
||||||
method. In some cases, such as when your activity operates as a temporary decision maker to
|
method. In some cases, such as when your activity operates as a temporary decision maker to
|
||||||
launch another activity, you might call {@link android.app.Activity#finish()} from within {@link
|
launch another activity, you might call {@link android.app.Activity#finish()} from within {@link
|
||||||
android.app.Activity#onCreate onCreate()} to destory the activity. In this case, the system
|
android.app.Activity#onCreate onCreate()} to destroy the activity. In this case, the system
|
||||||
immediately calls {@link android.app.Activity#onDestroy} without calling any of the other
|
immediately calls {@link android.app.Activity#onDestroy} without calling any of the other
|
||||||
lifecycle methods.</p>
|
lifecycle methods.</p>
|
||||||
|
|||||||
Reference in New Issue
Block a user