|
|
(2 intermediate revisions by the same user not shown) |
Line 6: |
Line 6: |
| |- | | |- |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''UI Improvements''' | | | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''UI Improvements''' |
| |-
| |
| | Better Copy/Paste Support for texts
| |
| |
| |
| * User should be able to copy-paste from different panels such as information tab.
| |
| * Copy should work spreadhsheet view as well.
| |
| |
| |
| | Done
| |
| |-
| |
| | Revised Properties Panel
| |
| |
| |
| * The Properties and Display panel will be combined into a single panel with a mode to show/hide advanced properties.
| |
| * The panel will provide searching/filtering capabilities
| |
| * Users will be able to pick what widgets are show in the non-advanced mode.
| |
| * The framework will be 100% backwards compatible so that old custom panels still "work" although developers would have to reimplement their panels to take advantage of the new functionality such as search,advanced properties, etc.
| |
| | Kyle
| |
| | active development
| |
| |-
| |
| | Better Drag/Drop support
| |
| |
| |
| * User should be able to drag sources/filters from the pipeline browser into a view to show it in that view. Avoids the whole "active view" confusion.
| |
| |
| |
| | deferred
| |
| |-
| |
| | Filter Controls Toolbar
| |
| |
| |
| * A special toolbar at the top of the viewport that shows "select" properties from the active source/filter [[ParaView_Usability_Improvements#Filter_Controls_Toolbar|(see here)]].
| |
| * The properties that end up in the toolbar should be specifiable using hints in configuration XMLs, for example.
| |
| |
| |
| | deferred
| |
| |- | | |- |
| | Better Labeling | | | 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. | | * 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
| |
| |-
| |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''I/O Improvements'''
| |
| |-
| |
| | Update VisIt bridge
| |
| | Update VisIt bridge to latest version to bring in fixes for readers.
| |
| |
| |
| |
| |
| |-
| |
| | Update to CGNS (3.1.3)
| |
| | Update to using latest CGNS version (latest version of CGNS using CMake making build/deployment easier)
| |
| | | | | |
| | | | | |
Line 56: |
Line 15: |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Packaging/Deployment''' | | | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Packaging/Deployment''' |
| |- | | |- |
| | Enhanced Packaging | | | ParaView using External-VTK |
| |
| | | Add support to build ParaView using a pre-built VTK |
| * Create/update ParaView super-build that builds all dependencies
| | | Utkarsh/Marcus |
| * There should be options to use system MPI, Python, HDF5, and Qt (at the very least)
| |
| * ParaView install rules should *NEVER* install external dependencies. People will be encouraged to use super-build to build packages will dependencies included.
| |
| | Utkarsh/Dave DeMarle | |
| | active development | | | active development |
| |-
| |
| | Modularization
| |
| |
| |
| * Enable building tiny binaries for co-processing for ParaView by incorporating VTK modularization into ParaView.
| |
| | Dave DeMarle
| |
| | active development
| |
| |- | | |- |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Multiblock Improvements''' | | | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Multiblock Improvements''' |
Line 79: |
Line 29: |
| | | | | |
| |- | | |- |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Plotting Improvements''' | | | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Query Enhancements''' |
| |-
| |
| | 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.
| |
| |
| |
| |
| |
| |-
| |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''Statistics Enhancements'''
| |
| |- | | |- |
| | Extensions to Find Data | | | Extensions to Find Data |
| | | | | Add suport for min/max/mean esp. in parallel |
| * Enable locating elements using statistical queries.
| |
| | Philippe
| |
| |
| |
| |-
| |
| | Extensions to Calculator
| |
| |
| |
| * Enable adding advanced statistically computed arrays using Array Calculator
| |
| | Philippe
| |
| |
| |
| |-
| |
| | style="color:green; background-color:#ffffcc;" colspan=4 align="center"| '''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)
| |
| |- | | |- |
|
| |
| |} | | |} |