itaps-parallel DOCUMENTS subdirectories

[Onkar Sahni]

Lori,

Thats a good point and we (RPI) very much want it this way.

Infact we would prefer to include all i"ITAPS".h header files from a
central location instead of using copies provided by any
implementation/library (we would even prefer that implementations
specifically FMDB doesn't have a copy of ITAPS header files rather it
includes it from a central place, in case of applications people using
their own local system they can download it from ITAPS repository and
appropriately set some build parameter). I tried to make this point
earlier but it got lost in some details.

As per my understanding, currently each implementation/library provide a
copy of ITAPS header files.

Thanks,
Onkar

> When we create the new subdirectory that has all the tutorial examples,
> I think we should have a single subdirectory that contains the iMesh.h
> iMeshP.h and iBase.h files that all the exercises can reference.
> Essentially Karen's DOCUMENTS directory from Hello.  Martin also refers
> to these functions and it doesn't make sense to repeat the
> subdirectory.  I'd probably change the name to be more iMesh specific -
> something like iMESH_INCLUDES or iMESH_DOCS.
>
> We'll also need a high level README that describes each of the exercises
> at the highest level.
>
> Just wanted to get these ideas out into public space - no immediate
> action items.
>
> Lori
>
>