Talk:Titan Data Structures: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== vtkTable parent class == | |||
vtkDataObject contains the methods SetFieldData and GetFieldData, which could be used to set or get the columns of the table. The columns may currently contain primitive data types and recently vtkStringArray has been added to VTK. | vtkDataObject contains the methods SetFieldData and GetFieldData, which could be used to set or get the columns of the table. The columns may currently contain primitive data types and recently vtkStringArray has been added to VTK. | ||
| Line 5: | Line 7: | ||
vtkTable should probably extend vtkDataObject, and then be converted to a subclass of vtkDataSet using a filter which determines coordinates for each row. | vtkTable should probably extend vtkDataObject, and then be converted to a subclass of vtkDataSet using a filter which determines coordinates for each row. | ||
[[User:Jeff|Jeff]] 10:03, 2 Jun 2006 (EDT) | --[[User:Jeff|Jeff]] 10:03, 2 Jun 2006 (EDT) | ||
Revision as of 10:06, 2 June 2006
vtkTable parent class
vtkDataObject contains the methods SetFieldData and GetFieldData, which could be used to set or get the columns of the table. The columns may currently contain primitive data types and recently vtkStringArray has been added to VTK.
We could also consider inheriting from vtkDataSet, which contains mechanisms for assigning coordinates to each row of the table. These could be initialized to zero and modified when the table is graphically presented. However, vtkDataSet also has the concept of cells, but tables do not have this concept since all rows are independent of each other.
vtkTable should probably extend vtkDataObject, and then be converted to a subclass of vtkDataSet using a filter which determines coordinates for each row.
--Jeff 10:03, 2 Jun 2006 (EDT)
