ParaView 3.2 Deliverables: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
Line 4: | Line 4: | ||
! Deliverable | ! Deliverable | ||
! Description | ! Description | ||
|- | |||
| Better testing | |||
| | |||
* Increase coverage | |||
* Test compositing | |||
* Memory checking | |||
|- | |||
| Compositing | |||
| Support for desktop delivery without MPI | |||
|- | |- | ||
| Display rearchitecture | | Display rearchitecture |
Revision as of 07:14, 13 April 2007
Descriptions
Deliverable | Description |
---|---|
Better testing |
|
Compositing | Support for desktop delivery without MPI |
Display rearchitecture | Make it easier to add new views. As the infovis comes online, we will be making many new views we need to integrate into ParaView and its vertical apps. |
Multi-block | Improve multi-block support:
|
Exodus reader |
|
Exodus writer | It should work. If the original data was from Exodus files, the Exodus-specific metadata should be maintained. |
Array calculator |
|
Animation |
|
Selection |
|
3D Widgets |
|
Annotation |
|
Spreadsheet view | Implement a model for a client side table that allows users to browse their data. It should only bring the portion of that data the user is viewing to the client (or a bigger cache that is still small) |
Line chart/Bar chart |
|
Support for multiple output (custom) filters | |
Miscellaneous |
|