am 6409e445: am 1c2056d6: am 98d4d719: am 2ed01adc: a few more crosslinks for design guide (to other design docs or dev docs)
* commit '6409e445':
a few more crosslinks for design guide (to other design docs or dev docs)
<p>For more discussion, see the <a href="{@docRoot}design/patterns/actionbar.html">Action Bar</a>
design guide.</p>
</div>
<div class="layout-content-col span-8">
@@ -164,6 +167,10 @@ in view at the same time.</p>
</div>
</div>
<p>For more discussion, see the <a href="{@docRoot}design/building-blocks/tabs.html">Tabs</a>
design guide.</p>
<h4>Allow cutting through hierarchies</h4>
<p>Take advantage of shortcuts that allow people to reach their goals quicker. To allow top-level
invocation of actions for a data item from within list or grid views, display prominent actions
@@ -183,6 +190,12 @@ are often good reasons to act on collections of data as well.</p>
delete multiple items in the category view. Analyze which detail view actions are applicable to
collections of items. Then use multi-select to allow application of those actions to multiple items
in a category view.</p>
<p>For more discussion, see the <a href="{@docRoot}design/patterns/selection.html">Selection</a>
design guide.</p>
<h2 id="details">Details</h2>
<p>The detail view allows you to view and act on your data. The layout of the detail view depends on the data type being displayed, and therefore differs widely among apps.</p>
@@ -239,6 +252,10 @@ to achieve this.</p>
thumbnail view control that lets people quickly jump to specific pages.
</div>
<p>For more discussion, see the <a href="{@docRoot}design/patterns/swipe-views.html">Swipe Views</a>
@@ -36,8 +36,21 @@ ensure that your app looks great on any device.</p>
<h4>Strategies</h4>
<p>So where do you begin when designing for multiple screens? One approach is to work in the base
standard (medium size, <acronym title="Medium density (160 dpi)">MDPI</acronym>) and scale it up or
standard (normal size and <acronym title="Medium density (160 dpi)">MDPI</acronym>) and scale it up or
down for the other buckets. Another approach is to start with the device with the largest screen
size, and then scale down and figure out the UI compromises you'll need to make on smaller screens.</p>
<p>For more detailed information on this topic, please visit <a href="http://developer.android.com/guide/practices/screens_support.html">Supporting Multiple
Screens</a>.</p>
<p>For details about designing layouts for larger screens, see the <a