(best solution would be not to allocate empty steps at all -- todo...)

suggested by Nicolas Tardieu

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

No commit message

isInside tolerance in ref coordinates

val ranges on parts of models using new model-based post-pro format)

new sampling options to diplay one out of N elements (post-pro) or labels (mesh; this replaces the old labelsFrequency opt)

more bindings on PViewData : I'm not sure those bindings are the way to go but I needed a quick solution for the summer school, christophe please remove this commit if you think they are bad.

- Plugin(Skin) now works on adapted datasets
- addData() should now also work for high order datasets [we still need to
  add a new type+ref to FS in PViewDataGModel]

FIXME: we need to store the number of things stored for each element in stepData 
to make this clean (and make high-order I/O easier) + add a copy constructor in stepData

separate multistep, multipartition datasets)

prototype "-watch" option to watch for specific files according to 
a pattern (use 'w' shortcut in GUI to test)

- moved GUI to FlGui + added experimental QGui to test Qt

- fixed most MSVC and gcc compiler warnings

- converted some remaining tabs to whitespace (that's why the patch is
  so large; please try to remember to indent with 2 spaces and not
  tabs when you commit stuff to CVS)

- merged modified patch from Konstantinos Poulios to allow saving
  physical/partition as element tags in mesh formats that don't
  support them natively

- fix bb computation to avoid model jumping around when adding points in z=0 plane
- pass interpol matrices as ref

- fixed missing getShapeFunction/getGradShapeFunction + return all sf
  at once so we can implement MElement in term of these consistently
  (w or w/o FunctionSpace)

- can now merge multiple meshes and remove duplicate mesh vertices
  (useful e.g. when merging several STLs)

- added easy interface to create model-based postpro datasets on the
  fly + use this for mesh quality stats

   1) this removes the asymmetry in all the routines involving mesh
      elements associated with points

   2) it makes it possible to use point-based datasets in the
      model-based post-processing module

  **********************************************************
    PLEASE TEST --- ESPECIALLY THE INPUT/OUTPUT ROUTINES!
  **********************************************************

* made GModel::getEntities() more efficient and generalized its use

* implemented first rough draft of VTK mesh writer