1. 15 Apr, 2010 1 commit
  2. 13 Apr, 2010 1 commit
  3. 09 Apr, 2010 1 commit
    • Ken Leiter (Civ ARL/CISD) kleiter's avatar
      ENH: · 369f62ea
      Ken Leiter (Civ ARL/CISD) kleiter authored
      	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.
      369f62ea
  4. 10 Feb, 2010 1 commit
  5. 09 Feb, 2010 3 commits
    • Ken Leiter (Civ's avatar
    • Ken Leiter (Civ's avatar
      ENH: Allow XdmfGrids to insert XdmfAttribute elements. Add this to the... · ab806f9f
      Ken Leiter (Civ authored
      ENH: Allow XdmfGrids to insert XdmfAttribute elements.  Add this to the visitor logic to write to xml.
      ab806f9f
    • Ken Leiter (Civ's avatar
      ENH: Replace old way of creating static instances of XdmfTopologyType,... · 4acdd29e
      Ken Leiter (Civ authored
      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.
      4acdd29e
  6. 06 Feb, 2010 3 commits
  7. 03 Feb, 2010 1 commit