# Implementing a Visit Reader in Paraview 5.8.0 ADD\_VISIT\_PLUGIN\_READER
**URL:** https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726
**Category:** ParaView Support
**Created:** [March 3, 2020, 11:10am UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726 "2020-03-03T11:10:49Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@nitawa](https://discourse.paraview.org/u/nitawa)
#### Post date: [March 3, 2020, 11:10am UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/1 "2020-03-03T11:10:49Z")
Dear experts,
I recently moved to Paraview 5.8 and need to upgrade a Visit Reader plugin
With Paraview 5.6.0, following the online documentation:
[https://www.paraview.org/Wiki/VisIt\_Database\_Bridge#Custom\_Plugin\_of\_VisIt\_Reader](https://www.paraview.org/Wiki/VisIt_Database_Bridge#Custom_Plugin_of_VisIt_Reader)
the implementation of the plugin was straightforward since I could use the function:
ADD\_VISIT\_PLUGIN\_READER.
I can see that since Paraview 5.7.0, this function was simply removed.
Before starting to see how I can translate this function in the new Paraview CMake mechanism, I am wondering whether this feature is still supported and if this is the case, could you point me to some working example since the baseline example Examples/Plugins/VisItReader which is shipped with Paraview sources does not compile anymore.
In advance, many thanks for your valuable help.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 4, 2020, 2:45am UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/2 "2020-03-04T02:45:55Z")
@ben.boeckel
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 4, 2020, 2:02pm UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/3 "2020-03-04T14:02:03Z")
> [@nitawa](#):
>
> ADD\_VISIT\_PLUGIN\_READER
We have this issue to track it: [https://gitlab.kitware.com/paraview/paraview/issues/13577](https://gitlab.kitware.com/paraview/paraview/issues/13577)
---
### Author:  [@nitawa](https://discourse.paraview.org/u/nitawa)
#### Post date: [March 4, 2020, 2:25pm UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/4 "2020-03-04T14:25:50Z")
thanks for opening this issue. Nevertheless, can you confirm, that porting the Paraview 5.6 ADD\_VISIT\_PLUGIN\_READER function to the new Paraview 5.8 cmake machinery is the way to go, or does one have to take into account some additional points?
Thanks.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 4, 2020, 4:37pm UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/5 "2020-03-04T16:37:03Z")
I imagine the API won’t be exactly the same. New CMake APIs have gained much better argument parsing and other things. I’ll likely rename it so that it’s not confused with the old instance of the API.
---
### Author:  [@nitawa](https://discourse.paraview.org/u/nitawa)
#### Post date: [April 18, 2020, 6:29pm UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/6 "2020-04-18T18:29:49Z")
Dear all,
Thanks to the help of A.Gerschenfeld, we finally managed to fix the issues that we reported here about VisitBridge/Visit which was broken, since Paraview 5.7. and which did not enable us to use one widely used data format: Lata.
We would like to ask for integration of this data format to the list of supported data format by Paraview.
Thus we provide the sources for this plugin, and would like to ask to add this plugin to the list of centrally maintained plugins.
As an attachment, we put the patch which enables to support this data format which is one of the data format supported and heavily used by SALOME, an opensource platform developed at CEA (see [https://www.salome-platform.org/](https://www.salome-platform.org/))
We will appreciate if this patch could be integrated in Paraview, such that it becomes a standard Paraview supported data format.
What is the current process to ask for a plugin integration in Paraview?
Thanks for your reply.
[0001-LATA-reader.patch](https://discourse.paraview.org/uploads/short-url/tVeaohr5I4YpWHAx3ukFOXWrIFK.patch) (732.6 KB) [0002-vtkUnstructuredGridRelevantPointsFilter-fix-for-poly(1).patch](https://discourse.paraview.org/uploads/short-url/oC9qap2hnkB1uHgWbf3t9An9W7r.patch) (4.2 KB)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 20, 2020, 3:14am UTC](https://discourse.paraview.org/t/implementing-a-visit-reader-in-paraview-5-8-0-add-visit-plugin-reader/3726/7 "2020-04-20T03:14:18Z")
In order to get your plugin integrated into ParaView, you first need to create a Merge Request on ParaView gitlab.
[https://gitlab.kitware.com/paraview/paraview/-/merge\_requests](https://gitlab.kitware.com/paraview/paraview/-/merge_requests)
See here for the process :
[https://gitlab.kitware.com/paraview/paraview/-/blob/master/CONTRIBUTING.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/CONTRIBUTING.md)
We will then evaluate the code and (especially with reader plugins) the dependence of the code.
However, depending of the code quality, our review process can be a bit overwhelming.
Do not hesitate to take contact with our sales team if you are interested with our help with the process.