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

[Pebay, Philippe P]

Thanks Marcus. I must say that I am impressed by the task which you are tackling here.

A first quick comment regarding the module currently called "Filters/Filters". I think that it is a bit too generic.

For instance vtkMeshQuality heavily relies on Verdict, currently located in Utilities.
One could therefore imagine a situation where someone does not want Verdict but still needs some basic filtering algorithms currently
in Filtering/Filtering.

How about having a Filtering/Verdict module? Granted it would contain only one class at this point but that would allow to entirely do away
with this library.

Also, for similar reasons I would recommend that the R adaptor and calculators be moved to Statistics.

Thanks again for this most useful and arduous work.

Philippe

--
Philippe Pébay
Sandia National Laboratories

________________________________________
From: vtk-developers-bounces at vtk.org [vtk-developers-bounces at vtk.org] On Behalf Of Marcus D. Hanwell [marcus.hanwell at kitware.com]
Sent: Tuesday, March 08, 2011 2:07 PM
To: VTK Developers
Subject: [vtk-developers] VTK modularization: initial pass at new modules

Hi,

I have linked to a manifest file, this contains an early pass at
creating new VTK modules, as part of the VTK modularization project.
It maps source files, the old CMakeLists.txt, Testing and several
other parts have been intentionally left out for now. Once we have a
rough consensus on the classes that will go into the new kits we can
then map the tests to the appropriate places.

https://github.com/cryos/vtk-modularization/blob/master/manifest.txt

The [<ignore>] section marks files and directories that are not
mapped. All other sections denote new modules, for example,

[Core/Core]
Common/vtkABI.h:

Would map the vtkABI.h file currently in common to Core/Core/vtkABI.h
in the new modules. This would be a kit called vtkCoreCore. We are
planning on using two levels, with no modules in the first level and
only one word being allowed for top levels so that it is easy to
distinguish what the top level part of a library name is. This means
that the Core directory would contain several other modules that are
core libraries, with each module in the second level being a module.

I am pushing this list while it is still at an early stage (largely
with input from Berk, Will and Jeff so far) so that the wider
community can comment on the proposed moves. None of the names or
mappings are set in stone, and we welcome your input (especially from
those of you who have spent a lot of time working on some of these
classes). I will be updating it as I get things building, and once a
reasonable subset of VTK is building I will put up an experimental
modularized VTK repository for people to test. The history of that
repository will not be retained, and all source changes should still
go to VTK master.

As you can see some old modules have not been mapped yet (Imaging,
Parallel, Examples, Wrapping). I will let people know in advance of
the final move, the mappings will be applied to the latest source
files in master at that point using git file moves, and the new build
system committed. Until then I can update the experimental modularized
VTK by syncing to the latest source files in VTK master periodically.

We would appreciate input from the wider VTK developer community as we
modularize VTK. This will also impact other communities, such as
ParaView and Slicer, and we are looking into ways to ease porting to
the new layout. I have talked at length with the ITK modularization
team to see what we can share, and will be putting that together in
the experimental repository soon.

Thanks,

Marcus
--
Marcus D. Hanwell, Ph.D.
R&D Engineer, Kitware Inc.
(518) 881-4937
_______________________________________________
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