new static homepage

index.html

@@ -21,23 +21,23 @@
 <h1>Open Numerical Engineering LABoratory</h1>
 
 <div><span style="white-space:nowrap"><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Inductor"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/inductor/screenshot2_512.png"></a><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Magnetometer"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/magnetometer/screenshot1_512.png"></a><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Electric-machines"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/machines/screenshot2_512.png"></a><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Magnetodynamics-with-cohomology-conditions"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/indheat/screenshot1_512.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Inductor"><!--
+--><img width="25%" src="small_inductor.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Magnetometer"><!--
+--><img width="25%" src="small_magnetometer.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Electric-machines"><!--
+--><img width="25%" src="small_machines.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Magnetodynamics-with-cohomology-conditions"><!--
+--><img width="25%" src="small_indheat.png"></a><!--
 --></span><br><span style="white-space:nowrap"><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Waveguides"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/waveguides/screenshot2_512.png"></a><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Electromechanical-relay"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/relay/screenshot2_512.png"></a><!--
---><a href="http://gitlab.onelab.info/doc/models/wikis/Bloch-modes-in-periodic-waveguides"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/bloch_periodic_waveguides/screenshot1_512.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Waveguides"><!--
+--><img width="25%" src="small_waveguides.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Electromechanical-relay"><!--
+--><img width="25%" src="small_relay.png"></a><!--
+--><a href="https://gitlab.onelab.info/doc/models/wikis/Bloch-modes-in-periodic-waveguides"><!--
+--><img width="25%" src="small_bloch.png"></a><!--
 --><a href="http://gitlab.onelab.info/doc/models/wikis/Acoustic-scattering"><!--
---><img width="25%" src="http://gitlab.onelab.info/getdp/getdp/raw/master/benchmarks/acoustic_scattering/screenshot2_512.png"></a><!--
+--><img width="25%" src="small_acoustic.png"></a><!--
 --></span></div>
 
 <p>
@@ -88,17 +88,25 @@ easily interfaced as well.
   and <a href="https://play.google.com/store/apps/details?id=org.geuz.onelab">Android</a>
   devices
 </ol>
-
 <p>
-Other clients (<em>non-native</em>) are interfaced with ONELAB by a system of
-input file pre-processing. The different steps of a simulation (meshing,
-solving, post-processing) are controlled by a python script. See worked-out
-examples with:
+  Examples of models based on GetDP and Gmsh:
+</p>
+<ul>
+  <li><a href="https://gitlab.onelab.info/doc/tutorials/wikis/home">Step-by-step tutorials</a>
+    introducing new features gradually to learn how to build your own GetDP/Gmsh ONELAB models.
+  <li><a href="https://gitlab.onelab.info/doc/models/wikis/home">Full-featured
+      models</a> highlighting various phsyical models and numerical methods.
+</ul>
+<p>
+  Other clients (<em>non-native</em>) are interfaced with ONELAB by a system of
+  input file pre-processing. The different steps of a simulation (meshing,
+  solving, post-processing) are controlled by a python script. See worked-out
+  examples with:
 </p>
 <ol>
-  <li><a href="http://gitlab.onelab.info/doc/models/wikis/Elmer">Elmer</a>: a
+  <li><a href="https://gitlab.onelab.info/doc/models/wikis/Elmer">Elmer</a>: a
   finite element solver for multi-physic problems developed by CSC
-  <li><a href="http://gitlab.onelab.info/doc/models/wikis/OpenFOAM">OpenFOAM</a>:
+  <li><a href="https://gitlab.onelab.info/doc/models/wikis/OpenFOAM">OpenFOAM</a>:
   an open source CFD software package developed by OpenCFD
 </ol>
 <p>
@@ -107,8 +115,8 @@ examples with:
 </p>
 <p>
   Here are
-  some <a href="http://gitlab.onelab.info/doc/models/wikis/Hints">useful hints
-  to efficiently use the ONELAB graphical user interface</a>.
+  some <a href="https://gitlab.onelab.info/doc/tutorials/wikis/Onelab-graphical-user-interface-tips-and-tricks">useful
+  hints to efficiently use the ONELAB graphical user interface</a>.
 </p>
 
 <h2>Develop your own client</h2>
@@ -117,61 +125,62 @@ examples with:
 Implement your own native ONELAB clients:
 </p>
 <ol>
-  <li><a href="http://gitlab.onelab.info/doc/models/wikis/Python">With
+  <li><a href="https://gitlab.onelab.info/doc/models/wikis/Python">With
       Python</a>: any Python code can become a native ONELAB client
-  <li><a href="http://gitlab.onelab.info/doc/models/wikis/C++">With C++</a>: how
-  to create a native C++ ONELAB client
+  <li><a href="https://gitlab.onelab.info/doc/models/wikis/C++">With C++</a>:
+  how to create a native C++ ONELAB client
 </ol>
 
 <h2>Technical information</h2>
 
 <p>
-The ONELAB interface allows calling sequences of independent clients (e.g. mesh
-generators, finite element solvers and other related tools) and have them share
-parameters and modeling information. It is based on an abstraction of the
-interface to finite element solvers and related tools: for geometry modeling and
-meshing, for the definition of physical properties, constraints and other solver
-parameters, and for post-processing.
+  The ONELAB interface allows calling sequences of independent clients
+  (e.g. mesh generators, finite element solvers and other related tools) and
+  have them share parameters and modeling information. It is based on an
+  abstraction of the interface to finite element solvers and related tools: for
+  geometry modeling and meshing, for the definition of physical properties,
+  constraints and other solver parameters, and for post-processing.
 </p>
 <p>
-The implementation is based on a client-server model, with a server-side
-database and (optional) graphical front-end, and local or remote clients
-communicating in-memory or through TCP/IP sockets. Contrary to most available
-solver interfaces, the ONELAB server has no <em>a priori</em> knowledge about
-any specifics (input file format, syntax, ...) of the clients. In practice, 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 implementation is based on a client-server model, with a server-side
+  database and (optional) graphical front-end, and local or remote clients
+  communicating in-memory or through TCP/IP sockets. Contrary to most available
+  solver interfaces, the ONELAB server has no <em>a priori</em> knowledge about
+  any specifics (input file format, syntax, ...) of the clients. In practice,
+  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.
 </p>
 <p>
-Native ONELAB clients can be written in C++ or Python, and embed the ONELAB
-library. For native clients the specification of which data to share is
-completely dynamic. For non-native clients, the ONELAB server acts as a
-pre-processor of their input files, which should be instrumented to specify the
-information to be shared. In all cases the issues of completeness and
-consistency of the parameter sets are completely dealt with on the client side:
-the role of ONELAB is limited to data centralization, modification and
-re-dispatching.
+  Native ONELAB clients can be written in C++ or Python, and embed the ONELAB
+  library. For native clients the specification of which data to share is
+  completely dynamic. For non-native clients, the ONELAB server acts as a
+  pre-processor of their input files, which should be instrumented to specify
+  the information to be shared. In all cases the issues of completeness and
+  consistency of the parameter sets are completely dealt with on the client
+  side: the role of ONELAB is limited to data centralization, modification and
+  re-dispatching.
 </p>
 
 <h2>Sponsors</h2>
 
 <p>
-The ONELAB project was funded by the Walloon Region under
-<a href="http://recherche-technologie.wallonie.be/projets/index.html?IDD=17018">WIST3
-grant n° 1017086</a> and <em>Fonds de maturation</em> grant n° 1217742 (AWE),
-and was sponsored by <a href="http://www.gdtech.eu">GDTech</a>
-and <a href="http://www.audaxis.com">Audaxis</a>. Additional funding has been
-provided by <a href="http://www.belspo.be">the Belgian Science Policy</a> under
-grant IAP P7/02.
+  The ONELAB project was funded by the Walloon Region under
+  <a href="http://recherche-technologie.wallonie.be/projets/index.html?IDD=17018">WIST3
+    grant n° 1017086</a> and <em>Fonds de maturation</em> grant n° 1217742
+  (AWE), and was sponsored by <a href="http://www.gdtech.eu">GDTech</a>
+  and <a href="http://www.audaxis.com">Audaxis</a>. Additional funding has
+  been provided by <a href="http://www.belspo.be">the Belgian Science
+    Policy</a> under grant IAP P7/02.
 </p>
 
-<center style="margin-top:4ex;">
-  <a href="http://www.ulg.ac.be"><img src="http://onelab.info/files/logo_uliege.jpg" height="68px"></a>
-  <a href="http://www.uclouvain.be"><img src="http://onelab.info/files/logo_ucl.jpg" height="68px"></a>
-  <a href="http://www.wallonie.be"><img src="http://onelab.info/files/logo_rw.jpg" height="68px"></a>
-  <a href="http://www.belspo.be"><img src="http://onelab.info/files/logo_belspo.jpg" height="68px"></a>
-  <a href="http://www.gdtech.eu"><img src="http://onelab.info/files/logo_gdtech.jpg" height="68px"></a>
-  <a href="http://www.audaxis.be"><img src="http://onelab.info/files/logo_audaxis.png" height="68px"></a>
+<center style="margin-top:4ex;margin-bottom:4ex">
+  <a href="http://www.ulg.ac.be"><img src="logo_uliege.jpg" height="68px"></a>
+  <a href="http://www.uclouvain.be"><img src="logo_ucl.jpg" height="68px"></a>
+  <a href="http://www.wallonie.be"><img src="logo_rw.jpg" height="68px"></a>
+  <a href="http://www.belspo.be"><img src="logo_belspo.jpg" height="68px"></a>
+  <a href="http://www.gdtech.eu"><img src="logo_gdtech.jpg" height="68px"></a>
+  <a href="http://www.audaxis.be"><img src="logo_audaxis.png" height="68px"></a>
 </center>
 
 </body>