5cdadb48d0
* revise to the Compatibility doc, put it in Intro * put Permissions in Intro * put App Fundamentals in Intro * move Manifest docs to the top of side nav tree * move App Resources above UI Will perform another fix to the Best Practices section later to deprecate some docs there and point to Training instead Change-Id: I88a8f94167ba15e97eb3bbbc08fd82dd82498e4b
57 lines
2.7 KiB
Plaintext
57 lines
2.7 KiB
Plaintext
page.title=App Components
|
||
page.landing=true
|
||
page.landing.intro=Android's application framework lets you create rich and innovative apps using a set of reusable components. This section explains how you can build the components that define the building blocks of your app and how to connect them together using intents.
|
||
page.landing.image=images/develop/app_components.png
|
||
|
||
@jd:body
|
||
|
||
<div class="landing-docs">
|
||
|
||
<div class="col-6">
|
||
<h3>Blog Articles</h3>
|
||
|
||
<a href="http://android-developers.blogspot.com/2012/05/using-dialogfragments.html">
|
||
<h4>Using DialogFragments</h4>
|
||
<p>In this post, I’ll show how to use DialogFragments with the v4 support library (for backward compatibility on pre-Honeycomb devices) to show a simple edit dialog and return a result to the calling Activity using an interface.</p>
|
||
</a>
|
||
|
||
<a href="http://android-developers.blogspot.com/2011/03/fragments-for-all.html">
|
||
<h4>Fragments For All</h4>
|
||
<p>Today we’ve released a static library that exposes the same Fragments API (as well as the new LoaderManager and a few other classes) so that applications compatible with Android 1.6 or later can use fragments to create tablet-compatible user interfaces. </p>
|
||
</a>
|
||
|
||
<a
|
||
href="http://android-developers.blogspot.com/2010/07/multithreading-for-performance.html">
|
||
<h4>Multithreading for Performance</h4>
|
||
<p>A good practice in creating responsive applications is to make sure your main UI thread
|
||
does the minimum amount of work. Any potentially long task that may hang your application should be
|
||
handled in a different thread.</p>
|
||
</a>
|
||
</div>
|
||
|
||
<div class="col-6">
|
||
<h3>Training</h3>
|
||
|
||
<a href="http://developer.android.com/training/basics/activity-lifecycle/index.html">
|
||
<h4>Managing the Activity Lifecycle</h4>
|
||
<p>This class explains important lifecycle callback methods that each Activity
|
||
instance receives and how you can use them so your activity does what the user expects and does not consume system
|
||
resources when your activity doesn't need them.</p>
|
||
</a>
|
||
|
||
<a href="http://developer.android.com/training/basics/fragments/index.html">
|
||
<h4>Building a Dynamic UI with Fragments</h4>
|
||
<p>This class shows you how to create a dynamic user experience with fragments and optimize
|
||
your app's user experience for devices with different screen sizes, all while continuing to support
|
||
devices running versions as old as Android 1.6.</p>
|
||
</a>
|
||
|
||
<a href="http://developer.android.com/training/sharing/index.html">
|
||
<h4>Sharing Content</h4>
|
||
<p>This class covers some common ways you can send and receive content between
|
||
applications using Intent APIs and the ActionProvider object.</p>
|
||
</a>
|
||
</div>
|
||
|
||
</div>
|