Features needed for a ParaView replacement

From ParaQ Wiki
Jump to navigationJump to search

Here is a what I have so far. These do not include new features from Features for v1.0.

  • Comprehensive help: online (context sensitive) and printed
  • Animation
    • Simple animation interface
      • Load and hit play
    • Complex animation interface
      • Keyframe editor
    • Generation of animations
    • Geometry caching
    • Saving geometry
    • Targeted Mode Shape Animation Interface
  • Saving and loading state
  • Saving batch: To be loaded from the python client.
  • Ability to import modules (your own VTK filters): Should be both compile and run-time.
  • Pipeline/object browsers
    • Several types
      • Flat list
      • Hierarchical
      • Pipeline view
    • Capabilities
      • There should be a quick way of hiding/showing, deleting, changing appearance of sources/objects. It would be nice if the browsers did not limit themselves to just pipeline object but could include any proxy if desired.
      • One-click grouping. Operations on the group.
  • View manipulation
    • Quick: Setting the center of rotation, reset camera etc. from a toolbar
    • Comprehensive: See 3D View Properties - Camera. We might also want to incorporate some of the lookmarks functionality
  • Good annotation support
    • Text annotation.
    • Draggable annotation.
    • Scalar bar: needs property and lookup table editor and ability to load/save lookup tables
  • 3D view properties: See 3D View Properties -> General
  • Timer and Error logs.
    • We need a better graphical representation of these (future).
  • Progress: Must work in client/server mode as well. If we have time, we should also support aborting.
  • Object inspector
    • Custom pages for important sources/filters
    • Better automatic page generation for others
  • Data information
    • See the information tab on the properties frame. We also need more for quantitative analysis.
  • Display settings per source
    • The usual controls from Display tab on properties. Transfer function editor. Ability to load/save transfer functions.
  • Reader settings
    • We probably need a general wizard support for opening files. A lot of the readers in VTK/ParaView behave differently when it comes to setting parameters and getting information. We might want to unify this.
  • Good writer support.
    • Exodus
    • Ensight (version?)
    • VTK formats
  • Full pipeline construction support (you should be able to build the pipelines that you can today.)
  • A good demo
Retrieved from "http://www.paraview.org/ParaView/index.php?title=Features_needed_for_a_ParaView_replacement&oldid=4420"