Skip to content

Commit e40c463

Browse files
committed
docs: move AIDL doc under Services in api guides.
Change-Id: I525de97958e2093af15cce2b007ec022cb315a71
1 parent dbbfa70 commit e40c463

File tree

7 files changed

+10
-7
lines changed

7 files changed

+10
-7
lines changed

docs/html/guide/components/bound-services.jd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ can then extend within your service.</p>
170170
create a bound service, because it may require multithreading capabilities and
171171
can result in a more complicated implementation. As such, AIDL is not suitable for most applications
172172
and this document does not discuss how to use it for your service. If you're certain that you need
173-
to use AIDL directly, see the <a href="{@docRoot}tools/aidl.html">AIDL</a>
173+
to use AIDL directly, see the <a href="{@docRoot}guide/components/aidl.html">AIDL</a>
174174
document.</p>
175175

176176

@@ -341,7 +341,7 @@ service, which must then handle multi-threading.</p>
341341
<p>For most applications, the service doesn't need to perform multi-threading, so using a {@link
342342
android.os.Messenger} allows the service to handle one call at a time. If it's important
343343
that your service be multi-threaded, then you should use <a
344-
href="{@docRoot}tools/aidl.html">AIDL</a> to define your interface.</p>
344+
href="{@docRoot}guide/components/aidl.html">AIDL</a> to define your interface.</p>
345345
</div>
346346
</div>
347347

docs/html/guide/google/play/billing/billing_overview.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ messaging that takes place between your application and the Google Play applicat
154154
<p>Your application sends in-app billing requests by invoking a single IPC method
155155
(<code>sendBillingRequest()</code>), which is exposed by the <code>MarketBillingService</code>
156156
interface. This interface is defined in an <a
157-
href="{@docRoot}tools/aidl.html">Android Interface Definition Language</a> file
157+
href="{@docRoot}guide/components/aidl.html">Android Interface Definition Language</a> file
158158
(<code>IMarketBillingService.aidl</code>). You can <a
159159
href="{@docRoot}guide/google/play/billing/billing_integrate.html#billing-download">download</a> this AIDL
160160
file with the in-app billing sample application.</p>

docs/html/guide/guide_toc.cs

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,9 @@ localized titles are added in the language order specified below.
4141
<li><a href="<?cs var:toroot ?>guide/components/bound-services.html">
4242
<span class="en">Bound Services</span>
4343
</a></li>
44+
<li><a href="<?cs var:toroot ?>guide/components/aidl.html">
45+
<span class="en">AIDL</span>
46+
</a></li>
4447
</ul>
4548
</li>
4649
<li class="nav-section">

docs/html/intl/ja/guide/topics/fundamentals.jd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -526,7 +526,7 @@ RPC インターフェースに含めることができるのはメソッドの
526526
</p>
527527

528528
<p>
529-
このメカニズムを簡単に説明すると次のようになります。まず、シンプルなインターフェース定義言語(IDL)を使用して、実装したい RPC インターフェースを宣言します。<code><a href="{@docRoot}tools/aidl.html">aidl</a></code> ツールにより、RPC インターフェースの宣言から Java インターフェース定義が生成されます。この定義は、ローカルとリモートの両方のプロセスで使用する必要があります。定義には、次の図に示すように 2 つの内部クラスが含まれています:
529+
このメカニズムを簡単に説明すると次のようになります。まず、シンプルなインターフェース定義言語(IDL)を使用して、実装したい RPC インターフェースを宣言します。<code><a href="{@docRoot}guide/components/aidl.html">aidl</a></code> ツールにより、RPC インターフェースの宣言から Java インターフェース定義が生成されます。この定義は、ローカルとリモートの両方のプロセスで使用する必要があります。定義には、次の図に示すように 2 つの内部クラスが含まれています:
530530
</p>
531531

532532
<p style="margin-left: 2em">
@@ -560,7 +560,7 @@ onServiceDisconnected()}</code> メソッドが実装されているため、リ
560560
</ul>
561561

562562
<p>
563-
ここでは、説明を簡単にするため、RPC メカニズムの細かい点は省略しています。詳しくは、<a href="{@docRoot}tools/aidl.html">Designing a Remote Interface Using AIDL</a>、および {@link android.os.IBinder IBinder} クラスの説明をご覧ください。
563+
ここでは、説明を簡単にするため、RPC メカニズムの細かい点は省略しています。詳しくは、<a href="{@docRoot}guide/components/aidl.html">Designing a Remote Interface Using AIDL</a>、および {@link android.os.IBinder IBinder} クラスの説明をご覧ください。
564564
</p>
565565

566566

docs/html/sitemap.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ http://developer.android.com/tools/index.html
129129
http://developer.android.com/tools/aapt.html
130130
http://developer.android.com/tools/help/adb.html
131131
http://developer.android.com/tools/othertools.html
132-
http://developer.android.com/tools/aidl.html
132+
http://developer.android.com/guide/components/aidl.html
133133
http://developer.android.com/tools/avd.html
134134
http://developer.android.com/tools/bmgr.html
135135
http://developer.android.com/tools/ddms.html

docs/html/tools/help/index.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Android Debug Bridge is a versatile tool that lets you manage the state of an em
7474
Android-powered device. You can also use it to install an Android application (.apk) file on a
7575
device.</p>
7676

77-
<p>The other platform tools, such as <a href="{@docRoot}tools/aidl.html">aidl</a>,
77+
<p>The other platform tools, such as <a href="{@docRoot}guide/components/aidl.html">aidl</a>,
7878
<code>aapt</code>, <code>dexdump</code>, and <code>dx</code>, are typically called by the Android
7979
build tools or Android Development Tools (ADT), so you rarely need to invoke these tools directly.
8080
As a general rule, you should rely on the build tools or the ADT plugin to call them as needed.</p>

0 commit comments

Comments
 (0)