am bdb1cf0c: Merge "docs: Add links to Wear UI training from Design pages." into lmp-dev

* commit 'bdb1cf0c1bed1ae32d98c1efb269b87c9797182d':
  docs: Add links to Wear UI training from Design pages.
This commit is contained in:
Ricardo Cervera
2014-10-31 15:21:32 +00:00
committed by Android Git Automerger
4 changed files with 45 additions and 7 deletions

View File

@@ -76,6 +76,13 @@ page.title=UI Patterns for Android Wear
<li>The cue card can be invoked to continue specifying the action. For example in a messaging application, tapping a “Reply” action button invokes the Cue Card and prompts for voice input. In this case the prompt label (such as “Speak your message…”) and a set of sample voice suggestions can be specified by developers.</li> <li>The cue card can be invoked to continue specifying the action. For example in a messaging application, tapping a “Reply” action button invokes the Cue Card and prompts for voice input. In this case the prompt label (such as “Speak your message…”) and a set of sample voice suggestions can be specified by developers.</li>
</ol> </ol>
<a class="notice-developers left" href="{@docRoot}training/wearables/ui/confirm.html">
<div>
<h3>Developer Docs</h3>
<p>Showing Confirmations</p>
</div>
</a>
<h2 id="Continuing" style="clear:both">Continuing activities on phone</h2> <h2 id="Continuing" style="clear:both">Continuing activities on phone</h2>
@@ -100,6 +107,13 @@ page.title=UI Patterns for Android Wear
<p>Good examples of using an action on card include: play and pause music, toggle light switch on and off, navigate to an address, and call a phone number.</p> <p>Good examples of using an action on card include: play and pause music, toggle light switch on and off, navigate to an address, and call a phone number.</p>
<a class="notice-developers left" href="{@docRoot}training/wearables/ui/cards.html">
<div>
<h3>Developer Docs</h3>
<p>Creating Cards</p>
</div>
</a>
<h2 id="Stacks" style="clear:both">Card stacks</h2> <h2 id="Stacks" style="clear:both">Card stacks</h2>
<img src="{@docRoot}design/media/wear/expandable_stacks.png" width="147" height="147" style="float:right;margin:0 0 20px 40px"> <img src="{@docRoot}design/media/wear/expandable_stacks.png" width="147" height="147" style="float:right;margin:0 0 20px 40px">
@@ -124,6 +138,13 @@ to check-in to.</p>
<p>More information about how to use the 2D Picker pattern is provided in the <a href="{@docRoot}design/wear/structure.html#2DPicker">App Structure</a> guide.</p> <p>More information about how to use the 2D Picker pattern is provided in the <a href="{@docRoot}design/wear/structure.html#2DPicker">App Structure</a> guide.</p>
<a class="notice-developers left" href="{@docRoot}training/wearables/ui/2d-picker.html">
<div>
<h3>Developer Docs</h3>
<p>Creating a 2D Picker</p>
</div>
</a>
<h2 id="Voice" style="clear:both">Voice commands</h2> <h2 id="Voice" style="clear:both">Voice commands</h2>
@@ -148,3 +169,10 @@ href="{@docRoot}training/wearables/apps/layouts.html#UiLibrary"><code>WearableLi
<p>Of course, it is possible for Android Wear apps to extend themselves beyond the familiarities of these patterns. For a deeper look at the options available, see the <a href="{@docRoot}design/wear/structure.html">App Structure</a> guide.</p> <p>Of course, it is possible for Android Wear apps to extend themselves beyond the familiarities of these patterns. For a deeper look at the options available, see the <a href="{@docRoot}design/wear/structure.html">App Structure</a> guide.</p>
<a class="notice-developers left" href="{@docRoot}training/wearables/ui/lists.html">
<div>
<h3>Developer Docs</h3>
<p>Creating Lists</p>
</div>
</a>

View File

@@ -84,12 +84,18 @@ margin: 0 10px 20px 20px;
<img src="{@docRoot}design/media/wear/1D_picker.png" alt="" width="499px" /> <img src="{@docRoot}design/media/wear/1D_picker.png" alt="" width="499px" />
<p class="img-caption">This pattern can be used to present a single vertical list, or a “1D Picker”</p> <p class="img-caption">This pattern can be used to present a single vertical list, or a “1D Picker”</p>
<img src="{@docRoot}design/media/wear/2D_picker.png" alt="" width:760px" /> <img src="{@docRoot}design/media/wear/2D_picker.png" alt="" width="760px" />
<p class="img-caption">It can also be used as a 2D matrix of options, as a way of presenting categorized options.</p> <p class="img-caption">It can also be used as a 2D matrix of options, as a way of presenting categorized options.</p>
<h3>Actions</h3> <h3>Actions</h3>
<a class="notice-developers" style="clear:none" href="{@docRoot}training/wearables/ui/2d-picker.html">
<div>
<h3>Developer Docs</h3>
<p>Creating a 2D Picker</p>
</div>
</a>
<p>For actions on each card, use the <a href="{@docRoot}design/wear/patterns.html#Actions">Action cards pattern</a>.</p> <p>For actions on each card, use the <a href="{@docRoot}design/wear/patterns.html#Actions">Action cards pattern</a>.</p>
<h3>Making it fast</h3> <h3>Making it fast</h3>
@@ -155,6 +161,6 @@ href="#2DPicker">2D picker</a> is always available.</p>
<h3>Manually exiting</h3> <h3>Manually exiting</h3>
<p>Even with logical exit points like these, some cases may exist where the user may want to immediately exit. This may be common in apps that are used for a longer while. In all cases, you should treat long-press as the user's intent to exit, using <p>Even with logical exit points like these, some cases may exist where the user may want to immediately exit. This may be common in apps that are used for a longer while. In all cases, you should treat long-press as the user's intent to exit, using
<a href="{@docRoot}training/wearables/apps/layouts.html#UiLibrary"><code>DismissOverlayView</code></a>.</p> <a href="{@docRoot}training/wearables/ui/exit.html"><code>DismissOverlayView</code></a>.</p>

View File

@@ -90,9 +90,10 @@ PendingIntent notificationPendingIntent = PendingIntent.getActivity(this, 0, not
</ol> </ol>
<h2 id="UiLibrary">Create Layouts with the Wearable UI Library</h2> <h2 id="UiLibrary">Create Layouts with the Wearable UI Library</h2>
<p> <p>
There's an unofficial UI library that is automatically included when you create your wearable The Wearable UI Library is automatically included when you create your wearable
app with the Android Studio Project Wizard. You can also add the library to your <code>build.gradle</code> app with the Android Studio Project Wizard. You can also add this library to your <code>build.gradle</code>
file with the following dependency declaration: file with the following dependency declaration:
</p>
<pre> <pre>
dependencies { dependencies {
@@ -101,8 +102,11 @@ dependencies {
compile 'com.google.android.gms:play-services-wearable:+' compile 'com.google.android.gms:play-services-wearable:+'
} }
</pre> </pre>
This library helps you build UIs that are designed for wearables. Here are some of the major classes:
</p> <p>This library helps you build UIs that are designed for wearables. For more information, see
<a href="{@docRoot}training/wearables/ui/index.html">Creating Custom UIs for Wear Devices</a>.</p>
<p>Here are some of the major classes in the Wearable UI Library:</p>
<ul> <ul>
<li><code>BoxInsetLayout</code> - A FrameLayout that's aware of screen shape and can box its <li><code>BoxInsetLayout</code> - A FrameLayout that's aware of screen shape and can box its

View File

@@ -8,7 +8,7 @@ page.title=Sending and Syncing Data
<h2>Dependencies and prerequisites</h2> <h2>Dependencies and prerequisites</h2>
<ul> <ul>
<li>Android 4.3 (API Level 18) or higher on the handset device</li> <li>Android 4.3 (API Level 18) or higher on the handset device</li>
<li>The latest version of <a href="{@docRoot}google/play">Google Play services</a></li> <li>The latest version of <a href="{@docRoot}google/play-services/index.html">Google Play services</a></li>
<li>An Android Wear device or Wear AVD</li> <li>An Android Wear device or Wear AVD</li>
</ul> </ul>
</div> </div>