First pass at cleaning up lists in the .geo parser: 

- we now keep track of the variable type ("list of floats" or "single float")
- the brackets [] after the variable id are now optional (aa={1,2} == aa[]={1,2}) when creating a new list
- the old syntax is kept to enable forcing the type to "list of floats" when creating a single-entry list
- on single floats, += performs the usual arithmetic operation; on lists, += appends to the list (idem for -=)

WARNING! this is a possibly dangerous commit: please test your .geo files and your scripts and signal any weird behaviour

Added option for levelset cutting ""CutMeshTri(tag)", that saves only triangles and tets (no polygons or polyhedra)
Added new level set definition "Levelset Points(tag)={{x1,y1,z1},{x2,y2,z2}};", builds a level set from a set of data points using RBF interpolation

with tet meshes using pyramids.

It's not perfect (it introduces the pyramids in the extruded/transfinite mesh) but it's useful
nonetheless.

Use the following in your Geo file
Mesh.RemeshParametrization=2; //(0) harmonic (1) conformal (2) Rbf

compounds, transfinite, etc. easier

- fixed MED node ordering
- polished 64 bit Cocoa Mac OS X FLTK version
- updated copyright

No commit message

recoded way to create boundary layers using explicit extrusion directions from vector post-processing view

Mesh.RemeshParametrization=1; //(0) harmonic (1) conformal 
Mesh.RemeshAlgorithm=1; //(0) nosplit (1) automatic (2) split metis
!!! This replaces old parser stuff such as Compound Surface()={} Harmonic_NoSplit;
!!! Default values are harmonic and automatic
TODO: change this in FLTK/optionWindow.cpp

- boundary of combined entities in parser

No commit message

- new GetEnv and GetString functions