![]() ![]() The XML plugin configuration file format looks like this: ParaView will read these files on startup to load specified plugins. PV_PLUGIN_CONFIG_FILE can be used to list a set of XML plugin configuration files (separated by colon ( :) on Unix platforms or semi-colon ( ) on Windows). Finer control can be used using the PV_PLUGIN_CONFIG_FILE environment variable. ![]() Paths in this list may also be of the structure created by the ParaView plugin macros (e.g., MyPlugin/MyPlugin.so). Note that plugins in PV_PLUGIN_PATH are always auto-loaded irrespective of the status of the Auto Load checkbox in the Plugin Manager. This environment variable needs to be set on both the client and server sides to load their respective plugins. PV_PLUGIN_PATH may be used to list a set of directories (separated by colon ( :) for Unix platforms or semi-colon ( ) on Windows) which ParaView will search on startup to load plugins. In order to have ParaView automatically load a set of plugins on startup, one can use the PV_PLUGIN_PATH environment variable.Using environment variable (Auto-loading plugins).You can set up ParaView to automatically load the plugin at startup (for client plugins) or on connecting to the server (for server plugins) by checking the "Auto Load" checkbox on a loaded plugin.The Plugin Manager remembers all loaded plugins across ParaView instances, so once a plugin is loaded once, it will appear in the future (unloaded).The Plugin Manager also lists the paths it searched to load plugins automatically. If the plugin is loaded successfully, it will appear in the list of loaded plugins. To load a plugin on the client and server side, simply browse to the plugin shared library. The Plugin Manager has two sections for loading client plugins and server plugins (shown only when connected to a server). Plugins can be loaded into ParaView using the Plugin Manager accessible from the 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. For example, 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. These plugins need to be loaded on the client. Client-side plugins: These are plugins that extend the ParaView GUI including property panels for new filters, toolbars or views.Since ParaView processes data on the server-side, these plugins need to be loaded on the server. For example, new filters, readers or writers. Server-side plugins: These are plugins that extend the algorithmic capabilities for ParaView.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 and macOS, and *.dll on Windows). Second section contains information for developers about writing new plugins for ParaView.First section covers how to use existing plugins in ParaView.Add custom GUI components such as toolbar buttons to perform common tasksĮxamples for different types of plugins are provided with the ParaView source under Examples/Plugins/.Plugins can be used to extend ParaView in several ways: ParaView makes it possible to add new functionality by using an extensive plugin mechanism. However, it is not uncommon for developers to want to add new functionality to ParaView to, for example, add support to their new file format or incorporate a new filter into ParaView. ParaView comes with plethora of functionality bundled in: several readers, multitude of filters, different types of views, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |