![]() The Plugin Manager has two sections for loading local plugins and remote plugins (enabled only when connected to a server). Plugins can be loaded into ParaView using the Plugin Manager accessible from Tools | Manage Plugins/Extensions menu. ![]() ParaView will include relevant components from plugin on each of the processes. Simply load the plugin on the server as well as the client. Generally, users don't have to worry whether a plugin is a server-side or client-side plugin. Such plugins need to be loaded both on the server as well as the client. a plugin that adds a new filter and a property panel that goes with that filter. Oftentimes a plugin has both server-side as well as client-side components to it eg. These plugins need to be loaded on the client. property panels for new filters, toolbars, views etc. These are plugins that extend the ParaView GUI eg. Since in ParaView data is processed on the server-side, these plugins need to be loaded on the server. These are plugins that extend the algorithmic capabilities for ParaView eg. Plugins can be classified into two broad categories: For a plugin to be loadable in ParaView, it must be built with the same version of ParaView as it is expected to be deployed on. Plugins are distributed as shared libraries (*.so on Unix, *.dylib on Mac, *.dll on Windows etc).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |