Talk:ParaView/Plugin HowTo: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
(Save time for plugin developers)
 
(Added suggestion for improvement in this page)
 
Line 1: Line 1:
About: "To create a plugin, one must have their own build of ParaView3."
===About: "To create a plugin, one must have their own build of ParaView3."===
Building Paraview takes hours, more than 24 in my case. A packaged build of Paraview's resources needed for plugin development would be very welcomed by plugin developers. For example, there could be a git repository containing all headers, libs and everything else needed.
* Building Paraview takes hours, more than 24 in my case. A packaged build of Paraview's resources needed for plugin development would be very welcomed by plugin developers. For example, there could be a git repository containing all headers, libs and everything else needed.
 
===Adding GUI Parameters===
* There are parts where more documentation would be useful. For example when you say that in the XML one can write <tt>command="SetbStartByMatchingCentroids"</tt>. The question unresolved there is "what is that command?" because the reader cannot know if it needs to be the name of a function inside the class or if it can be something else.

Latest revision as of 00:12, 6 January 2015

About: "To create a plugin, one must have their own build of ParaView3."

  • Building Paraview takes hours, more than 24 in my case. A packaged build of Paraview's resources needed for plugin development would be very welcomed by plugin developers. For example, there could be a git repository containing all headers, libs and everything else needed.

Adding GUI Parameters

  • There are parts where more documentation would be useful. For example when you say that in the XML one can write command="SetbStartByMatchingCentroids". The question unresolved there is "what is that command?" because the reader cannot know if it needs to be the name of a function inside the class or if it can be something else.