Difference between revisions of "ParaView/Extending ParaView at Compile Time"

From KitwarePublic
Jump to: navigation, search
Line 1: Line 1:
 
[[Plugin_HowTo|Plugins]] can be used to extend ParaView functionality. However, that requires that ParaView is built with shared libraries. It is also possible to extend ParaView at compile time by compiling extra source into it. This documents describes how that can be done.  
 
[[Plugin_HowTo|Plugins]] can be used to extend ParaView functionality. However, that requires that ParaView is built with shared libraries. It is also possible to extend ParaView at compile time by compiling extra source into it. This documents describes how that can be done.  
  
 +
==Build code as part of ParaView==
  
 
Let's say we have a file format called '''MyFancy''' and we require a reader for it. The file format is something completely new, so we cannot reuse any other class. So we write our own VTK reader and now we want to use it in the ParaView. Let's say the header file for the reader looks like this:
 
Let's say we have a file format called '''MyFancy''' and we require a reader for it. The file format is something completely new, so we cannot reuse any other class. So we write our own VTK reader and now we want to use it in the ParaView. Let's say the header file for the reader looks like this:

Revision as of 17:02, 11 September 2008

Plugins can be used to extend ParaView functionality. However, that requires that ParaView is built with shared libraries. It is also possible to extend ParaView at compile time by compiling extra source into it. This documents describes how that can be done.

Build code as part of ParaView

Let's say we have a file format called MyFancy and we require a reader for it. The file format is something completely new, so we cannot reuse any other class. So we write our own VTK reader and now we want to use it in the ParaView. Let's say the header file for the reader looks like this:

#ifndef __vtkMyFancyReader_h
#define __vtkMyFancyReader_h
 
#include "vtkUnstructuredGridAlgorithm.h"
 
...
 
class VTK_EXPORT vtkMyFancyReader : public vtkUnstructuredGridAlgorithm 
{
public:
  static vtkMyFancyReader *New();
  vtkTypeMacro(vtkMyFancyReader,vtkUnstructuredGridAlgorithm);
  void PrintSelf(ostream& os, vtkIndent indent);
 
  // Description:
  // Specify file name of the MyFancy file.
  vtkSetStringMacro(FileName);
  vtkGetStringMacro(FileName);
 
  ...
 
protected:
  vtkMyFancyReader();
  ~vtkMyFancyReader();
 
  ...
 
private:
  vtkMyFancyReader(const vtkMyFancyReader&); // Not implemented
  void operator=(const vtkMyFancyReader&); // Not implemented
};
 
#endif

First, we need to write the server manager configuration XML describing the interface.

  <ServerManagerConfiguration>
    <ProxyGroup name="sources">
      <SourceProxy name="MyFancyReader" 
                   class="vtkMyFanceReader">
        <StringVectorProperty name="FileName"
                              command="SetFileName"
                              number_of_elements="1">
           <FileListDomain name="files"/>
          <Documentation>
            This property specifies the file name for the PNG reader.
          </Documentation>
        </StringVectorProperty>
      </SourceProxy>
  </ProxyGroup>
</ServerManagerConfiguration>

Readers, Writers, and Filters also require additional GUI side XML to describe file extensions associated with those file types.

<ParaViewReaders>
  <Reader name="MyFancyReader"
          extensions="myfan"
          file_description="My Fancy Files">
  </Reader>
</ParaViewReaders>
<ParaViewFilters>
  <Filter name="MyFancyFilter" />
</ParaViewFilters>