Easy File Reader Creation: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
(New page: Creating a file reader for ParaView is actually pretty hard. There is a lot of tribal knowledge about what the Request* methods do, how to handle information objects, what all the informa...) |
No edit summary |
||
| Line 2: | Line 2: | ||
It would be a much lower barrier to entry if we had a layer that simplified the implementation of readers, at least for the easy cases. One place to look first is [https://wci.llnl.gov/codes/visit/1.5.4/GettingDataIntoVisIt1.5.4.pdf VisIt's reader plugin interface]. | It would be a much lower barrier to entry if we had a layer that simplified the implementation of readers, at least for the easy cases. One place to look first is [https://wci.llnl.gov/codes/visit/1.5.4/GettingDataIntoVisIt1.5.4.pdf VisIt's reader plugin interface]. | ||
: If we can come up with a "VisIt Database" like API for writing readers, we may be able to provide an adaptor that maps from "ParaView Interface" to VisIt Database thus making it easier to bring in VisIt plugins in to ParaView. - [[User:Utkarsh|Utkarsh]] 09:35, 4 April 2009 (EDT) | |||
Revision as of 08:35, 4 April 2009
Creating a file reader for ParaView is actually pretty hard. There is a lot of tribal knowledge about what the Request* methods do, how to handle information objects, what all the information keys mean, and what to do with them.
It would be a much lower barrier to entry if we had a layer that simplified the implementation of readers, at least for the easy cases. One place to look first is VisIt's reader plugin interface.
- If we can come up with a "VisIt Database" like API for writing readers, we may be able to provide an adaptor that maps from "ParaView Interface" to VisIt Database thus making it easier to bring in VisIt plugins in to ParaView. - Utkarsh 09:35, 4 April 2009 (EDT)
