I'd suggesting starting simple and just adding to existing modules in ParaView. Once you are familiar with the CMake code, you can experiment with adding separate modules.
On Thu, Nov 9, 2017 at 1:55 PM, Kolja Petersen <petersenko...@gmail.com> wrote: > Thanks, I was missing those details about the modules system. I'll try > your suggestions. > Is the modules system documented somewhere? I don't remember reading > anything about it in the ParaView Guide. > Kolja > > On Thu, Nov 9, 2017 at 7:38 PM, Utkarsh Ayachit < > utkarsh.ayac...@kitware.com> wrote: > >> Where are you adding your classes? If you add them to one of the >> "modules" e.g. ParaViewCore/VTKExtensions/Default, you'd only need to >> add them to the CMakeLists.txt and they'd get wrapped. You'll then need to >> add a XML config for the proxy e.g in ParaViewCore/ServerManager/ >> SMApplication/Resources/filters.xml. That should be it. >> >> Another option is to add a new module. You can also add a new "module". >> See `ParaViewCore/VTKExtensions/Points/`. You can have the source >> directory external to your ParaView source, and in your build simply set >> `PARAVIEW_EXTERNAL_MODULE_ROOTS` CMake cache variable in your ParaView >> build to include the directory containing your new module's dir. You will >> need to manually enable the module in CMakeLists.txt as well as ParaView >> wont' enable it by default. >> >> Utkarsh >> >> On Thu, Nov 9, 2017 at 1:14 PM, Kolja Petersen <petersenko...@gmail.com> >> wrote: >> >>> Heya, >>> I'd like to add some custom classes to paraview that should also be >>> accessible through proxies on the client side. And a Python interface is >>> also needed. >>> >>> I found that the classes that should be wrapped need to be listed in a >>> few different CMakeLists.txt files in the paraview sources, and again in >>> the scripts that take care of generating the wrappers. But I must have >>> missed more, as I am getting more and more errors the more I try to fix. >>> >>> Which steps do I have to follow to implement a new class with wrapping? >>> Thank you >>> Kolja >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>> Virenfrei. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>> <#m_-6224627429951704770_m_4958346466197006339_m_-5312748509129356624_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
