talk + rework homepage

onelab.html

@@ -85,33 +85,29 @@ or not) can be easily interfaced as well.
 
 <p>
   ONELAB can interface finite element and related software (<em>ONELAB
-    clients</em>) in two ways:
+    clients</em>) in several ways:
 </p>
 <ol>
-  <li>By directly embedding the ONELAB C++ library or the ONELAB Python
-    module. This is what <a href="https://getdp.info">GetDP</a> (a finite element
-    solver for electromagnetism, heat transfer, acoustics and generic
-    PDEs), <a href="https://gmsh.info">Gmsh</a> (a mesh generator with built-in
-    CAD engine and post-processor) and the ONELAB mobile app do. Any C++ and
-    Python code can do the same.
-  <li>By preprocessing the input files of any software. The different steps of a
-    simulation (meshing, solving, post-processing) are then controlled by a
-    python script, which dynamically regenerates the input
-    files. <a href="https://www.csc.fi/web/elmer">Elmer</a>,
+  <li>By using the ONELAB C++ library or the ONELAB Python module to communicate
+    with the Gmsh ONELAB server over TCP/IP or Unix sockets. This is what is
+    done by <a href="https://getdp.info">GetDP</a>; any C++ and Python code can
+    do the same with minimal code modifications.
+  <li>By using the Gmsh API in C++, C, Python or Julia to comunicate with the
+    ONELAB server over TCP/IP or Unix sockets, or directly in-memory. This
+    allows complete flexibility over how the client interacts with ONELAB
+    (e.g. by pre-processing its input files) and has been successfully used with
+    e.g.  <a href="https://www.csc.fi/web/elmer">Elmer</a>,
     <a href="https://www.openfoam.com/">OpenFOAM</a>,
     <a href="https://www.code-aster.org/">Code_Aster</a>,
     <a href="https://www.3ds.com/fr/produits-et-services/simulia/produits/abaqus">Abaqus</a>
-    or <a href="http://www.calculix.de">CalculiX</a> can for example be readily
-    interfaced this way.
+    <a href="http://www.calculix.de">CalculiX</a>,
+    <a href="https://www.uee.uliege.be/cms/c_6331644/fr/uee-safir">Safir</a>, ...
 </ol>
 <p>
-  The ONELAB interface allows to call such clients and have them share
-  parameters and modeling information.  The implementation is based on a
-  client-server model, with a server-side database, an (optional) graphical
-  front-end, and local or remote clients communicating in-memory or through
-  TCP/IP sockets. Contrary to most solver interfaces, the ONELAB
-  server has no <em>a priori</em> knowledge about any specifics (input file
-  format, syntax, ...) of the clients. This is made possible by having any
+  The ONELAB interface allows to interact with clients and have them share
+  parameters and modeling information.  Contrary to most solver interfaces, the
+  ONELAB server has no <em>a priori</em> knowledge about any specifics (input
+  file format, syntax, ...) of the clients. This is made possible by having any
   simulation preceded by an analysis phase, during which the clients are asked
   to upload their parameter set to the server. The issues of completeness and
   consistency of the parameter sets are completely dealt with on the client
@@ -119,8 +115,10 @@ or not) can be easily interfaced as well.
   re-dispatching.
 </p>
 <p>
-  See the <a href="https://gitlab.onelab.info/doc/tutorials/wikis">tutorials</a>
-  for examples.
+  See this <a href="slides/onelab.pdf">general presentation</a> for more
+  information and
+  the <a href="https://gitlab.onelab.info/doc/tutorials/wikis">tutorials</a> for
+  examples.
 </p>
 
 <h2>Sponsors</h2>