X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/e181444b5b07bc19821f91cfcc4cc118f6968b26..354e319e7ea5e2206df51a2e8f8b20caaff01240:/doc/doxygen/deployment.doc

diff --git a/doc/doxygen/deployment.doc b/doc/doxygen/deployment.doc
index b4d96cad94..20dd046db6 100644
--- a/doc/doxygen/deployment.doc
+++ b/doc/doxygen/deployment.doc
@@ -2,6 +2,17 @@
 
 @tableofcontents
 
+\htmlonly
+<div align="center">
+\endhtmlonly
+\htmlinclude graphical-toc.svg
+\htmlonly
+</div>
+<script>
+document.getElementById("Deployment").style="opacity:0.93999999;fill:#ff0000;fill-opacity:0.1;stroke:#000000;stroke-width:0.35277778;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1";
+</script>
+\endhtmlonly
+
 Once you've specified your @ref platform "virtual platform" and the
 @ref application "application" you want to study, you must describe
 the mapping of the application onto the platform. This page says how
@@ -13,7 +24,7 @@ a trace captured from a past applicative run, as briefly explained
 
 There is two ways to specify the mapping of your program onto virtual
 hosts: either directly from your program (with @ref MSG_process_create
-or as in @ref s4u_ex_basics "this S4U example"), or using an external
+or as in @ref s4u_ex_actors_start "this S4U example"), or using an external
 XML file.  You should really logically separate your application from
 the deployment, as it will ease your experimental campain afterward.
 How exactly you organize your work remains up to you.
@@ -21,8 +32,8 @@ How exactly you organize your work remains up to you.
 @section deploy_s4u Deployment with S4U
 
 The following example shows the several ways of doing so in the S4U
-interface: @ref examples/s4u/actor-create/s4u_actor-create.cpp.
-Associated XML file: @ref examples/s4u/actor-create/s4u_actor-create_d.xml
+interface: @ref examples/s4u/actor-create/s4u-actor-create.cpp.
+Associated XML file: @ref examples/s4u/actor-create/s4u-actor-create_d.xml
 
 @section deploy_msg Deployment with MSG