GitLab

ENH: Create a generic XdmfVisitor class and move writing operations to XdmfWriter.  Incorporate Loki library to perform asymmetric visitor operation (allows customizable behavior for eventual Xdmf / NetDMF library split).  Modify Loki
Visitor to work happily with boost::shared_ptr and modify swig wrapping to properly handle boost::shared_ptr inheritance.

STYLE: Split XdmfArray.tpp from XdmfArray.hpp --- this will hold template implementations for XdmfArray instead of stuffing them all in XdmfArray.hpp (merely a style difference).  Do some minor formatting on some other files.

unnecessarily duplicated functionality.

ENH: Split visitor operation into a visit and a traverse operation so that logic of how to traverse the xdmf graph is kept with xdmf objects rather than the visitor.  The visitor calls this function rather than relying on its own logic.

	Add XdmfArray to store values --- modify XdmfDataItem to contain an XdmfArray.
	Modify Tests to use new XdmfArray.
	Modify XdmfVisitor to use new XdmfArray.
	Add Python Tests and move Cxx tests to their own directory.

ENH: Use libxml2 to do construction of xml file rather than using the crude stringstream way we were using previously.  XML does not own the data, it is used to make constructing XML files easier and libxml2 will be needed eventually anyway to parse xml files.

ENH: Add ability to set Light Data Limit for Visitor, which controls how many values there need to be in a DataItem before it writes those values to a heavy data format.  Set the default value to 100.

ENH: Add XdmfDataItems to XdmfTopology and XdmfGeometry and write them out correctly in the XdmfVisitor.  Verified to work with simple Hexahedron file.

ENH:  Replace old way of creating static instances of XdmfTopologyType, XdmfGeometryType, and storing them by reference in their respective topologies.  These now work by providing a specific constructor method that returns specific instances of the objects populated with correct values.  This was changed because there are some type options in Xdmf where static instances don't make sense (e.g. XdmfTopologyType Polygon can have many different values for nodesPerElement) but we still need to restrict construction of these types with specific values.  Each parent item merely keeps a copy of a topology type.  I considered doing this with smart pointers, but I believe it to be unnecessarily complicated, especially when direct comparison of topology types is needed.  I am considering separating these types into separate classes.

Added XdmfAttribute implementation and began populating XdmfVisitor to write out XML.

ENH: Add write() method to XdmfItem and implement in subclasses.  The write() method calls the visitor on the current object which performs some predetermined acivity (writing to heavy data, writing to light data, parallel output, etc.

ENH: Add XdmfGeometryType to XdmfGeometry in a similar implementation as XdmfTopologyType.  Add tests for XdmfGeometry.  Add XdmfItem, an abstract class that is able to be traversed by an XdmfVisitor to write out its information to XML and HDF5 or other heavy data formats.  Modify XdmfGeometry, XdmfGrid, XdmfTopology, and XdmfAttribute to inherit from XdmfItem.