summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/2_Architecture_Guides/1_Introduction/0_Overview.md2
-rw-r--r--docs/2_Architecture_Guides/1_Introduction/images/architecture.jpg (renamed from docs/2_Architecture_Guides/1_Introduction/architecture.jpg)bin687441 -> 687441 bytes
-rw-r--r--docs/3_Developer_Guides/1_Application_Framework/0_Introduction.md8
-rw-r--r--docs/3_Developer_Guides/1_Application_Framework/1_afm-daemons.md2
-rw-r--r--docs/3_Developer_Guides/1_Application_Framework/images/AppFW-APP_install_sequences.svg (renamed from docs/3_Developer_Guides/1_Application_Framework/pictures/AppFW-APP_install_sequences.svg)0
-rw-r--r--docs/3_Developer_Guides/1_Application_Framework/images/Security_model_history.svg (renamed from docs/3_Developer_Guides/1_Application_Framework/pictures/Security_model_history.svg)0
-rw-r--r--docs/3_Developer_Guides/1_Application_Framework/images/afm-daemons.svg (renamed from docs/3_Developer_Guides/1_Application_Framework/pictures/afm-daemons.svg)0
-rw-r--r--docs/3_Developer_Guides/1_Application_Framework/images/make-units.svg (renamed from docs/3_Developer_Guides/1_Application_Framework/pictures/make-units.svg)0
-rw-r--r--docs/3_Developer_Guides/2_Application_Framework_Binder/0_Overview.md4
-rw-r--r--docs/3_Developer_Guides/2_Application_Framework_Binder/4_Binder_events_guide.md2
-rw-r--r--docs/3_Developer_Guides/2_Application_Framework_Binder/images/basis.svg (renamed from docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/basis.svg)0
-rw-r--r--docs/3_Developer_Guides/2_Application_Framework_Binder/images/interconnection.svg (renamed from docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/interconnection.svg)0
-rw-r--r--docs/3_Developer_Guides/2_Application_Framework_Binder/images/signaling-basis.svg (renamed from docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/signaling-basis.svg)0
13 files changed, 9 insertions, 9 deletions
diff --git a/docs/2_Architecture_Guides/1_Introduction/0_Overview.md b/docs/2_Architecture_Guides/1_Introduction/0_Overview.md
index f2351bc..0648aa9 100644
--- a/docs/2_Architecture_Guides/1_Introduction/0_Overview.md
+++ b/docs/2_Architecture_Guides/1_Introduction/0_Overview.md
@@ -44,7 +44,7 @@ The Automotive Grade Linux Software Architecture diagram is below. The architect
of five layers. The App/HMI layer contains applications with their associated business logic and
HMI.
-![Architecture Diagram](architecture.jpg)
+![Architecture Diagram](images/architecture.jpg)
The Application Framework layer provides the APIs for creating both managing and running
applications on an AGL system. The Services layer contains user space services that all
diff --git a/docs/2_Architecture_Guides/1_Introduction/architecture.jpg b/docs/2_Architecture_Guides/1_Introduction/images/architecture.jpg
index e83cbc4..e83cbc4 100644
--- a/docs/2_Architecture_Guides/1_Introduction/architecture.jpg
+++ b/docs/2_Architecture_Guides/1_Introduction/images/architecture.jpg
Binary files differ
diff --git a/docs/3_Developer_Guides/1_Application_Framework/0_Introduction.md b/docs/3_Developer_Guides/1_Application_Framework/0_Introduction.md
index 7aae18f..efc31ee 100644
--- a/docs/3_Developer_Guides/1_Application_Framework/0_Introduction.md
+++ b/docs/3_Developer_Guides/1_Application_Framework/0_Introduction.md
@@ -61,7 +61,7 @@ The 3 layers are providing components for:
The figure below shows the history of these layers.
-![Security_model_history](./pictures/Security_model_history.svg)
+![Security_model_history](./images/Security_model_history.svg)
We took the decision to use these security layers that provide the
basis of the Tizen security, the security framework.
@@ -96,7 +96,7 @@ The figure below shows the major components of the framework
and their interactions going through the following scenario:
- APPLICATION installs an other application and then launch it.
- ![AppFW-APP_install_sequences](./pictures/AppFW-APP_install_sequences.svg)
+ ![AppFW-APP_install_sequences](./images/AppFW-APP_install_sequences.svg)
Let follow the sequence of calls:
@@ -257,5 +257,5 @@ future to include for example incremental delivery.
[app-manifest]: http://www.w3.org/TR/appmanifest "Web App Manifest"
[tizen-security]: https://wiki.tizen.org/wiki/Security "Tizen security home page"
[tizen-secu-3]: https://wiki.tizen.org/wiki/Security/Tizen_3.X_Overview "Tizen 3 security overview"
-[AppFW-APP_install_sequences]: pictures/AppFW-APP_install_sequences.svg
-[Security_model_history]: pictures/Security_model_history.svg \ No newline at end of file
+[AppFW-APP_install_sequences]: images/AppFW-APP_install_sequences.svg
+[Security_model_history]: images/Security_model_history.svg \ No newline at end of file
diff --git a/docs/3_Developer_Guides/1_Application_Framework/1_afm-daemons.md b/docs/3_Developer_Guides/1_Application_Framework/1_afm-daemons.md
index 2f7e2c0..b8eb21b 100644
--- a/docs/3_Developer_Guides/1_Application_Framework/1_afm-daemons.md
+++ b/docs/3_Developer_Guides/1_Application_Framework/1_afm-daemons.md
@@ -646,4 +646,4 @@ Here is how to list applications using ***afm-util***:
afm-util runnables
```
-[afm-daemons]: pictures/afm-daemons.svg
+[afm-daemons]: images/afm-daemons.svg
diff --git a/docs/3_Developer_Guides/1_Application_Framework/pictures/AppFW-APP_install_sequences.svg b/docs/3_Developer_Guides/1_Application_Framework/images/AppFW-APP_install_sequences.svg
index fab8399..fab8399 100644
--- a/docs/3_Developer_Guides/1_Application_Framework/pictures/AppFW-APP_install_sequences.svg
+++ b/docs/3_Developer_Guides/1_Application_Framework/images/AppFW-APP_install_sequences.svg
diff --git a/docs/3_Developer_Guides/1_Application_Framework/pictures/Security_model_history.svg b/docs/3_Developer_Guides/1_Application_Framework/images/Security_model_history.svg
index 7935437..7935437 100644
--- a/docs/3_Developer_Guides/1_Application_Framework/pictures/Security_model_history.svg
+++ b/docs/3_Developer_Guides/1_Application_Framework/images/Security_model_history.svg
diff --git a/docs/3_Developer_Guides/1_Application_Framework/pictures/afm-daemons.svg b/docs/3_Developer_Guides/1_Application_Framework/images/afm-daemons.svg
index 02b2c92..02b2c92 100644
--- a/docs/3_Developer_Guides/1_Application_Framework/pictures/afm-daemons.svg
+++ b/docs/3_Developer_Guides/1_Application_Framework/images/afm-daemons.svg
diff --git a/docs/3_Developer_Guides/1_Application_Framework/pictures/make-units.svg b/docs/3_Developer_Guides/1_Application_Framework/images/make-units.svg
index d52a8c7..d52a8c7 100644
--- a/docs/3_Developer_Guides/1_Application_Framework/pictures/make-units.svg
+++ b/docs/3_Developer_Guides/1_Application_Framework/images/make-units.svg
diff --git a/docs/3_Developer_Guides/2_Application_Framework_Binder/0_Overview.md b/docs/3_Developer_Guides/2_Application_Framework_Binder/0_Overview.md
index 1b2163c..22a88ba 100644
--- a/docs/3_Developer_Guides/2_Application_Framework_Binder/0_Overview.md
+++ b/docs/3_Developer_Guides/2_Application_Framework_Binder/0_Overview.md
@@ -26,7 +26,7 @@ is tuned by the AGL framework and the AGL system.
The following figure shows main concepts linked to the ***binder***.
-![Figure: binder basis](pictures/basis.svg)
+![Figure: binder basis](images/basis.svg)
The shown elements are:
@@ -79,7 +79,7 @@ to setup the ***bindings*** configuration of the ***binders***.
The figure below shows that ***binders*** are interconnected.
-![Figure: binder interconnection](pictures/interconnection.svg)
+![Figure: binder interconnection](images/interconnection.svg)
The figure shows 4 several **application/service**: **A**, **B**,
**C** and **D**.
diff --git a/docs/3_Developer_Guides/2_Application_Framework_Binder/4_Binder_events_guide.md b/docs/3_Developer_Guides/2_Application_Framework_Binder/4_Binder_events_guide.md
index 0b91a23..57175a6 100644
--- a/docs/3_Developer_Guides/2_Application_Framework_Binder/4_Binder_events_guide.md
+++ b/docs/3_Developer_Guides/2_Application_Framework_Binder/4_Binder_events_guide.md
@@ -20,7 +20,7 @@ Events must be described and explained.
The basis of a signaling agent is shown in the following figure:
-![scenario of using events](pictures/signaling-basis.svg)
+![scenario of using events](images/signaling-basis.svg)
This figure shows the main role of the signaling framework for the events
propagation.
diff --git a/docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/basis.svg b/docs/3_Developer_Guides/2_Application_Framework_Binder/images/basis.svg
index 0d42d76..0d42d76 100644
--- a/docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/basis.svg
+++ b/docs/3_Developer_Guides/2_Application_Framework_Binder/images/basis.svg
diff --git a/docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/interconnection.svg b/docs/3_Developer_Guides/2_Application_Framework_Binder/images/interconnection.svg
index 4a10217..4a10217 100644
--- a/docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/interconnection.svg
+++ b/docs/3_Developer_Guides/2_Application_Framework_Binder/images/interconnection.svg
diff --git a/docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/signaling-basis.svg b/docs/3_Developer_Guides/2_Application_Framework_Binder/images/signaling-basis.svg
index b13fcf1..b13fcf1 100644
--- a/docs/3_Developer_Guides/2_Application_Framework_Binder/pictures/signaling-basis.svg
+++ b/docs/3_Developer_Guides/2_Application_Framework_Binder/images/signaling-basis.svg