Array Refactoring: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
(New page: == Overview == Now that we have [http://kitware.com/InfovisWiki/index.php/N-Way_Array_Data_Structures N-Way Array Data Structures], it would be ideal if we could use them as attributes in...)
 
mNo edit summary
Line 2: Line 2:


Now that we have [http://kitware.com/InfovisWiki/index.php/N-Way_Array_Data_Structures 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.
Now that we have [http://kitware.com/InfovisWiki/index.php/N-Way_Array_Data_Structures 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

Revision as of 11:54, 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