- save physicals labels when saving unrolled geometries
- fixed crash in unrolled geo save (discrete points)
- Delete Physicals now also deletes the physicals in GModel
- removed unused rules and terminals in parser
- put at least one mid-point when meshing non-straight lines
  in OCC: this fixes most of the trivial 2d meshing problems

removed most unused, untested or non-working stuff in old CAD code

new option to compute char lengths from curvature + removed most unused mesh options

curvature control is ok
divide and conquer algo has been cleaned up

more infrastructure for projection face gui

minimize the number of files that include GmshVersion.h: it's annoying to
recompiletoo many files just because the version string changes

"pure windows" version (without cygwin) is almost there: the solver
interface now works quite nicely using native Windodiows sockets and
the timers work too. There are still some bugs with binary files and
user-created functions in the parser.

removed the STEP parser: it's unusable, it makes the parser bigger,
and it introduces conflicts in the syntax.

fix memory leak + missing depend

Removed the last bits of the "Discrete Surface/Line" stuff.

Gmsh can now simply read a .msh file, and use it as the boundary mesh
of a 3D mesh. For an example on how to do this, cf.
demos/sphere-discrete.geo.

This complements nicely the STL remeshing stuff: Gmsh can now
for example very easily be used to extrude surface meshes that
come from other tools.

- Generalized the "View" parser so that we can add new elements more easily
  (the code is *much* shorter, but unfortunately about 10-15% slower)

- Upgraded all post-pro file formats to handle curved (second order)
  elements: SL2, VL2, TL2, ST2, VT2, ... The new version number for the
  postpro files is 1.4

- Added code to automatically split the curved elements into linear
  elements when the view is created. WARNING: this is only a temporary
  solution: weshould generalize Adaptive_Post_View to handle these curved
  elements.

- fixed double free in case there is an error in tSprintf

- new StrRelative command

- small demo on how one can add a generic title to a plot using
  Plugin(Annotate)

- added new "spectral" colormap (truncated hsv)
- added GUI button for elliptic mesh + geometry coherence
- added GMSH_MAJOR_VERSION, GMSH_MINOR_VERSION and GMSH_PATCH_VERSION
  in the parser

new "AliasWithOptions" command

- renamed "Duplicate View" into "Alias View" (suggested by Philippe;
  less confusing since "Duplicate" implies that we actually copy the
  data, which is not what we are doing)

- added general "on the fly" tranformation matrix option. This allows
  for very efficient visualization of aliased datasets with
  non-destructive rotations, symmetries, etc.

- removed all the crappy STL code and rewrote it using JF's POLY_rep
  class

- generalized POLY_rep so that we can use the polygonal discretization
  as a surface mesh, and mesh in 3D afterwards. I.e., we can now take
  an input triangulation (a single surface in STL format, multiple
  surfaces in STL format, one or more surfaces defined using the new
  "Discrete Surface" commands), and generate a 3D mesh that uses it. We
  could in theory even mix triangulated and "normal" surfaces in the
  same geometry, but nothing is done at the moment to ensure that the
  mesh at the interfaces would match (if it does, it actually works
  very nicely)

- new STL mesh output format to export a surface mesh as a STL file

- added an option to the GEO output routine to save the surface mesh
  as discrete surfaces associated with the geometrical surfaces

- added STL and Text output formats for post-processing views (the
  text output allows for example to exploit plugin-generated data in
  gnuplot)

- generalized Plugin(Evaluate):

  * can loop automatically over all the timestep and/or components

  * can do operations using data from an external view

     - if the 2 views are based on the same grid, the plugin does the
       evaluation very efficiently

     - if the 2 views are based on differenet grids, the plugin
       automatically interpolates the external view data onto the
       grid of the current view

- added new Rand() function in MathEval

- default colormap is now # 2 (the Matlab "Jet" colormap)

add special token "Today" to return the current date

- new parser function GetValue("text", default_value) to query a value
  interactively in a script

- added a nice example using this (to compute slices automatically):
  demos/multislice.script

one can now specify a TIME list of values in parsed views to give the
values of the time (or whatever) steps (like in ascii/binary views)

- Added a bunch of colormaps from:

  Color Theory and Modeling for
  Computer Graphics, Visualization,
  and Multimedia Applications

  Haim Levkowitz
  University of Massachusetts Lowell
  Lowell, Massachusetts, USA

- Increased max size of colormap to 1024

- Small cleanup in parser+plugin

This patch fixes an old design flaw in the post-processing module,
namely that we used a list of Post_View objects instead of a list of
pointers to Post_View objects in CTX.post.list.

This had many annoying consequences, in particular the fact that we
needed to be extra careful every time the list was reallocated (as
pointers to the list elements would become invalid).

I tried very hard to change the code everywhere it should be changed,
but I might have missed something. Please let me know if you see
anything suspicious (like a crash when you duplicate/remove/combine/...
post-processing views).

cleanup (and remove 2 shift/reduce conflicts in parser)

New high order interpolation.

JFR

new BoundingBox command to force the computation of the bounding box (useful
when there is no geometry and we don't include/merge any views)

make parser

issue a small warning if we try to include or merge an unexisting file
in the parser

make parser && make depend

- Simplified the bounding box computation. It is now computed as
follows (after each include/merge/open):

1. If there is a geometry (i.e., at least one geometrical point), the
bounding box is taken as the box enclosing all the geometrical points;

2. If there is no geometry but there is a mesh (i.e., at least one
mesh vertex), the bounding box is taken as the box enclosing all the
mesh vertices;

3. If there is no geometry and no mesh, but there are some
post-processing views, the bounding box is taken as the box enclosing
all the primitives of the last post-processing view.

This should fix the weird things that sometimes happen when we animate
scenes that do not contain any geometrical entities.

- Deprecated MergeWithBoundingBox()

- Removed Replot()

- Removed the "Last_NumberOfPoints" hack in the parser

- Removed CTX.expose

remove tMesh

- Slightly reorganized the visibility browser window (the "toggle"
  behaviour in the input field was confusing)

- added Show and Hide commands in the parser to enable scripting of
  the visibility stuff

- Moved Visibility.{cpp,h} into Common/ to avoid dependencies with the
  Graphics library in the parser