[Insight-developers] Code/Interfaces subdirectory

[Vikram Chalana]

Will,

I am assuming this interface stuff will be only temporary.
I thought the consensus was that our final toolkit would not depend on any
outside software (except the numeric toolkit, vnl) and we would all rewrite
our software to comply with ITK. Please let me know if I am missing
something.

Thanks,
Vikram




-----Original Message-----
From: insight-developers-admin at public.kitware.com
[mailto:insight-developers-admin at public.kitware.com]On Behalf Of Will
Schroeder
Sent: Thursday, August 10, 2000 6:39 AM
To: Insight-Developers
Subject: [Insight-developers] Code/Interfaces subdirectory


Hi Folks-

We've been experimenting and testing the itkMesh class and related classes.
As part of this process, Bill Hoffman has written some code that translates
itkMesh into vtkUnstructuredGrid and vtkUnstructuredGrid into itkMesh.

Performing these experiments has lead us to create a Code/Interfaces
directory,
with the subdirectory Code/Interfaces/vtk as the first example of some
interface code.
We are assuming (and hoping) that others will also want to create similar
code for their
packages. We expect the Interfaces directory to be the place where we put
code that
depends on optional external packages, and interfaces one system to another.
Our thinking
is that for each package that we interface with, we will create a separate
sub-directory in
Interfaces/.

If there are comments or issues please voice them. Thanks,
Will


_______________________________________________
Insight-developers mailing list
Insight-developers at public.kitware.com
http://public.kitware.com/mailman/listinfo/insight-developers