[vtk-developers] VTK modularization: initial pass at new modules

[David Cole]

On Wed, Mar 9, 2011 at 9:47 AM, Marcus D. Hanwell <
marcus.hanwell at kitware.com> wrote:

> Hi Andrew,
>
> On Tue, Mar 8, 2011 at 11:13 PM, Andrew Maclean
> <andrew.amaclean at gmail.com> wrote:
> > Hi Marcus,
> >    Firstly congratulations to you all on a brilliant first effort.
> > One minor change, could I suggest moving:
> > [Filters/Sources]
> >
> > Graphics/vtkParametricFunctionSource.cxx:
> > Graphics/vtkParametricFunctionSource.h:
> >
> >
> > To:
> > [Core/ComputationalGeometry]
> > Logically vtkParametricFunctionSource belongs with the rest of the
> > vtkParametric classes.
>
> This is one case where it would be nice to keep it where it is. The
> Core/ComputationalGeometry module should only depend on Core/Core
> right now, but if we made this move then it would also depend on
> Core/ExecutionModel. Filters/Sources would of course link to
> Core/ExecutionModel, and to Core/ComputationalGeometry if necessary.
>
> That said I have not gotten this far with the build system, but I
> think it would be nice to keep the minimal dependency set for
> ComputationalGeometry if this is feasible.
>
> Marcus
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
Perhaps the other vtkParametric classes belong wherever they need to belong
in order to minimize the dependencies then? Perhaps a Parametric module
itself somewhere?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20110309/91a6dd54/attachment.html>