The AndroidManifest.xml File - ìëë¡ì´ë 기ì 커뮤ëí° : Korea ...
The AndroidManifest.xml File - ìëë¡ì´ë 기ì 커뮤ëí° : Korea ...
The AndroidManifest.xml File - ìëë¡ì´ë 기ì 커뮤ëí° : Korea ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
AIDL (Android Interface Definition Language)<br />
Implementing IPC Using AIDL : Creating an .aidl <strong>File</strong><br />
AIDL is a simple syntax that lets you declare an interface with one or more methods, that can<br />
take parameters and return values. <strong>The</strong>se parameters and return values can be of any type,<br />
even other AIDL-generated interfaces. However, it is important to note that you must import all<br />
non-built-in in types, even if they are defined in the same package as your interface. Here are the<br />
data types that AIDL can support:<br />
• Primitive Java programming language types (int, boolean, etc) - No import statement is needed.<br />
• One of the following classes (no import statements needed):<br />
• String<br />
• List - All elements in the List must be one of the types in this list, including other AIDL-generated<br />
interfaces and parcelables. List may optionally be used as a "generic" class (e.g. List). <strong>The</strong><br />
actual concrete class that the other side will receive will always be an ArrayList, although the method will<br />
be generated to use the List interface.<br />
• Map - All elements in the Map must be of one of the types in this list, including other AIDL-generated<br />
interfaces and parcelables. Generic maps, (e.g. of the form Map are not supported. <strong>The</strong><br />
actual concrete class that the other side will receive will always be a HashMap, although the method will<br />
be generated to use the Map interface.<br />
• CharSequence - This is useful for the CharSequence types used by TextView and other widget objects.<br />
• Other AIDL-generated interfaces, which are always passed by reference. An import statement<br />
is always needed for these.<br />
• Custom classes that implement the Parcelable protocol and are passed by value. An import<br />
statement t t is always needed d for these.<br />
<strong>Korea</strong> Android Community- www.kandroid.org<br />
9