[Dune] VTKWriter Changes

[Jö Fahlke]

I just thought I'd better give you an abstract of the changes in the
VTKWriter.

Most important first:  The old VTKWriter is still around and should work as
before, though some stuff was moved around and the compatibility typedefs
etc. have been marked deprecated.

Lots of stuff has been moved into the namespace VTK.  Most important

 * Dune::VTKOptions::DataMode is now Dune::VTK::DataMode, the enum constants
   conforming and nonconforming have been moved as well.

 * Dune::VTKOptions::OutputType is now Dune::VTK::OutputType, the enum
   constants have been moved as well, and some have been rename:

   - ascii keeps it's name

   - binary is now called base64

   - binaryappended is now called appendedraw

   - there is a new constant appendedbase64

   The renaming was mostly done because "binary" can mean either "base64" or
   "raw" encoding, and there is a difference between the two in the vtk
   format.

Of course, Dune::VTKOptions ist still around, and the constants there still
have their old named, they are just aliases for the new names from Dune::VTK.

There is now Dune::VTK::NonConformingBoundaryWriter.  It can write functions
that are defined on the domain boundary, such as the unit outer normal.  That
was actually the reason for all this.

The is a class Dune::VTK::ConformingVolumeWriter, which does essentially the
same as Dune::VTKWriter in conforming mode.  This ist mostly there as a proof
of concept that the infrastructure used for the BoundaryWriter is general
enough to support volumewriters as well.

Thanks,
Jö.

-- 
<ex-bart> beleidige cernlib
-:- SignOff Volk1: #macht (EOF From client)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20100615/94844297/attachment.sig>