| Name
|
Description
|
Owner
|
Status
|
| UI Improvements
|
| Better Labeling
|
- This has been on and off many lists, we really need better labeling support for data. The current mechanism of "selecting and labeling" is cumbersome to say the least.
|
|
deferred
|
| Packaging/Deployment
|
| ParaView using External-VTK
|
Add support to build ParaView using a pre-built VTK
|
Utkarsh/Marcus
|
active development
|
| Modularization
|
- Enable building tiny binaries for co-processing for ParaView by incorporating VTK modularization into ParaView.
|
Dave DeMarle
|
active development
|
| Multiblock Improvements
|
| Toggle visibility of individual blocks
|
- Provide VTK-level infrastructure to toggle visibility and other properties for individual blocks in a composite dataset.
- Develop user-interface to allow setting up of properties for individual blocks.
|
|
|
| Plotting Improvements
|
| Plotting composite datasets
|
- Currently only 1 block can be plotted at a time. We need to allow plotting multiple blocks in the same chart, whenever applicable.
|
|
|
| Statistics Enhancements
|
| Extensions to Find Data
|
- Enable locating elements using statistical queries.
|
Philippe
|
|
| Extensions to Calculator
|
- Enable adding advanced statistically computed arrays using Array Calculator
|
Philippe
|
|
| Plugins
|
| Python support
|
- We need better support for plugins in Python. They seem like second class citizens right now: no easy way for loading distributed plugins, PV_PLUGIN_PATH is not respected.
- Python trace must have some indication of what plugins were loaded.
|
|
Done (3.14)
|
| XML Plugins
|
- Another second class citizen in the plugin world, it cannot be auto-loaded, I wonder if it even gets saved in the list.
|
Utkarsh
|
fixed (3.14)
|
