X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/60723cc9062e7d1ef8216d1e85d90892603e0df6..e2e8fe5601125b3c81e3eb51b5cea86ad51fbb66:/docs/source/application.rst

diff --git a/docs/source/application.rst b/docs/source/application.rst
index 3898c38b7d..4e46704a50 100644
--- a/docs/source/application.rst
+++ b/docs/source/application.rst
@@ -5,7 +5,7 @@ Describing your Application
 
 .. raw:: html
 
-   <object id="TOC" data="graphical-toc.svg" width="100%" type="image/svg+xml"></object>
+   <object id="TOC" data="graphical-toc.svg" type="image/svg+xml"></object>
    <script>
    window.onload=function() { // Wait for the SVG to be loaded before changing it
      var elem=document.querySelector("#TOC").contentDocument.getElementById("ApplicationBox")
@@ -16,17 +16,49 @@ Describing your Application
    <br/>
 
 Every SimGrid simulation entails a distributed application, that
-virtually executes on the simulated platform. This application can
-be either an existing MPI program (if you use the SMPI interface), or
-a program specifically written to execute within SimGrid, using one of
-the dedicated APIs.
+virtually executes on the simulated platform. You can express this
+application using one of the following interfaces. It is even possible
+to mix several interfaces in the same simulation.
 
+ - :ref:`Describing Algorithms with the S4U interface <S4U_doc>` (in C++ or Python)
+ - :ref:`Simulating existing MPI programs with the SMPI toolsuite <SMPI_doc>`
+   (in C, C++, or Fortran)
+ - In some cases, you may want to replay an execution trace in the simulator. This
+   trace lists the events of your application or of your workload, and
+   your application is decomposed as a list of event handlers that are
+   fired according to the trace. SimGrid comes with a built-in support
+   for MPI traces (with solutions to import traces captured by several
+   MPI profilers). You can reuse this mechanism for any kind of trace
+   that you want to replay, for example to study how a P2P DHT overlay
+   reacts to a given workload.
+ - Simulating algorithms with one of the legacy interfaces: :ref:`MSG
+   for distributed algorithms <MSG_doc>` (in :ref:`C <MSG_doc>` or
+   :ref:`Java <Java_doc>`) and SimDAG for
+   centralized algorithms (in C). SimGrid was founded in 1998, and
+   many interfaces were proposed along the way. MSG (introduced
+   around 2002) and SimDag (introduced before 2000), are still present
+   in SimGrid. They do not evolve anymore, but given their popularity,
+   they will not be removed until at least 2020. That being said, our
+   goal is to make S4U so useful that these legacy APIs become useless
+   and obsolete.
+ - We are currently working on the ability to modify any existing
+   application so that it can run on top of SimGrid. This project,
+   called `Remote-SimGrid
+   <https://framagit.org/simgrid/remote-simgrid>`_, is somewhat
+   experimental but should be already usable.
 
-.. include:: app_smpi.rst
+As you can see, SimGrid is very modular and can be used in many
+ways. We are working to improve it along two main directions. First,
+we plan to further increase the modularity of the simulator so that
+users can invent the specific API or DSL they need for their usage. We
+call this project BYOS: Build Your Own Simulator.
 
-.. include:: app_legacy.rst
+Executing existing applications within the simulator is another
+long-term goal. SMPI and Remote-SimGrid already allow you to execute some
+applications, but our long term goal would be to allow for the execution
+of any legacy application, with absolutely no modification. We call it
+SimOS, even if it will not become usable before several years of
+additional work.
 
-.. toctree::
-   :hidden:
-
-      The S4U Interface <app_s4u.rst>
+.. The old documentation of the obsolete MSG replay module was removed in
+..  https://github.com/simgrid/simgrid/commit/e05361c201fb95d2b7605e59001cd0a49a489739