Array Refactoring: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
mNo edit summary |
m (→Recent Work) |
||
| Line 11: | Line 11: | ||
** vtkDenseArray::StaticMemoryBlock | ** vtkDenseArray::StaticMemoryBlock | ||
** vtkDenseArray::HeapMemoryBlock | ** vtkDenseArray::HeapMemoryBlock | ||
* vtkSparseICSArray | |||
** Changes the way coordinates are stored, one contiguous array of coordinates per dimension, instead of a single contiguous array for all dimensions. | |||
** Implements value sorting. | |||
** Could probably replace the current vtkSparseArray implementation. | |||
== Proposed Work == | |||
* | |||
* Make | |||
Revision as of 10:57, 8 April 2009
Overview
Now that we have N-Way Array Data Structures, it would be ideal if we could use them as attributes in data objects. This will likely involve some tricky work to somehow merge the vtkAbstractArray- and vtkArray- hierarchies.
Recent Work
- Added vtkArray::GetName() and vtkArray::SetName()
- vtkDenseArray memory management.
- vtkDenseArray::MemoryBlock
- vtkDenseArray::StaticMemoryBlock
- vtkDenseArray::HeapMemoryBlock
- vtkSparseICSArray
- Changes the way coordinates are stored, one contiguous array of coordinates per dimension, instead of a single contiguous array for all dimensions.
- Implements value sorting.
- Could probably replace the current vtkSparseArray implementation.
Proposed Work
- Make
