integrate bg of rasta in bg section
All checks were successful
/ test_checkout (push) Successful in 1m15s
All checks were successful
/ test_checkout (push) Successful in 1m15s
This commit is contained in:
parent
94d26973d3
commit
5e512b585a
11 changed files with 170 additions and 107 deletions
|
@ -40,7 +40,21 @@ When used directly by ART, the classes are usually stored in an application file
|
|||
#image(
|
||||
"figs/classloaders-crop.svg",
|
||||
width: 80%,
|
||||
alt: ""
|
||||
alt: "
|
||||
A box diagram. The diagram is split into two; the right section is labeled Runtime.
|
||||
On the left, there are 9 boxes. 3 are gray, labeled ClassLoader, SecureClassLoader, and URLClassLoader, and the other 6 are white: BootClassLoader, BaseDexClassLoader, DexClassLoader, InMemoryDexClassLoader, PathClassLoader, and DelegateLastClassLoader.
|
||||
Arrows go from SecureClassLoader, BaseDexClassLoader, and BootClassLoader to ClassLoader,
|
||||
from URLClassLoader to SecureClassLoader,
|
||||
from DexClassLoader, InMemoryDexClassLoader, and PathClassLoader to BaseDexClassLoader,
|
||||
and from DelegateLastClassLoader to PathClassLoader.
|
||||
|
||||
On the runtime side, there are 5 boxes: bootClassLoader, appClassLoader (multi dex), systemClassLoader,
|
||||
Specific delegator with two delegates, X.
|
||||
Arrows labeled delegate go from appClassLoader, systemClassLoader, and Specific delegator to bootClassLoader, and from Specific delegator to X.
|
||||
bootClassLoader, appClassLoader, and systemClassLoader are grouped in a dotted box labeled Android default behavior.
|
||||
Dotted lines labeled instance go across the central demarcation from appClassLoader to PathClassLoader, from systemClassLoader to PathClassLoader, and from Specific delegator to DelegateLastClassLoader.
|
||||
Another dotted line labeled instance singleton goes from bootClassLoader to BootClassLoader.
|
||||
"
|
||||
)
|
||||
gray -- Java-based, white -- Android-based
|
||||
],
|
||||
|
@ -115,7 +129,19 @@ We discuss in the next section how to obtain these classes from the emulator.
|
|||
image(
|
||||
"figs/architecture_SDK-crop.svg",
|
||||
width: 80%,
|
||||
alt: ""
|
||||
alt: "
|
||||
On the top right, a diagram of a web browser open at https//develoer.android.com, with the webpage reading: API documentation, SDK classes, and method descriptions.
|
||||
The web browser is labelled Documentation.
|
||||
On the bottom right, a box with the Android Studio logo (a blue pair of compasses in front of a green robot) is labeled 'Development Environment'.
|
||||
It contains two boxes: Developer classes and android.jar, and the text Dev SDK classes in bold.
|
||||
An arrow labeled API access goes from Developer classes to android.jar.
|
||||
On the left, a diagram of a smartphone with the Android logo (a green robot) contains two boxes: Platform classes and APK files.
|
||||
Platform classes contain the text 'boot.art: framework.jar + 24 .jar = Android SDK classes + Hidden classes'.
|
||||
APK file is split in two, in the top part: Developer classes + some extra classes, and on the bottom part: Multi DEX.
|
||||
An arrow labeled API access goes from APK file to Platform classes.
|
||||
Another arrow goes from Developer environment to APK file.
|
||||
|
||||
"
|
||||
),
|
||||
caption: [Location of SDK classes during development and at runtime]
|
||||
) <fig:cl-archisdk>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue