[Paraview] 3.2 Plugin loading
Sean Ziegeler
seanzig at users.sourceforge.net
Thu Nov 8 17:41:00 EST 2007
Ahh, of course I missed it. Also, of course, I just finished getting
3.2.0 set up and deployed to all the users. :)
I'll wait for your 3.2.1 announcement, get the source, make the mods
there and send a patch. I'll deploy my modified version to the users
until 3.2.2 comes out.
Thanks again,
Sean
Berk Geveci wrote:
> Sounds good Sean. However, you missed the 3.2.1 release. I finished
> making the binaries yesterday :-) If it is small enough patch, we can
> put it in 3.2.2.
>
> -berk
>
> On 11/8/07, Sean Ziegeler <seanzig at users.sourceforge.net> wrote:
>> What do you all think of adding a minor convenience to the plugin
>> loading process? I know it isn't that hard, but many of my users don't
>> remember to use Plugin Manager or PV_PLUGIN_PATH, and don't want to
>> bother adding it to their dot-files. Thus I am forced to wrap all the
>> executables with scripts that set it.
>>
>> What about the following alternative:
>> Modify pqPluginManager::loadPlugins() to also load plugins from
>> CMAKE_INSTALL_PREFIX/plugins (where CMAKE_INSTALL_PREFIX gets set in
>> CMake).
>>
>> That way (assuming I do a make install) any plugins that I place in the
>> plugins directory get loaded.
>>
>> If you like it, what chance is there of getting it into the 3.2.1
>> release? I'm willing to try it myself and make a patch for you all at
>> Kitware.
>>
>> Thanks,
>> Sean
>>
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
More information about the ParaView
mailing list