diff options
Diffstat (limited to 'docs/html')
13 files changed, 41 insertions, 26 deletions
diff --git a/docs/html/training/accessibility/accessible-app.jd b/docs/html/training/accessibility/accessible-app.jd index f4087b8..dd26feb 100644 --- a/docs/html/training/accessibility/accessible-app.jd +++ b/docs/html/training/accessibility/accessible-app.jd @@ -50,11 +50,14 @@ cues are needed.</p> <p>Fortunately, it's easy to add labels to UI elements in your application that can be read out loud to your user by a speech-based accessibility service like <a - href="https://market.android.com/details?id=com.google.android.marvin.talkback">TalkBack</a>. +href="https://play.google.com/store/apps/details?id=com.google.android.marvin.talkback">TalkBack</a> +. If you have a label that's likely not to change during the lifecycle of the application (such as "Pause" or "Purchase"), you can add it via the XML layout, by setting a UI element's <a - href="{@docRoot}reference/android/view.View#attr_android:contentDescription">android:contentDescription</a> attribute, like in this + +href="{@docRoot}reference/android/view/View.html#attr_android:contentDescription" +>{@code android:contentDescription}</a> attribute, like in this example:</p> <pre> <Button @@ -83,7 +86,7 @@ the noise a user needs to navigate in order to pull useful information from your interface.</p> <p>Try it out! Download <a - href="https://market.android.com/details?id=com.google.android.marvin.talkback">TalkBack</a> +href="https://play.google.com/store/apps/details?id=com.google.android.marvin.talkback">TalkBack</a> (an accessibility service published by Google) and enable it in <strong>Settings > Accessibility > TalkBack</strong>. Then navigate around your own application and listen for the audible cues provided by TalkBack.</p> @@ -101,21 +104,21 @@ modification can be done at runtime using the {@link android.view.View#setFocusable View.setFocusable()} method on that UI control, or by setting the <a - href="{@docRoot}android.view.View#attr_android:focusable">{@code + href="{@docRoot}reference/android/view/View.html#attr_android:focusable">{@code android:focusable}</a> attrubute in your XML layout files.</p> <p>Also, each UI control has 4 attributes, -<a href="{@docRoot}reference/android/view/View#attr_android:nextFocusUp">{@code +<a href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusUp">{@code android:nextFocusUp}</a>, <a - href="{@docRoot}reference/android/view/View#attr_android:nextFocusDown">{@code + href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusDown">{@code android:nextFocusDown}</a>, <a - href="{@docRoot}reference/android/view/View#attr_android:nextFocusLeft">{@code + href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusLeft">{@code android:nextFocusLeft}</a>, and <a - href="{@docRoot}reference/android/view/View#attr_android:nextFocusRight">{@code + href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusRight">{@code android:nextFocusRight}</a>, which you can use to designate the next view to receive focus when the user navigates in that direction. While @@ -178,7 +181,8 @@ public void onTextChanged(String before, String after) { <p>Be sure to test the accessibility functionality as you add it to your application. In order to test the content descriptions and Accessibility events, install and enable an accessibility service. One option is <a - href="https://play.google.com/store/details?id=com.google.android.marvin.talkback">Talkback</a>, +href="https://play.google.com/store/apps/details?id=com.google.android.marvin.talkback">Talkback</a> +, a free, open source screen reader available on Google Play. With the service enabled, test all the navigation flows through your application and listen to the spoken feedback.</p> diff --git a/docs/html/training/basics/firstapp/building-ui.jd b/docs/html/training/basics/firstapp/building-ui.jd index 847163a..dae70a2 100644 --- a/docs/html/training/basics/firstapp/building-ui.jd +++ b/docs/html/training/basics/firstapp/building-ui.jd @@ -56,7 +56,8 @@ but it's especially important on Android because it allows you to define alterna different screen sizes. For example, you can create two versions of a layout and tell the system to use one on "small" screens and the other on "large" screens. For more information, see the class about <a -href="{@docRoot}training/supporting-hardware/index.html">Supporting Various Hardware</a>.</p> +href="{@docRoot}training/basics/supporting-devices/index.html">Supporting Different +Hardware</a>.</p> </div> </div> diff --git a/docs/html/training/basics/firstapp/running-app.jd b/docs/html/training/basics/firstapp/running-app.jd index 2398fa0..43b8983 100644 --- a/docs/html/training/basics/firstapp/running-app.jd +++ b/docs/html/training/basics/firstapp/running-app.jd @@ -35,7 +35,7 @@ next.link=building-ui.html </div> -<p>If you followed the <a href="{@docRoot}creating-project.html">previous lesson</a> to create an +<p>If you followed the <a href="creating-project.html">previous lesson</a> to create an Android project, it includes a default set of "Hello World" source files that allow you to run the app right away.</p> diff --git a/docs/html/training/basics/firstapp/starting-activity.jd b/docs/html/training/basics/firstapp/starting-activity.jd index 16a6fd8..c548c1d 100644 --- a/docs/html/training/basics/firstapp/starting-activity.jd +++ b/docs/html/training/basics/firstapp/starting-activity.jd @@ -128,7 +128,7 @@ can also be <em>implicit</em>, in which case the {@link android.content.Intent} the desired component, but allows any app installed on the device to respond to the intent as long as it satisfies the meta-data specifications for the action that's specified in various {@link android.content.Intent} parameters. For more informations, see the class about <a -href="{@docRoot}training/intents/index.html">Interacting with Other Apps</a>.</p> +href="{@docRoot}training/basics/intents/index.html">Interacting with Other Apps</a>.</p> </div> </div> @@ -301,7 +301,8 @@ on Android 4.0. <p>To learn more about building Android apps, continue to follow the basic training classes. The next class is <a -href="{@docRoot}training/activity-lifecycle/index.html">Managing the Activity Lifecycle</a>.</p> +href="{@docRoot}training/basics/activity-lifecycle/index.html">Managing the Activity +Lifecycle</a>.</p> diff --git a/docs/html/training/basics/fragments/communicating.jd b/docs/html/training/basics/fragments/communicating.jd index b2292b1..e3e308f 100644 --- a/docs/html/training/basics/fragments/communicating.jd +++ b/docs/html/training/basics/fragments/communicating.jd @@ -4,7 +4,7 @@ parent.link=index.html trainingnavtop=true previous.title=Building a Flexible UI -previous.link=fragment-ui.html +previous.link=fragment-ui.html @jd:body diff --git a/docs/html/training/basics/fragments/creating.jd b/docs/html/training/basics/fragments/creating.jd index 9f3ed06..c4a9b46 100644 --- a/docs/html/training/basics/fragments/creating.jd +++ b/docs/html/training/basics/fragments/creating.jd @@ -6,7 +6,7 @@ trainingnavtop=true previous.title=Using the Android Support Library previous.link=support-lib.html next.title=Building a Flexible UI -next.link=fragment-ui.html +next.link=fragment-ui.html @jd:body diff --git a/docs/html/training/basics/fragments/support-lib.jd b/docs/html/training/basics/fragments/support-lib.jd index c26f6c8..e2166f5 100644 --- a/docs/html/training/basics/fragments/support-lib.jd +++ b/docs/html/training/basics/fragments/support-lib.jd @@ -63,9 +63,8 @@ API level to the latest release: Android or don't exist in the platform at all and merely provide additional support to you when developing specific application features.</p> -<p>You can find all the API reference documentation for the Support Library included in the -platform docs in the {@link android.support.v4} package. For which API references are available -at {@link android.support.v4}.</p> +<p>You can find all the API reference documentation for the Support Library in the +platform docs at {@link android.support.v4.app android.support.v4.*}.</p> <div class="warning"><p><strong>Warning:</strong> To be sure that you don't accidentally use new APIs on an older system version, be certain that you import the {@link diff --git a/docs/html/training/basics/location/currentlocation.jd b/docs/html/training/basics/location/currentlocation.jd index 4692530..29b0fa6 100644 --- a/docs/html/training/basics/location/currentlocation.jd +++ b/docs/html/training/basics/location/currentlocation.jd @@ -143,7 +143,15 @@ private boolean isSameProvider(String provider1, String provider2) { <h2 id="TaskTerminateUpdates">Terminate Location Updates</h2> -<p>When you are done with using location data, you should terminate location update to reduce unnecessary consumption of power and network bandwidth. For example, if the user navigates away from an activity where location updates are displayed, you should stop location update by calling {@link android.location.LocationManager#removeUpdates(android.location.LocationListener) removeUpdates()} in {@link android.app.Activity#onStop()}. ({@link android.app.Activity#onStop()} is called when the activity is no longer visible. If you want to learn more about activity lifecycle, read up on the <a href="/training/basic-activity-lifecycle/stopping.html">Starting and Stopping an Activity</a> lesson.</p> +<p>When you are done with using location data, you should terminate location update to reduce +unnecessary consumption of power and network bandwidth. For example, if the user navigates away +from an activity where location updates are displayed, you should stop location update by calling +{@link android.location.LocationManager#removeUpdates(android.location.LocationListener) +removeUpdates()} in {@link android.app.Activity#onStop()}. ({@link android.app.Activity#onStop()} +is called when the activity is no longer visible. If you want to learn more about activity +lifecycle, read up on the <a +href="{@docRoot}training/basics/activity-lifecycle/stopping.html">Stopping and Restarting an +Activity</a> lesson.</p> <pre> protected void onStop() { diff --git a/docs/html/training/displaying-bitmaps/display-bitmap.jd b/docs/html/training/displaying-bitmaps/display-bitmap.jd index 7a93313..5eac04c 100644 --- a/docs/html/training/displaying-bitmaps/display-bitmap.jd +++ b/docs/html/training/displaying-bitmaps/display-bitmap.jd @@ -315,7 +315,8 @@ additional processing needs to be done, your UI grinds to a halt.</p> <p>The same asynchronous processing and caching methods from the previous section can be implemented here. However, you also need to wary of concurrency issues as the {@link android.widget.GridView} recycles its children views. To handle this, use the techniques discussed in the <a -href="process-bitmap#concurrency">Processing Bitmaps Off the UI Thread</a> lesson. Here is the updated +href="process-bitmap.html#concurrency">Processing Bitmaps Off the UI Thread</a> lesson. Here is the +updated solution:</p> <pre> diff --git a/docs/html/training/search/backward-compat.jd b/docs/html/training/search/backward-compat.jd index 0894fa9..11473a0 100644 --- a/docs/html/training/search/backward-compat.jd +++ b/docs/html/training/search/backward-compat.jd @@ -1,7 +1,7 @@ page.title=Remaining Backward Compatible trainingnavtop=true previous.title=Storing and Searching for Data -previous.link=search.html +previous.link=search.html @jd:body diff --git a/docs/html/training/sharing/receive.jd b/docs/html/training/sharing/receive.jd index a0a5bc8..9c932b1 100644 --- a/docs/html/training/sharing/receive.jd +++ b/docs/html/training/sharing/receive.jd @@ -34,7 +34,7 @@ Intent Filters</a></li> from applications. Think about how users interact with your application, and what data types you want to receive from other applications. For example, a social networking application would likely be interested in receiving text content, like an interesting web URL, from another app. The -<a href="https://play.google.com/store/details?id=com.google.android.apps.plus">Google+ Android +<a href="https://play.google.com/store/apps/details?id=com.google.android.apps.plus">Google+ Android application</a> accepts both text <em>and</em> single or multiple images. With this app, a user can easily start a new Google+ post with photos from the Android Gallery app.</p> diff --git a/docs/html/training/tv/optimizing-layouts-tv.jd b/docs/html/training/tv/optimizing-layouts-tv.jd index e4a8e69..49c278c 100644 --- a/docs/html/training/tv/optimizing-layouts-tv.jd +++ b/docs/html/training/tv/optimizing-layouts-tv.jd @@ -186,8 +186,8 @@ cause out-of-memory errors in your app. To avoid this, follow these tips: {@link android.graphics.Bitmap} views that are no longer needed. </li> <li>Use {@link java.lang.ref.WeakReference} for storing references - to {@link android.graphics.Bitmap} objects in a in-memory - <a href="{@link java.util.Collection}.</li> + to {@link android.graphics.Bitmap} objects in an in-memory + {@link java.util.Collection}.</li> <li>If you fetch images from the network, use {@link android.os.AsyncTask} to fetch them and store them on the SD card for faster access. Never do network transactions on the application's UI thread. diff --git a/docs/html/training/tv/unsupported-features-tv.jd b/docs/html/training/tv/unsupported-features-tv.jd index 6b0f8c8..a9f090b 100644 --- a/docs/html/training/tv/unsupported-features-tv.jd +++ b/docs/html/training/tv/unsupported-features-tv.jd @@ -82,8 +82,9 @@ Android doesn't support touchscreen interaction for TV devices, most TVs don't h and interacting with a TV using a touchscreen is not consistent with the 10 foot environment. For these reasons, users interact with Android-powered TVs using a remote. In consideration of this, ensure that every control in your app can be accessed with the D-pad. Refer back to the previous two lessons -<a href="{@docRoot}training/tv/optimizing-layouts-tv">Optimizing Layouts for TV</a> and -<a href="{@docRoot}training/tv/optimizing-navigation-tv">Optimize Navigation for TV</a> for more details +<a href="{@docRoot}training/tv/optimizing-layouts-tv.html">Optimizing Layouts for TV</a> and +<a href="{@docRoot}training/tv/optimizing-navigation-tv.html">Optimize Navigation for TV</a> for +more details on this topic. The Android system assumes that a device has a touchscreen, so if you want your application to run on a TV, you must <strong>explicitly</strong> disable the touchscreen requirement in your manifest file: <pre> |