Go to file
Kenneth Moreland 21823500c3 Change ArrayContainerControl to Storage.
After a talk with Robert Maynard, we decided to change the name
ArrayContainerControl to Storage. There are several reasons for this
change.

1. The name ArrayContainerControl is unwieldy. It is long, hard for
humans to parse, and makes for long lines and wraparound. It is also
hard to distinguish from other names like ArrayHandleFoo and
ArrayExecutionManager.

2. The word container is getting overloaded. For example, there is a
SimplePolymorphicContainer. Container is being used for an object that
literally acts like a container for data. This class really manages
data.

3. The data does not necessarily have to be on the control side.
Implicit containers store the data nowhere. Derivative containers might
have all the real data on the execution side. It is possible in the
future to have storage on the execution environment instead of the
control (think interfacing with a simulator on the GPU).

Storage is not a perfect word (what does implicit storage really mean?),
but its the best English word we came up with.
2014-06-24 09:58:32 -06:00
CMake Properly name the VTKm CMakeFiles. 2014-02-11 14:56:03 -05:00
docs revise the header guard naming convention to not conflict with macro names. 2014-03-07 10:22:36 -05:00
vtkm Change ArrayContainerControl to Storage. 2014-06-24 09:58:32 -06:00
CMakeLists.txt Create and install CMake configure files for external projects. 2014-05-22 15:20:41 -06:00
LICENSE.txt Add a license to vtkm. 2014-02-10 15:00:17 -05:00
README.md Initial commit. 2014-02-04 15:08:03 -05:00

Welcome to vtkm design and hackathon.

Resources:

EAVL: https://github.com/jsmeredith/EAVL DAX: https://github.com/Kitware/DaxToolkit