Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,758
    • Issues 1,758
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #4062

Closed
Open
Opened Nov 21, 2006 by Kitware Robot@kwrobotOwner

Extension independent reader chooser

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


Right now, ParaView uses the file extension to determine what type of reader to use for a file. Unfortunatly, it is not always clear by the file extension what the format for the file is.

It would be much better to give readers the capability to determine for themselves whether they can read a file. For each reader, there could be a mechanism (which may be independent from the actual reader) that could introspect the file (read some header information) and determine if the file is definitely readable, possibly readable, or definitely not readable. If exactly one reader says it can definitely read the file, use that reader. Otherwise, present to the user the subset of readers that can definitely or possibly read the file.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#4062