[Libmesh-devel] Mesh & MeshBase are too big!

[John P. <pet...@cf...>]

 > Benjamin S. Kirk writes:
 > It seems that the Mesh & MeshBase class have gotten out of control. 
 > Don't get me wrong...  All the functionality is great, but I think we 
 > need to split some of it into other classes.  For example:
 > 
 > MeshIO
 >    - encompasses all the read/write methods.
 >    - Mesh::read() & Mesh::write() will still exist, but will simply
 >      call methods in this class.
 Or what about (don't contain a MeshIO in Mesh):
 Mesh   mesh(3);
 MeshIO mesh_io(mesh);
 mesh_io.read("foo");
 mesh_io.write("bar");

 > MeshGeneration
 >    - build_cube()
 >    - build_sphere()
 >    - all_tri()
 >    - etc...
Maybe call it MeshGenerator (semantics) ?

 > MeshModification
 >    - build_inf_elem()
 >    - translate()
 >    - scale()
 >    - distort()
 >    - etc...
As above, maybe MeshModifier e.g. something which
modifies meshes.


-- 
John