Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 3354f4dc authored by Scott Main's avatar Scott Main Committed by Android Git Automerger
Browse files

am 369c1c1f: cherrypick Change-Id: I52bc4e2d34015e6e30887590f920b580a034180e... 

am 369c1c1f: cherrypick Change-Id: I52bc4e2d34015e6e30887590f920b580a034180e docs: anchor link fixes

* commit '369c1c1f':
  cherrypick Change-Id: I52bc4e2d34015e6e30887590f920b580a034180e docs: anchor link fixes
parents 3c585db2 369c1c1f

docs/html/guide/developing/eclipse-adt.jd

+3 −3
Original line number Diff line number Diff line
@@ -13,7 +13,7 @@ page.title=Developing In Eclipse, with ADT 
        <li><a href="#RunningOnDevice">Running on a device</a></li>

      </ol>

    </li>

    <li><a href="#RunConfig">Creating a Custom Run Configuration</a></li>

    <li><a href="#RunConfig">Creating a Run Configuration</a></li>

    <li><a href="#Signing">Setting Up Application Signing</a></li>

    <li><a href="#libraryProject">Working with Library Projects</a>

      <ol>
@@ -222,7 +222,7 @@ debugger is attached, Eclipse will open the Debug perspective.</p> 


<p>To set or change the launch configuration used for your project, use the launch configuration

manager.

See <a href="#launchconfig">Creating a Launch Configuration</a> for information.</p>

See <a href="#RunConfig">Creating a Run Configuration</a> for information.</p>



<p>Be certain to create multiple AVDs upon which to test your application. You should have one AVD

for each platform and screen type with which your application is compatible. For
@@ -296,7 +296,7 @@ configuration</em> 
  <li>Adjust your desired launch configuration settings.

    <p>In the Target tab, consider whether you'd like to use Manual or Automatic mode

    when selecting an AVD to run your application.

    See the following section on <a href=#AutoAndManualModes">Automatic and manual target 

    See the following section on <a href="#AutoAndManualTargetModes">Automatic and manual target 

    modes</a>).</p>

    <p>You can specify any emulator options to the Additional Emulator Command

    Line Options field. For example, you could add <code>-scale 96dpi</code> to

docs/html/guide/developing/other-ide.jd

+1 −1
Original line number Diff line number Diff line
@@ -804,7 +804,7 @@ href="{@docRoot}guide/topics/manifest/manifest-intro.html">AndroidManifest.xml</ 


<p>To build an application project that depends on one or more library projects,

you can use the standard Ant build commands and compile modes, as described in

<a href=#Building">Building Your Application</a>, earlier in this document. The

<a href="#Building">Building Your Application</a>, earlier in this document. The

tools compile and merge all libraries referenced by the application as part

of compiling the dependent application project. No additional commands or steps

are necessary. </p>

docs/html/guide/developing/testing/testing_eclipse.jd

+5 −9
Original line number Diff line number Diff line
@@ -505,15 +505,14 @@ page.title=Testing In Eclipse, with ADT 
    pane and moves the focus to the first line of the test method.

</p>

<p>

    The results of a successful test are shown in

    <a href="#TestResults">Figure 1. Messages for a successful test</a>:

    The results of a successful test are shown in figure 1.

</p>

<a href="{@docRoot}images/testing/eclipse_test_results.png">

    <img src="{@docRoot}images/testing/eclipse_test_results.png"

         alt="Messages for a successful test" height="327px" id="TestResults"/>

</a>

<p class="img-caption">

    <strong>Figure 1.</strong> Messages for a successful test

    <strong>Figure 1.</strong> Messages for a successful test.

</p>

<p>

    The lower pane is for stack traces. If you highlight a failed test in the upper pane, the
@@ -521,14 +520,11 @@ page.title=Testing In Eclipse, with ADT 
    test code, you can double-click it to display the code in an editor view pane, with the

    line highlighted. For a successful test, the lower pane is empty.

</p>

<p>

    The results of a failed test are shown in

    <a href="#FailedTestResults">Figure 2. Messages for a test failure</a>

</p>

<p>The results of a failed test are shown in figure 2.</p>

<a href="{@docRoot}images/testing/eclipse_test_run_failure.png">

    <img src="{@docRoot}images/testing/eclipse_test_run_failure.png"

         alt="Messages for a test failure" height="372px" id="TestRun"/>

         alt="" height="372px" id="TestRun"/>

</a>

<p class="img-caption">

    <strong>Figure 2.</strong> Messages for a test failure

    <strong>Figure 2.</strong> Messages for a test failure.

</p>

docs/html/guide/practices/screens_support.jd

+1 −1
Original line number Diff line number Diff line
@@ -214,7 +214,7 @@ screen.</p> 
<p class="table-caption" id="screens-table"><strong>Table 1.</strong> Screen

sizes and densities of emulator skins included in the Android SDK.</p>



  <table id="screens-table">

  <table>

    <tbody>

    <tr>

      <td style="border:none"></td>

docs/html/guide/publishing/app-signing.jd

+1 −1
Original line number Diff line number Diff line
@@ -563,7 +563,7 @@ and align, as discussed above. Once the wizard has compiled and signed your pack 
it will also perfom package alignment with {@code zipalign}.

Because the Export Wizard uses both Keytool and Jarsigner, you should

ensure that they are accessible on your computer, as described above

in the <a href=#setup">Basic Setup for Signing</a>.</p>

in the <a href="#setup">Basic Setup for Signing</a>.</p>



<p>To create a signed and aligned .apk in Eclipse:</p>