ParaView 3.0 Deliverables: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
|- | |- | ||
| Data analysis | | Data analysis | ||
| Better plotting. Better picking. | | Better plotting. Better picking. Wait, what part isn't covered by the plotting and picking deliverables? | ||
| 5 | | 5 | ||
|- | |- | ||
| Line 35: | Line 35: | ||
| Reimplement the ParaView 2 transfer function editors. | | Reimplement the ParaView 2 transfer function editors. | ||
| 4 | | 4 | ||
|- | |||
| Icons | |||
| 'Knuff said. | |||
| 4 | |||
|- | |||
| Custom filters/lookmarks | |||
| Lots of old features, lots of new features. | |||
| 4 | |||
|- | |||
| Linking | |||
| Add GUI to link server manager proxy objects (such as camera view and pipeline object parameters). | |||
| 4 | |||
|- | |||
| Plotting | |||
| Wait, how does this differ from data analysis? | |||
| 4 | |||
|- | |||
| Testing | |||
| Testing, testing, and more testing. | |||
| 4 | |||
|- | |||
| Support for multiple outputs | |||
| Multiple outputs are useful for lookmarks/custom filters. It would also be nice to have node sets and side sets be handled as multiple outputs on the Exodus filter. | |||
| 3 | |||
|} | |} | ||
Revision as of 21:37, 29 November 2006
| Deliverable | Description | Priority |
|---|---|---|
| Dynamic default parameters | ParaView 2 has lots of custom GUI code for filter parameters. ParaView 3 relies much more on server manager XML code and autogenerated panels. Missing from the new panels is the ability to vary parameters based on the size of the input geometry. This is very important in some filters such as the streamlines filter. | 5 |
| Annotation | Much of the annotation abilities in ParaView 2 are missing in ParaView 3 (corner annotation, turninging off axis annotation, annotation with time value) and some new features (labels on specific cells). | 5 |
| New time support | Ken Martin has recently updated the time support in VTK. We need to take advantage of that in ParaView 3. For example, we move the time setting parameters from reader parameters to pipeline keys. | 5 |
| Pipeline browser improvements | Already our pipeline browser is much better than its predecessor. However, there still some improvements to go. Of special importance are feature gaps like handling multiple inputs. | 5 |
| Animation | We need to reimplement all of the Animation GUI features of ParaView 2. | 5 |
| Readers/filters | The backbone of ParaView needs to be tight. | 5 |
| Data analysis | Better plotting. Better picking. Wait, what part isn't covered by the plotting and picking deliverables? | 5 |
| Volume rendering GUI | Reimplement the ParaView 2 transfer function editors. | 4 |
| Icons | 'Knuff said. | 4 |
| Custom filters/lookmarks | Lots of old features, lots of new features. | 4 |
| Linking | Add GUI to link server manager proxy objects (such as camera view and pipeline object parameters). | 4 |
| Plotting | Wait, how does this differ from data analysis? | 4 |
| Testing | Testing, testing, and more testing. | 4 |
| Support for multiple outputs | Multiple outputs are useful for lookmarks/custom filters. It would also be nice to have node sets and side sets be handled as multiple outputs on the Exodus filter. | 3 |
