diff --git a/TODO b/TODO
index f556d1a95e56c98308dad6ed840b5e5f4ec0a261..ba79630eacb391ac68fa613008b9dfde99171d93 100644
--- a/TODO
+++ b/TODO
@@ -1,8 +1,8 @@
-$Id: TODO,v 1.10 2003-03-03 16:07:15 geuzaine Exp $
+$Id: TODO,v 1.11 2003-03-06 23:01:17 geuzaine Exp $
-=================================================================================
+********************************************************************
-* Combine view + save view with != nb of time steps
+Combine view + save view with != nb of time steps
gmsh tutorial/view*.pos
View->Combine->All
@@ -17,31 +17,31 @@ values up to MIN(NbTimeStep for all merged views).
-> need to make merge() more intelligent. First pass on NbTimeStep,
then List_Add() only up to common TimeStep value.
-=================================================================================
+********************************************************************
-* Include Tetgen (the same way we did it with Triangle--the license is
+Include Tetgen (the same way we did it with Triangle--the license is
the same).
-=================================================================================
+********************************************************************
-* Rewrite the View interface in C++
+Rewrite the View interface in C++
-=================================================================================
+********************************************************************
-* Memory leaks, memory leaks (start with mesh_domain() and the parser)
+Memory leaks, memory leaks (start with mesh_domain() and the parser)
-=================================================================================
+********************************************************************
-* Two-field plots <nicolas.moes@ec-nantes.fr>
+Two-field plots <nicolas.moes@ec-nantes.fr>
Imagine I would like to plot a temperature field on a deformed
mesh. This requires two field : the temperature field and the
displacement field to deform the mesh. Is there something done in gmsh
done for this?
-=================================================================================
+********************************************************************
-* Pb avec View->Reload si plusieurs vues dans le meme fichier
+Pb avec View->Reload si plusieurs vues dans le meme fichier
> > Hmm, je viens de tester sous Linux et je n'arrive pas a reproduire le
> > bug. A moins que... Aurais-tu toutes tes vues stockees dans le meme
@@ -60,11 +60,9 @@ bien toutes les vues, mais tu ne sais acceder qu'a la derniere... Pour
corriger ca, il faudrait que l'on garde comme info supplementaire dans
chaque vue quelle etait sa position dans le fichier.
-=================================================================================
+********************************************************************
-* Tenseurs
-
-Laurent Stainier <l.stainier@ulg.ac.be>
+Tenseurs, Laurent Stainier <l.stainier@ulg.ac.be>
L'approche que je suggérerais est la suivante. Tout d'abord, on peut
commencer par le cas particulier (mais sans doute le plus courant) des
@@ -102,18 +100,16 @@ Remarque finale: le calcul des valeurs et vecteurs propres est
à partir des v.p.), et cela nous rappelle cette belle expression "No
free meal" !
-=================================================================================
-
-* Stockage et acces aux normales en post-pro:
+********************************************************************
-- stocker les normales autrement (generer les noeuds?) pour acces
-plus rapide.
+Stockage et acces aux normales en post-pro: generer les noeuds pour
+acces plus rapide?
Idem pour le maillage.
-=================================================================================
+********************************************************************
-* Orientation des surfaces
+Orientation des surfaces
mesh: il faut vraiment que je regarde la relation entre l'orientation
des surfaces geometriques et les l'orientation des elements du
diff --git a/doc/FAQ b/doc/FAQ
index d4103f795a5644f427365914d57ff66419b80b48..52b256c26808c6f5d6a847cdac086e1002cd92be 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,4 +1,6 @@
-This is the Gmsh FAQ - $Date: 2003-03-02 18:44:21 $
+$Id: FAQ,v 1.29 2003-03-06 23:01:17 geuzaine Exp $
+
+This is the Gmsh FAQ
********************************************************************
diff --git a/doc/FORMATS b/doc/FORMATS
index d44cdc3de329a8e8fd8a330845da3ed188b113b5..f4763a2ab1b07269ff3f1f92aa42e72c54462376 100644
--- a/doc/FORMATS
+++ b/doc/FORMATS
@@ -1,16 +1,16 @@
-$Id: FORMATS,v 1.15 2003-03-01 23:11:35 geuzaine Exp $
+$Id: FORMATS,v 1.16 2003-03-06 23:01:17 geuzaine Exp $
This document describes the version 1.2 of Gmsh's mesh and
-post-processing file formats
+post-processing file formats.
(This document deals only with the import/export interfaces for
Gmsh. The language driving the behaviour of Gmsh for defining
geometries, options, scripts, etc. is explained step by step in the
tutorials.)
+********************************************************************
-Gmsh Mesh File Format
-=====================
+Section 1: Gmsh Mesh File Format
The 'msh' file format is the native output file format for Gmsh. The
file is divided in two sections (enclosed in $KEY and $ENDKEY pairs):
@@ -30,8 +30,12 @@ $NOD/$ENDNOD defines the nodes and $ELM/$ENDELM defines the elements.
All the syntactic variables stand for integers except coord1, coord2
and coord3 which stand for floating point values, and node-numbers
-which stand for a list of nb-nodes integers. The elm-type value
-defines the geometrical type for the element:
+which stand for a list of nb-nodes integers.
+
+Please note that the the node-number and elm-number numbers are not
+necessarily given in a consecutive or even an ordered way.
+
+The elm-type value defines the geometrical type for the element:
1 Line (2 nodes, 1 edge).
2 Triangle (3 nodes, 3 edges).
@@ -43,16 +47,16 @@ defines the geometrical type for the element:
15 Point (1 node).
The elm-region value is the number of the physical entity to which the
-element belongs.
+element belongs.
+********************************************************************
-Gmsh ASCII Post-Processing File Format
-======================================
+Section 2: Gmsh ASCII Post-Processing File Format
-A post-processing file is divided in several sections: one format
-section (enclosed between $PostFormat/$EndPostFormat) and (possibly
-multiple) post-processing views (enclosed between $View/$EndView
-pairs).
+An ASCII post-processing file is divided in several sections: one
+format section, enclosed between $PostFormat/$EndPostFormat, and
+(possibly multiple) post-processing views, enclosed between
+$View/$EndView pairs:
$PostFormat
1.2 file-type data-size
@@ -95,7 +99,7 @@ pairs).
tensor-pyramid-value ...
text2d ... text2d-chars ...
text3d ... text3d-chars ...
- $endView
+ $EndView
file-type is an integer equal to 0 in the ASCII file format.
@@ -151,8 +155,9 @@ string in text3d-chars.
text3d-chars is a list of nb-text3d-chars chars. Substrings are
separated with the '^' characted.
-Gmsh Binary Post-Processing File Format
-=======================================
+********************************************************************
+
+Section 3: Gmsh Binary Post-Processing File Format
The binary post-processing file format is the same as the ASCII file
format, except that:
@@ -200,15 +205,17 @@ precision numbers containing all the scalar-point-value lists, put one
after each other in order to form a long array of doubles. The
principle is the same for all other kinds of values.
+********************************************************************
-Gmsh Parsed Post-Processing Format
-==================================
+Section 4: Gmsh Parsed Post-Processing Format
-For testing purposes (or with very small data sets, e.g. in the
-tutorials), there is an additional post-processing format which is
-parsed by the same grammar analyzer as the geometry. You can thus, for
-example, embed small post-processing views into your geometrical
-descriptions. The format of the parsed post-processing files is the
+For relatively small data sets Gmsh provides an additional
+post-processing format, which is parsed by the same grammar analyzer
+as the geometry. You can thus, for example, embed small
+post-processing views directly into your geometrical descriptions (see
+the tutorial). This format is also very useful for testing purposes:
+it's syntax is very permissive, and you can easily generate it by hand
+or on the fly. The format of the parsed post-processing file is the
following:
View "name" {
@@ -247,16 +254,24 @@ following:
text 2d T2 4 arbitrary
text 3d T3 5 arbitrary
-Contrary to the ASCII post-processing file format, the coordinates are
-given by node, i.e. (coord1, coord2, coord3) for a point,
-(coord1-node1, coord2-node1, coord3-node1, coord1-node2, coord2-node2,
-coord3-node2) for a line, (coord1-node1, coord2-node1, coord3-node1,
-coord1-node2, coord2-node2, coord3-node2, coord1-node3, coord2-node3,
-coord3-node3) for a triangle, etc. The values are given in the same
-order as for the ASCII post-processing file format.
+Contrary to the ASCII and Binary post-processing file formats (see
+below), the coordinates are given by node, i.e.
+
+(coord1, coord2,coord3) for a point,
+
+(coord1-node1, coord2-node1, coord3-node1,
+ coord1-node2, coord2-node2, coord3-node2) for a line,
+
+(coord1-node1, coord2-node1, coord3-node1,
+ coord1-node2, coord2-node2, coord3-node2,
+ coord1-node3, coord2-node3, coord3-node3) for a triangle,
+
+etc. The values are given in the same order as for the ASCII and
+Binary post-processing file formats.
+
+********************************************************************
-Ordering of nodes
-=================
+Section 5: Gmsh node ordering
* POINT
v
diff --git a/doc/KEYWORDS b/doc/KEYWORDS
index 0fb1a8ff2b60434aa2d90a7add2b84705d6d4424..1d316e518a8d4af8017efc17443ca08bbc03bb24 100644
--- a/doc/KEYWORDS
+++ b/doc/KEYWORDS
@@ -1,4 +1,4 @@
-// $Id: KEYWORDS,v 1.2 2003-03-01 23:11:35 geuzaine Exp $
+$Id: KEYWORDS,v 1.3 2003-03-06 23:01:17 geuzaine Exp $
/* List of reserved keywords for Gmsh 1.19 */
diff --git a/doc/README.cvs b/doc/README.cvs
index 863d51814045c589e609e023baa4198d822ed0a5..df67de1a649bbc283dfeccdf24e6a0e121a7a984 100644
--- a/doc/README.cvs
+++ b/doc/README.cvs
@@ -1,3 +1,4 @@
+$Id: README.cvs,v 1.4 2003-03-06 23:01:17 geuzaine Exp $
0) Set the variable CVS_RHS to ssh ('export CVS_RHS=ssh' with bash, or
'setenv CVS_RHS ssh' with tcsh)
diff --git a/doc/README.devel b/doc/README.devel
index 16859f5b47a77deb32fa656f6887ee02cb1a74c6..5590b5c838ea2a53d816343b1f0ce6a31cdaf938 100644
--- a/doc/README.devel
+++ b/doc/README.devel
@@ -1,3 +1,4 @@
+$Id: README.devel,v 1.5 2003-03-06 23:01:17 geuzaine Exp $
Some easy rules to make the code easy to read/debug/maintain:
@@ -6,7 +7,7 @@ Some easy rules to make the code easy to read/debug/maintain:
- indent your files using ../utils/indent.sh
- if working on Windows, don't leave tabs in your files (../utils/untabify)
-===========================================================================
+********************************************************************
How to add an option in the graphical user interface?
@@ -29,7 +30,7 @@ Optional:
handling routine opt_XXX to the OK callback for the corresponding
option panel (in Fltk/Callbacks.cpp).
-===========================================================================
+********************************************************************
Tools to check memory leaks
diff --git a/doc/README.mac b/doc/README.mac
index 08e8401aa75da7733a3a9f79c85586aa6d5da372..9dd0aadd611df7aa44b52a36d41f667191c9efbc 100644
--- a/doc/README.mac
+++ b/doc/README.mac
@@ -1,8 +1,8 @@
+$Id: README.mac,v 1.4 2003-03-06 23:01:17 geuzaine Exp $
-How to distribute the Mac version...
-====================================
+How to make a version recognized by the Mac Finder?
-The old way (using resource forks)
+The old way (using resource forks):
- compile
@@ -19,16 +19,15 @@ The old way (using resource forks)
b) you can also create the disk image on the command line, using
utils/make-dmg.sh (WARNING: modify the script to suit your needs)
-
The new way:
- use the new XML-based scheme: see 'make distrib-mac'
-- and just 'tar zcvf' the directory! No more resources!
+- ...and just 'tar zcvf' the directory. No more crappy resources!
+********************************************************************
Apple Creator Registration
-==========================
Please include the line below in follow-up emails for this request.
diff --git a/doc/README.win32 b/doc/README.win32
index 811a44c1b3d9d01149b0fa9ee870546c497c0353..498ff59c592ae5830018f1e6fa7f10ff35cbb3fc 100644
--- a/doc/README.win32
+++ b/doc/README.win32
@@ -1,7 +1,4 @@
-$Id: README.win32,v 1.1 2003-03-01 22:50:48 geuzaine Exp $
-
-For Windows versions of Gmsh only:
-==================================
+$Id: README.win32,v 1.2 2003-03-06 23:01:17 geuzaine Exp $
1) About opengl32.dll and glu32.dll:
diff --git a/doc/gmsh.1 b/doc/gmsh.1
index 9648cbcb877d14675ac45d89d060b4e6f9c1fc1d..4f223616b03fb2f0d24a67e29b0cd10de677416e 100644
--- a/doc/gmsh.1
+++ b/doc/gmsh.1
@@ -1,15 +1,14 @@
-.\" $Id: gmsh.1,v 1.45 2003-03-02 16:24:19 geuzaine Exp $
-.\" ======================================================================
+.\" $Id: gmsh.1,v 1.46 2003-03-06 23:01:17 geuzaine Exp $
.TH Gmsh 1 "12 November 2001" "Gmsh > 1.30" "Gmsh Manual Pages"
.UC 4
-.\" ======================================================================
+.\" ********************************************************************
.SH NAME
Gmsh \- an automatic three-dimensional finite element mesh generator
with built-in pre- and post-processing facilities
-.\" ======================================================================
+.\" ********************************************************************
.SH SYNOPSIS
.B gmsh [file(s)] [option(s)]
-.\" ======================================================================
+.\" ********************************************************************
.SH DESCRIPTION
\fIGmsh\fR is an automatic three-dimensional finite element mesh
generator, primarily Delaunay, with built-in pre- and post-processing
@@ -91,12 +90,12 @@ maps. Post-processor functions include offsets, elevation, interactive
color map modification, range clamping, interactive animation, vector
postscript output, etc. All post-processing options can be accessed
either interactively or through the input ascii files.
-.\" ======================================================================
+.\" ********************************************************************
.SH GEOMETRY OPTIONS
.TP 4
.B \-0
parse all input files, output unrolled geometry, and exit.
-.\" ======================================================================
+.\" ********************************************************************
.SH MESH OPTIONS
.TP 4
.B \-1
@@ -161,7 +160,7 @@ use the old extrusion mesh generator.
.TP 4
.B \-recombine
recombine meshes from the old extrusion mesh generator.
-.\" ======================================================================
+.\" ********************************************************************
.SH POST-PROCESSING OPTIONS
.TP 4
.B \-dl
@@ -178,7 +177,7 @@ smooth views at startup.
.TP 4
.B \-convert file file
convert an ascii view into a binary one.
-.\" ======================================================================
+.\" ********************************************************************
.SH DISPLAY OPTIONS
.TP 4
.B \-nodb
@@ -196,7 +195,7 @@ specify display.
.TP 4
.B \-perspective
use perspective instead of orthographic projection.
-.\" ======================================================================
+.\" ********************************************************************
.SH OTHER OPTIONS
.TP 4
.B \-a, \-g, \-m, \-s, \-p
@@ -220,11 +219,11 @@ show detailed version information.
.TP 4
.B \-help
show help message.
-.\" ======================================================================
+.\" ********************************************************************
.SH AUTHORS
Christophe Geuzaine (geuzaine@acm.caltech.edu) and Jean-Francois
Remacle (Remacle@scorec.rpi.edu).
-.\" ======================================================================
+.\" ********************************************************************
.SH SEE ALSO
.BR getdp (1),
.br