Here are a few of the issues that I have had with migrating a few plugins from
ParaView 3.10 to 3.12:
I now use EXTRA_EXTERNAL_PLUGIN_DIRS instead of EXTERNAL_MODULES.
Where I used to have code in my cmake files such as:
# -- Add the Server Manager XML
PARAVIEW_INCLUDE_SERVERMANAGER_RESOURCES(
Awesome, thanks for documenting it!
On 10/18/2011 10:28 AM, Michael Jackson wrote:
Here are a few of the issues that I have had with migrating a few plugins from
ParaView 3.10 to 3.12:
I now use EXTRA_EXTERNAL_PLUGIN_DIRS instead of EXTERNAL_MODULES.
Where I used to have code in my cmake
Ah yes, now I remember. I think we meant to deprecate the support for
compiling in external modules in favor of the ability to add
plugins. I've updated
http://www.paraview.org/Wiki/Extending_ParaView_at_Compile_Time to
indicate the same.
In short, extending ParaView at compile time one now has
Hi,
From a few of the recent posts it sounds like there are potentially
disruptive changes in 3.12 that could affect existing external plugins.
It would be very helpful if these changes were documented on the wiki as
a courtesy to plugin authors/maintainers. Any chance you have such a
wiki
Burlen,
What changes are you referring to?
The changes to ServerManager have been documented at:
http://paraview.org/ParaView3/images/2/24/ParaViewCollaborationChanges.pdf
Reader/filter plugins should be unaffected for the most part.
Utkarsh
On Mon, Oct 17, 2011 at 12:46 PM, Burlen Loring
Hi Utkarsh,
Perhaps I was reading too much into recent posts by Michael Jackson
mike.jack...@bluequartz.net about 3.12 changes that affected his
plugins. I'm a bit defensive on this issue as over the past couple of
years I can think of 3 changes that bit me. all showed up at run time
and
