Author: iulian Date: 2011-01-31 15:34:50 -0600 (Mon, 31 Jan 2011) New Revision: 4478 Modified: MOAB/trunk/itaps/igeom/iGeom.h MOAB/trunk/itaps/igeom/iGeom_MOAB.cpp MOAB/trunk/itaps/igeom/iGeom_MOAB.hpp Log: Change the iGeom.h file to be the one from CGM/itaps folder. One of the changes is that "iGeom_EntityIterator"s are replaced with iBase_EntityIterator's Some other changes in iGeom.h are not clear. Need to investigate more, to see why there are different iGeom.h files in our 2 different implementations of iGeom Modified: MOAB/trunk/itaps/igeom/iGeom.h =================================================================== --- MOAB/trunk/itaps/igeom/iGeom.h 2011-01-31 18:17:23 UTC (rev 4477) +++ MOAB/trunk/itaps/igeom/iGeom.h 2011-01-31 21:34:50 UTC (rev 4478) @@ -1,3283 +1,3789 @@ -#ifndef _ITAPS_iGeom -#define _ITAPS_iGeom - - /** \mainpage The ITAPS Geometry Interface iGeom - * - * The ITAPS Geometry Interface iGeom provides a common interface for - * accessing geometry and data associated with a mesh. Applications written - * to use this interface can use a variety of implementations, choosing - * the one that best meets its needs. They can also use tools written - * to this interface. - * - * \section ITAPS Data Model - * - * The ITAPS interfaces use a data model composed of four basic data types:\n - * \em Entity: basic topological entities in a model, e.g. vertices, - * edges, faces, regions. \n - * \em Entity \em Set: arbitrary grouping of other entities and sets. - * Entity sets also support parent/child relations with other sets which - * are distinct from entities contained in those sets. Parent/child links - * can be used to embed graph relationships between sets, e.g. to - * represent topological relationships between the sets. \n - * \em Interface: the object with which model is associated and on which - * functions in iGeom are called. \n - * \em Tag: application data associated with objects of any of the other - * data types. Each tag has a designated name, size, and data type. - * - * \section JTAPS Entity Type - * Each entity has a specific Entity Type. The Entity - * Type is one of VERTEX, EDGE, FACE, and REGION, and is synonymous with - * the topological dimension of the entity. Entity Type is an enumerated - * type in the iBase_EntityType enumeration. - * - * \section KTAPS Entity-, Array-, and Iterator-Based Access - * - * The iGeom interface provides functions for accessing entities - * individually, as arrays of entities, or using iterators. These access - * methods have different memory versus execution time tradeoffs, - * depending on the implementation. - * - * \section LTAPS Lists Passed Through Interface - * - * Many of the functions in iGeom have arguments corresponding to lists of - * objects. In-type arguments for lists consist of a pointer to an array and - * a list size. Lists returned from functions are passed in three arguments, - * a pointer to the array representing the list, and pointers to the - * allocated and occupied lengths of the array. These three arguments are