| ▶QT Installer Although this is not required for simple plugins I highly recommend you use QT because it is much easier to design an appealing user interface using the editor rather than scripting them drily using XML files. Go ▷here and download and install the qt-win-opensource-4.6.3-vs2008.exe file. |
| ▶CMake You're going to need CMake in order to generate the VS project. I used Version 2.8.4 but anything later than that should be fine. Go ▷here and download the Win32 installer. |
| ▶ParaView Of course you're going to need the actual software. I used Version 3.8.0 so either get that version to play safe or use a newer one. In either case make sure the versions of your ParaView installer and the Development installation match. Click ▷here to download ParaView. |
| ▶ParaView Development In addition to ParaView you're going to need the ParaView ▷development binaries in order to compile your plugin. Remember this has to be the same version as your ParaView installation. Also your plugin will only work for this specific version of ParaView. |
CMake
Before you can generate your Visual Studio project you will have to prepare a bunch of files in order to tell the plugin how it's supposed to interact with ParaView. Put the files in the same folder. The most important one is CMakeLists.txt which can look like this.
cmake_minimum_required(VERSION 2.6)
PROJECT(MyTestFilter)
FIND_PACKAGE(ParaView REQUIRED)
INCLUDE(${PARAVIEW_USE_FILE})
ADD_PARAVIEW_PLUGIN(
MyTestFilterSMPlugin
"1.0"
SERVER_MANAGER_XML MyTestFilter.xml
SERVER_MANAGER_SOURCES vtkMyTestFilter.cxx
GUI_RESOURCE_FILES MyTestFilterGUI.xml
)
This tells CMake that we're about to create a plugin with the name MyTestFilterSMPlugin, Version 1.0, and using the respective Server Manager (Configuration), source (VTK code) and GUI files. The filenames are case sensitive here. Now lets take a look at the other 3 files.
Server Manager Configuration
<ServerManagerConfiguration>
<ProxyGroup name="filters">
<SourceProxy name="MyTestFilter"
class="vtkMyTestFilter">
<InputProperty
name="Input"
command="SetInputConnection">
<ProxyGroupDomain name="groups">
<Group name="sources"/>
<Group name="filters"/>
</ProxyGroupDomain>
<DataTypeDomain name="input_type">
<DataType value="vtkPolyData"/>
</DataTypeDomain>
</InputProperty>
</SourceProxy>
</ProxyGroup>
</ServerManagerConfiguration>
This example shows the server manager configuration for a filter plugin, that takes ▷vtkPolyData as input. Depending on the implementation of your plugin these attributes can change. For example you can specify multiple outputs or different input types like String, Vector or ComboBox even without using QT.
GUI Resource File
Finally you need to tell the plugin where it's supposed to be located once loaded into ParaView. Using the resource file you can specify the name and the category of the plugin. The following example will put the filter in the Extensions group, however it will be grayed out unless you select a valid ▷vtkPolyData object as input.
<ParaViewFilters>
<Category name="Extensions" menu_label="&Extensions">
<Filter name="MyTestFilter" />
</Category>
</ParaViewFilters>
So much for the setup files. Of course CMake is going to ask for a code file to generate the project from so let's take a quick look at that.
VTK Code
So this is where the real fun starts. Every ParaView plugin must be implemented as an extended ▷vtkAlgorithm since it must be usable within the VTK pipeline. The VTK class (and only this class!) should have the prefix vtk. I dont know whether this is mandatory but for some reason this convention avoids many nasty bugs.
This is the header file for a simple filter plugin that processes ▷vtkPolyData. Note that the input type must match the extended class. You might want to take a look at the VTK ▷documentation at this point.
#ifndef _vtkMyTestFilter_h
#define _vtkMyTestFilter_h
#include "vtkPolyDataAlgorithm.h"
class VTK_EXPORT vtkMyTestFilter :
public vtkPolyDataAlgorithm
{
public:
static vtkMyTestFilter *New();
vtkTypeRevisionMacro(vtkMyTestFilter,vtkPolyDataAlgorithm);
void PrintSelf(ostream& os, vtkIndent indent);
int RequestInformation([...]);
int RequestData([...]);
int FillInputPortInformation([...]);
int FillOutputPortInformation([...]);
protected:
vtkMyTestFilter();
~vtkMyTestFilter();
private:
vtkMyTestFilter(const vtkMyTestFilter&);
void operator = (const vtkMyTestFilter&);
};
#endif
Despite the confusing details the general setup is rather simple. The plugin sets the number of input and output ports and the respective data types. This is important because other plugins will only work (connect to the pipeline) if the data types match.
The next function is the core of the algorithm. This is where all the data processing is to be implemented. In case of our simple test plugin the most basic implementation would look something like this. The filter takes the input and passes it on to the output without doing anything.
int vtkMyTestFilter::RequestData([...])
{
vtkPolyData *input = vtkPolyData::GetData([...]);
vtkPolyData *output = vtkPolyData::GetData([...]);
output->CopyStructure(input);
return 1;
}
That's it. Put all the files in the same folder, fire up CMake, select the Paraview Development directory and QT and you're done. When you start the Visual Studio project, set it to "Release" mode and compile the DLL. In case of linker errors check the settings for the correct library paths (especially QT) and remove the Python stuff. That did the trick in my case.
